Wiki - Parrot Implementors BOF
We should have a BOF/dinner at YAPC on Monday night. We'd like to discuss:
* improving our bus number and our milestone efficacy
* L1 and the future
* <add other topics here>
I'm sure there are other topics to discuss as well. Is anyone else
interested?
* Patrick Michaud (Pm)
* chromatic
* Bruce Gray (Util)
* James E Keenan (kid51)
* Christoph Otto (cotto)
Transcription of Parrot BOF Discussion Points
Parrot Implementers BOF
Monday June 22 5:00 pm
What went right in our releases since 1.0?
--on time
--on budget
--hit some milestones
--rotating release managers work
--external languages still work
--development cycle still works
--received publicity
What went wrong with those releases?
--last-minute life interruptions
--missed several milestones
--missing release artifacts
--last-minute HLL testing necessary
--incomplete client-language separation
--low bus number on multiple branches
--vague or missing descriptions of multiple milestones
--milestones removed from roadmap
--poor triage of HLL blockers
--miscommunication with HLL implementors
--infrastructure changes and schedules
make install, lexical support, calling conventions were all identified as critical for HLL (esp Rakudo) at developer summit -- but only lexical support got done
Why?
Not enough tuits/developers for the aggressive plan.
One miss multiplies.
Lack of concrete plans on which "anyone" can work on.
Design stuck in peoples' heads.
What's problematic about recruting, training and retaining in an OS project like Parrot?
Incomplete/ineffective milestone ticket review, leading to no action
#parrotsketch more focused on last-week review than prospective
Missing tactical, useful, timely information
How Do We Fix It?
Big tasks need sub-tasks.
Analyze, appreciate and publicize design tradeoffs.
New milestones need some written plan.
Publicize vision for supported releases.
Technical descriptions of completed milestones.
Document project management requirements.
Review critical tickets/assign volunteers in #parrotsketch.
Request task analysis from critical ticket reporters.
#parrotsketch is too long. Require pre-reporting of reports by 1800 UCT, in standardized format.
version 6 saved on 06/23/09 01:09 AM by James E Keenan (kid51)
Home | Tags | Recent changes | History
Platinum Sponsors
