From: Wladimir <laanwj@gmail•com>
To: Gregory Maxwell <gmaxwell@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>,
Amir Taaki <genjix@riseup•net>
Subject: Re: [Bitcoin-development] BIP process
Date: Wed, 15 Oct 2014 11:36:58 +0200 [thread overview]
Message-ID: <CA+s+GJCzBHGoBo8mcubbaavwR2HPave8GbA90+aGYgiJDKm=4g@mail.gmail.com> (raw)
In-Reply-To: <CAAS2fgQRWAk6+ZvEaAX+Mp+_dtg9G_h8+tYxtZpVhu=Djb0k7A@mail.gmail.com>
> 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
next prev parent reply other threads:[~2014-10-15 9:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-15 8:29 Wladimir
2014-10-15 9:22 ` Gregory Maxwell
2014-10-15 9:36 ` Wladimir [this message]
2014-10-15 18:58 ` Cory Fields
2014-10-16 7:50 ` Thomas Zander
2014-10-15 15:37 ` Gavin Andresen
2014-10-15 15:46 ` Mike Hearn
2014-10-15 15:54 ` Adam Back
2014-10-15 16:47 ` Peter Todd
2014-10-15 18:13 ` Mike Hearn
2014-10-16 7:38 ` Thomas Zander
2014-10-16 14:19 ` Oliver Egginger
2014-10-15 19:00 ` Btc Drak
2014-10-15 19:40 ` Peter Todd
2014-10-16 4:41 ` Luke Dashjr
2014-10-19 7:17 ` xor
2014-10-19 9:42 ` Btc Drak
2014-10-19 9:49 ` Wladimir
2014-10-19 18:58 ` Thomas Zander
2014-10-20 0:33 ` odinn
-- strict thread matches above, loose matches on Subject: below --
2011-10-18 19:17 Gavin Andresen
2011-10-18 21:26 ` Nils Schneider
2011-10-20 5:02 ` Alex Waters
2011-10-20 11:27 ` Christian Decker
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+GJCzBHGoBo8mcubbaavwR2HPave8GbA90+aGYgiJDKm=4g@mail.gmail.com' \
--to=laanwj@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=genjix@riseup$(echo .)net \
--cc=gmaxwell@gmail$(echo .)com \
/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