Move authorative source for BIPs to git repository
7 messages, 5 to 6 Dec 2013. Started by Wladimir J. van der Laan.
Wladimir J. van der Laan (3), Luke Dashjr, Jeff Garzik, Gary Rowe, Gavin Andresen
Hello all,
A while ago after discussion on the mailing list a repository was set up to store the BIP documents, as this is deemed a more secure solution than having them on the wiki:
https://github.com/bitcoin/bips
To prevent confusion the next step should probably be to replace the BIPs on the wiki with links to the github documents, with a notice that changes should be proposed on github or mailed to the BIP editor (gmaxwell).
Agreed?
Regards, Wladimir
On Thursday, December 05, 2013 1:37:10 PM Wladimir wrote:
Quoted text (13 lines)
> Hello all, > > A while ago after discussion on the mailing list a repository was set up to > store the BIP documents, as this is deemed a more secure solution than > having them on the wiki: > > https://github.com/bitcoin/bips > > To prevent confusion the next step should probably be to replace the BIPs > on the wiki with links to the github documents, with a notice that changes > should be proposed on github or mailed to the BIP editor (gmaxwell). > > Agreed?
I think this would stifle active BIP draft editing. We're already having a hard time getting some developers to write BIPs for their proposals - I don't think we should be putting up bigger hurdles.
Luke
On Thu, Dec 5, 2013 at 3:27 PM, Luke-Jr <luke@dashjr•org> wrote:
Quoted text (7 lines)
> On Thursday, December 05, 2013 1:37:10 PM Wladimir wrote: > > I think this would stifle active BIP draft editing. We're already having a > hard time getting some developers to write BIPs for their proposals - I > don't > think we should be putting up bigger hurdles. >
How is github a hurdle?
It's easy enough to create a fork and submit back the changes as a pull request.
In the case of text documents, this can be completely done through the web interface.
If anything creating a github account is a smaller hurdle than having to pay to create a wiki account and wait for it to be activated.
Aside: my proposal is for the BIPs that are already accepted, and should not be edited without dicussion. If people want to put their drafts in the wiki that's a different story.
Regards, Wladimir
This entire discussion is recycled. Please review the previous discussion, before asking the same questions over again.
Properly done, there are FEWER hurdles. In the previous discussion, there was outlined a process whereby the BIPS Editor would receive an email, and could take it from there. No wiki login or bitcoin payment required. More advanced users may submit pull requests.
Compared with a hash-sealed git repo as primary source, the wiki is second class.
On Thu, Dec 5, 2013 at 9:27 AM, Luke-Jr <luke@dashjr•org> wrote:
Quoted text (30 lines)
> On Thursday, December 05, 2013 1:37:10 PM Wladimir wrote: >> Hello all, >> >> A while ago after discussion on the mailing list a repository was set up to >> store the BIP documents, as this is deemed a more secure solution than >> having them on the wiki: >> >> https://github.com/bitcoin/bips >> >> To prevent confusion the next step should probably be to replace the BIPs >> on the wiki with links to the github documents, with a notice that changes >> should be proposed on github or mailed to the BIP editor (gmaxwell). >> >> Agreed? > > I think this would stifle active BIP draft editing. We're already having a > hard time getting some developers to write BIPs for their proposals - I don't > think we should be putting up bigger hurdles. > > Luke > > ------------------------------------------------------------------------------ > Sponsored by Intel(R) XDK > Develop, test and display web and hybrid apps with a single code base. > Download it for free now! > http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists•sourceforge•net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development
Personally, I would be more inclined to submit and work on a BIP if it was in GitHub. It's a regular home from home for me now.
On 5 December 2013 14:43, Jeff Garzik <jgarzik@bitpay•com> wrote:
Quoted text (70 lines)
> This entire discussion is recycled. Please review the previous > discussion, before asking the same questions over again. > > Properly done, there are FEWER hurdles. In the previous discussion, > there was outlined a process whereby the BIPS Editor would receive an > email, and could take it from there. No wiki login or bitcoin payment > required. More advanced users may submit pull requests. > > Compared with a hash-sealed git repo as primary source, the wiki is > second class. > > > On Thu, Dec 5, 2013 at 9:27 AM, Luke-Jr <luke@dashjr•org> wrote: > > On Thursday, December 05, 2013 1:37:10 PM Wladimir wrote: > >> Hello all, > >> > >> A while ago after discussion on the mailing list a repository was set > up to > >> store the BIP documents, as this is deemed a more secure solution than > >> having them on the wiki: > >> > >> https://github.com/bitcoin/bips > >> > >> To prevent confusion the next step should probably be to replace the > BIPs > >> on the wiki with links to the github documents, with a notice that > changes > >> should be proposed on github or mailed to the BIP editor (gmaxwell). > >> > >> Agreed? > > > > I think this would stifle active BIP draft editing. We're already having > a > > hard time getting some developers to write BIPs for their proposals - I > don't > > think we should be putting up bigger hurdles. > > > > Luke > > > > > ------------------------------------------------------------------------------ > > Sponsored by Intel(R) XDK > > Develop, test and display web and hybrid apps with a single code base. > > Download it for free now! > > > http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk > > _______________________________________________ > > Bitcoin-development mailing list > > Bitcoin-development@lists•sourceforge•net > > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > > > > -- > Jeff Garzik > Bitcoin core developer and open source evangelist > BitPay, Inc. https://bitpay.com/ > > > ------------------------------------------------------------------------------ > Sponsored by Intel(R) XDK > Develop, test and display web and hybrid apps with a single code base. > Download it for free now! > > http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists•sourceforge•net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development >
RE: replace BIPs on the wiki with links to github documents: agreed.
Wladimir or Gregory: can one of you update BIP 0001 to describe the Proper Process for creating/editing a BIP? It doesn't mention the github repo at all right now.
Yes, i'm updating BIP 0001 right now, will send a pull when ready.
On Fri, Dec 6, 2013 at 12:16 AM, Gavin Andresen <gavinandresen@gmail•com>wrote:
Quoted text (10 lines)
> RE: replace BIPs on the wiki with links to github documents: agreed. > > Wladimir or Gregory: can one of you update BIP 0001 to describe the Proper > Process for creating/editing a BIP? It doesn't mention the github repo at > all right now. > > -- > -- > Gavin Andresen >