I sort of like this better. The problem we have today was identified by Dave Cridland: it is already so hard to charter a work group, people give up and leave. You need an active mail list, an active BOF, and active BOF, run through the Dave Crocker and jck filter, and finally get chartered. Easily a year if not more. Even with that heavyweight process, we manage to take on work that probably belongs elsewhere. I like the I-D approach. Provide the resources to get a proto WG going, let it run for six months, and see if it is getting any traction. I think that will let people relax that don’t want to see the IETF take on work that no one is interested in - if no one is really interested in the work, it will die in 6 months. Conversely, if something that an AD or two thought would not be interesting takes off in that initial six months, I’m sure they will claim parentage :-) Other thoughts? > On Jul 22, 2015, at 11:06 AM, Ofer Inbar <cos@xxxxxxxxx> wrote: > > What about a sort of "working group handfasting"? > Much lower bar for chartering, but the initial goal of the group is > very short term (like 6 months) and mainly designed to see if the > group seems likely to be productive. With the expectation that, > by default, such a group would end after the initial period, unless > the group's members actively think it should continue; it would > take positive action to request a recharter at this point, with a > longer term mission, but it would be expected that such a recharter > be approved if the consensus of the group is behind it. > > That seems similar to the idea of a higher bar for chartering, because > it makes the bar be "actually try having a working group for a number > of months and see what comes of it" - much like Dave's suggestion. > But, it also makes it much clearer and more transparent what is going > on, easier for new people to see it, and gives some support and > guidance to reaching that higher bar, making it more likely that > worthwhile efforts will clear the bar. > -- Cos >
Attachment:
signature.asc
Description: Message signed with OpenPGP using GPGMail