Talk:Grassroots bootcamp: Difference between revisions

From OLPC
Jump to navigation Jump to search
m (How can this be generalized?)
 
(7 intermediate revisions by 5 users not shown)
Line 12: Line 12:


* Mike Lee who is running the OLPC Learning Club DC
* Mike Lee who is running the OLPC Learning Club DC
Christoph, thank you for suggesting me. I won't be able to get away from work and family obligations for the Boston events, but I may be able to make it to NYC. --[[User:Mikelee|Mike Lee]] 20:20, 2 June 2008 (EDT)

* someone from the Dallas FortWorth Area XO users group to come to Boston.
* someone from the Dallas FortWorth Area XO users group to come to Boston.
* Maybe also one of the Nortel folks?
* Maybe also one of the Nortel folks?
Line 19: Line 21:
* someone from [[OLPC Chicago]] - Sheila Miguez, someone from [[MVCC]] (Larry, Steve) or [[IMSA]] (Scott, Kevin, Jason, April-Hope)?
* someone from [[OLPC Chicago]] - Sheila Miguez, someone from [[MVCC]] (Larry, Steve) or [[IMSA]] (Scott, Kevin, Jason, April-Hope)?
* maybe Ben Racher (the guy who wants to start OLPC Tennessee)
* maybe Ben Racher (the guy who wants to start OLPC Tennessee)
=Grassroots activists from Peru and Uruguay=

* Peru
** IEEE Student Chapter
** Free Culture Peru
** Peruvian Association of Free Software

* Uruguay


== Ideas for June 2008 ==
== Ideas for June 2008 ==
Line 39: Line 49:
** People in the contributors program / with XOs
** People in the contributors program / with XOs
** People in the community-group program
** People in the community-group program

=== Proposed schedule ===

Example sessions/talks/presentations/discussions/tutorials listed below.

Everyone should come Monday through Thursday. People not involved in the weekend test jam, and interested in grassroots org more than jam prep, can leave then. Everyone else should stay through the weekend and come to NYC Friday night for the test jam.

; Cost : roughly $100/person for the week -- reimbursed for core team members & session leads
* '''June 2''' - application review for core team, scholarship decisions
* '''June 7-8 (Sat-Sun) - Open space''' : ''see http://en.wikipedia.org/wiki/Open_Space_Technology for how this will run''
* '''June 9 - Grassroots day'''
** How to start a grassroots group
** Survey/directory of existing grassroots groups
** How to run a local jam (list of examples)
*** Teasers for ''Jam prep day'' -- '''select ~3-person core team''', assign tasks, send out save-the-date
** Local organization : communication, meetups, events, partnerships
*** Teasers for ''laptop day''. '''select ~4 session leads''' and notetakers, assign prepwork
* '''June 10 - Education day'''
** Roleplay being kids in an XO pilot, like they did in Nepal
** Presentation on current deployments, what they're doing in classrooms
** Constructionism 101
** How to start a pilot
* '''June 11 - Infrastructure day'''
** Grassroots groups support program / developers program / community program from OLPC: what's needed? Let's make it.
** Newsletter/communications (Seth)
** Set up your group's webpage/wiki/mailing list/RT/trac/etc time
** Practice setting pu the above for the test Jam
** Joining global efforts : support-gang, open working groups
* '''June 12 - Laptop day'''
** How to disassemble/repair an XO + how to run a repair center (X1 & Adam?)
** Running a content project (X2 & SJ)
** Running a translation/il8n project (X3 & SJ)
** Running an Activity-making project (X4 & CJB?)
** Getting involved in core development (X5 & mstone?)
* '''June 13 - Jam prep day'''
** Review of how to run a jam
** Presentation/timeline from core team (selected on Grassroots day)
* '''June 14-15 (Sat-Sun) - Final exam: Run a Jam in NYC'''

There will be sessions for hacking (and learning how to hack) on different areas of the XO's stack and supporting software/infrastructure, discussions of our satellite communities around volunteering, learning, and sugar -- globally and in countries, and much more. Stay tuned.


== next steps ==
== next steps ==
Line 98: Line 66:
** See what's needed, below
** See what's needed, below


== "See my Wares" - design for possible poster ==
== Jam ==

Hi Mel, it seems to me that the top svg image at [[User:HoboPrimate/socon]] would be a great fit for a poster for this camp.[[User:HoboPrimate|HoboPrimate]] 18:12, 14 May 2008 (EDT)


== Some quick todos ==
''for current and future bootcamps''

: ^ define where bootcamps and non-olpc grassroots jams fit in the scheme of things; how to organize similar events elsewhere; what sorts of groups to call on and engage
: ^= pick out a dozen in each of boston and nyc and contact them directly


: x pick out a score of community members who have been active and awesome in organizing themselves and those around them; encourage them and ask them for their input and brainstorming, find out what they would like to teach or learn at such an event, whether or not they can come; find out where there is interest in running a followup
We're running a Jam in NYC for the "final exam" of the bootcamp. June 14-15 are the dates.
: x+ define times to invite others to the bootcamp on appropriate days, make sure they are free (rabi, teleconferencers; scott, francesca; tyler, &c; adam, richard; chuck)
: x@ are there cool local people/speakers we'd like to have drop in to enrich the mood? timing can be flexible, but the earlier poked the better.
: x_ similarly, could we use 'deployment demos' from people who have built grassroots or other orgs, similar to the way we had 'tech/XO demos' for the not-so-techy guests at the country workshop?


: _ define core projects -- organized subsets of activities, ideas from SoC and SoCon projects that are only being partly pursued or claimed, wiki organization and community building ideas, previously suggested projects in each of the core days/areas -- that people could take and work on productively for 2 days.
=== What we need from a host location ===
: _x Imagine that pairs of attendees break off and tackle one of these to mould it into manageable organized pieces.


: * Prepare topics and sessions : turn each of the following into material for a potential 90m ad-hoc hands-on workshop:
* space, chairs and tables (our crew can come on Friday afternoon to set up and so forth) - access to a microphone, projectors/large-screen monitor, etc. would help, but we can improvise equipment
: *= repair guides and manuals
* wireless internet access for attendees at the location
: *= small-scale trial guidelines and proposals
* a budget for supplies, t-shirt printing, and food (say $20/person and you can set how many people you'd like to have - 100?)
: *= large-scale deployment guide review
* permission to use your logo (if you want it on the publicity)
: *= activity review
* permission to bug your developers, if you want your projects worked on - we can send somebody in NYC for a day or two this month to spend an hour or two with the team for each project you'd like people to work on
: *= testing guidelines and process
* access to development resources (your server/bug-tracking tools/repositories if you want people to contribute directly to those resources, or a request to set something like that up for your project on your servers, or a request to set something like that up for your project on our servers)
: *= trac tagging, modules, and use
: *= rt volunteer queues and local volunteer mailing lists (exs: uru, peru)
: *= pootle and l10n of {python, documents}
: *_ do we need laptops for people? maps? anything else?


: + production : define swag and gear to prepare for the event / line up producers / schedule making it and get it made
=== What we can provide ===
: ++ timing : find someone to organize open space over the course of the week
: +x people : find someone to take charge of guiding the NY Jam organizers over the course of the week, in parallel with other interns/attendees; someone else to look after the list of guests, making sure they have travel, lodging, and finances all worked out... help get a stack of T passes and organize couch space
: +_ recording and A/V : find someone to handle recording infrastructure for the core days of the event / transcoding & transcribing


: @ review : organize times for final reminders, invitations, schedule printing
We can do the rest.
: @_ set up time and space for coordination, laying out materials, reviewing progress each day. organize wiki pages, flickr feeds, blogs and other channels for sharing the progress of the event as it takes shape
: @@ schedule time for capturing and disseminating thoughts afterwards


== How can this be generalized? ==
* publicity
* attendee recruitment
* registration
* designing and printing t-shirts
* running the space during the weekend itself
*making sure code repositories and tickets and etc. are hosted and ready to go
* setup and cleanup
* talking with your developers to get their projects ready for jammin'
* can talk about additional things as needed


As we go along, I'd like to try to generalize resources for the bootcamp so that others can run their own grassroots bootcamps elsewhere afterwards to train grassroots group organizers and community facilitators. Some questions.
=== Context ===


To participants who at 1cc during the event:
The context is that we're having an OLPC grassroots bootcamp in Boston from June 9-13, and want to have the attendees run a Jam as their "final exam" - and we'd love to do it for you folks (wanted to talk to SJ about that last sentence clause, which is why I said I'd email you about this later - this is that "later" email.)


* What are your most/least favorite things about the bootcamp so far?
I'd propose a focus on development/deployment of projects from the host organzation that involve software (or hardware) that could work on/with the XO, or projects/deployment that could involve the use of XOs.
* What should we do/not-do in the future? (Both for the remainder of this week and for future bootcamps.)
* Can you think of a better way to record/capture the experience?
* How can we best enable you to run a similar event when you get home?


To remote participants:
== Prerequisites ==


* How can we provide you with more opportunities to join into and interact with the ongoing bootcamp? (We are currently live-transcribing in #olpc-groups.)
'''This is a draft list of prereqs - you can start doing them, but know that it's not final at all!'''
* What about the current notes is good? Helpful? Incoherent? What gaps have we left in our notes and transcripts that need to be filled in with context for you to be able to understand what was going on?
* What resources do you need to be able to run a bootcamp of your own, remotely?


For everyone:
(Need to provide useful links to help people complete all these prerequisites)


* What questions have I not asked in this section that I really should ask?
Link to the following pages in a "Grassroots bootcamp exercises" portion of your wiki page.


[[User:Mchua|Mchua]] 23:50, 9 June 2008 (EDT)
* Create and release an .xo Activity bundle with a wikipage - with screenshots - documenting its installation and usage (programming, Activity-making, wiki usage)
* Translate at least 40 terms in pootle. If you don't know a foreign language, find a friend who does and sit down with them; they provide the translations, you put them in. (pootle)
* Find at least 2 bugs, create Trac tickets for them, and cc yourself on the tickets. (bugtracking, testing)
* Resolve 10 RT tickets (deletions of spam don't count). List the ticket numbers resolved and your username. If you don't have RT access, ask Adam. (RT, support)
* Using as few of your own words as possible (in other words, use phrases from other sources and cite them), write a 500-word minimum essay on how OLPC (you may define this term any way you want) does and does not exemplify the Constructionist theory of learning.

Latest revision as of 03:50, 10 June 2008

I need help in order to attend

Post what you need here and some info about your situation, and we'll start a conversation with you about what resources we can find to help.

  • I need a place to crash from Friday evening (June 6) to at least Sunday (June 8) or possibly longer depending on whether I can get a day off work. ChristophD 18:23, 6 May 2008 (EDT)
Christoph, if my housemates say it's okay, we may have a futon in the living room you can crash at. Mchua 21:56, 6 May 2008 (EDT)
Thanks, that would be great! A futon, free wifi and the daily shower is all I really need anyway... ChristophD 23:43, 6 May 2008 (EDT)

People who should be invited

A suggestion list - add your thoughts here. Being on this list doesn't mean they will come to the event - we're not sure how much space we have yet... (Initial list by Christoph Derndorfer)

  • Mike Lee who is running the OLPC Learning Club DC

Christoph, thank you for suggesting me. I won't be able to get away from work and family obligations for the Boston events, but I may be able to make it to NYC. --Mike Lee 20:20, 2 June 2008 (EDT)

  • someone from the Dallas FortWorth Area XO users group to come to Boston.
  • Maybe also one of the Nortel folks?
  • Greg DeKonigsberg
  • Benjamin Mako Hill
  • support-gang members
  • someone from OLPC Chicago - Sheila Miguez, someone from MVCC (Larry, Steve) or IMSA (Scott, Kevin, Jason, April-Hope)?
  • maybe Ben Racher (the guy who wants to start OLPC Tennessee)
=Grassroots activists from Peru and Uruguay=
  • Peru
    • IEEE Student Chapter
    • Free Culture Peru
    • Peruvian Association of Free Software
  • Uruguay

Ideas for June 2008

Have a relatively open and potentially larger session (open space session) on the preceding Saturday and/or Sunday to gather feedback from as many people as possible and then use the more private meeting from June 9 to 13 to draw upon that input in deciding on how to proceed with the community / grassroots / volunteer efforts.

To invite

People who should be on the community@ mailing list.

  • Existing groups
    • Team: contributors
    • Support-gang members
  • People who actively want to come / have been suggested to invite individually
  • Contributors
    • People in the contributors program / with XOs
    • People in the community-group program

next steps

  • Inviting people
    • We want 20-40. Can we make a list of people to invite?
    • Prerequisites list - see below
  • Open space weekend
    • The site of Community Jam Boston was glorious... can someone from MIT book the space for us?
    • Need to find someone to run this, preferably someone who's facilitated open space before.
  • Supplies
    • Tshirts?
    • Food?
    • Markers, giant post-it notes, nametags for the first day
    • Loaner XOs - Jam kit should be okay
  • Jam
    • See what's needed, below

"See my Wares" - design for possible poster

Hi Mel, it seems to me that the top svg image at User:HoboPrimate/socon would be a great fit for a poster for this camp.HoboPrimate 18:12, 14 May 2008 (EDT)


Some quick todos

for current and future bootcamps

^ define where bootcamps and non-olpc grassroots jams fit in the scheme of things; how to organize similar events elsewhere; what sorts of groups to call on and engage
^= pick out a dozen in each of boston and nyc and contact them directly
x pick out a score of community members who have been active and awesome in organizing themselves and those around them; encourage them and ask them for their input and brainstorming, find out what they would like to teach or learn at such an event, whether or not they can come; find out where there is interest in running a followup
x+ define times to invite others to the bootcamp on appropriate days, make sure they are free (rabi, teleconferencers; scott, francesca; tyler, &c; adam, richard; chuck)
x@ are there cool local people/speakers we'd like to have drop in to enrich the mood? timing can be flexible, but the earlier poked the better.
x_ similarly, could we use 'deployment demos' from people who have built grassroots or other orgs, similar to the way we had 'tech/XO demos' for the not-so-techy guests at the country workshop?
_ define core projects -- organized subsets of activities, ideas from SoC and SoCon projects that are only being partly pursued or claimed, wiki organization and community building ideas, previously suggested projects in each of the core days/areas -- that people could take and work on productively for 2 days.
_x Imagine that pairs of attendees break off and tackle one of these to mould it into manageable organized pieces.
* Prepare topics and sessions : turn each of the following into material for a potential 90m ad-hoc hands-on workshop:
*= repair guides and manuals
*= small-scale trial guidelines and proposals
*= large-scale deployment guide review
*= activity review
*= testing guidelines and process
*= trac tagging, modules, and use
*= rt volunteer queues and local volunteer mailing lists (exs: uru, peru)
*= pootle and l10n of {python, documents}
*_ do we need laptops for people? maps? anything else?
+ production : define swag and gear to prepare for the event / line up producers / schedule making it and get it made
++ timing : find someone to organize open space over the course of the week
+x people : find someone to take charge of guiding the NY Jam organizers over the course of the week, in parallel with other interns/attendees; someone else to look after the list of guests, making sure they have travel, lodging, and finances all worked out... help get a stack of T passes and organize couch space
+_ recording and A/V : find someone to handle recording infrastructure for the core days of the event / transcoding & transcribing
@ review : organize times for final reminders, invitations, schedule printing
@_ set up time and space for coordination, laying out materials, reviewing progress each day. organize wiki pages, flickr feeds, blogs and other channels for sharing the progress of the event as it takes shape
@@ schedule time for capturing and disseminating thoughts afterwards

How can this be generalized?

As we go along, I'd like to try to generalize resources for the bootcamp so that others can run their own grassroots bootcamps elsewhere afterwards to train grassroots group organizers and community facilitators. Some questions.

To participants who at 1cc during the event:

  • What are your most/least favorite things about the bootcamp so far?
  • What should we do/not-do in the future? (Both for the remainder of this week and for future bootcamps.)
  • Can you think of a better way to record/capture the experience?
  • How can we best enable you to run a similar event when you get home?

To remote participants:

  • How can we provide you with more opportunities to join into and interact with the ongoing bootcamp? (We are currently live-transcribing in #olpc-groups.)
  • What about the current notes is good? Helpful? Incoherent? What gaps have we left in our notes and transcripts that need to be filled in with context for you to be able to understand what was going on?
  • What resources do you need to be able to run a bootcamp of your own, remotely?

For everyone:

  • What questions have I not asked in this section that I really should ask?

Mchua 23:50, 9 June 2008 (EDT)

Retrieved from "http://wiki.laptop.org/mediawiki/index.php?title=Talk:Grassroots_bootcamp&oldid=137067"