Search · Index

Weblog

Showing 1 - 10 of 848 Postings (summary)

Chat Includelet

Created by Gustaf Neumann, last modified by Gustaf Neumann 29 Nov 2016, at 08:20 AM

Package specification Summary for package chat-includelet

Summary:
Description:
Maturity: New Submission or Maturity Unknown
This package depends on: layout-manager chat
Packages that depend on chat-includelet: None

Bug Tracker Summary for package chat-includelet

There is no package with the name "chat-includelet" known to bug-tracker.


Code Metrics Summary for package chat-includelet

# Tcl Procs 2
# Tcl Lines 43
# Automated Tests 0
# Stored Procedures PG: 0 ORA: 0
# SQL Lines PG: 0 ORA: 0
# ADP pages 0
# ADP lines 0
# Include pages (chat-includelet/lib/) 2
# Documentation pages 0
# Documentation lines 0
Source Not installed

 

 

Installing OpenACS on Mac OS X

Created by OpenACS community, last modified by Gustaf Neumann 28 Nov 2016, at 03:18 AM

See one of these:

Should you decide to Install OpenACS from source using general en:openacs-system-install instructions, refer to these notes for changes:

Installing PostgreSql

OS X conventions

On Mac OS X type sudo su - to become root.

Use curl -L -O instead of wget

If you are running Mac OS X prior to 10.3, you should be able to install and use PostGreSQL 7.3.x. Mac OS X 10.3 requires PostGreSQL 7.4. Note: if you're installing PG on an Intel Mac, you'll need to install 8.x; 7.4.x won't compile because of a lack of "native spinlock support" -- and this is something that the PG maintainers aren't inclined to fix. See this. PG 8.0.x installs fine, as does PG 8.1 or 8.2.

Creating postgres user

Do this instead:

First make sure the gids and uids below are available (change them if they are not). To list taken uids and gids:

nireport / /groups name gid | grep "[0-9][0-9][0-9]"
nireport / /users name uid | grep "[0-9][0-9][0-9]"

Now you can install the users

sudo niutil -create / /groups/web
sudo niutil -createprop / /groups/web gid 201
sudo niutil -create / /users/postgres
sudo niutil -createprop / /users/postgres gid 201
sudo niutil -createprop / /users/postgres uid 502
sudo niutil -createprop / /users/postgres home /usr/local/pgsql
sudo niutil -create / /users/$OPENACS_SERVICE_NAME
sudo niutil -createprop / /users/$OPENACS_SERVICE_NAME gid  201
sudo niutil -createprop / /users/$OPENACS_SERVICE_NAME uid 201
mkdir -p /usr/local/pgsql
chown -R postgres:web /usr/local/pgsql /usr/local/src/postgresql-7.4.7
chmod 750 /usr/local/pgsql

Compile and install PostgreSQL

If you're using Fink:

Append --with-includes=/sw/include/ --with-libraries=/sw/lib flags to ./configure.

./configure --with-includes=/sw/include/ --with-libraries=/sw/lib

Set PostgreSQL to start on boot

cd /Library/StartupItems/
tar xfz /var/lib/aolserver/$OPENACS_SERVICE_NAME/packages/acs-core-docs/www/files/osx-postgres-startup-item.tgz

Alternatively, one can use an XML file like the following to start postgres via launchd (specifying the postgres binary directory and database directory)

For Mac OS X Tiger (10.4.*), use:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>GroupName</key>
	<string>nsadmin</string>
	<key>Label</key>
	<string>org.postgresql.PostgreSQL</string>
	<key>OnDemand</key>
	<false/>
	<key>ProgramArguments</key>
	<array>
		<string>/usr/local/pg820/bin/pg_ctl</string>
		<string>-D</string>
		<string>/usr/local/pg820/data</string>
		<string>-l</string>
		<string>/usr/local/pg820/data/server.log</string>
		<string>start</string>
	</array>
	<key>ServiceDescription</key>
	<string>PostgreSQL Server</string>
	<key>UserName</key>
	<string>postgres</string>
</dict>
</plist>

For Mac OS X Leopard (10.5.*), use:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>Label</key>
	<string>org.postgresql.PostgreSQL</string>
	<key>UserName</key>
	<string>postgres</string>
	<key>GroupName</key>
	<string>nsadmin</string>
	<key>OnDemand</key>
	<false/>
	<key>ProgramArguments</key>
	<array>
		<string>/usr/local/pg820/bin/postmaster</string>
		<string>-D</string>
		<string>/usr/local/pg820/data</string>
		<string>-c</string>
		<string>log_connections=YES</string>
	</array>
</dict>
</plist>

Save the above files as /Library/LaunchDaemons/org.postgresql.PostgreSQL.plist and postgres will be started automatically on the next boot of the system. One can use launchctl to start the service for testing;

 

launchctl % load /Library/LaunchDaemons/org.postgresql.PostgreSQL.plist % start org.postgresql.PostgreSQL % ^D

To get Tcl to build on Leopard or newer

for compiling under Mac OS X Leopard or newer, use the following flags to compile Tcl:

./configure --prefix=/opt/aolserver --enable-threads --disable-corefoundation --enable-symbols

 

To get tDOM to build on tiger

  1. Download and install/update to the latest version of xcode tools (version2.2) from http://developer.apple.com/tools/xcode which updates the gcc compiler.
     
  2. Then make some additional changes to the unix/CONFIG file (after modifying the unix/CONFIG file according to instructions at en:aolserver-install, uncomment:
    'CC=gcc; export CC'
  3. add a new line, somewhere after the first line:
    export CPP="/usr/bin/cpp"

When versions of aolservers different to aolserver 4.5 (head, including changes from Mar 22, 2008) are used, aolserver is likely to segfault on startup due to recent changes in the Mac OS X System libraries. To avoid this, use

ulimit -n 256

in the startup script (don't use unlimited).

Marketing Materials Home

Created by Ryan Gallimore, last modified by Michael Aram 25 Nov 2016, at 01:30 PM

Please find here marketing materials to help you sell OpenACS.

Documentation for everyone ( docs-end-user ) includes a marketing slant. These docs follow Marketing documentation requirements

End-users - Requirements

Created by Torben Brosten, last modified by Michael Aram 25 Nov 2016, at 12:08 PM

Documentation Requirements for End-users

By the OpenACS Community. This section is a collection of documentation requirements that have been expressed in the OpenACS forums to 4th July 2003.

OpenACS end-user documentation should meet the following requirements. No significance has been given to the order presented, topic breadth or depth here.

  • End-users should not have to read docs to use the system.

  • Include how to get help. How and where to find answers, contact others, what to do if one gets an AOLserver or other error when using the system. Include types of available support (open-source, private commercial etc.) including references.

  • Explain/foster understanding of the overall structure of the system. This would be an overview of the system components, how it works, and how to find out more or dig deeper... To promote the system by presenting the history of the system, and writing about some tacit knowledge re: OpenACS.org and the opensource culture.

  • Introduce and inspire readers about the uses, benefits, and the possibilities this system brings (think customer solution, customer cost, convenience, value). A comprehensive community communications system; How this system is valuable to users; Reasons others use OpenACS (with quotes in their own words) "...the most important thing that the ACS does is manage users, i.e. provide a way to group, view and manipulate members of the web community. -- Talli Somekh, September 19, 2001" using it to communicate, cooperate, collaborate... OpenACS offers directed content functionality with the OpenACS templating system. ... OpenACS is more than a data collection and presentation tool. OpenACS has management facilities that are absent in other portals. ...The beauty of OpenACS is the simplicity (and scalability) of the platform on which it is built and the library of tried and tested community building tools that are waiting to be added. It seems that most portals just add another layer of complexity to the cake. See Slides on OACS features...a set of slides on OACS features that can be used for beginners who want to know OACS is about and what they can do with it. Screen captures that highlight features. Example shows BBoard, calendar, news, file storage, wimpy point, ticket tracking. An OpenACS tour; an abbreviated, interactive set of demo pages.

  • From a marketing perspective,

    • differentiate "product" by highlighting features, performance quality, conformance to standards, durability (handling of technological obsolescence), reliability, repairability, style of use, design (strategy in design, specifications, integrated, well-matched systems etc).

    • differentiate "service" by highlighting software availability (licensing and completeness from mature to early adopters or development versions), community incident support, project collaborative opportunities, and contractor support availability

    • differentiate price (economic considerations of opensource and features)

    • Discussion and details should rely on meeting criteria of design, completeness of implementation, and related system strengths and weaknesses. Marketing should not rely on comparing to other technologies. Competitive analysis involves mapping out strengths, weaknesses, opportunities and threats when compared to other systems for a specific purpose, and thus is inappropriate (and becomes stale quickly) for general documentation.

    • When identifying subsystems, such as tcl, include links to their marketing material if available.

    • create an example/template comparison table that shows versions of OpenACS and other systems (commonly competing against OpenACS) versus a summary feature list and how well each meets the feature criteria. Each system should be marked with a date to indicate time information was gathered, since information is likely volatile.

     

  • To build awareness about OpenACS, consider product differentiation: form, features, performance quality, conformance quality (to standards and requirements), durability, reliability, repairability, style, design: the deliberate planning of these product attributes.

  • Include jargon definitions, glossary, FAQs, site map/index, including where to find Instructions for using the packages. FAQ should refer like answers to the same place for consistency, brevity and maintainability.

  • Explain/tutorial on how the UI works (links do more than go to places, they are active), Page flow, descriptions of form elements; browser/interface strengths and limitations (cookies, other)

  • Discuss criteria used to decide which features are important, and the quality of the implementation from a users perspective. Each project implementation places a different emphasis on the various criteria, which is why providing a framework to help decide is probably more useful than an actual comparison.

Package documentation requirements have additional requirements.

  • A list of all packages, their names, their purposes, what they can and cannot do (strengths, limitations), what differentiates them from similar packages, minimal description, current version, implementation status, author/maintainers, link(s) to more info. Current version available at the repository.

  • Include dependencies/requirements, known conflicts, and comments from the real world edited into a longer description to quickly learn if a package is appropriate for specific projects.

  • Create a long bulleted list of features. Feature list should go deeper than high-level feature lists and look at the quality of the implementations (from the user's perspective, not the programmer's). Example issues an end-user may have questions about: Ticket Tracker and Ticket Tracker Lite, why would I want one of them vs the other? And, before I specify to download and install it, what credit card gateways are supported by the current e-commerce module? There are some packages where the name is clear enough, but what are the limitations of the standard package?

  • End-user docs should not be duplicative. The package description information and almost everything about a package for administrators and developers is already described in the package itself through two basic development document templates: a Requirements Template and Detailed Design Document.

OpenACS Performance Tuning

Created by OpenACS community, last modified by Gustaf Neumann 23 Nov 2016, at 12:08 AM

OpenACS Performance Tuning

Here is some documentation on general OpenACS performance tuning:

Much performance tuning is targeted at the subsystems level, and so you will find some specific tuning information in these pages:

A broad scope of causes can be attributed to OpenACS performance issues. These forum threads help identify useful diagnostic techniques and accurate testing to help narrow the scope of problem areas etc.

dotLRN Roadmap

Created by Gustaf Neumann, last modified by Gustaf Neumann 15 Nov 2016, at 01:11 AM

Current Version: .LRN 2.9.0

  • .LRN 2.5.0:
    • Full accessibility
    • validated HTML for all packaged .LRN packages
  • .LRN 2.9.0:
    • Improved flexibility on package and installation management
    • Ability to install .LRN from existing OpenACS installations and via "install from repository"
    • thus no need to have only pre-packaged installations
    • Removed calls to deprecated code
  • .LRN 2.9.1:
    • Improved security: Content Security Policy (CSP) support
    • Improved theme-ability including theme switching (Bootstrap  theme in preparation)
    • Improved stability (various fixes in application packages)

Old Roadmap 

Windows-OpenACS

Created by Maurizio Martignano, last modified by Maurizio Martignano 12 Nov 2016, at 02:59 PM

Windows-OpenACS (vers. 3.1.13 - November 2016) is a  Windows 64 port of OpenACS 5.9.0 and the latest snapshot of NaviServer and is available here.

This port installs and runs on the following systems:

  • Windows 8.1,
  • Windows 10,
  • Windows Server 2012 R2, and
  • Windows Server 2016 TP.

 

OpenACS TODO List

Created by Dave Bauer, last modified by Gustaf Neumann 11 Nov 2016, at 01:13 AM

Release Status

See openacs-release-status

Development is taking place in the oacs-5.9 branch.

OpenACS Version 5.9.1 agenda/wish list

  • Refactoring of rich-text editor integration
    • Driving force: Debian packaging
    • we have now the new packages
      • richtext-xinha
      • richtext-tinymce
      • richtext-ckeditor4
  • SQL:
    • Further cleanup of .xql files (like what as done for acs-subsite in 5.9.0)
      • so far, 36 files deleted
      • removed more than 100 obsolete named queries
      • stripped misleading SQL statements
    • Mark redundant / uncalled sql functions as deprecated
    • Remove type discrepancy introduced in 2002:
      • acs_object_types.object_type has type varchar(1000), while
      • acs_object_types.supertype has type varchar(100)
      • ... several more data types are involved, using acs_object_types.object_type as foreign key
    • Replace usages of obsolete view "all_object_party_privilege_map" by "acs_object_party_privilege_map"
    • Simplify core sql functions by using defaults
      • Number of functions reduced by a factor of 2 compared to OpenACS 5.9.0 (while providing compatibility for clients using old versions),
      • reduced code redundancy
      • Affected functions:
        • reduced content_item__new from 12 versions to 6,
        • reduce content_revision__new from 7 to 4
        • similar in image__new, image__new_revision, content_item__copy, content_item__get_title, content_item__move
    • PG 9.5 supports named parameter in the same syntax as in Oracle. Further reduction of variants will be possible, once OpenACS requires at least pg 9.5
    • Modernize SQL
      • use real Boolean types instead of character(1)
        (done for new-portal, forums, faq, attachments, categories, dotlrn, dotlrn-forums, evaluation)
      • use real enumeration types rather than check constraints (done for storage type text/file/lob)
         
  • CR hygienics (reduce cr bloat)
    • Provide means to avoid insert/update/delete operations in the search queue: OpenACS adds for every new revision often multiple entries to the search_queue, without providing any means to prevent this. This requires for busy sites very short intervals between queue sweeps (otherwise too many entries pile up). Another consequence is that this behavior keeps the PostgreSQL auto-vacuum daemons permanently active. Many of these operations are useless in cases where the content repository is used for content that should not be provided via search. The changed behavior should honors a publish-date set to the future, since it will not add any content with future publish dates to the search-queue.
    • Insert into cr_child_rels just when needed. cr_child_rels provide only little benefit (allow to use roles in a child-rel), but the common operation is a well available in cr_items via the parent_id. cr_child_rels do not help for recursive queries either. One option would be to add an additional argument for content_item__new to omit child-rel creation (default is old behavior) and adapt the other cases.
       
  • Security improvements:
    • improve protection against XSS and SQL-injection
    • add support against CSRF (cross site request forgery)
    • support for W3C "Upgrade-Insecure-Headers" (see https://www.w3.org/TR/upgrade-insecure-requests/)
    • support for W3C "Subresource Integrity" (SRI; see https://www.w3.org/TR/SRI/)
    • support for W3C "Content Security Policy" (CSP; see https://www.w3.org/TR/CSP/)
    • remove "javascript:*" links (all such urls are removed from the 90 packages in oacs-5-9, excluding js libraries (ajaxhelper) and richtext code)
    • remove "onclick", "onfocus", "onblur", "onchange" handlers from all .adp and .tcl files in the 90 packages in oacs-5-9 (excluding js libraries (ajaxhelper) and richtext code)
    • added optional nonces to all <script> elements with literal JavaScript content
       
  • Finalize cleanup of permissions:
    • Get rid of acs_object_context_index (and therefore on acs_object_party_privilege_map as well) on PostgreSQL
      • huge table,
      • expensive maintenance, used only in a few places,
      • used as well by Oracle (effort has to be determined)
         
  • Data bloat hygiene:
    • rethink package parameter and portlet parameter data models
       
  • registry for .js and .css libaries: allow besides classical urls symbolic names for loading external resources (e.g. jquery), this would make it easier to upgrade  libraries in multiple packages (without running into problems with duplicate versions) or switching between CDN and local paths
  • say farewell to CVS

OpenACS Version 5.9.0 Agenda

  • Slimming pg SQL core:
     
    • Part 1: improve performance of object deletion
      • remove manual delete operations from acs_object__delete()
         
    • Part 2: content-repository - manual referential integrity management
      • handle referential integrity via pg's integrity constraints rather by functions cr_revision_del_ri_tr, cr_revision_ins_ri_tr, cr_revision_up_ri_tr, cr_revision_del_rev_ri_tr, and cr_revision_del_rev_ri_tr
      • fix broken/missing upgrade scripts from earlier updates
         
    • Part 3: content-repository - manual deletions and nulling
      • Removed manual nulling of live_revision and latest_revision
      • Removed manual deletion of old_revision and new_revision in cr_item_publish_audit
      • Removed manual deletion of item_id in cr_item_publish_audit, cr_release_periods, cr_item_template_map, and cr_item_keyword_map
      • Removed manual deletion of direct permissions
      • Added missing index for child_id to cr_child_rels.
         
    • Part 4: get rid of tree_sortkey in acs-objects
      • Check/fix dependencies in oacs-5-8 packages
      • Get rid of broken/uncalled functions using the column
      • Check/fix dependencies in other packages
      • Remove tree_sortkey and max_child_sortkey
  • Web interface:
    • Improve client performance
      • moving core.js from head to body
      • provide kernel parameter to control expiration date for /resources/
    • Protect against more XSS attacks
    • Improved HTML validity (see oacs-5-9-html-validity for the checklist)
    • Add lightweight support for ckeditor4 for templating::richtext widget (configurable via package parameter "RichTextEditor" of acs-templating. ckeditor4 supports mobile devices (such as iPad, ...).
    • New kernel parameter ResourcesExpireInterval to control expiration dates of resources
       
  • Templating:
    • Improve theme-ability
      • Move more information into theme packages in order to create responsive designs
      • Reduce hard-coding of paths, HTML etc.
    • Dimensional slider reform (ad_dimensional):
      • Remove hard-coded table layout from dimensional slider
      • Add backwards compatible templates
      • Move hard-coded styles into theme styling
      • Remove obsolete comments from ad_dimensional
    • Complete template variable controls (adding noi18n, addressing bug #2692):
      • @foo@: perform html quoting and internationalization
      • @foo;noquote@: perform internationalization
      • @foo;noi18n@: perform html quoting
      • @foo;literal@: perform neither html quoting nor internationalization
    • Improved Russian nationalization
    • Support of expiration dates and passwords for signed variables
       
  • Documentation:
    • Use ACS templating for the (static) OpenACS documentation to provide a more consistent layout and user experience.
    • Make pretty-naming of acs-core packages more consistent.
       
  • Misc improvements:
    • Mark unused functions of acs-tcl/tcl/table-display-procs.tcl as deprecated
    • Reduce number of muxtex locks by pre-request and per-thread caching
    • Improved development und debugging aids:
      • use "ad_log error|warning  .... " instead of "ns_log" to include information of request and callstack in error.log
      • ability to display ns_log entries caused by a request in ds-footer
      • ability to save delivered web pages in file-system for testing HTML validity (especially for admin pages, which are unaccessible for external validity testers)
    • More bug fixes
       
  • Version numbers:
    * require PG 9.0 (End Of Life of PostgreSQL 8.4 was July 2014)
    * require XOTcl 2.0 (presented at the Tcl conference in 2011).
     

OpenACS Version 5.8 Agenda

  • PostgreSQL 9.2+:
    • Get rid of nonstandard backslash escapes in function definitions
    • Change quote syntax in sql files (single quotes around the functions) to recommended PostgreSQL quoting using (recommended since pg8.0, jan 2005). li>Drop aliases in favor of named function arguments (recommended since pg8.0)
    • Fix wrong function_args, add missing function_args, align default semantics with the defaults in pg (providing "null" as default means the argument is optional)
    • Make OpenACS loadable without any tweaks in the pg config files
  • Use recursive queries for e.g. permission lookup to avoid performance problems in pg 8.4 and newer)
  • ADP: Use byte-compiled function wherever possible in compiled adp-code, support "@var;literal@" when neither quotes nor localization is needed in compiled adp-code
  • Improve support of NaviServer
  • Switch to Tcl 8.5 (TIP #143)
  • Improve scalability: Reduce mutex-stress on util-memoize cache and for cache maintenance in general
  • Code cleanup:
    • Get rid of calls to deprecated code (e.g. ad_tables, ad_parameter, ... in acs-core and main packages)
    • Improve awareness of usage of deprecated code (complain to error.log)
    • Use Tcl 8.5 idioms
    • cleanup of various http-client approaches and introduce a common implementation util::http::get and util::http::post; get rid of other usages, mark these as deprecated
    • page-contracts: Perform checking of all ids in acs-core and main packages to improve error messages and to improve security
  • OpenACS 5.8.1 should be released with main packages

OpenACS Version 5.7 Agenda

  • Support for object management in core 
  • Postgresql 9.0
  • TinyMCE update (fix for random JS injection issue, affecting Safari)
  • Fix for "remember me" issue
  • WCAG2-AA

OpenACS Version 5.6 Agenda

  • global parameters
  • package "embeds" 
  • fix search by package_id
  • core works on Postgresql 8.4

OpenACS Version 5.5 Agenda

  • DONE: Postgresql 8.3 support: especially regarding tsearch2
  • DONE: acs-authentication:
    • fix upgrade, add conditional logic into site wide tcl library so that you can login to perform the rest of the upgrade
  • DONE: tinymce:
    • upgrade to 3.1.1 + language packs
    • HTML Strict cleanup
    • create appropriate parameters for its config in acs-templating
  • acs-mail-lite:
    • DONE: cleanup duplicated procs (bounce)
    • review the parsing of bouncing messages (case user_id 0)
    • DONE: rollout support
  • Documentation improvements as discussed at the Guatemala conference:
    • Make current openacs.org/test-doc source for static files included in the release and provide ease means to achieve this for the release manager
      • DONE (CVS HEAD): Provide in XoWiki an alternative table of contents by nested UL/LI (without JavaScript) for static output
      • DONE (CVS HEAD): Provide in XoWiki a prototype page similar to "book" without edit-buttons etc., using the new table of contents
    • Update openacs.org/test-doc where necessary (incomplete list):
      • DONE: Fix the page ordering for the higher chapters (the original document  had no 3rd. level numbering)
      • update pages in /test-doc which are more recent in openacs/xowiki
      • bump version numbers of OpenACS, where appropriate (some places talk about openacs-5-0, others about openacs-5-1, oacs-5-2-3rc1 or 5-3) 
      • some version numbers of the required components are quite a mess. e.g. some parts say that Postgres 7.3 is required,  some examples talks about postgres 7.4.7 and 8.2.4 in the same listing.
      • also the dotlrn version numbers are old dotrln-2.0
      • Tcl version numbers should be 8.4.19
      • The install section for XOTcl is missing in II.3.4
      • remove ChangeLog from documentation
      • find some other prominent place for the ChangeLog
      • Fix indenting in examples  (e.g. in Rocael's robust web    development framework)
      • overthink Win2000 guidelines.  There are the native compiled packages from Maurizio, including everything from postgres, xotcl ....
    • It is desired to find a single person responsible for overworking the documentation, however, funding is unclear.

OpenACS Version 5.4 Agenda

  • DONE: HTML Strict (openacs core)
  • DONE: finish template::head (daveb)
  • DONE: test acs-mail-lite (complex send)
  • DONE: test notifications (complex send)
  • DONE: new XinHA release, get rid of RTE & HTMLarea, test on Safari
  • DONE: Form builder: add the ID attribute  to the form tag
  • DONE: acs-lang - keepLocalTranslationP to be removed
  • DONE search and intermedia-driver: move intermedia specific stuff to its package
  • DONE: acs-mail-lite - patch for mime::qp_encode bug

Future

  • Split Xinha and TinyMCE into seperate packages see: http://openacs.org/forums/message-view?message_id=2750958
  • Usability ("my account" page)
  • XHTML ?
  • Testing and documentation for recording automated tests using the firefox plugin and the upload feature for it new in automated testing. Probably needs some polishing and should be talked to with Quest who are getting into this.
  • Parameter Scope Patch http://openacs.org/bugtracker/openacs/patch?patch%5fnumber=845 
  • Remove obsolete master template stuff (default and site master template in openacs-4/www, acs-subsite's group-master, and related CSS and images).  Probably in the version which follows 5.5 (probably 5.6).  Also remove the compat master stuff at the same time.

Things to merge into this page

Old 5.0 Roadmap  discussion 

Roadmap discussion 1 

 [Ideas for Boston 2006 Future of OpenACS discussion]

My previous attempt at collaborative roadmap 

A .LRN Roadmap 

Another .LRN Roadmap discussion 

 

What's on this page?

This page should include work that is planned on and has someone comitted to working on it.

.LRN Governance

Created by Caroline Meeks, last modified by Gustaf Neumann 07 Nov 2016, at 07:52 PM

Definitions

 

.LRN Consortium  – A nonprofit corporation incorporated in Massachusetts

.LRN Organizational Member  – An organization that has paid its yearly membership fee of $250 (or more).

.LRN Voting Member  – The individual designated by a .LRN Organizational Member to vote on its behalf.

.LRN Board  – A member of the 7 person board of directors that is elected by the .LRN Voting Members.

.LRN Chairman  – The chairman is a member of the .LRN board elected to chair the board by the .LRN board.

.LRN Leadership Team  – A group of people decided on by the .LRN Board and Leadership Team. .LRN Leadership Team members do not have to be voting .LRN members. 

.LRN Decision  – A decision that has gone through the decision making process described below

 

*******DRAFT**********DRAFT**********DRAFT***********DRAFT********

Please note that the decision making process is being modified as of July 8, 2007  

The Decision Making Process

Goals

  • Make it easy for motivated people to make decisions and implement them with minimal overhead.
  • Give the elected .LRN Board oversight over .LRN decisions without requiring too much of the Board's time. 
  • Give the appointed (in the future - elected?) Leadership Team (authority || permission) to move forward on technical decisions if the Board can not give input.

 

Informal description of the process

 

If you have an idea you'd like to implement, discuss it with people who care, post in OpenACS and/or talk about it in a .LRN meeting as appropriate. After you have listened, post your suggestion to the .LRN Decision board. Then implement it.  Mostly we all want the same things and we need action.  The .LRN Board vote is available as an oversight and in those hopefully infrequent times when there is significant dissent.
 

Formal Process

  1. All members of the .LRN Board and Leadership Team subscribe to the .LRN Decision Forum.
  2. The Leadership Team is the governing body primarily responsible for technical decisions with respect to .LRN. The Leadership Team has been appointed carefully by the Board hence there is implied trust by the Board in the Leadership Team. (NOTE: I am not sure how this would change if the Leadership Team changes to be elected.) 
  3. There is no formal process for small technical decisions. The Leadership Team will keep discussions as open as possible via open meetings where anyone is free to attend. Ideally, most technical decisions will be made at the weekly Leadership Team Meetings (currently Tuesdays at 16GMT on #openacs at irc.freenode.net), but some informal discussions may take place via the Leadership Team mailing list (honchos at dotlrn.org) in order to be more efficient.
  4. Members of the .LRN Board and Leadership Team are jointly responsible for making large technical and non-technical decisions with respect to .LRN.
  5. There is a formal process for large technical and non-technical decisions. What constitutes a large technical decision is determined by the Board and the Leadership Team.  (NOTE1: Though most decisions for .LRN may be technical, I feel .LRN is much more than just a technical framework and will encounter non-technical issues/decisions; NOTE2: I consider a large technical decision to be something along the lines of: "Are we going to do the Zen Project?")
  6. For all large decisions and all non-technical decisions, a new thread is started in the .LRN Decision Forum.  The first posting will contain the issue up for decision and the possible solutions on which the Board and Leadership Team members can vote. Once the thread is posted, voters have  (48 hours || 72 hours || 7 days) to vote.  A simple majority (51%) based on the members attending the vote will decide the decision up for vote. The Board and the Leadership Team members receive 1 vote each. In case of a tie, the present Board Members + (1 || 2) member(s) of the Leadership Team (which members are to be decided by the Leadership Team) will have a revote. Again a simple majority, will decide the vote. (NOTE: I don't know wtf to do if there is a tie after the revote.) (DAVEB: What is the motivation to make the votes scheduled and held in IRC, as opposed to a longer voting period on the forums. I think it would be easier to get participation from more members of the board and leadership team with a voting period on the forums. Since these are "large" decisions a few days of voting should not cause a signifigant delay.)(AVNI: Dave - that makes sense. Changed 17 july 07. :-) )
  7. If a member of the Board or the Leadership Team disagrees strongly with a small or large technical or non-technical decision made, s/he may post his disagreement (the reason for the disagreement must be made clear in the forum posting) on the .LRN Decision Forum. If (2 || 3 || 4) other Board or Leadership Team members in distinct locations (distinct university, company, country, etc) agree with the dissenting member and post as such with their own reasons for dissenting in the same thread, the decision is overturned.  Other Leadership Team and Board Members along with community members may post on this thread also to inform the Team and the  Board about their views.

---- Have cut the six below out for now. Feel free to add back in: ----------------------------------------------

  1. Members of the .LRN Board and Leadership Team are jointly responsible for making decisions. All people are expected to discuss and reach an appropriate level of consensus on issues. 
  2. When an individual believes he has done an appropriate level of communication and consensus building on a decision he posts it to the .LRN Decision Forum 
  3. If no one objects or calls for a vote the decision is confirmed in 2 weeks.
  4. If people agree they need take no action; however if there is disagreement or concern, any member of the Board or Leadership Team may “Call for a Vote” on any decision posted to the decision forum within 2 weeks of the post.
  5. If a decision is called for a vote only the .LRN Board members vote. .LRN Leadership Team members are encouraged to post their views to help inform the board.
  6. A decision is upheld with 2 Yes and 0 No’s or a 2/3 majority of all members (usually 5 people).

---- End cut ----------------------------------------------------------------------------------------------------------------

*****END DRAFT********END DRAFT********END DRAFT*****

 

The .LRN Board

  • Board members typically serve 3 year terms. (See Start Up procedure for exceptions)
  • Board members must be .LRN Voting Members from a .LRN Organization
  • Elections are held once per year for all vacant posts.
  • Board terms are staggered so that each year at least 2 or 3 posts are up for election.
  • If a Board member resigns or is no longer a .LRN Voting member prior to the end of his 3-year term then that post is filled during the yearly vote.  All candiates are voted on together. The people with the highest number of votes are given the longest terms.

Start Up Procedure

For this year's elections all 7 positions will be available.  Because we are still in startup mode all terms will be for 1 year.  Next year all 7 seats will be up for election again, at that point we will transition to 3 year terms.  The 3 people who receive the top 3 votes will get 3 year terms, the next two, 2-year terms and the next two, one-year terms.This will set up up to have 1/3 of the positions available every year in the future.

The current board will immediately begin to designate the Leadership Team. We will not wait for the election.

The .LRN Decision forum will be put into place in the next 2 weeks after the server is moved.

The current Board will have oversight, but anything that has a “Call for Vote” will be delayed until the new board is in place. That is, noncontroversial decisions can be implemented immediately, but controversial decisions will be postponed until we have a duly elected Board to vote.

Discussion

 

This proposal was created by Carl Blesius, Rocael Hernandez, Carlos Kloos and Caroline Meeks over lunch at the Argentina E-Lane meeting. It was written up by Caroline Meeks.  Our goal was to create the simplest possible start up plan and leave complex or controversial decisions to an elected board.

This is not meant to be the final plan. Specifically we discussed but did not reach conclusions about how large organizations vs. small should be represented, individual vs. organizational power or how parties that contribute more money should be rewarded. We also discussed but did not decide on issues around official/certified vendors and vendors contributing back to .LRN. We will work on these issues with the newly elected board.

We ask that the community look over this proposal and see if you agree that it will work for startup purposes. We also ask that you think about what you would like to see as part of permanent governance and policy; however, the appropriate time to fully engage in decisions around long term issues is after we have an elected board.  At that point all parts of this initial governance plan can be modified via the decision policy laid out above.

I would especially ask those familiar with our nonprofit incorporation if there are any legal requirements we need to meet as part of governance.

Release Notes .LRN 2.4.1

Created by Alvaro Rodriguez, last modified by Gustaf Neumann 06 Nov 2016, at 10:03 AM

Release Notes .LRN 2.4.1

Note: This release notes were created based on the change log from tag dotlrn-2-4-0-final to dotlrn-2-4-1-final on the branch oacs-5-4. (view full change log)

ASSESSMENT

Add arrayname prefix where it was missing

Add missing array prefix in the multiple block

Add new proc to calculate user readable times.

Checkpoint 11.2 (level AA): Avoid deprecated features of W3C technologies .

Checkpoint 3.7 (level AA): Mark up quotations. Do not use quotation markup for formatting effects such as indentation.

Don't display the "view results" link if the assessment has not been taken yet.

Localize status of the assessment.

Fix for bug 3149: don't let users access an assessment that is not live!

Fix item edit url again. Since session-items can be included frm www or www/asm-admin we need to make sure we use the correct url all the time

Fix item-delete url.

Fix name of property (context instead of context_bar)

Fix score calculation. This checks the score for each question that was actually answered during a particular session and calculates the score based on that.

Fix swap URLs.

Fixed scores

Get_latest_session query is used by the script at www, not by the include in lib/. Moved to the right file.

HTML Strict cleanup: removed trailing slash of input, img, link and meta tags

HTML Strict cleanup: removed trailing slash of the BR tag

Key changing question rows on ad_item_id not TITLE! Itis easily conceivable that an assessment may have multiple questions with the same title which would completely break the formatting of multiple choice questions.

Max_time_to_complete does not belong to assessment_data

More fixed so that multiple choice questions work in title is repeated.

One more file keying on as_item_id instead of title.

The session include needs a value for session_id in order to display the result of that session, would throw an error otherwise.

Ticket#3143 Patch#869 from Ã…smund Realfsen to not link to results for anonymous answers.

Wrong edit this question url

ACS-DATETIME

Checkpoint 11.2 (level AA): Avoid deprecated features of W3C technologies .

HTML strict cleanup

ATTACHMENTS

Checkpoint 11.2 (level AA): Avoid deprecated features of W3C technologies .

Checkpoint 3.7 (level AA): Mark up quotations. Do not use quotation markup for formatting effects such as indentation.

Fix dependencies

BULK-MAIL

Checkpoint 3.7 (level AA): Mark up quotations. Do not use quotation markup for formatting effects such as indentation.

CALENDAR

- fixed octal number bug in view-week-display and view-one-day-display
- fixed bug for print-button in month display (items.weekday was not set)

Add missing translations

First shot at improving color difference in highcontrast CSS of calendar

HTML Strict cleanup: removed trailing slash of input, img, link and meta tags

Improve color differences to reach level AA

Last shot at improving difference in color

Refactored "list view" to use list builder

Removed print and calendar button as decided in .lrn meeting on sept 23, 2008 (see minutes at http://www.openacs.org/forums/message-view?message_id=2061351)

CATEGORIES

Checkpoint 3.7 (level AA): Mark up quotations. Do not use quotation markup for formatting effects such as indentation.

Remove useless limit clause in generic query.

DOTLRN

1. Set default applets to add to user, club, class and subgroup portals only for those that are installed by default during the standard installation.
2. Set toolbar off by default

Add missing translations

Add title and fix breadcrumbs

Added a label tag, and focus on first form element

Added missing message key

Added search users by first_name for ORACLE

Checkpoint 11.2 (level AA): Avoid deprecated features of W3C technologies .

Checkpoint 11.2 (level AA): Avoid deprecated features of W3C technologies. (<font> in this case)

Checkpoint 13.3 (level AA): Provide information about the general layout of a site (e.g., a site map or table of contents).

Checkpoint 3.5 (level AA): use header elements to convey document structure and use them according to specification. (main portlet headings were out of sequence, i.e. skiping directly from h1 to h3)

Checkpoint 3.7 (level AA): Mark up quotations. Do not use quotation markup for formatting effects such as indentation.

Created a new catalog key

Do not show checkbox nor other html stuff in csv list

Fix markup of the title of pseudo-portlet

Fix wrong use of export_vars to build an url.

HTML Strict cleanup.
Minor accessibility improvements.

HTML Strict cleanup: removed trailing slash of input, img, link and meta tags

HTML Strict cleanup: removed trailing slash of the BR tag

Nest form inside a td tag

Pass the doc array property up to the master

Removed 'update bio' action and references from user list

Show email without html in csv list

Show package_id in the toolbar

Sorting applets by name using i18n

Still trying to fix that bleeping versino number

Tabs 2 spaces

Tabs 2 spaces convertion and reindentation before some changes

Uid is an invalid variable name on Oracle (reserved word) changed to member_id

Using of export_vars to encode url right. fixed bad attributes quotation. Used new catalog keys

DOTLRN-BM

Checkpoint 3.7 (level AA): Mark up quotations. Do not use quotation markup for formatting effects such as indentation.

DOTLRN-FS

Checkpoint 3.7 (level AA): Mark up quotations. Do not use quotation markup for formatting effects such as indentation.

DOTLRN-PORTLET

<nobr> is not valid html strict

Checkpoint 11.2 (level AA): Avoid deprecated features of W3C technologies .

Checkpoint 3.7 (level AA): Mark up quotations. Do not use quotation markup for formatting effects such as indentation.

New indentation of actions, as commented on forums http://openacs.org/forums/message-view?message%5fid=1503658

EVALUATION

Checkpoint 3.7 (level AA): Mark up quotations. Do not use quotation markup for formatting effects such as indentation.

HTML Strict cleanup: removed trailing slash of input, img, link and meta tags

Remove extra CRs at end of line

EVALUATION-PORTLET

Checkpoint 11.2 (level AA): Avoid deprecated features of W3C technologies .

FAQ

Checkpoint 3.7 (level AA): Mark up quotations. Do not use quotation markup for formatting effects such as indentation.

Don't close the <master> tag, it would be output in the HTML and guess what! it's not valid HTML.

FILE-STORAGE

Checkpoint 3.7 (level AA): Mark up quotations. Do not use quotation markup for formatting effects such as indentation.

Removed the condition to build extra_vars so it won't be NULL, otherwise a null value was causing the query to retrieve URLs of items to fail.

FORUMS

HTML Strict cleanup: removed trailing slash of input, img, link and meta tags

HTML Strict cleanup: removed trailing slash of the BR tag

FORUMS-PORTLET

Checkpoint 3.6 (level AA): mark up lists and list items properly. (list template outputs a table not a list. It's not appropriate when the list has only 1 column)

GENERAL-COMMENTS

Checkpoint 3.7 (level AA): Mark up quotations. Do not use quotation markup for formatting effects such as indentation.

LARS-BLOGGER

Checkpoint 3.7 (level AA): Mark up quotations. Do not use quotation markup for formatting effects such as indentation.

HTML Strict cleanup: removed trailing slash of input, img, link and meta tags

HTML Strict cleanup: removed trailing slash of the BR tag

HTML strict cleanup

NEW-PORTAL

Checkpoint 11.2 (level AA): Avoid deprecated features of W3C technologies .

HTML Strict cleanup: removed trailing slash of the BR tag

NEWS

Add missing translations

Changed to use listtemplate

Changes to use ad_form and formtemplate for creating/editing a news item

Checkpoint 11.2 (level AA): Avoid deprecated features of W3C technologies .

Checkpoint 3.7 (level AA): Mark up quotations. Do not use quotation markup for formatting effects such as indentation.

HTML Strict cleanup and minor tweaks

HTML Strict cleanup: removed trailing slash of input, img, link and meta tags

HTML Strict cleanup: removed trailing slash of the BR tag

HTML Strict cleanup: removed trailing slash of the HR tag

Missing es_ES translation

Refactored to use ad_form and formtemplate. Queries and xql cleanup.

Refactored to use listtemplate

Refactoring:
- HTML STrict cleanup
- Extract SQL to xql files

NEWS-PORTLET

Checkpoint 3.7 (level AA): Mark up quotations. Do not use quotation markup for formatting effects such as indentation.

HTML Strict cleanup. Fix text to HTML transformation.

HTML Strict cleanup: removed trailing slash of input, img, link and meta tags

HTML Strict cleanup: removed trailing slash of the BR tag

Refactored to use list template in an accessible way.

OACS-DAV

HTML Strict cleanup: removed trailing slash of the HR tag

THEME-SELVA

HTML Strict cleanup: removed trailing slash of the BR tag

Remove "Templates.html" that is a duplicate of "templates.html" which is the one in use

THEME-ZEN

Add missing style for portlets title

Checkpoint 13.3 (level AA): Provide information about the general layout of a site (e.g., a site map or table of contents).

Don't print the "you are here" of the breadcrumbs when printing. Added "screen-reader-only" class to the list of styles not to print.

HTML Strict cleanup: removed trailing slash of the BR tag

Improve color difference to reach level AAA (contrast is not enough)

Improve difference in color to reach level AA for colors pattern.

Improving color difference in forms

Rephrase the level AA compliance

Update accessibility statement to the current status: level AA!!

This work was done for the .LRN Consortium

Next Page
Previous Month December 2016
Sun Mon Tue Wed Thu Fri Sat
27 28 29 30 1 2 3
4 5 6 7 8 9 10
11 12 13 14 15 16 17
18 19 20 21 22 23 24
25 26 27 28 29 30 31

Popular tags

17 , 5.9.0 , ad_form , ADP , ajax , aolserver , asynchronous , bgdelivery , bootstrap , bugtracker , CentOS , COMET , cvs , debian , emacs , fedora , FreeBSD , hstore , includelets , install , installation , installers , install-ns , javascript , libthread , linux , monitoring , munin , NaviServer , nginx
No registered users in community xowiki
in last 30 minutes
Contributors

OpenACS.org