Summary/Minutes for Wednesday's FESCo meeting (2012-12-05)

Josh Boyer jwboyer at gmail.com
Thu Dec 6 16:20:22 UTC 2012


On Thu, Dec 6, 2012 at 11:02 AM, Tomas Mraz <tmraz at redhat.com> wrote:
> On Thu, 2012-12-06 at 09:07 -0500, Josh Boyer wrote:
>> On Thu, Dec 6, 2012 at 5:42 AM, Vít Ondruch <vondruch at redhat.com> wrote:
>> >> * 896 - Refine Feature Process  (notting, 18:07:50)
>> >>    * AGREED: Feature process modification: features are announced on
>> >>      devel-announce by feature wrangler once wrangler verifies feature
>> >>      page content (+:9, -:0)  (notting, 18:34:51)
>> >
>> >
>> > Well done! Thank you.
>> >
>> >
>> >>    * AGREED: FESCo votes on new features no sooner than a week after the
>> >>      devel-announce announcement. (+:8, -:0, 0:0)  (notting, 18:46:03)
>> >
>> >
>> > Now the rest of the change: "The feature is automatically accepted (no FESCo
>> > involved at all) after one week if there is no negative feedback on ML.
>> > Otherwise it must be evaluated by FESCo."
>>
>> At the least, that should be rephrased.  Negative feedback isn't the
>> thing you really want to trigger off of.  It's more "if there is no
>> significant discussion" or something similar.  You can have something
>> with a lot of positive discussion that is still a large and invasive
>> Feature that should be reviewed by FESCo.
>
> Let's rephrase it:
> The feature is automatically accepted (no FESCo involved at all) after
> one week if the submitter of feature or anybody else explicitly does not
> ask for FESCo review and approval.

Sure, better at least from a starting point.

>> Also, there was dissent already in the "auto-approving" of leaf-features
>> during the meeting discussion so I am not sure that auto-accepting of
>> Features in general given a lack of response is ever going to actually
>> happen.  I personally wouldn't vote for it.
>
> I still hope that some kind of auto-accepting of features will be
> approved by FESCo. I personally would vote for it if it is reasonably
> worded.

As I said in the meeting yesterday, I think the definition of a Feature
needs to be cleared up before we can really tackle this one.  Feature to
me is something important enough that it shouldn't be auto-accepted.  If
there is some other class of thing people submit that isn't a Feature,
then I might be for auto-accepting of those.

josh


More information about the devel mailing list