Roadmap

Here's roughly what we want to accomplish. We'll try out each step at a workshop or two and get feedback from the participants about the app.

Event Approval

• We can't send out emails to large groups of people until we lock down the event creation process. Spammers are not our friends.
• Always show organizers their own events, with some indication if they aren't approved yet
• Create a place where meta-organizers can review event postings for legitimacy & approve them
• Notify organizer(s) that event is public
• Send out announcement email to everyone in their chapter

Organize Workshops by Chapter

• Each user & location is associated with a chapter
• Users can have more than one chapter, and get an email every time a new workshop is approved
• Users can opt out of announcement emails

Post-Workshop Survey

• At the end of the last session, a link should go out to all participants soliciting feedback about the workshop they attended. It'll be similar to our Google Docs survey
• It should also include a question about feedback for their teachers specifically
• The organizer should be able to add a note to the email, so they can include any specific info
• The email should also include links to our next steps ideas
• Teachers should be able to choose to see feedback about them aggregated (possibly with some kind of review functionality so that RailsBridge can ensure that the feedback is helpful before it's visible)
• There should also be a place for students to leave really anonymous feedback (just a web form somewhere available when logged out, but still linked to the specific workshop)

Student Ability Survey

• Currently, students choose their own level based on class level descriptions (see this page for examples for Rails.) Since people chronically underestimate their abilities, we'd like to give them a short survey and then tell them what level we think they should be in.
• Students are prompted to take 10 question survey to determine class placement
  • Every curriculum has 10 questions that have logic attached to them for sorting
  • Organizers choose which curricula will be available
  • If more than one curricula is available for a single workshop, student RSVP will include preference

Host / Location Survey

• Build out the location functionality so that the admin/ops people at the hosting location can directly give us more details about the space, including:
• number and approx. capacity of conference rooms
• capacity of open area for presentations / installfest
• assurance that their public wifi network will be available
• space for childcare
• bike parking situation
• contact info for 1 admin/operations person and 1 technical person who will be giving a brief pitch during the installfest or opening presentation
• Contact information for hosting staff will only be available after the event has been approved

Wishlist

• The student / volunteer profile has a Projects section to list their previously created apps.
• Even more wishlist items on our Someday Feature Wishlist

Things that are done. Woo hoo!!!

Volunteer registration (done)

• Volunteers can create an account
• Volunteers can bring Meetup.com attendance history over
• Organizers can create and edit events
• Events list their organizers
• Volunteers can RSVP to events
  • When volunteers RSVP, they are prompted to say whether they want to teach/TA and other details.
• Organizers can email volunteers
• Organizers can check in volunteers when they arrive

Student registration (done)

• Students can create an account
• Students can bring Meetup.com attendance history over
• Students can RSVP to workshops
  • Every event has "RSVP as a volunteer" and "RSVP as a student" with coordinating details
  • Students can join waitlist if necessary
• Organizers can email students