Consortium activities organization (DRAFT)

Created by Rocael Hernández Rizzardini, last modified by Rocael Hernández Rizzardini 22 Sep 2009, at 05:40 PM

DOCUMENT STATUS: A draft that HAS NOT YET been endorsed by the OpenACS OCT, the .LRN Board, or the .LRN Leadership Team (Honchos)

These areas and list of activities has been summarized of a discussion over the lists. The aim is to have a more integrated set of activities created and provided by the different working groups (board, leadership team, oct).

Consortium investment in .LRN:

• Create a budget for the next 12 months / year, has to include also all administrative costs. (Alvaro can prepare a preliminary budget).
  
• Figure out the priorities for technical development (QA, new releases, etc.), documentation & tutorials, marketing.

Some areas to invest in that have been already formulated:

1. Bug-fixes: #3 & #4: prioritize technical tasks is OCT and leadership authority
2. QA testing for releases
3. Release Management
4. See original proposed set of jobs: https://docs.google.com/Doc?docid=0AUeGYMa72ygGZGhjbnc0bm1fN2R3czdxeGZ0&hl=en

Documentation:

1. Tutorials for basic areas of openacs technical development.
2. Update on installation process for official documentation (already on creation process, a plan about how to address it will be posted soon, so approval is give to proceed with it)

Marketing:

1. Training on .LRN usage.
2. Users help section
3. A demo-course of .LRN (already on creation process)
4. All these actions (and probably new ones) towards getting more users.

The Consortium investment process:

1. The priorities has to be agreed at the Leadership Team / OCT. Any formulated item will require a description clear enough to be able to justify a given investment.
2. Figure out which investment channels we can have:
3. • There is the initial Jobs small - incentives.
   • Some other people argue for better rates, that can lead us to monthly contract: directly contract monthly time in a yearly basis for some developers (at lets say open source rates, not as small as in the jobs): for instance one or two experienced community recognized developers, and one newbie (which is not expensive) that will do the bee-work.
   • Other possible paths? such as posting for a job and people make an offer and from there negotiate a give amount. Different people might require different amounts.
   • We might contract either an individual or an organization (Institution or a company)
4. Assign a given priority / task to the interested developer / party.
5. OCT / Leadership Team review and approved the work finished
6. Consortium pays.

Oracle support:

At this point we cannot guarantee oracle support for .LRN.
There are specific donations to Oracle, such from UCLA.
Additionally, UNED & Bergen use oracle and has given their donation, so a part of that funds should go to Oracle support.
Also, since UNED has an active group of developers supporting their installation, we should ask them to test Oracle as well.

Increase community participation:

• Consortium will request active and committed technical developer participation in the Leadership Team to the institutions that might have technical developers. (nominate an active developer for open-source with lets say 10-20 hours a week). Additionally, to be able to contribute better the best scenario will be to have this institutions to have their .LRN installations up-to-date, and have mechanisms that allow them to separate their code from what the official distribution is, that as well will let them influence more directly into the official distribution.
  
• Improve communication from OCT & Leadership Team:
• post the meeting minutes in time (the day after at the latest)
• get the IRC logger back and have a usable page to access logs
• move technical discussion to forums
• Improve communication with the board.
• Others?

Community growth:

• Create means to get new developers:  any ideas?
• Emma: That won't happen alone. The main issue is "getting new users" and
  it's a marketing matter.

dotlrn.org:

• git will be replaced with cvs checkout from the cvs.openacs.org
• update content
• The technical management is assigned to the Leadership Team.
  
• Leadership team can assume the technical management BUT ONLY ONCE the
  site is a CVS checkout from the openacs.org tree

The new tutorial:

• Has to have a place, where it links and download it.
• It can be included on the distribution file and in the documentation.
• With which tool we'll produce future tutorials and based on which templates still need to be settled. Maybe a comparison chart will help to make the decision.
• A tutorial has not the same format and purpose of a traditional documentation (format as how is structured, organized and designed, and not to which is the document type).
• Has to reflect any engineering standard that it might come across within its examples. While understanding that the tutorial is not to explain the engineering standards. The engineering standards has to be clearly defined with examples if necessary in the engineering standards section of the standard documentation (including the accessibility ones). The better explained, the easier to follow them!
• It can be exported to different formats but its mandatory format is html.
• As for documentation: we see in the repository no major changes in the documentation itself over the last years, so probably we need good review and really involve people to update on it, since none of the members of the groups seems to be doing maintenance over them.

Time/Topics Planner for dotLRN Courses

Created by Alvaro Rodriguez, last modified by Alvaro Rodriguez 01 Sep 2009, at 04:12 PM

News Item

Created by , last modified by Victor Guerra 11 Mar 2009, at 03:44 PM

Workshop Announcement

Created by Gustaf Neumann, last modified by Victor Guerra 11 Mar 2009, at 03:44 PM

@event@

Abstract: @_text@
@detail_link@

Talk Announcement

Created by Gustaf Neumann, last modified by Victor Guerra 11 Mar 2009, at 03:44 PM

@event@

Abstract: @_text@
@detail_link@

Book

Created by , last modified by Victor Guerra 11 Mar 2009, at 03:44 PM

E-learning is denominator (Also known as e-learning) to Distance Education virtualized through electronic channels (The new communication networks, especially the Internet) using para This Tools or Applications hypertext (E-mail, web pages, Discussion forums, Instant Messaging, Platforms Training, among others) and support the teaching and learning processes. In a concept more related to what blended learning, also called b-learning (blended learning). 1

The b-learning is a modality that combines distance education and classroom education, taking up the advantages of both modalities and complementing LEARNING apprentices.

Also Florist defined as a system based on the Mass and two-way communication system that replaces personal interaction in the classroom of teacher and student, as preferred means of education, the systematic and Joint DIFFERENT Resource Action and support of a tutorial organization, that promotes learning AUTONOMO of Students, in addition to strengthening skill of effective communication with participants through platforms implemented.

  It consists of the Education and Training through Internet. This type of online education allows user interaction with the material By using various tools.

This new educational concept is a revolutionary form of training enabled Internet, and today is positioned as the predominant form of future training. This system has transformed Education, Abriendo Puertas to individual and organizational learning. That is why today esta un Lugar occupying increasingly prominent and recognized within business and educational organizations.

# OpenACS
nano /etc/default/openacs

# .LRN
nano /etc/default/dotlrn       

# OpenACS
/etc/init.d/openacs stop

# OpenACS
ln -s /usr/share/openacs/etc/daemontools /etc/service/openacs

# .LRN
 
    

su - $OPENACS_SERVICE_NAME
pg_dump -f /var/lib/aolserver/$OPENACS_SERVICE_NAME/database-backup/before_upgrade_to_4.6.dmp openacs-dev
ls -al /var/lib/aolserver/$OPENACS_SERVICE_NAME/database-backup/before_upgrade_to_4.6.dmp
exit

Install OpenACS on Linux

Created by Gustaf Neumann, last modified by Gustaf Neumann 06 Dec 2008, at 10:36 AM

The following pre-packaged installations for OpenACS and .LRN under Linux are available:

• Installing OpenACS/.LRN for ubuntu
• Installing OpenACS/.LRN for debian

OpenACS and .LRN can be installed certainly as well from scratch using the guidelines for stepwise installation of all necessary components.

In general, OpenACS and its components works very well under Linux. It is used in many large installation with up to 10 million hits per day. For most applications, the systems runs nicely with a wide range of versions of Linux and its components. Due to some library changes in some Linux versions (especially in the native Linux thread installations), some precautions might be necessary. In case of problems on sites with high loads (e.g. server hangs) we recommend the following versions

• Linux Kernel <2.6.9 or better,  >2.6.25
  
• NTPL >= 2.7
• gcc >= 4.2
  
• Tcl libthread should be > 2.6.5 (including changes from 2008-05-22)

Mentorship Program

Created by Ryan Gallimore, last modified by Ryan Gallimore 01 Nov 2008, at 10:35 PM

The OpenACS Mentorship program connects new developers with experienced mentors to support students in the development of their OpenACS skills.

Our methodology includes the following:

• minimal time commitment of a mentor to a developer
• assignments are selected based on a student's interest and skill level, as well as community need, if applicable.
• mentor and developer meet on a regular basis (e.g weekly) in a chat session or via e-mail to discuss his/her project.
• creation of improved documentation for new developers.
• participation from mentors, students and the community in the development of a core OpenACS curriculum.

OpenACS Feature Summary

Created by Ryan Gallimore, last modified by Brian Fenton 08 Oct 2008, at 02:36 PM

Updated from CMS Matrix.org

Install Postgresql

Created by OpenACS community, last modified by Ryan Gallimore 03 Oct 2008, at 06:27 PM

A quick install guide for Postgres 8.2 which takes everything into account can be found at http://cognovis.de/developer/en/pg82 

For RPMs, see http://yum.pgsqlrpms.org/

These instructions should work for 7.4 to 8.2.

Get the source code

http://www.postgresql.org/download/

Install from source

Unpack PostgreSQL 7.4.7. If you have downloaded the postgresql tarball to /var/tmp/postgresql-7.4.7.tar.gz

[root root]# cd /usr/local/src
[root src]# tar xzf /var/tmp/postgresql-7.4.7.tar.gz
[root src]# 
cd /usr/local/src
tar xzf /var/tmp/postgresql-7.4.7.tar.gz

If you have downloaded the postgresql tarball to /var/tmp/postgresql-7.4.7.tar.bz2

[root root]# cd /usr/local/src
[root src]# tar xfj /var/tmp/postgresql-7.4.7.tar.bz2
[root src]# 
cd /usr/local/src
tar xfj /var/tmp/postgresql-7.4.7.tar.bz2

Create the Postgres user. Create a user and group (if you haven't done so before) for PostgreSQL. This is the account that PostgreSQL will run as since it will not run as root. Since nobody will log in directly as that user, we'll leave the password blank.

[root src]# groupadd web
[root src]# useradd -g web -d /usr/local/pgsql postgres
[root src]# mkdir -p /usr/local/pgsql
[root src]# chown -R postgres.web /usr/local/pgsql /usr/local/src/postgresql-7.4.7
[root src]# chmod 750 /usr/local/pgsql
[root src]#
groupadd web
useradd -g web -d /usr/local/pgsql postgres
mkdir -p /usr/local/pgsql
chown -R postgres.web /usr/local/pgsql /usr/local/src/postgresql-7.4.7
chmod 750 /usr/local/pgsql

Set up postgres's environment variables. They are necessary for the executable to find its supporting libraries. Put the following lines into the postgres user's environment.

[root src]# su - postgres
[postgres ~] emacs ~postgres/.bashrc

Paste this line into .bash_profile:

source $HOME/.bashrc

Paste these lines into .bashrc:

export PATH=/usr/local/bin/:$PATH:/usr/local/pgsql/bin
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/pgsql/lib

Test this by logging in as postgres and checking the paths; you should see /usr/local/pgsql/bin

[root src]# su - postgres
[postgres pgsql]$ env | grep PATH
LD_LIBRARY_PATH=:/usr/local/pgsql/lib
PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin:/usr/bin/X11:/usr/X11R6/bin:/root/bin:/usr/local/pgsql/bin:/usr/local/pgsql/bin
[postgres pgsql]$ exit

Don't continue unless you see correct output from env | grep PATH

Compile and install PostgreSQL. Change to the postgres user and run ./configure to set the compilation options automatically. This is the point at which you can configure PostgreSQL in various ways. To see what the possibilities, run ./configure --help.

[root src]# su - postgres
[postgres pgsql]$ cd /usr/local/src/postgresql-7.4.7
[postgres postgresql-7.4.7]$ ./configure
creating cache ./config.cache
checking host system type... i686-pc-linux-gnu
(many lines omitted>
linking ./src/makefiles/Makefile.linux to src/Makefile.port
linking ./src/backend/port/tas/dummy.s to src/backend/port/tas.s
[postgres postgresql-7.4.7]$ make all
make -C doc all
make[1]: Entering directory `/usr/local/src/postgresql-7.4.7/doc'
(many lines omitted)
make[1]: Leaving directory `/usr/local/src/postgresql-7.4.7/src'
All of PostgreSQL successfully made. Ready to install.
[postgres postgresql-7.4.7]$ make install
make -C doc install
make[1]: Entering directory `/usr/local/src/postgresql-7.4.7/doc'
(many lines omitted)
Thank you for choosing PostgreSQL, the most advanced open source database
engine.
su - postgres
cd /usr/local/src/postgresql-7.4.7
./configure 
make all
make install

Start PostgreSQL. The initdb command initializes the database. pg_ctl is used to start up PostgreSQL.

[postgres postgresql-7.4.7]$ /usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data
The files belonging to this database system will be owned by user "postgres".
This user must also own the server process.
(17 lines omitted)
or
    /usr/local/pgsql/bin/pg_ctl -D /usr/local/pgsql/data -l logfile start
[postgres postgresql-7.4.7]$ /usr/local/pgsql/bin/pg_ctl -D /usr/local/pgsql/data -l /usr/local/pgsql/data/server.log start
postmaster successfully started
[postgres postgresql-7.4.7]$
/usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data
/usr/local/pgsql/bin/pg_ctl -D /usr/local/pgsql/data -l /usr/local/pgsql/data/server.log start

PostgreSQL errors will be logged in /usr/local/pgsql/data/server.log

Install Pl/pgSQL.Set up plpgsq and allow your user to have access. Plpgsql is a PL/SQL-like language. We add it to template1, which is the template from which all new databases are created. We can verify that it was created with the createlang command in list mode.

[postgres postgresql-7.4.7]$ createlang plpgsql template1
[postgres pgsql]$ createlang -l template1
Procedural languages
  Name   | Trusted?
---------+----------
 plpgsql | t
(1 row)

[postgres pgsql-7.4.7]$
createlang plpgsql template1
createlang -l template1

If you are installing Postgres 8.x, follow additional instructions at en:How_to_install_in_Postgres_8.x

If you are installing tsearch2, follow additional instructions at en:postgresql-tsearch2

Test PostgreSQL (OPTIONAL). Create a database and try some simple commands. The output should be as shown.

[postgres pgsql]$ createdb mytestdb
CREATE DATABASE
[postgres pgsql]$ psql mytestdb
Welcome to psql, the PostgreSQL interactive terminal.

Type:  \copyright for distribution terms
       \h for help with SQL commands
       \? for help on internal slash commands
       \g or terminate with semicolon to execute query
       \q to quit

mytestdb=# select current_timestamp;
          timestamptz
-------------------------------
 2003-03-07 22:18:29.185413-08
(1 row)

mytestdb=# create function test1() returns integer as 'begin return 1; end;' language 'plpgsql';
CREATE
mytestdb=# select test1();
 test1
-------
     1
(1 row)

mytestdb=# \q
[postgres pgsql]$ dropdb mytestdb
DROP DATABASE
[postgres pgsql]$ exit
logout

[root src]#

Set PostgreSQL to start on boot. First, we copy the SERVERROOT/packages/acs-core-docs/www/files/postgresql.txt init script, which automates startup and shutdown, to the distribution-specific init.d directory. Then we verify that it works. Then we automate it by setting up a bunch of symlinks that ensure that, when the operating system changes runlevels, postgresql goes to the appropriate state. Red Hat and Debian and SuSE each work a little differently. Be sure to check OS distribution notes for specifics (and examples)

Once installed, PostgreSQL should start automatically each time you boot up and it should shutdown gracefully each time you shut down.