## Contributing Flow
One tenet of Bitcoin Backbone philosopy is to minimize the used infrastructure,
where the infrastructure refers to things like source version code collaborative
plateform, hosting providers, CNDs, etc. For this reason, the project is favoring
the project collaboration among contributors to happen on minimal infrastructure,
i.e currently the mailing list:
https://framagroupes.org/sympa/info/bitcoin-backbone-dev
The code can be download from here:
- git clone git://bitcoinbackbone.org/linux-backbone.git (test linux build)
- git clone git://bitcoinbackbone.org/linux-libbitcoinkernel.git (test linux build)
To contribute a patch, the workflow is as follows:
- 1. Fork Repository
- 2. Create Topic Branch
- 3. Commit Patches
In general commits should be atomic and diffs should be easy to read.
When you wish to submit, attach it as a git formatted patch and send
an email to the mailing list with a title in the following format:
- [Code Patch] : patch_short_description
The team of maintainers will pick up the code patch, comes back
with a review and iterate it on until it's ready for merging. At
the present time, a single mailing list is enough.
Technical decision-making is done on an "ideas meritocracy" principle,
by the team of maintainers in a collegial fashion.
## Contributing Culture
Working and hacking on a cryptocurrency project demands a high-level of
rigor, adversarial thinking, thorough testing and risk-minimization.
Therefore, we're privileging the onboarding of already skilled contributors,
especially the ones with a track records in kernel, compiler, applied
cryptography, electronic engineering or networking. Lack of familiarity
with bitcoin is not a bottleneck to contribute, it might even been seen
as an advantage. Strong skills in physics, mathematics or logics is appreciated.
We're are welcoming all kind of code contributions, be it code patches,
technical review, project documentation or quality assurance testing.
For organizational reasons and in a goal to keep the project lean for now,
we're also privileging onboarding contributors who are mostly located in
Western Europe or Northern America. We do plan to extend to other geographical
areas as the project grows, even ones geographically distant in the southern
part of the terresterial globe.
The contributing culture might be a deliberately "rude". We aim to adhere to
a cypherpunk ethos. Nevertheless, we aim to treat every contributor, potential
or actual, with ethics and respect.
## Contributing Rules
The Bitcoin Backbone project is a collective software work created and maintained
at the initiative of the team of maintainers. The team of maintainers is merging
the code, publishing the releases and distribute the code artifacts under its
direction. The team of maintainers is vested with the rights associated to this
collective software work, and in return commits to economically appreciate all the
technical contributions, and give back to all the active contributors, one way or another.
In the occurence of social conflicts, the project maintainers are collegially
taking the decision according to the project's rules of precedents, the tradition
of open-source software, and in the silence or approximition of such corpus,
according to the laws of Switzerland.
In the light of persistent disagreements among the maintainers and a contributor,
all the parties agree to submit their disagreement to a neutral meditation to seek
a common solution, at a physical place of hearing being convenient for all the involved
parties.
By brining a de minimis technical contribution to the project, a contributor
agree to the present rules.
The team of maintainers stays open for discussions on improvements of said rules.
v0.0.1
block height 952519
hash 000000000000000000012bb2f63693b3ba58b763b1694069460c6e6b59380c69