ToDo list
Mark Ramm
It would be fantastic if we could do a bit of work to lower the
barrier to entry for new developers -- including Alberto who recently
expressed a bit of trepidation on working on the branch without a few
more tests.
I thought I might have time to work on tests tonight, but pretty much
my whole evening got taken up with writing a blog post about the
sprint, and working on tomorrow's announcement email.
I'll try to at least create a few docstrings tonight, and read up on
paste.fixture.
But I would say that working on tests and developer docs is the single
most important thing we can do at this point. We need the results of
the pygears sprint to attract additoinal development help from the
rest of the TG community. And tests, docstrings, and good code
comments are a critical piece of making that happen.
--
Mark Ramm-Christensen
email: mark at compoundthinking dot com
blog: www.compoundthinking.com/blog
Mike Schinkel
> It would be fantastic if we could do a bit of work to lower
> the barrier to entry for new developers -- including Alberto
> who recently expressed a bit of trepidation on working on the
> branch without a few more tests.
Still being very new to TG, I could be a good test case. I'd promise to get
stuck on lots of unclear things and ask lots of stupid questions... '-)
--
-Mike Schinkel
http://www.mikeschinkel.com/blogs/
http://www.welldesignedurls.org
http://atlanta-web.org - http://t.oolicio.us
Barry Hawkins
any blurb about what we'd need to do in order to work on this without
hosing our current get-work-done Python/TG/Pylons installations? I am
more familiar with TG than Pylons, but have been reading up to try and
understand where Pylons is coming from.
Regards,
Barry
--
Barry Hawkins
All Things Computed
site: http://www.alltc.com
weblog: http://www.yepthatsme.com
Registered Linux User #368650
