Changes between Version 6 and Version 7 of Yapc10Bof

Show
Ignore:
Timestamp:
11/28/09 03:12:49 (5 years ago)
Author:
coke
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Yapc10Bof

    v6 v7  
    7272=== Austin adds: === 
    7373 
    74 Several of these items are redundant, or are aspects of the same underlying need. The "sub tasks" item, along with the "written plan for new milestones" and "request task analysis" are all essentially the same. Patrick pointed out, with support from others including Andrew, that when even a weak, ineffectual roadmap or plan was laid out there were suddenly plenty of people who could help. (Specific reference here to GC and Dtrace in the PVMW.) 
     74Several of these items are redundant, or are aspects of the same underlying need. The "sub tasks" item, along with the "written plan for new milestones" and "request task analysis" are all essentially the same. Patrick pointed out, with support from others including Andrew, that when even a weak, ineffectual roadmap or plan was laid out there were suddenly plenty of people who could help. (Specific reference here to GC and [wiki:Dtrace] in the PVMW.) 
    7575 
    7676Someone else (I think cotto, but not sure) mentioned that Dan Sugalski's posts on the technical details and tradeoffs were enormously valuable/informative, both for "learning to code" and "learning to code Parrot." Thus, the "analyze approach" and "technical descriptions" items. I suggested that the technical description be added to the project manager's checklist, to encourage developers who complete a milestone to provide documentation on what has been delivered.