-
-
Notifications
You must be signed in to change notification settings - Fork 259
Someday Feature Wishlist
Sarah Allen edited this page Apr 19, 2015
·
6 revisions
- Based on prior attendance / no-show data, Bridge Troll provides an attendance forecast for a given event – what percentage of the volunteers and students who are signed up are likely to actually show up.
- Let me easily see the experience level of my teaching crew -- easy view of *Bridge experience in addition to their one-liner
- Let me easily find experienced teachers in a region (by technology), so I can reach out if I need help
- Clear identification of chapter leaders
- Auto-match people with mentors who reach out as soon as they post their first draft workshop and stay in touch!
- Google calendar connection
- People would take photos at every workshop and there would be a blog post afterwards.
- Bridge Troll would help organizers identify who to specifically ask to blog about the workshop
- Bridge Troll could help collect the tweets / posts about that specific workshop
- Students would be aware of post-workshop resources
- Online / well-known resources
- In-person / less-advertised resources from RailsBridge volunteers
- Teachers would get feedback from students and other volunteers
- Students would track their learning progress between workshops
- App could prompt students to reflect on what they learned, what was hard, etc.
- Students would be able to see a list of the people in their group and be able to get in touch afterwards
- Profiles that focus on community and teaching
- Organizers could see whether people often flake out, but public profiles should just show what they have done
- Organizers to be able to know each other, and be able to easily see a list of organizers and/or volunteers sorted by how active they have been.
- Tell our stories
- finish the workshop-map and make it dynamic, where new workshops automatically show up on the map
- scale dots by # of workshops
- slider/animated timeline to show history
- rollover regions to display blog posts from that region
- finish the workshop-map and make it dynamic, where new workshops automatically show up on the map
- create more small workshop roles (like greeter, volunteer finder, listener, blogger, photographer) and then have peer affirmation to give out badges. Create a leadership track based on the organizer roles and a tech track that includes TA, Teacher, Curriculum improvement, wiki edit, pull request. Resurrect people pattern ideas -- we have a Google docs of these for *Bridge chapters somewhere.
- Support a profile that combines "github resume" of code contributions with other skills demonstrated by volunteer work
- Some kind of mentoring network? learning/accomplishment badges given out by mentors who do code reviews then could also serve as references in a job hunt?
- A job board? the job I want / the person I want to hire
- post-workshop survey
- opt-in anonymized demographics <-- requires some serious thought, but grant applications typically ask about characteristics of who we serve. Of course, we could track education level, work experience and other things, instead of (or in addition to) race & gender...
- Very someday: track people's success over time, understand quantitatively the efficacy of the workshops
- For a given locale, make it easier for meta-organizers to identify students to ask to volunteer or organizer and volunteers to ask to organize.
- Remind everyone (organizers + meta-organizers) to be sending thanks to sponsors and volunteers
- Make it easy to see a list of venues in a region, along with annotations (like: "Jane is the primary point of contact." or "They were very nervous at first about cleanup, but since the volunteers left it spotless, they said we could come back every month if we wanted too. Let's keep up our great reputation." or "I wrote a thank you note to Pat, their COO, and it started a really great conversation about using their volunteer service time for workshops. We should be sure to engage Bob in HR before the next workshop, so he can loop in the engineering managers") As we scale, our word-of-mouth is not as effective as it once was.