Ruby DCamp Schedule

There are only so many details that we can provide you about Ruby DCamp. Why? Because most of the details are provided by you.

That said, here is a skeleton of the weekend.

Here's an approximation of Saturday's schedule. Note that this isn't final but close:

8:00am - 9:00am:        Breakfast

9:00am - 10:00am        Planning Session

10:00am - 11:00am       Scheduling Session (attended by those people who suggested sessions
                        that made the cut during the Planning Session)
                        
10:00am - 11:00am       Plenary Discussion: What's Broken

11:00am - 5:30pm        Sessions!

12:00pm - 1:30pm        Working Lunch

3:00pm - 4:00pm         Afternoon Coffee Break

The Saturday morning planning session will be led by Lucas Cioffi, a trained and professional facilitator. During the planning session, Lucas will solicit ideas for sessions from the gathered attendees. After the topics are suggested, Lucas will call for a vote. Based on the number of votes by session, we will decide which sessions will occur that day. This will also take into account the number of sessions that we can hold in parallel within the space and the length of each suggested session.

Immediately following the planning session, Lucas will lead a scheduling session, attended by those individuals who suggested sessions that made the vote cut. These individuals will act as representatives for their respective suggested session, discussing where best to fit their session in the schedule (if at all) for that day. At the end of the scheduling session, the final schedule for the day will be published (likely on the wiki and on the spot in paper form) for attendees.

For those of us not involved in the scheduling session, David James will lead us in a plenary discussion called "What's Broken". David is an experienced Rubyist but also a community activist and talented facilitator in his own right. The purpose of "What's Broken" is to identify those broken windows in the Ruby ecosystem. We expect that this may begin as a list of individualized nitpicks. That's a fine place to start. However, we seek to abstract these beginnings to find the larger problem. This gives us goals to consider over the remainder of Ruby DCamp.

Following the conclusion of the scheduling session and "What's Broken", it's off to the sessions!

Sunday's schedule is a little less certain. However, it is our intent for Sunday to be run similarly to Saturday except to build upon it. While parts of Saturday may be spent identifying "broken windows" and perhaps discussing how to approach boarding them up or perhaps replacing them, it is our hope that Sunday will, among the discussions and presentations, also bear the fruit of new open source Ruby projects, developed by attendees, to begin the actual window repair or replacement work.

Content copyright © Triple Dog Dare, LLC 2008 Site design and logo copyright © 2008