DIP 1018--The Copy Constructor--Formal Review

Manu turkeyman at gmail.com
Tue Feb 26 02:26:21 UTC 2019


On Mon, Feb 25, 2019 at 12:20 PM Andrei Alexandrescu via
Digitalmars-d-announce <digitalmars-d-announce at puremagic.com> wrote:
>
> On 2/25/19 2:41 PM, bachmeier wrote:
> > On Monday, 25 February 2019 at 19:24:55 UTC, Mike Parker wrote:
> >
> >> From the process document:
> >>
> >> “the DIP Manager or the Language Maintainers may allow for exceptions
> >> which waive requirements or responsibilities at their discretion.”
> >>
> >> If you were to write a DIP for a feature they think important enough,
> >> it could be fast tracked, too.
> >
> > I hate to be so negative, but when I see D's corporate management
> > structure, the lack of community contribution is obvious. It doesn't
> > exactly motivate contributions. This is no way to run an open source
> > project. I understand that it works well for Facebook because everyone
> > on the team is paid six figures, and they can be replaced in two hours,
> > but an open source project is not Facebook.
> >
> > I know the whole argument about why it is that way. That doesn't mean
> > it's going to work.
>
> What do you recommend? Should we carry a final review here?

In my case, you could have produced useful and not-completely-wrong
rejection text with the rejection, and then not insulted me a few
times before eventually producing some actionable feedback.
I mean, its in your interest to foster contribution, not repel it.



More information about the Digitalmars-d-announce mailing list