Ubuntu Wiki

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.

• Launchpad Entry: edubuntu-content-server

• Packages affected: moodle

Summary

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.

Release Note

Installing Moodle will be easier in Hardy because the edubuntu-content-server package handles all the heavy lifting!

Rationale

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.

Use Cases

• 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.

• 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,

Implementation

• 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

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.

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.

Test/Demo Plan

Outstanding Issues

BoF agenda and discussion

• Embedded code copies
  • Debian and Ubuntu maintain a list of embedded code copies in various programs, having these libraries externally packaged would help for updates, security or otherwise. Making sure the code uses the system copies instead of the internal copies would be great. (Best to actively not install the internal copies in the release packages).

    • http://svn.debian.org/wsvn/secure-testing/data/embedded-code-copies?op=file&rev=0&sc=0

    • for moodle, there is currently listed (there may be others worth investigating):
      • AdoDB (libphp-adodb)
      • AdoDB-XML Schema
      • ipatlas
      • PHPMailer (libphp-phpmailer)
      • Smarty (smarty)
      • htmlArea
      • TinyMCE (tinymce)
      • bennu

• Web application packaging draft Debian policy: http://webapps-common.alioth.debian.org/draft/html/

  • Ubuntu Server Team has been discussing this policy and wwwconfig-common (which has flaws): https://blueprints.launchpad.net/ubuntu/+spec/improved-web-application-framework

• Due to moodle's history of security issues, it would be valuable to have a good working relationship with the upstream and have them maybe help produce updates for stable releases

  • http://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=moodle

CategorySpec