Cream roadmap: identifying features

Events happening in the community are now at Drupal community events on www.drupal.org.
You are viewing a wiki page. You are welcome to join the group and then edit it. Be bold!
Posted by aburrows on March 19, 2014 at 4:35pm
Last updated by joachim on Thu, 2014年03月20日 14:30

Here are some of the features we are proposing for CREAM.

The plan is to assemble this list over the next few days and then do a prioritizing exercise (probably with a Google survey; we'll invite votes from the community). This will then help us produce a roadmap showing the order in which we'll implement features:

  • Features which form the MVP which should be implemented first.
  • Additional feature in order of preference, which subsequent builds of CREAM can add.
  1. Signup: Site visitors can create an account and sign up for the camp and become attendees.
  2. Payment: Site visitors are required to pay to become attendees.
  3. Session submission: Attendees can submit sessions (and thus become participants)
  4. Event creation Wizard: The site builder sets event title and dates in the CREAM installation process. The process of creating the event and schedule nodes is automated.
  5. Session Management - approval: The camp organiser can approve and deny sessions on a single admin page.
  6. Session Management - scheduling: The camp organiser can arrange sessions by time and room on a single admin page.
  7. Speaker Management: The camp organiser can manage all speakers in one page
  8. Sponsor Management: The camp organiser can manage all sponsors in one page, change sponsor types.
  9. Bulk contact of speakers: The camp organiser can send email in bulk to all attendees who have submitted a session.
  10. View submitted sessions: Prior to sessions being approved, site visitors can see the sessions submitted so far.
  11. Vote on sessions (organiser and attendees): Prior to sessions being approved, organisers and attendees can vote on the sessions they'd most like to see approved.
  12. Personal schedule: Participants can select from the approved sessions and bofs to create their personal schedule for the camp.
  13. Keynote speaker block: Site visitors can see a list of the keynote speakers showing profile pictures and names
  14. Today's session block
  15. Sponsor block
  16. Sponsored jobs
  17. Default CREAM layouts: a selection of Features for the site builder to choose from, each providing a different site layout. Available in Panels or Context flavours!
  18. Attendee check-in: Volunteers assisting with registration use the site to check in a participant. Helps camp organisers monitor attendance and plan mailshots for the following year's camp.
  19. Room map: Participants see a map of the camp venue on the map page, and on each session the map is repeated with a marker for the session's location. Site builders select co-ordinates by clicking on the venue map in the edit form for each room.

You may want to refer to the list of site personas: https://groups.drupal.org/node/415203

Comments

Should we get further input

Posted by joachim on April 2, 2014 at 8:23pm

Should we get further input on this, or go ahead and make a survey based on these?

Here are my initial

Posted by mikebell_ on April 7, 2014 at 9:39pm

Here are my initial thoughts:

Room Management - As an event organiser I want to see an overview of the rooms available for talks/sessions. The more I think about this the more it’s probably a bit redundant.

Standard Sponsorship levels - Platinum, Gold, Silver, Bronze, Personal. Configurable amounts of each tier. Node/Entity ref to sponsor (user/node type?).

Ability to easily turn off voting for sessions or restrict to certain roles e.g. volunteers/organisers. Possible config option during install

Bulk contact of Atendees and Speakers as well

As an event organiser I want

Posted by joachim on April 8, 2014 at 7:53am

As an event organiser I want to see an overview of the rooms available for talks/sessions. The more I think about this the more it’s probably a bit redundant.

As we're using an entity type for rooms, we've effectively accomplished that already. But fair point, it's not that important.

Configurable amounts of each tier. Node/Entity ref to sponsor (user/node type?).

I hadn't thought of that. You want to be able to limit the number of Gold sponsors to 5, say.

CREAM - Event Management system

Group organizers

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds:

AltStyle によって変換されたページ (->オリジナル) /