Events

Differences between revisions 11 and 12
Revision 11 as of 2009-04-03 06:21:33
Size: 2833
Editor: phoebe
Comment:
Revision 12 as of 2009-04-09 20:36:25
Size: 3763
Editor: ip-83-134-208-106
Comment: Adding feedbacks from jean7491 and MatthewDeboysere
Deletions are marked like this. Additions are marked like this.
Line 7: Line 7:
== User stories (sorted by priority) == == User Stories (sorted Sby priority) ==
=== Must Have ===
Line 12: Line 13:
 * As an Ubuntu-be member, I want to edit or delete the information about an event I added earlier.   * As an Ubuntu-be member, I want to edit or delete the information about an event I added earlier.
Line 14: Line 15:

=== Nice to Have===
 * As an Ubuntu-be member, when adding an event, I want the option to automatically link to a wiki page for working on the event organisation (and have a quick link to create a new page based on a template).
 * As an Ubuntu-be member, I want to allow other Ubuntu-be members to edit or delete the information about an event I added earlier.
Line 16: Line 21:
 * As a visitor, I want to publish report about a past event (possibly with pictures) so that everybody can see how great it was.
Line 17: Line 23:
 * As a visotor, I want to publish report (possibly with pictures) about a past event so that everybody can see how great it was.
Line 24: Line 29:

== Discussion ==
 * There is no requirement that the submitter of an event is also its organizer. Actually, it's expected that many events will be added by a reduced team of volunteers acting as relay for events announced on mailing lists, LUGs, direct email, etc.
 * ''Must Have'' User Stories are the ''features'' we want to see implemented before considering the work has done. Others are like bonuses, no required but nice to have.
Line 39: Line 48:
  * Create a second ''content-type'' for report
  * Use a field to link a report to the event, and vice-versa
  * Allow pictures upload for this content-type
  * On the website:
 
* Create a second ''content-type'' for report
   * Use a field to link a report to the event, and vice-versa
   * Allow pictures upload for this content-type
  * On the wiki
   * Auto-generate a link to an event report page on the wiki

Promote Ubuntu-be Events on Website

User Stories (sorted Sby priority)

Must Have

  • As a visitor of the website, I want to access to the list of upcoming events presented as a traditional calendar view so that I can quickly see what's happening soon.

  • As a visitor of the website, I want to know where, when and by whom an event is organized.
  • As a visitor of the website, I want to access information about an event in Dutch, English, French or German.
  • As an Ubuntu-be member, I want to add information about an upcoming event to the website so that visitor will be aware of the event.
  • As an Ubuntu-be member, I want to edit or delete the information about an event I added earlier.
  • As an Ubuntu-be Web Editor, I want to add, edit or delete information about any events.

=== Nice to Have===

  • As an Ubuntu-be member, when adding an event, I want the option to automatically link to a wiki page for working on the event organisation (and have a quick link to create a new page based on a template).
  • As an Ubuntu-be member, I want to allow other Ubuntu-be members to edit or delete the information about an event I added earlier.
  • As an Ubuntu-be member, I want to assert my availability to help with the organization of an announced event.
  • As a visitor of the website, I want to assert my intention to attend to an announced event.
  • As a visitor, I want to publish report about a past event (possibly with pictures) so that everybody can see how great it was.
  • As a visitor, when accessing information about an event, I want to see its location on a map with quick access to instruction on how to get there.
  • As a visitor, I want to access the list of upcoming events presented on a single map.

Glossary

Discussion

  • There is no requirement that the submitter of an event is also its organizer. Actually, it's expected that many events will be added by a reduced team of volunteers acting as relay for events announced on mailing lists, LUGs, direct email, etc.
  • Must Have User Stories are the features we want to see implemented before considering the work has done. Others are like bonuses, no required but nice to have.

Approach

  • Base features
    • The Date and Calendar.

    • Or the event module. There is no current stable release but Ubuntu South Dakota uses a development snapshot without any major issue.

    • A content type for events with fields for

      • Organizer
      • Location
      • start and end date/time
      • the kind of event (taxonomy ?)
      • Use body to describe the event

  • Attendees using the signup module visitors can register to nodes (events are nodes).

  • Helpers
    • how ?
  • Reports
    • On the website:
      • Create a second content-type for report

      • Use a field to link a report to the event, and vice-versa
      • Allow pictures upload for this content-type
    • On the wiki
      • Auto-generate a link to an event report page on the wiki

BelgianTeam/Website/Events (last edited 2009-05-26 08:31:56 by ip31)