Repository navigation
Add Domains.md to describe rules around domain maintainer role - #50
Conversation
|
ACK, with Johns' suggestions. |
Co-authored-by: Johns Beharry <johns@peakshift.com>
Co-authored-by: Johns Beharry <johns@peakshift.com>
moneyball
left a comment
There was a problem hiding this comment.
ACK. A few nits if you wish to make those changes but I approve as-is.
2bbd42a
danielnordh
left a comment
There was a problem hiding this comment.
All comments addressed. Moving out of Draft.
|
ACK. I'm very happy with the current state. |
|
ACK |
| - bitcoin.design | ||
| - bitcoindesigners.org | ||
|
|
||
| ## The community |
There was a problem hiding this comment.
I am not sure if Community is proper term here, though it sounds good, but is it fair to communicate it like this? Perhaps core contributors or maintainers is more appropriate?
In reality community is not the one making decisions in FOSS. Though we were though that FOSS is participatory and that everyone can participate, not everyone participates in the decision-making. The ones in charge of the decision making are always core-contributors, people who in most cases are responsible for 95% of the code and have way better insight on what's going on.
In my personal view, decisions like this cannot be decided by community nor core contributors represent community.
In reality open-source isn't what we were told to. It's not lalaland where anybody vote counts. Votes that count in the decision making process are determined by meritocracy and that's perfectly fine. Some decisions can be public and read-only but as community grows it'll be hard to make "community" consensus, nor community consensus is needed. People who spend significant time contributing have their heart and mind into FOSS are the ones who participate into decision-making process. Now, anybody from community can become the part of this by simply - contributing significant time towards FOSS.
There was a problem hiding this comment.
By the way I don't consider my comment as a blocker to this PR. Just a minor food for thoughts as it may become a blocker in the future as imo community-approval or community consensus can't be achieved.
It's a solid document with great outline. ACK.
johnsBeharry
left a comment
There was a problem hiding this comment.
The proposal has been open and has not seen any NACKs so it's time to approve and merge!
This document sets out rules for community domains and the responsibilities and expectations of anyone that maintains and manages the domain settings of official domains used by the Bitcoin Design community. Community domains are used to promote and host content that the community has created and committed to the github.com/bitcoindesign repositories.
Please provide feedback and improvements before we convert this from a Draft to PR