From: T. B. <tb...@py...> - 2005-01-31 16:50:47
|
Martin Aspeli wrote: > I've been working on the PHC a bit, adding the Reference Manual type and > fixing a bug here and there. I also went through the TODO.txt and tried to > work out what's been done and what hasn't. These are the remaining items. > If someone notices any errors, please update TODO.txt; other than that, > please help out getting the last issues resolved! I'm one of the people from the first Plone Boot Camp that Joel taught here in North Carolina. I asked on our local Python/Zope user group mailing list, and there are a few people interested in sprinting on PHC. One wants to use PHC on his site. A couple of us just want to get more practice with developing and unit testing in Plone. I'm not sure what everyone's availability is yet, but here was my idea. I schedule a one day sprint with at least three or four people in a room here in NC. I think that this time we'll be show up to the sprint with our machines configured and ready to go. (We jumped the configuration hurdles at the sprint on Jan. 8.) Before the sprint, I'd need to talk you all about what PHC is actually supposed to do. I was talking to Martin on #plone last weekend, and there are pieces of PHC where it's not clear what the desired behavior actually is. If we could iron out some of that before the sprint and have someone available during the sprint to make requirement decisions for us, then we could probably make some good progress (adding tests, fixing bugs, etc.). I don't even need an absolute list of things that are broken. If we can just come up with a list of "here's what it should do," then we can test it through the web and add unit tests. If we find something that doesn't work as specified, then we'll try to fix it, too. The group who would be sprinting here has been through the Plone Boot Camp, and they've done a tiny bit of Plone development. I'm sure that we'd still have a lot of questions, but maybe the enthusiasm will make up for the lack of true plone fu. ---Tom |