public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Btc Drak <btcdrak@gmail.com>
To: Luke Dashjr <luke@dashjr.org>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP 2 promotion to Final
Date: Fri, 18 Mar 2016 09:42:16 +0000	[thread overview]
Message-ID: <CADJgMzsc1znp2tXxHa+LFmeZUnHxEcD+rfexg=5rG1T4=fN07A@mail.gmail.com> (raw)
In-Reply-To: <201603162224.32315.luke@dashjr.org>

[-- Attachment #1: Type: text/plain, Size: 2389 bytes --]

On Wed, Mar 16, 2016 at 10:24 PM, Luke Dashjr <luke@dashjr.org> wrote:

> BIP Comments are not a part of the BIP itself, merely post-completion notes
> from various external parties. So having them external does not make the
> BIP
> any less self-contained. Right now, this information takes the form of
> reddit/forum comments, IRC chats, etc.
>

BIP2 does not state the comments section is where discussion happens for
the BIP, but for a sort of final summary.


> It is important that the forum for comments have a low barrier of use. The
> Bitcoin Wiki requires only a request for editing privileges, whereas GitHub
> wiki would require reading and agreeing to a lengthy Terms of Service
> contract.
>

Seems weak, it's much easier to sign up for a Github account and most have
one already. It's certainly easier than either paying to get edit
privileges on the Bitcoin Wiki find someone to convince you're genuine an
obscure IRC channel.


> In terms of staleness, the Wiki has been shown to stand the test of time,
> and
> is frankly less likely to move than the GitHub repository.
>
> The BIP process originated on the Wiki, and was only moved to GitHub
> because
> stronger moderation was needed (eg, to prevent random other people from
> editing someone else's BIP; number self-assignments; etc). Such moderation
> is
> not only unnecessary for BIP Comments, but would be an outright nuisance.
>

I'm not sure that is the reason why, but in any case, Github is a more
sensible place because of the collaborative features which is why they
became the centre of OSS software development for hundreds of thousands of
projects.


> I hope this addresses all your concerns and we can move forward with BIP 2
> unmodified?
>

I am sorry but it has not. I still strongly object to using the Bitcoin
Wiki or any external source source for the commentary part of BIP2. I
believe it should be done on using the Wiki feature at bitcoin/bips. If
that is not acceptable, then I would suggest a separate page in the bip
assets folder, called bip<nnnn>/comments.md. On a side note, more complex
reference implementation code should be stored in that folder too.


> (On another note, I wonder if we should recommend non-reference
> implementation
> lists/links be moved to BIP Comments rather than constantly revising the
> BIPs
> with them...)
>

Certainly those could be on the comments page.

[-- Attachment #2: Type: text/html, Size: 3393 bytes --]

  reply	other threads:[~2016-03-18  9:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-08 19:04 [bitcoin-dev] BIP 2 promotion to Final Luke Dashjr
2016-03-10  0:36 ` Mustafa Al-Bassam
2016-03-10 15:46   ` Jorge Timón
     [not found] ` <56E0BFDC.5070604@musalbas.com>
     [not found]   ` <201603100053.43822.luke@dashjr.org>
2016-03-10 14:02     ` Mustafa Al-Bassam
2016-03-10 15:59       ` Jorge Timón
2016-03-10 16:28         ` Mustafa Al-Bassam
2016-03-10 16:33           ` Mustafa Al-Bassam
2016-03-10 18:30           ` Jorge Timón
2016-03-10 16:43       ` Luke Dashjr
2016-03-16 20:43 ` Btc Drak
2016-03-16 22:24   ` Luke Dashjr
2016-03-18  9:42     ` Btc Drak [this message]
2016-03-18 19:34       ` Luke Dashjr
2016-03-18 22:52         ` David A. Harding
2016-03-18 11:59     ` Tom

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='CADJgMzsc1znp2tXxHa+LFmeZUnHxEcD+rfexg=5rG1T4=fN07A@mail.gmail.com' \
    --to=btcdrak@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=luke@dashjr.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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