Summary
The Cleveland Code Co-op (C³) is a new group that invites people in Northeast Ohio to meet in Cleveland to directly collaborate on Free Software project development.
Next meeting...
Date: Sunday, February 22, 2009 at 1:00pm
Location: EECS Student Lounge, Glennan Building, Case Western Reserve University
The fifth C³ meeting is scheduled for February 22, 2009 starting at 1:00pm, where we will work on various projects. Projects will be decided on during the meeting, but will most likely include redit, 80sheep, and a Python tutorial for beginners. Please join us! Note that some of our collaboration takes place in IRC. We hang out in #C3 on irc.freenode.net; even if you can't make it to a C³ meeting in person, you are welcome to hack with us remotely.
Details
The mission statement for C³ is to strengthen the Free Software community in the area by encouraging us to code together, notably including work done on projects beyond our current experience. At each session, we will work on a project of interest to one of the members. We may end up working on a number of very different projects, with a number of different programming languages.
The current plan is to have these sessions be very casual, and to allow structure to form during each session as appropriate. In this spirit of informality, we don't intend for any membership requirements or the like. Those who are interested in a given focal project meet, code, push the code back to the community, and discuss successes and failures here, on our blogs, over beer, or whereever.
This concept sounds very similar to a Coding Dojo, and in fact it could be quite fun to have some C³ sessions focus more on programming challenges, perhaps to teach certain languages or skills for future projects.
How do we choose projects?
Anyone can suggest any FLOSS project to work on at a future C³ session. Please post suggestions to the nooss-talk mailing list or on the project proposals page, or both! Ideally, the proponent of the project would have some experience contributing to that project or would have researched how to contribute to the project, and would have a set of concrete contributions in mind. At a given C³ session, the participants decide on the focal project for the next C³ session. The proponent of the project would then serve as the guide while working on that project at that session.
How often do we hold sessions?
Once a month, and possibly more or less frequently depending on demand.
Where do we meet?
Meeting places have included the following locations:
BitBacker, Inc.
- Lakewood Public Library
Case Western Reserve University (next meeting)
TODO
Address the following questions on this page:
- What should a project proponent do to prepare for a session?
- What do I need to bring to sessions?
- How can I prepare for sessions? How prepared do I need to be for sessions?
- What happens during a session?
It will be easier to answer these questions once we actually see how things go the first few times.