Explain clearly why we can't accept new executors
Problem to solve
From time to time we receive issues or ~"Community Contribution" about new executors.
We are not in the position to accept those contributions for several reasons:
- some executors requires licensed software or hardware that we do not have
- those executors than have to be maintained
- some executors can be hard to test in CI
- each executor bring his dependencies (that has to be maintained as well), and it is hard to avoid conflicts
Intended users
The wider community and anyone who wants to submit a ~"Community Contribution" relative to gitlab-runner
executors.
Further details
As we are closing in on creating a Generic Executor to handle cases like those described in the problem statement above, but in a supportable and extensible way, it is critical to make this stance clear in our contributor documentation.
Proposal
-
express clearly our position on the topic -
document the position in CONTRIBUTING.md
-
place a notice about this in the new issue template -
prepare a close issue/MR template pointing to this and #2885 (closed) -
close all the MR implementing new executors -
close all the issues about new executors
-
Links / references
Edited by Brendan O'Leary