GEDA developers, A couple of us gEDA developers and FreeDoggers spent a day at the Trinity College firefighting robot contest in Hartford, CT. This was an interesting and fruitful trip since we had the chance to swap a number of ideas and viewpoints about the gEDA Project and the direction it was taking. Amongst the ideas which arose out of that field trip is one which you may find compellling: A coding sprint.
Therefore, I'd like to propose a six hour coding sprint for a Saturday sometime this spring. We would each choose one or two features or bugs we'd like to tackle, sit together, and work on getting those features implemented/bugs squished. Working together, we can quickly exchange ideas and pointers about getting the job done. Here is a preliminary plan: We will hold it in a room at MIT. Ales and I will be present in person, working on our respective tasks. Others are welcome -- and encouraged -- to attend and work on their tasks. Since MIT has internet access, we will also open an IRC channel on SEUL.org so that hackers around the world can participate. We'd schedule it to run from 9 -- 12am EST, and then again from 1 -- 4pm EST (we get a 1 hour lunch break). This allows for a good window of availability for both folks in Europe as well as on the west coast of the US. As far as tasks go, here is a preliminary list: * Discuss how to facilitate hierarchical bus support. Possibly implement something? (This might be involved ...) * Fix gattrib bug in which gattrib soaks up processor cycles executing a NOP loop. (I claim this one -- SDB.) * Gattrib: enable exporting a CSV files. (I claim this one too -- SDB.) * Bugfixes from SF bugtracker (as long as Carlos, Patrick, and Werner don't completely exhaust the list before we hold the sprint!) * Implement arbitrary promotable attributes in gschem/libgeda. * Other items listed at http://geda.seul.org/dokuwiki/doku.php?id=geda:todos Please reply to this e-mail with your favorite feature enhancement/bug fix. Note that the chances of getting your feature implemented will *radically* increase if you show up in person (or on IRC) and work on your feature! I suggest we hold it on a Saturday in May. If you are interested in participating, please let me know which Saturdays you are *not* available. I will announce a day once I get some feedback from developers about their interest and their availability. Looking forward to hearing from you, Stuart
