> On Jan 4, 2019, at 1:06 PM, Joan Touzet <woh...@apache.org> wrote:
>
>
> ----- Original Message -----
>> From: "Allen Wittenauer" <a...@effectivemachines.com.INVALID>
>
>> This is the same model the ASF has used for JIRA for a decade+.
>> It’s always been possible for anyone to submit anything to Jenkins
>> and have it get executed. Limiting PRs or patch files in JIRAs to
>> just committers is very anti-community. (This is why all this talk
>> about using Jenkins for building artifacts I find very
>> entertaining. The infrastructure just flat out isn’t built for it
>> and absolutely requires disposable environments.)
>
> Then we build a new, additional Jenkins that is committer-only (or PMC-
> only, perhaps, if it's for release purposes). This is a tractable
> problem.
I think people forget that the ASF is a non-profit for individuals.
It’s not a business. It’s not a non-profit that requires its members to be
companies willing to pay astronomical fees. People-time is almost all
volunteer. As such, time to work on these problems is in *extremely* short
supply, never mind the actual hardware, power, etc, costs. That’s not even
covering the legal issues...
> We are stuck at an impasse where people need something to reduce the
> manual workload, and we have an obsolete policy standing in its way.
I’m honestly confused as to why suddenly running scripts on one server
vs. running them on another one suddenly makes the release process less manual.
> We must be the last organisation in the world where people are forced
> to release software through a manual process.
lol, no, hardly. How many other non-profits have this much software
with so few paid employees running the show?
> I don't see why this is something to be gleeful about.
Being entertained is not the same thing as being gleeful.
