CAcert Code Development list.

[Mario Lipinski <mario AT cacert.org>]

Hello,

at https://bugs.cacert.org/view.php?id=437 the requirements for the
event management software have been posted recently.

We still need someone to implement it. If you are interested contact me
or the software officer.

Below the requirements.


Mario
CAcert Event Organisation Officer



Requirements for event management software

The software should be a kind of calendar application.
For each event the following information should be available.

 * title
 * (long) description
 * location
 * event information (url)
 * event organiser
 * event organiser email
 * begin
 * end
 * comments
 * status (maybe only for internal purposes)

The information should be entered at a form. This form should be
available to anybody to propose an event. Only the event organisation
officer should be allowed to publish them after review. He is also the
only one who can edit. The field status is not available to any regular
user. The field comments can only be seen by event admins.

Title takes a short text - about one line. Description takes a longer
text which might be a few paragraphs and should take a few basic (HTML)
elements like hyper references. begin and end are dates, times optional.
Status takes predefined options (details tbd).

A few events coming up next should be listed on the cacert homepage with
title, location and (start)date(s). Details should be available on a
page referenced from there.

If the software allows such extensions it should be possible to refer to
an event in news messages. News messages are used to announce special
events to the public and to highlight special features to the community
or ask for help with it. The news must contain some basic information
and a hyper reference to the events detail page.

Events with end date in the past are listed in an event archive. A link
to it is places accordingly.

The event organisation officer is notified by email of any new entries
and any changes. The pr officer is notified on any changes to published
events.

All this must be implemented to be on the CAcert main page (not
neccessarily homepage, no external software just half-integrating like
current news blog) to ensure having a central point to go to.

Attachment: smime.p7s
Description: S/MIME cryptographic signature