cryptogera/zorro
cryptogera/zorro
1
0
Fork 0
Code Issues Pull Requests Projects Releases 2 Wiki Activity

Change references from BTC Core to LTC Core (#373)

Browse Source 
In this commit, all references to `Bitcoin` or `Bitcoin Core` are replaced with `Litecoin` and `Litecoin Core`, respectively.  

In addition, I added a copyright line for *The Litecoin Core Developers* and provided the rightful attribution to the original `Bitcoin Core` team as per their MIT license.
This commit is contained in:
Gerald Nash⚡️ 2017-08-15 17:37:04 -04:00 committed by Adrian Gallagher
parent 83d36e7e24
commit 826e81155f
No known key found for this signature in database
GPG Key ID: FE3348877809386C
1 changed files with 10 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
CONTRIBUTING.md
View File

@ -1,7 +1,7 @@
Contributing to Bitcoin Core
Contributing to Litecoin Core
============================
The Bitcoin Core project operates an open contributor model where anyone is
The Litecoin Core project operates an open contributor model where anyone is
welcome to contribute towards development in the form of peer review, testing
and patches. This document explains the practical process and guidelines for
contributing.
@ -157,11 +157,10 @@ where possible keep them short, uncomplex and easy to verify.
"Decision Making" Process
-------------------------
The following applies to code changes to the Bitcoin Core project (and related
projects such as libsecp256k1), and is not to be confused with overall Bitcoin
The following applies to code changes to the Litecoin Core project, and is not to be confused with overall Litecoin
Network Protocol consensus changes.
Whether a pull request is merged into Bitcoin Core rests with the project merge
Whether a pull request is merged into Litecoin Core rests with the project merge
maintainers and ultimately the project lead.
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
demonstrating the bug and also proving the fix. This helps prevent regression.
Patches that change Bitcoin consensus rules are considerably more involved than
Patches that change Litecoin consensus rules are considerably more involved than
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
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
of consensus critical code.
Where a patch set proposes to change the Bitcoin consensus, it must have been
Where a patch set proposes to change the Litecoin consensus, it must have been
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
a worthwhile change based on the judgement of the maintainers.
@ -260,10 +259,13 @@ about:
Release Policy
--------------
The project leader is the release manager for each Bitcoin Core release.
The project leader is the release manager for each Litecoin Core release.
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
MIT license unless specified otherwise in `contrib/debian/copyright` or at