Niels Reedijk wrote:
Hi gang, Sorry in advance for the staccato message I just created a list of proposals based on the discussion we had recently. Find it at: http://dev.haiku-os.org/wiki/R1/Alpha1Proposals It might not be fully complete. Because alpha 1 is nearing, the goal is: 1. Clear up some general goals 2. Make a selection of software Developers can change the wiki page above: I encourage every developer to have a look at the list and see if there are any proposals you would like to endorse. If you endorse a proposal, you say you very much want this to be in alpha 1 and that you try to make sure that it will be done. This does not mean that you have to do it yourself, of course. Developers can also add their own pet peeves to the list.
Ah! About my pet peeve :)What about a Tester/Feedback Package (like the Welcome Package) that would contain one or more small tools to ease failure and success reporting. At least some standardized way to send your config details and your success at running it in a few clicks (yes i know, you have to at least boot to the desktop but it's better than nothing). It doesn't need to be super precise and shouldn't replace real bug reporting on trac, but at least we'll have a rough idea of how things goes for our users (and how many they are).
Should we push this idea further?
This all looks pretty good and encouraging to me, thanks for your work Niels!My personal hope is that this list is to get everyone in 'release mode' to focus their energy and get things ready. It's our time to shine! So here's what I propose we do: # Freeze the list this Sunday at 13:00 GMT. All proposals that aren't adopted by any developer, are automatically rejected as being required for the release. # Have a week of discussion on the various items. # Have a vote among all developers with subversion access (this might be a long list, currently there are 25 items I think, but that seems the most fair way). Set a deadline on the vote. Of course, this might be overkill, but then again, this might kick everyone into 'release gear'.
What about _you_ as the release coordinator? :-D Regards, Alex