Many thanks to you and the other organizers of this event!
Please forgive me, I'm new to this group, but I'm unsure how this mailing list
([address removed]) relates to the stream of comments posted at  and,
therefore, whether my message proposing a command-line script (appended below)
reached everyone on this list.
On Fri, Jan 25, 2013 at 12:25:59AM -0500, Ryan Day wrote:
> We have a strong showing, several different projects and a few areas of
> focus so there should be something for everybody.
> Scientific Computing:
> Hurricane Sandy
> Game Dev
Has list of candidate projects has already been fixed to the above? Is there a
page where we can or should sign up for a particular project, or will the
groups be sorted out as the first step of tomorrow's meeting? Someone
suggested, for example, that the day might start with lightning talks.
I'm also wondering whether there might be -- given sufficient interest, of
course -- any sessions about command-line scripts. I'm guessing that the areas
of focus listed above involve graphical interfaces and website design, which
are way beyond my simple needs. Specifically, I'm wondering whether I should
prepare a lightning talk on my command-line script -- or not bother because it
does not fit any of these areas of focus?
I would like to propose my own relatively simple command-line script,
The script re-writes and re-sorts folders of plain-text to-do lists according
to rules that you edit as your needs evolve, then urlifies the lists for your
browser. I have run this script, which in its previous Korn shell incarnation
was featured in UnixWorld (1994) and lifehacker.com (2006), for 20 years.
The current Python version is fast and stable, but I would now like to re-write
it, completely from scratch, with unit tests, per-directory configuration files
in YAML, documentation in markdown, and possibly OO design.
I could demo the current script in a lightning talk and present the
requirements as I see them. We could use it as an opportunity to test the
Pythonic ideal of starting a coding project with unit tests and collectively
walk through the paces of documenting even a relatively simple project in a
well-managed Github repository.
Tom Baker <[address removed]>