ContentServer

Differences between revisions 4 and 5
⇤ ← Revision 4 as of 2007-11-01 21:51:42 →
Size: 4148
Editor: 12
Comment:
← Revision 5 as of 2007-11-02 20:16:20 → ⇥
Size: 3912
Editor: 12
Comment:
Deletions are marked like this. Additions are marked like this.
Line 10: Line 10:
We will make it easier to install Moodle in Edubuntu as a content server for educators. We will reduce the number of installation questions and create a [meta]package to handle all the dependencies. We will make it easier to install Moodle in Edubuntu as part of a content server solution for educators. We will reduce the number of installation questions via preseeding; if Recommends: are still not supported for hardy we will create a moodle-standalone metapackage to provide a single package install that results in a working Moodle.
Line 13: Line 13:
Installing Moodle will be easier in Hardy because the edubuntu-content-server package handles all the heavy lifting! The edubuntu-content-server package handles all the heavy lifting to create a server for many kinds of educational content; e.g., interactive course materials and assignments, collaborative documents, and locally cached wikipedia articles can live right here on your very own server.
Line 16: Line 16:
The moodle package was added to main for gutsy, but it still has some rough edges. (For example, the postgres or mysql server package must have been installed manually beforehand for the moodle package installation to work properly without further manual configuration.) These rough edges need to be smoothed out so that Ubuntu system administrators will use the supported ubuntu package[s] to install their Moodle systems. The existing moodle package still has some rough edges, and there must be a straightforward way to install Moodle and the choice offerings in other content server areas on an Edubuntu system.
Line 19: Line 19:
 * Marjorie downloads the Ubuntu Education CD to transform her high-end Ubuntu Desktop system into an LTSP server. During the Ubuntu Education Edition installation, she has the option to make this an Edubuntu Content Server, which means that Moodle is installed and ready to roll when the installation completes. Marjorie will be instructed to open a Web browser to http://localhost/moodle/ to complete the installation, but no further debconf questions will be asked.  * Marjorie downloads the Ubuntu Education CD to transform her Ubuntu server into an education content server. Marjorie will be instructed to open a Web browser to http://localhost/moodle/ to complete the installation, but no debconf questions will be asked.
Line 25: Line 25:
 * the edubuntu-content-server metapackage will depend on multiple content-related applications (e.g., moodle, wiki,  * the edubuntu-content-server metapackage will depend on multiple content-related applications (e.g., moodle, wiki, gobby, etc.)
Line 28: Line 28:
 * Apparently Recommends: will be honored in the near future, so the existing package will begin installing the database correctly; no metapackage(s) necessary.

This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:

=== UI Changes ===

Should cover changes required to the UI, or specific UI that is required to implement this		  * Recommends: will be honored in the near future, so the existing package will begin installing the database server correctly.
 * The existing Moodle has quite a number of other projects' sources included in the upstream source; these should be broken out and packaged separately, and the moodle package should add these as dependencies. It would be nice to complete this process, and we will get as close as we can by hardy's release. (See BoF agenda & discussion below.)
Line 37: Line 32:
We will modify the set of debconf questions to minimize what is asked by default, and we will create a metapackage with dependencies sufficient to set up a complete, working Moodle by installing only one package.

=== Migration ===

Include:
 * data migration, if any
 * redirects from old URLs to new ones, if any
 * how users will be pointed to the new way of doing things, if necessary.		  * We will modify the set of debconf questions to minimize what is asked by default, and we will create a metapackage with dependencies sufficient to set up a complete, working Moodle by installing only one package.

Please check the status of this specification in Launchpad before editing it. If it is Approved, contact the Assignee or another knowledgeable person before making changes.

Summary

We will make it easier to install Moodle in Edubuntu as part of a content server solution for educators. We will reduce the number of installation questions via preseeding; if Recommends: are still not supported for hardy we will create a moodle-standalone metapackage to provide a single package install that results in a working Moodle.

Release Note

The edubuntu-content-server package handles all the heavy lifting to create a server for many kinds of educational content; e.g., interactive course materials and assignments, collaborative documents, and locally cached wikipedia articles can live right here on your very own server.

Rationale

The existing moodle package still has some rough edges, and there must be a straightforward way to install Moodle and the choice offerings in other content server areas on an Edubuntu system.

Use Cases

  • Marjorie downloads the Ubuntu Education CD to transform her Ubuntu server into an education content server. Marjorie will be instructed to open a Web browser to http://localhost/moodle/ to complete the installation, but no debconf questions will be asked.

  • Shamu starts Synaptic and selects the 'moodle' package for installation. She is asked a minimum of debconf questions and a working Moodle is the result.

Assumptions

Design

  • the edubuntu-content-server metapackage will depend on multiple content-related applications (e.g., moodle, wiki, gobby, etc.)

Implementation

  • Recommends: will be honored in the near future, so the existing package will begin installing the database server correctly.

  • The existing Moodle has quite a number of other projects' sources included in the upstream source; these should be broken out and packaged separately, and the moodle package should add these as dependencies. It would be nice to complete this process, and we will get as close as we can by hardy's release. (See BoF agenda & discussion below.)

Code Changes

  • We will modify the set of debconf questions to minimize what is asked by default, and we will create a metapackage with dependencies sufficient to set up a complete, working Moodle by installing only one package.

Test/Demo Plan

Outstanding Issues

BoF agenda and discussion

CategorySpec

Edubuntu/Specifications/ContentServer (last edited 2010-01-21 15:26:43 by 196-210-177-89-wblv-esr-3)