[Issue 14381] It is too difficult to contribute to the auto-tester

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=14381

--- Comment #4 from Brad Roberts <braddr at puremagic.com> ---
(In reply to Andrei Alexandrescu from comment #2)
> (In reply to Brad Roberts from comment #1)
> > My major comment is to stop thinking of the auto-tester as the D
> > auto-tester.  Think of it as a tool that the D community uses that is owned
> > and operated by me.  I agree that it's currently and for the past year
> > poorly owned.  But it's not specific to D and I don't intend to add
> > capabilities to it that are specific to D or the D development process.
> > 
> > Some of the feature work you suggest below can fit within either the build
> > or the test target without requiring changes to the auto-tester.
> > 
> > Some of it is general enough to work for more than D.
> 
> So what is the action item here, Brad? Do you plan to open things up

Depends on what you mean by open things up?  I've always accepted pull
requests, though most have been reworked before being merged as they're
typically not workable as is.

Do I plan on allowing anyone other than me to have merge / pull permissions? 
Not at this time.

Do I plan on allowing anyone other than me to have login access to the client
build machines?  Not blanketly no.  If there's some extraordinary need for
debugging purposes, maybe.  That said, there's almost always going to be a
better way to do that.. like a VM for instance.

> or do we need to duplicate the effort?

I hope not, it'd be a pretty large duplication of effort.

> I said this and I maintain: we need to move away the setup in which only one
> person is the bottleneck for everything about D vitals.

That's a huge exaggeration over the current situation.  Me for the auto-tester
is far from a bottleneck for everything about D vitals.  I'm a bottleneck for
one key tool, certainly.

> Please let us know if and when you are willing to open the system. Thanks.

I'm open to discussion and feature requests.  I'm open to accepting
contributions, but only in directions that I believe are right for the tool. 
I'm going to say no to things that I don't believe are a good fit.

--