Repository navigation
Add Domains.md to describe rules around domain maintainer role #50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
d20fac3
dbcd113
7dfd4f8
77dd7bd
103453b
ccad132
ad06094
f83c4d2
9f219fd
b5349a2
94bfc39
2bbd42a
f8dbced
a96a282
f208206
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,52 @@ | ||
| # Community domains | ||
|
|
||
| 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. This currently applies to: | ||
|
|
||
| - bitcoin.design | ||
|
GBKS marked this conversation as resolved.
Resolved
|
||
| - bitcoindesigners.org | ||
|
|
||
| ## The community | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I am not sure if 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.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 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 It's a solid document with great outline. ACK. |
||
| The Bitcoin Design community, defined as; | ||
|
|
||
| *“The active members of the Slack workspace at bitcoindesign.slack.com, represented in rough-consensus by the maintainers of the BitcoinDesign Github organization at github.com/bitcoindesign”.* | ||
|
|
||
| ## Ownership | ||
| A community domain shall be considered owned by the Bitcoin Design community. | ||
| The role of domain maintainer does not imply any ownership of the domain. | ||
|
|
||
| ## Registration and payments | ||
| The community will pay for, or solicit donations to pay for the long term registration of the community domain(s). The current yearly fees are $49.88 for bitcoin.design, and $12 plus tax for bitcoindesigners.org. | ||
|
|
||
|
danielnordh marked this conversation as resolved.
Resolved
|
||
| ## Maintainer | ||
| A domain maintainer needs to enact the will of the community and should be strongly disincentivized to act in their own interest. They are NOT allowed to change the domain settings in any way without the approval from the community as set out in domain changes. The domain maintainer is selected from the community github maintainers, should be an active contributor at the time of selection and should notify the community if they no longer wish to be a maintainer or are planning to leave their active role in the community. | ||
|
|
||
| ## Changes | ||
| The domain maintainer will not make any changes to the domain (including pointing it to other content than hosted by the github.com/bitcoindesign repositories) without the consent of the community. To make a change, a community github maintainer needs to propose a change; | ||
|
|
||
| 1. Create a pull request with a clear description and rationale for the change in the bitcoindesign/meta repository. | ||
| 2. Post a link to the pull request in the #general Slack channel | ||
| 3. The pull request needs to remain open for at least 30 days and all comments and concern need to be addressed before a decision can me made | ||
| 4. Decision will be made by rough consensus of the community and the github maintainers | ||
| 5. The proposing maintainer can participate in the discussion but should not be the one to merge the pull request once a decision has been made | ||
|
|
||
| The domain maintainer can NOT sell, rent or give the domain away nor accept any form of payment for proposing or changing domain settings. The domain maintenance authority can only be handed over to another community maintainer through the domain change process outlined above. | ||
|
|
||
| --- | ||
| # Domain information | ||
|
|
||
| ## bitcoin.design | ||
| Maintainer: @gbks, as [decided](https://github.com/BitcoinDesign/Guide/pull/21#issuecomment-738131599) | ||
|
|
||
| Expiry date: 2021-06-27T23:59:59.0Z | ||
|
|
||
| DNS records: | ||
|
|
||
| ## bitcoindesigners.org | ||
| Maintainer: @moneyball | ||
|
|
||
| Expiry date: 2021-06-22T23:09:32Z | ||
|
|
||
| DNS records: | ||
|
|
||
|
|
||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.