From: Wladimir <laanwj@gmail•com>
To: Luke-Jr <luke@dashjr•org>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Move authorative source for BIPs to git repository
Date: Thu, 5 Dec 2013 15:38:45 +0100 [thread overview]
Message-ID: <CA+s+GJC5LB_9n9ktCby=st-2-y-6x2jQ27D9UOo6WzWrD2CQZQ@mail.gmail.com> (raw)
In-Reply-To: <201312051427.44179.luke@dashjr.org>
[-- 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 --]
next prev parent reply other threads:[~2013-12-05 14:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-05 13:37 Wladimir
2013-12-05 14:27 ` Luke-Jr
2013-12-05 14:38 ` Wladimir [this message]
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+s+GJC5LB_9n9ktCby=st-2-y-6x2jQ27D9UOo6WzWrD2CQZQ@mail.gmail.com' \
--to=laanwj@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=luke@dashjr$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox