Hyrum, I know that you (and Greg) have been asked about this before, but I've never quite seen a response that really packages stuff up for the newbie. And yes, for WC-NG purposes, I'm a newbie. That said, I'm sure I'm not the only one. And I'm sure I'm not alone in wanting to jump in and help with the WC-NG work but not knowing where to start poking. So...
What identifiable tasks remain to get WC-NG into a state of 1.7-readiness? Are issues filed to track those things so that casual observers can a) be aware of them and b) feel empowered to attack them without stepping on somebody's toes? To what degree is notes/wc-ng/* up to date with the current thinking? To what degree is notes/wc-ng/* considered complete? To what degree is the knowledge in notes/wc-ng/* beneficial for the task at hand? Is there a whole different class of knowledge that's needed either in addition to or instead of those design notes in order to adequately address the immediate WC-NG incompleteness? I guess another form of these questions could be: If you were in charge of bossing Subversion devs around, how would you divvy up what needs to be done on WC-NG and with what would you equip your charges in order to get the job done? -- C. Michael Pilato <cmpil...@collab.net> CollabNet <> www.collab.net <> Distributed Development On Demand
signature.asc
Description: OpenPGP digital signature
