spec process proposal and tracking list for 0.8 (warning: this is long)
Cassie
So a bunch of new gadgets and opensocial issues have been proposed on
this list and it seems like we need a way to decide on which changes
will make it into the next iteration of the spec. (See list of
current issues at bottom of email - ie read the whole thing :)
First, it seems like we need to set a deadline for proposing new
issues to make it into 0.8 - perhaps something like next Friday?
(April 18)
Second, we then need to come up with corresponding spec changes for
each issue that has been proposed. I've been doing this on a bunch of
threads and will continue to speak up if others don't.
Third, we then need to decide when issues make it or do not make it
into the spec itself. It would be great if we could shoot for a
consensus agreement on each change, perhaps having some minimum number
of people which have to chime in? (Let's call it n people) So, in
order for a change to make it into the next iteration, it will need n
positive agreements and no negative agreements within a certain time
period. (Otherwise this could go on forever and ever...) Perhaps
allowing an additional week after all proposals are in for discussion
- so 3 fridays from now? (April 25)
Note: I realize that achieving consensus might not work in the real
world, but I propose that we give it a shot until we prove that it
won't work :)
Fourth, it seems like we should gather everything up, produce all the
necessary spec changes and send out a link to the whole thing to the
group. That will get a bunch of eyes on all the spec changes at once
which will help make sure everything is cohesive. Then we could
perhaps allow one more week to review all of that - so 4 fridays from
now? (May 2)
Fifth, then, everything should be extremely golden and the spec would
officially be at 0.8. If everything goes well and we feel happy with
how the process went then I suppose we would repeat it for the next
iteration. If we do not like how things went we can of course tweak
everything we do for the next version or scrap this way of making new
specs altogether.
Alright, so if this overall thing sounds good to everybody then we
will need a couple things:
1. Deadline date for a "call for changes". proposal: April 18
2. Deadline date for commenting on an issue. proposal: April 25
3. Minimum number of positive agreements an change must have before it
can go into the spec. proposal: 5
3. Deadline date for reviewing the entire new spec draft: May 2
4. Someone to keep track of all of the threads and encourage or push
issues to resolution. I volunteer myself for this job for 0.8.
If you all think that these proposals are okay, then please +1 this
thread. I'll need 5 people to chime in before we can go on :)
For all of those who want a structured view of the mailing list btw I
have been tracking things (just for personal use) here:
http://spreadsheets.google.com/pub?key=pigtmOB55Aw_YJHz040u0Kg
If I continue being the scribe for 0.8 I will simply use the sheet to
help keep all these crazy threads organized. (Note: I am about 20-30
emails behind on that spreadsheet due to Shindig and OpenSocial
related activities abroad - yea for the hackathon attendees! But I
will update the rest of the issues very shortly.)
Please let me know what you think.
Thanks.
- Cassie
Reinoud Elhorst
Hash: SHA1
+1 chime!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFH/fFaqCQnCrE98GgRAi/JAJ9OzU9e1sBm0AdecJvhx0fprfCjSgCgl7wM
ua8LkJVWmDd+doCN11vGMH0=
=xGJp
-----END PGP SIGNATURE-----
Louis Ryan
Zhen Wang
On Thu, Apr 10, 2008 at 3:31 AM, Cassie <do...@google.com> wrote:
>
Chris Chabot
Lane LiaBraaten (Google)
Ram Ramani
Ram
Kevin Brown
~Kevin
Cassie
Don't forget to chime in on all of the threads. I will continue to
update the spreadsheet (which links to all of the threads) and will
send out reminder and status emails to keep us all on track.
- Cassie