|
|
|
|
|
by nickstinemates
4293 days ago
|
|
I'm sorry to hear you've had a frustrating experience. The governance model should be outlined in the CONTRIBUTING.md file located in the repository which should address the concerns. There are project maintainers that are not on the Docker, Inc. payroll, and getting anything committed requires the approval of at least 2. We actually consider this a litmus test for our involvement with the ecosystem, and it's fundamentally a great thing. As for the issue at hand, I personally understand desire on both sides. I have been frustrated multiple times by the lack of being able to have multiple Dockerfiles per repo as a simple example. On the other, providing strict guarantees about context ensures true portability of Dockerfiles. What I will say, is that this is a topic we talk about a lot, whether it be on the issues themselves or in IRC. It's tough to get the right balance. |
|
This has been the case on other issues I have seen as well, either things languish, or they get magically swept into the project, with the decision happening elsewhere.
Stewardship would mean actually explaining the position above, and discussing with the community how the issue affects them in order to gain an understanding of what we are talking about.
Yelling "repeatability" with no context and then disappearing is pretty frustrating.