* [Bitcoin-development] Move authorative source for BIPs to git repository
@ 2013-12-05 13:37 Wladimir
2013-12-05 14:27 ` Luke-Jr
2013-12-05 23:16 ` Gavin Andresen
0 siblings, 2 replies; 7+ messages in thread
From: Wladimir @ 2013-12-05 13:37 UTC (permalink / raw)
To: Bitcoin Dev, Pieter Wuille, Gregory Maxwell
[-- Attachment #1: Type: text/plain, Size: 464 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 689 bytes --]
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [Bitcoin-development] Move authorative source for BIPs to git repository
2013-12-05 13:37 [Bitcoin-development] Move authorative source for BIPs to git repository Wladimir
@ 2013-12-05 14:27 ` Luke-Jr
2013-12-05 14:38 ` Wladimir
2013-12-05 14:43 ` Jeff Garzik
2013-12-05 23:16 ` Gavin Andresen
1 sibling, 2 replies; 7+ messages in thread
From: Luke-Jr @ 2013-12-05 14:27 UTC (permalink / raw)
To: bitcoin-development
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
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [Bitcoin-development] Move authorative source for BIPs to git repository
2013-12-05 14:27 ` Luke-Jr
@ 2013-12-05 14:38 ` Wladimir
2013-12-05 14:43 ` Jeff Garzik
1 sibling, 0 replies; 7+ messages in thread
From: Wladimir @ 2013-12-05 14:38 UTC (permalink / raw)
To: Luke-Jr; +Cc: Bitcoin Dev
[-- Attachment #1: Type: text/plain, Size: 868 bytes --]
On Thu, Dec 5, 2013 at 3:27 PM, Luke-Jr <luke@dashjr•org> wrote:
> 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
[-- Attachment #2: Type: text/html, Size: 1433 bytes --]
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [Bitcoin-development] Move authorative source for BIPs to git repository
2013-12-05 14:27 ` Luke-Jr
2013-12-05 14:38 ` Wladimir
@ 2013-12-05 14:43 ` Jeff Garzik
2013-12-05 20:49 ` Gary Rowe
1 sibling, 1 reply; 7+ messages in thread
From: Jeff Garzik @ 2013-12-05 14:43 UTC (permalink / raw)
To: Luke-Jr; +Cc: Bitcoin Dev
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/
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [Bitcoin-development] Move authorative source for BIPs to git repository
2013-12-05 14:43 ` Jeff Garzik
@ 2013-12-05 20:49 ` Gary Rowe
0 siblings, 0 replies; 7+ messages in thread
From: Gary Rowe @ 2013-12-05 20:49 UTC (permalink / raw)
To: Bitcoin Development List
[-- Attachment #1: Type: text/plain, Size: 2685 bytes --]
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:
> 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
>
[-- Attachment #2: Type: text/html, Size: 4157 bytes --]
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [Bitcoin-development] Move authorative source for BIPs to git repository
2013-12-05 13:37 [Bitcoin-development] Move authorative source for BIPs to git repository Wladimir
2013-12-05 14:27 ` Luke-Jr
@ 2013-12-05 23:16 ` Gavin Andresen
2013-12-06 13:41 ` Wladimir
1 sibling, 1 reply; 7+ messages in thread
From: Gavin Andresen @ 2013-12-05 23:16 UTC (permalink / raw)
To: Wladimir; +Cc: Bitcoin Dev
[-- Attachment #1: Type: text/plain, Size: 257 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 365 bytes --]
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2013-12-06 13:41 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-12-05 13:37 [Bitcoin-development] Move authorative source for BIPs to git repository Wladimir
2013-12-05 14:27 ` Luke-Jr
2013-12-05 14:38 ` Wladimir
2013-12-05 14:43 ` Jeff Garzik
2013-12-05 20:49 ` Gary Rowe
2013-12-05 23:16 ` Gavin Andresen
2013-12-06 13:41 ` Wladimir
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox