[Foundation] Last Call standards
stpeter at jabber.org
Mon Dec 16 21:06:06 CST 2002
I like this best of all (so far).
Jabber Software Foundation
On Sat, 14 Dec 2002, Peter G. Millard wrote:
> Justin -
> Why should the council "sponsor" be responsible for "marshalling" support
> for a JEP they didn't author?? The idea of a sponsor was for that person to
> act as a 'conduit' for council <-> members communication, and to marshall
> support and gather concerns & issues from the _council_, not the entire JSF
> Believe it or not, the council already does quite a bit of work... I'm not
> sure any of us want to take on this additional role. I do like have the JEP
> Editor be involved via this process though. I'd modify the flow to:
> 1. Author consults w/ JEP editor about going fwd.
> 2. JEP editor says ok & requests sponsor from council via the council
> mailing list.
> 3. Author & Sponsor consult about any initial issues, and (hopefully) decide
> to proceed.
> 4. Author rounds up 5% of JSF members to second the last call.
> ----- Original Message -----
> From: "Justin Kirby" <justin at openaether.org>
> > While all the suggestions are perfectly fine. Personally I would like to
> > see something like this as the method to bring a jep to last call and
> > presentation to the council......
> > 1. Author (or JSF member) consults with jep editor about going forward
> > 2. jep editor says ok
> > 3. jep editor issues request for "sponsor" from council
> > 4. sponsor then rounds up 5% JSF members to second
> Members mailing list
> Members at jabber.org
More information about the Members