@ -1,7 +1,7 @@
Contributing to Bit coin Core
Contributing to Lite coin Core
============================
============================
The Bit coin Core project operates an open contributor model where anyone is
The Lite coin Core project operates an open contributor model where anyone is
welcome to contribute towards development in the form of peer review, testing
welcome to contribute towards development in the form of peer review, testing
and patches. This document explains the practical process and guidelines for
and patches. This document explains the practical process and guidelines for
contributing.
contributing.
@ -157,11 +157,10 @@ where possible keep them short, uncomplex and easy to verify.
"Decision Making" Process
"Decision Making" Process
-------------------------
-------------------------
The following applies to code changes to the Bitcoin Core project (and related
The following applies to code changes to the Litecoin Core project, and is not to be confused with overall Litecoin
projects such as libsecp256k1), and is not to be confused with overall Bitcoin
Network Protocol consensus changes.
Network Protocol consensus changes.
Whether a pull request is merged into Bit coin Core rests with the project merge
Whether a pull request is merged into Lite coin Core rests with the project merge
maintainers and ultimately the project lead.
maintainers and ultimately the project lead.
Maintainers will take into consideration if a patch is in line with the general
Maintainers will take into consideration if a patch is in line with the general
@ -179,7 +178,7 @@ In general, all pull requests must:
- Where bugs are fixed, where possible, there should be unit tests
- Where bugs are fixed, where possible, there should be unit tests
demonstrating the bug and also proving the fix. This helps prevent regression.
demonstrating the bug and also proving the fix. This helps prevent regression.
Patches that change Bit coin consensus rules are considerably more involved than
Patches that change Lite coin consensus rules are considerably more involved than
normal because they affect the entire ecosystem and so must be preceded by
normal because they affect the entire ecosystem and so must be preceded by
extensive mailing list discussions and have a numbered BIP. While each case will
extensive mailing list discussions and have a numbered BIP. While each case will
be different, one should be prepared to expend more time and effort than for
be different, one should be prepared to expend more time and effort than for
@ -220,7 +219,7 @@ higher in terms of discussion and peer review requirements, keeping in mind that
mistakes could be very costly to the wider community. This includes refactoring
mistakes could be very costly to the wider community. This includes refactoring
of consensus critical code.
of consensus critical code.
Where a patch set proposes to change the Bit coin consensus, it must have been
Where a patch set proposes to change the Lite coin consensus, it must have been
discussed extensively on the mailing list and IRC, be accompanied by a widely
discussed extensively on the mailing list and IRC, be accompanied by a widely
discussed BIP and have a generally widely perceived technical consensus of being
discussed BIP and have a generally widely perceived technical consensus of being
a worthwhile change based on the judgement of the maintainers.
a worthwhile change based on the judgement of the maintainers.
@ -260,10 +259,13 @@ about:
Release Policy
Release Policy
--------------
--------------
The project leader is the release manager for each Bit coin Core release.
The project leader is the release manager for each Lite coin Core release.
Copyright
Copyright
---------
---------
Copyright 2017 The Litecoin Core Developers
- bitcoin: Copyright (c) 2009-2017 Bitcoin Core Developers (MIT License)
By contributing to this repository, you agree to license your work under the
By contributing to this repository, you agree to license your work under the
MIT license unless specified otherwise in `contrib/debian/copyright` or at
MIT license unless specified otherwise in `contrib/debian/copyright` or at