Open rba opened 5 years ago
Make sure every service has at least two admins and every core member has access
What's a “core member”? This typically used to refer to rakudo core developers, which we have a lot nowadays (51 currently). Do all of them need access? And why?
Also, I wonder if it's possible to create some sort of git-based thing for access. For example, let's say there's a service that I want to tweak. I can commit to the corresponding git repo, and then ping whoever maintains that service so that they pull the changes. This way lots of people would be able to propose changes (making it easier to contribute), yet only a few will have proper access so there's no security problem.
We like transparently decide about the upcoming infrastructure changes together.
I therefore propose change on a
service
level or for agroup of services
. A service could be for example "hosting perl6.org static website" and an example for a group of service could be "dns hosting".There will always be a proposed solution. If there is no better proposal in the comments, we will start implementing the proposed solution, a week after opening the issue.
Here is how we like to handle the Perl6 Infrastructure. Feel free to comment.
Rules and guidelines