From ClaroDevel

Les roadmaps contiennent les développements décidés (si possible affectés).

Les to do et wishlist contiennent ce qui n'est pas décidé.

---

Table of contents

1 Documentation 2 PHP.ini 3 files permissions 4 Installation 5 Upgrade 6 kernel 6.1 comptes utilisateurs 6.2 Campus Homepage 6.3 My course list 7 Courses tools 7.1 Course properties 7.1.1 datas 7.1.2 delete 7.1.3 export 7.1.4 import 7.1.5 quota 7.1.6 expiration 7.2 Tool list in course 7.3 The course description settings 7.4 The agenda tool 7.5 The announcements tool 7.6 The document and links tool 7.7 The exercises tool 7.8 The learning path tool 7.9 The assignments tool 7.10 The forums tool 7.11 The groups tool 7.12 The users tool 7.13 The chat tool 7.13.1 date 7.13.2 save 8 New tools 8.1 A search tool 9 Administration interface 9.1 Administrator view 9.2 Administering the platform users 9.3 Administering the platform courses 9.4 Plateform settings 9.5 check platform 10 Tracking 11 LaTeX

Documentation

• nécessité d'avoir un résumé des coding rules à jour (suite à la réunion de juin)
• CIG: Claroline Interface Guideline

 <guim> les popup d'aide pourrait pas être de simple liens vers la bonne page du wikidoc ?
 <M00sh> sur des wikidoc bloqués en écriture alors: )
 <hugues_> à mettre dans liste des choses possible pour la 1.7

PHP.ini

• error_reporting = E_ALL

files permissions

• use a good mask with mkdir (mask= 02770)
• work on server with no chmod

Installation

• installer light, download last version on an official server
• check more before work

• check if zipLib work (if not work, it's not possible to unzip zip files and to upload SCORM packages)
• check ereg
• check if script can use a better local zipper/unzipper

• purpose to edit course repository

Upgrade

• upgrade by module, not by all claroline
• tuning of upgrade du max_execution_time
• test de l'upgrade en php-cli.

split upgrade

1. upgrade kernel
2. upgrade course
3. upgrade tools

campus would be opened after kernel upgrade (and not after all course upgraded)

• isoler les "check" dans des scripts indépendant appelable avant l'upgrade (ou n'important quand pendant l'utilisation normale de claroline)

kernel

comptes utilisateurs

• expiration des comptes utilisateur
• fusion de comptes
• blocage de comptes
• demande par l'utilisateur mais validation par l'admin de statut "créateur de cours"
• demande par l'utilisateur mais validation par l'admin de statut "créateur de cours" via "mon profil"
• ajout d'extradata (CV platforme) FOAF ? vCard (http://www.ietf.org/rfc/rfc2426.txt) ? hcard (http://microformats.org/wiki/hcard)
• plus de tracking-administratif sur les actions (plus le lecteur de ce tracking)
• validation d'email (par envoi de clé à l'dresse mentionnée)
• raffinement des status (simple_user/course_creator/platform_admin -> secrétaire, responsable facultaire, course_creator__de_confiance ....
• lostPassword would be able to send a copy in bcc to plaform admin
• lostPassword would be able to send a warn in bcc to plaform admin when multiple found are detected
• send password by mail from "user-admin"
• choix de la time-zone pour chaque profil (pour les users qui ne sont pas dans le fuseau horaire de leur institution
• choix de la langue plateforme pour chaque profil (pour les institutions avec plusiseurs langues officielles)
• choix de la méthode d'affichage pour chaque profil (choix d'une css et interface adaptée aux capacités de l'utilisateur, des son client et de ses habitudes)
• revocation request from my profile
• promote course creation request from profile

• check login -> Une regex en config
• check email -> Une regex en config
• check officialCode -> Une regex en config
• check password -> Une regex en config
• picture in the profil, with config to allow or not user to add/modify it

Campus Homepage

• news system

My course list

• See if there are new items in courses: messages, documents, ...

Courses tools

Course properties

• split edition of properties and management action

datas

delete

• admin would be eable to redirect garbage on /dev/null
• garbage collector

export

• split export, backup and archives concept (archive = backup + delete, but delete include an backup...)

import

• can import an exported courses (from wich claroline version ? wich campus ? is secure ? ...)

quota

• show quota allowed
• show course size

expiration

• detect ghosts

Tool list in course

• find a valid W3C substitution to validationmsg attribute of submit in "noscript"

The course description settings

• [CIG] La suppression n'est pas semblable aux autres supp de claroline.

The agenda tool

• [CIG] Confirmation to delete all items

The announcements tool

• [CIG] Confirmation to delete all items

The document and links tool

• Possiblity to unzip an archive, if it's missed on the upload
• Tar.gz files
• Thumbnail + media view
• [CIG] Confirmation before delete a folder and all items

The exercises tool

The learning path tool

The assignments tool

• Display of the list of all users should be replaced
• Add links (prev and next student) to browse students one by one without having to go back to the userlist
• Students see the full list of students with 0 submissions (e.g. if default visibility is 'hidden'), it can bring confusion
• Find a solution for the works that have been submitted by a student that is now unregistered

The forums tool

• empty empty all (http://www.claroline.net/forum/viewtopic.php?p=15297#15297) (backport from 1.7 to 1.6)

[ DONE 1.7]

The groups tool

The users tool

• teacher can export list
• list by group, name or state
• view ghost
• edit ghost

The chat tool

date

15:39   > cwxcwxc
13:33 > holla, buenas
14:32 super zon > salut tout le monde
14:32 super zon > comment ça va ?
14:33 super zon > y a personne dans cette salle ?
11:33 Mathieu Laurent > test

[ DONE 1.6: 16/09/04 ] Display date, like : dd/mm/yy [hh:mm] username > message

save

[ DONE 1.6: 16/09/04 ] ajouter un <head><title> éventuellement une css

New tools

New tool that could be coded for claroline, that some people form forum or else where would like to have

A search tool

A search engine like google but that looks into the courses and maybe into the tools with given keywords.

Administration interface

Administrator view

Administering the platform users

• display uneditable fields (creation date, nb courses, is_ghost, creatorId, is_officialcode valid,...)
• See the username in the list
• manage old user without delete it.
• link to admin action
  • send auth info by mail
  • gen new loginpass and send auth info by mail
  • lock this user
  • send a private message
  • check ext ressousces (ldap, google, ext script..)

Administering the platform courses

• search param on "strange case"
• display uneditable fields (creationDate, creatorid, ...)
• edit quota
• manage expiration
• export a result (txt, csv, pdf, ...)

Plateform settings

DONE * edit all config files via web DONE * display uneditable param DONE * use definition file as template for config files.

check platform

• check database integrity

Tracking

• [CIG] Looks like Admin interface (use of claro_pager, ...)
• add security event (login logout, lost password, create course, create account, subscribe, unsbscribe, edit profile,...)

LaTeX

• usage on post in forum
• usage on answer in exercise
• doesn't work with htmlarea WYSIWIG view