Hi Folks, Open issues in gwt-steering don't seem to get resolved unless either there's a SC meeting, or someone send a poll email asking people for their opinions, which sometimes take too long. I'd like to propose that we make this a more formal process, so we'll get quicker decisions. Here's my thoughts on a process:
1. Initiator sends email to gwt-contrib & gwt-steering to get initial thoughts, asking for responses within a fixed timeframe. For example: "I propose we drop support for IE8 in GWT 3.0, coming around spring 2014". The motivation is to get some conversation going, as well as flushing out some of the questions, for example: does that mean we will continue to update 2.6 for those who need IE8 support', or 'when does IE8 support start disappearing from trunk?'. 2. After the specified time period, if there's enough initial support, the initiator writes up a formal proposal (in Google docs) in a template similar to: 1. Proposal 2. Motivation 3. Schedule 4. Owner(2) 5. Decision date and checkbox for each SC member to signify position on it (yes, no, nuetral) 3. The proposal is discussed in the Google doc (open to comments from everyone, but editable only by the owner). 4. By the decision date, each SC member indicates whether they support the proposal. If a SC meeting is needed, a meeting is held. Note: I'm not saying we do this for every CL or change in GWT - that should be the decision of the committers and reviewers. This is for mainly higher level (perhaps non-technical) decisions. Thoughts? Bhaskar -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
