[haiku-web] Re: [haiku-admin] Re: Website

Okay, here is the full list of requirements for the website:

Please update the wiki page at
http://www.haiku-os.org/wiki/index.php?title=Website_Team
if you have something to add/change.
This might not be complete...


== Overview ==
* moderated community CMS (replacing wiki)
* ticket tracker
* mailing lists with forum gateway (or better: integrate both into one)
* single-sign-on for all site modules
* if possible, non-separated look

== CMS ==
Highest priority: it must be *extremely* easy to use. There should be no learning curve *at all*. This includes WYSIWYG editing.

Everyone can register and submit content to the moderators. The moderators review it and may decide to publish or reject.

Allow for multiple blogs and easy article management.

We need access control, so we can restrict special website sections to developers, only (e.g.: secret in-development RFCs, planning, admin discussions, etc.).

Multi-lingual CMS. We will at least need very simple translations, so you see the most important news, a list of goals, screenshots, "How To Install", and a download page.

Easy to use FAQ manager with support for categorizing FAQs. One page per category. Only display question and answer (no author, date, etc.).

== Unified Mailing List and Forum ==
Some people prefer to poll for new posts (forum), others want to run email conversations (ML). Combine both into one and use a forum-like interface.

== Ticket Tracker ==
Trac will replace Bugzilla and our current website's task tracker. These modifications are needed:

Replace Cc field with subscriptions.
* use email notifications
* author is subscribed, automatically
* assigned person is subscribed, automatically
* you are *not* auto-subscribed when commenting
* add "subscribe"/"unsubscribe" link
* every mail contains "unsubscribe" link, so you can quickly stop receiving emails if you're annoyed (if you're assigned to the ticket unsubscription closes it. mention that in the email!)

Simplify "resolve as" drop-down list (I hope nobody shouts at me for over-simplifying...):
* fixed
* duplicate
* deleted (and comment on *why*)

Only developers and admins are allowed to create tasks. Users may only create "defect" and "wish" tickets (later, we might not allow for wishes, anymore). This probably requires permissions per ticket type.

Only developers and admins can be assigned to tickets.

Milestone, Priority, and Status (and for ticket creation: Assign-To) should only be editable by developers and admins. For normal users the drop-down fields should be hidden. TICKET_APPEND is okay to start with, but non-editable fields should be hidden instead of just disabling them.

When creating tickets, next to the description field there should be a little note:
-----
For "defect" reports, please specify:
* how to reproduce
* experienced behavior
* expected behavior
* if applicable: revision
-----
The Version list should not be flooded with specific revisions. Only official releases should be listed (R1.0.5, etc.).

Components should be organized as a tree instead of a flat list.

Remove Keywords.

Remove Severity (FYI, Priority will stay!).

When clicking on "View Tickets" you are taken to the default query: "open tickets by component"

Disable wiki.

If the svn plugin does not yet work with remote repositories then we can live without it.

-----------------------------------------------------------------------
haiku-web@xxxxxxxxxxxxx - Haiku Web & Developer Support Discussion List

Other related posts: