Hello,


As part of our continued efforts to improve the process, we have added the "preapproved" tag to bugzilla.

An enhancement request that has the "preapproved" tag is considered reviewed and vetted by Walter (and myself on occasion). An implementation of the issue is guaranteed to be approved pending technical review.

This is part of a larger attempt to make it easy for contributors to work on items of maximum impact, while hedging the risk of working on some feature without entering production. One nice perk is that this flow will encourage well-written and well-argued enhancement requests.

We will follow later today with a preapproved enhancement request. (Of course, we will also preapprove enhancements written by others, too.)


Thanks,

Andrei

Andrei Alexandrescu:

> We will follow later today with a preapproved enhancement request. (Of course, we will also preapprove enhancements written by others, too.)

I don't remember of other language communities doing this, but it seems a nice idea :-)

Bye,
bearophile

On 1/9/13, Andrei Alexandrescu <SeeWebsiteForEmail@erdani.org> wrote:
> An enhancement request that has the "preapproved" tag is considered reviewed and vetted by Walter (and myself on occasion).

I would also like the BDFLs to start closing down some enhancements, there's too many opened in bugzilla as is (854) and there are bound to be many worthy of a rejection. Some reasons to reject: existing code would break / a workaround already exists / enhancement too large or abstract and should be a DIP / outright insane request / etc.

On 2013-30-09 04:01, Andrej Mitrovic <andrej.mitrovich@gmail.com> wrote:

>  Some reasons to reject:
>  outright insane request.

RESOLVED: OUTRIGHT INSANE REQUEST
Yup, I likes that.

-- 
Simen

Andrei Alexandrescu, el  8 de January a las 18:09 me escribiste:
> Hello,
> 
> 
> As part of our continued efforts to improve the process, we have added the "preapproved" tag to bugzilla.
> 
> An enhancement request that has the "preapproved" tag is considered reviewed and vetted by Walter (and myself on occasion). An implementation of the issue is guaranteed to be approved pending technical review.
> 
> This is part of a larger attempt to make it easy for contributors to work on items of maximum impact, while hedging the risk of working on some feature without entering production. One nice perk is that this flow will encourage well-written and well-argued enhancement requests.
> 
> We will follow later today with a preapproved enhancement request. (Of course, we will also preapprove enhancements written by others, too.)

Great. I think as a simple improvement to that, people willing to implement the feature seriously, should assign themselves to the issue. This way the "preapprovers" can see if there are any takes for the issue and prioritize giving feedback to issues that are more likely to be implemented by contributors.

-- 
Leandro Lucarella (AKA luca)                     http://llucax.com.ar/
----------------------------------------------------------------------
GPG Key: 5F5A8D05 (F8CD F9A7 BF00 5431 4145  104C 949E BFB6 5F5A 8D05)
----------------------------------------------------------------------
"Somos testigos de Jaimito, venimos a traer la salvación, el mundo va a
desaparecer, somos testigos de Jaimito!". Nos enyoguizamos... Así que
"somos testigos"? Te dejo el culo hecho un vino, y la conch'itumá, y la
conch'itumá!
	-- Sidharta Kiwi

bearophile, el  9 de January a las 04:05 me escribiste:
> Andrei Alexandrescu:
> 
> >We will follow later today with a preapproved enhancement request. (Of course, we will also preapprove enhancements written by others, too.)
> 
> I don't remember of other language communities doing this, but it seems a nice idea :-)

There are, usually they are more formal, but maybe we can't afford that yet.

I guess you already know Python PEPs for example: http://www.python.org/dev/peps/pep-0001/

We had our run with DIPs, but I think they were unsuccessful.

And given how D community works, seems to make more sense to put "Improvement Proposals" in bugzilla directly. The only drawback I see on this is maybe big improvement proposals get less visibility and are not easily differentiable from minor enhancements or even bugs.

-- 
Leandro Lucarella (AKA luca)                     http://llucax.com.ar/
----------------------------------------------------------------------
GPG Key: 5F5A8D05 (F8CD F9A7 BF00 5431 4145  104C 949E BFB6 5F5A 8D05)
----------------------------------------------------------------------
"Lidiar" no es lo mismo que "holguear"; ya que "lidiar" es relativo a
"lidia" y "holguear" es relativo a "olga".
	-- Ricardo Vaporeso

Leandro Lucarella:

> And given how D community works, seems to make more sense to put
> "Improvement Proposals" in bugzilla directly. The only drawback I see on
> this is maybe big improvement proposals get less visibility and are not
> easily differentiable from minor enhancements or even bugs.

Let's see one of more of such pre-approved ER, and we'll see how much good this idea is in practice.

Regarding visibility, it's easy to write a page in the site that links to each one of them.

Bye,
bearophile

On 13-01-08 9:09 PM, Andrei Alexandrescu wrote:

> As part of our continued efforts to improve the process, we have added
> the "preapproved" tag to bugzilla.
>
> An enhancement request that has the "preapproved" tag is considered
> reviewed and vetted by Walter (and myself on occasion). An
> implementation of the issue is guaranteed to be approved pending
> technical review.
>
> This is part of a larger attempt to make it easy for contributors to
> work on items of maximum impact, while hedging the risk of working on
> some feature without entering production. One nice perk is that this
> flow will encourage well-written and well-argued enhancement requests.
>
> We will follow later today with a preapproved enhancement request. (Of
> course, we will also preapprove enhancements written by others, too.)
>
>

Would it also make sense to have a separate mailing list to post and discuss D development process announcements such as this important one?  That would make it easier for some trying to learn the development process of the group.

Something like D.devprocess, D.processes or D.development.


-- 
/Pierre Rouleau

On 1/9/13 9:15 PM, Pierre Rouleau wrote:
> On 13-01-08 9:09 PM, Andrei Alexandrescu wrote:
>
>> As part of our continued efforts to improve the process, we have added
>> the "preapproved" tag to bugzilla.
>>
>> An enhancement request that has the "preapproved" tag is considered
>> reviewed and vetted by Walter (and myself on occasion). An
>> implementation of the issue is guaranteed to be approved pending
>> technical review.
>>
>> This is part of a larger attempt to make it easy for contributors to
>> work on items of maximum impact, while hedging the risk of working on
>> some feature without entering production. One nice perk is that this
>> flow will encourage well-written and well-argued enhancement requests.
>>
>> We will follow later today with a preapproved enhancement request. (Of
>> course, we will also preapprove enhancements written by others, too.)
>>
>>
>
> Would it also make sense to have a separate mailing list to post and
> discuss D development process announcements such as this important one?
> That would make it easier for some trying to learn the development
> process of the group.
>
> Something like D.devprocess, D.processes or D.development.

I think we're in good shape. D.announce has low enough traffic as is.

Andrei

On 13-01-10 12:15 AM, Pierre Rouleau wrote:

>   That would make it easier for some trying to learn the development
> process of the group.

s/some/someone/


-- 
/Pierre Rouleau