Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from <laanwj@gmail.com>) id 1XeL0y-0003RY-Jm for bitcoin-development@lists.sourceforge.net; Wed, 15 Oct 2014 09:37:04 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.213.180 as permitted sender) client-ip=209.85.213.180; envelope-from=laanwj@gmail.com; helo=mail-ig0-f180.google.com; Received: from mail-ig0-f180.google.com ([209.85.213.180]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1XeL0x-00072t-P0 for bitcoin-development@lists.sourceforge.net; Wed, 15 Oct 2014 09:37:04 +0000 Received: by mail-ig0-f180.google.com with SMTP id uq10so1018581igb.13 for <bitcoin-development@lists.sourceforge.net>; Wed, 15 Oct 2014 02:36:58 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.42.147.135 with SMTP id n7mr9836505icv.25.1413365818443; Wed, 15 Oct 2014 02:36:58 -0700 (PDT) Received: by 10.64.141.112 with HTTP; Wed, 15 Oct 2014 02:36:58 -0700 (PDT) In-Reply-To: <CAAS2fgQRWAk6+ZvEaAX+Mp+_dtg9G_h8+tYxtZpVhu=Djb0k7A@mail.gmail.com> References: <CA+s+GJCAWXgpzyQnAar6ecKdcci+tdR8yJjCOUpB=xmj-ytZZQ@mail.gmail.com> <CAAS2fgQRWAk6+ZvEaAX+Mp+_dtg9G_h8+tYxtZpVhu=Djb0k7A@mail.gmail.com> Date: Wed, 15 Oct 2014 11:36:58 +0200 Message-ID: <CA+s+GJCzBHGoBo8mcubbaavwR2HPave8GbA90+aGYgiJDKm=4g@mail.gmail.com> From: Wladimir <laanwj@gmail.com> To: Gregory Maxwell <gmaxwell@gmail.com> Content-Type: text/plain; charset=UTF-8 X-Spam-Score: -1.6 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (laanwj[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1XeL0x-00072t-P0 Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>, Amir Taaki <genjix@riseup.net> Subject: Re: [Bitcoin-development] BIP process X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: <bitcoin-development.lists.sourceforge.net> List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe> List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development> List-Post: <mailto:bitcoin-development@lists.sourceforge.net> List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help> List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, <mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe> X-List-Received-Date: Wed, 15 Oct 2014 09:37:04 -0000 > This all makes a lot of sense to me, and would help a lot with the > workflow. Unfortunately github pulls and issues really have nothing > to faciltate a multistage workflow... e.g. where something can go > through several steps. Indeed, pull requests don't have a "status". It would be possible to (ab)use labels for this. The drawback of labels is that only the repository team can set these, there is no way to delegate. But I suppose it'd be possible to build something on top of the github API that handles this. > We're also having problems with people failing to comment on things, > not even "I looked at this and have no opinion", which is really > obstructing things. Well - the only way to avoid that is to set a reasonable deadline, after which there is a default decision. You'd hope this would motivate people to get involved in time. Wladimir