public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "Jorge Timón" <jtimon@monetize.io>
To: Jean-Paul Kogelman <jeanpaulkogelman@me.com>
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] A critique of bitcoin open source community
Date: Mon, 21 Oct 2013 12:21:27 +0200	[thread overview]
Message-ID: <CAC1+kJOvrcK5-W9HsBZLPKVxR=iMkR9F8RAhUsrnjpq7E3vxwQ@mail.gmail.com> (raw)
In-Reply-To: <5D2C71C4-565F-4991-90E4-5782A9C83360@me.com>

I think it's great to move BIPs to github.
I also agree with the states -> directories mapping.
Git manages moved files well.


On 10/21/13, Jean-Paul Kogelman <jeanpaulkogelman@me.com> wrote:
>
> On 2013-10-21, at 2:44 AM, Arto Bendiken <arto@bendiken.net> wrote:
>
>>
>> Indeed. The BIP analogs that immediately come to mind would be the
>> enhancement proposal processes for Python, XMPP, and BitTorrent:
>
> Bitcoin's BIP process is directly based off of Python's PEP process.
>
> Quote from BIP 1, History:
>
> This document was derived heavily from Python's PEP-0001. In many places
> text was simply copied and modified.
>


-- 
Jorge Timón

http://freico.in/



  reply	other threads:[~2013-10-21 10:21 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-19 16:38 [Bitcoin-development] A critique of bitcoin open source community Mitar
2013-10-19 16:50 ` Melvin Carvalho
2013-10-19 20:40 ` Gregory Maxwell
2013-10-19 21:09   ` Mitar
2013-10-19 21:16   ` Jean-Paul Kogelman
2013-10-19 22:29     ` Luke-Jr
2013-10-19 23:20       ` Gregory Maxwell
2013-10-19 23:35         ` Jean-Paul Kogelman
2013-10-19 23:57           ` Peter Todd
2013-10-20  0:52             ` Jean-Paul Kogelman
2013-10-20 22:43               ` Peter Todd
2013-10-20 23:11                 ` Peter Todd
2013-10-21  0:27                 ` Jeff Garzik
2013-10-21  6:25                   ` Peter Todd
2013-10-21  6:40                     ` Jean-Paul Kogelman
2013-10-21  6:43                       ` Peter Todd
2013-10-21  6:52                         ` Jean-Paul Kogelman
2013-10-21  7:03                           ` Martin Sustrik
2013-10-21  7:07                             ` Jean-Paul Kogelman
2013-10-21  7:28                               ` Martin Sustrik
2013-10-21  9:36                             ` Melvin Carvalho
2013-10-21  9:44                               ` Arto Bendiken
2013-10-21  9:49                                 ` Jean-Paul Kogelman
2013-10-21 10:21                                   ` Jorge Timón [this message]
2013-10-20 10:00         ` Wladimir
2013-10-19 23:21       ` Jean-Paul Kogelman
2013-10-19 23:22         ` Jean-Paul Kogelman
2013-10-19 22:33 ` Mike Hearn

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='CAC1+kJOvrcK5-W9HsBZLPKVxR=iMkR9F8RAhUsrnjpq7E3vxwQ@mail.gmail.com' \
    --to=jtimon@monetize.io \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=jeanpaulkogelman@me.com \
    /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