Hi all,

I'd like to thank everyone who participated in this weeklong debate and
for being patient with my incessant nagging to get this done. :-)

I replied to Sally's hackathon request (CC'd to this list a little while
ago). Hopefully everyone is happy with it.

It's not perfect. Sadly, we didn't end up listing any Python work. But
this has been a good learning experience.

My hope is to attract more developers to this great project. I know
that the chances of a hackathon participant becoming a long term
developer are slim, but nevertheless that's still within the realm of
possibility. The more we put ourselves out there, the better the
chances.

What I learned:

This time around we were passive. We didn't act until the request came
to us. In the future, I hope to actively search for these kinds of
opportunities.

Also, this time we weren't quite ready. Our issue tracker contains
items marked "bite size" that aren't and needs some housecleaning in
general. I like Julian's suggestion of bringing one item to the list
each week and gradually getting it under control (and I'll make sure that
it happens). Also, I'd like to get "bite size" items properly labeled,
so that the next time we need to provide a list of hackathon-ready work
items, we'll be able to do it much more quickly and easily.

But for a first effort, we put something out there, and maybe we'll
get a few of those items worked on. Whatever happens, we're better
off for trying.

Again, thank you to everyone for your input (and your patience!!).
Your efforts are much appreciated.

Nathan

Reply via email to