From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1XeUFS-0002Ki-4V for bitcoin-development@lists.sourceforge.net; Wed, 15 Oct 2014 19:28:38 +0000 X-ACL-Warn: Received: from mail-wi0-f174.google.com ([209.85.212.174]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1XeUFQ-000880-MZ for bitcoin-development@lists.sourceforge.net; Wed, 15 Oct 2014 19:28:38 +0000 Received: by mail-wi0-f174.google.com with SMTP id h11so10871623wiw.7 for ; Wed, 15 Oct 2014 12:28:29 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=SA/aA9wt8ALG4yrHQ/Jk+9VFMZi2UOoifpp9lkrtYtA=; b=eKdAPN9EVAKlh88G4+7gUeBISpRUOX/xBwGzdPH7Y/NgJ8RjqfSyADsIiTbteeUFy8 2XRUxBTvUTvoZRATfi8aos4VLj9K7rWB0uenyBNY1XKTUwQpPtujmC5rdNyv++Zs+3dk 9atx1Sfrftt0/snBhTeoUVE+utx5clsFEqgI1nPAWHbpy8NV9XpEc+Lwe9a01b8yXWUj q+bEyG4y46IZzqSSP7nx6JMXmDE2Iv2UcZfibV6l08ZeG58VisBsVVxi4RX2mf9nNZpo E5P2nzV1mHU5RO+fYPHnp8L9+6BAZG75SBS6POJqXoyLmbD5jfLA6EXbdatxGcKAn6BJ XgKQ== X-Gm-Message-State: ALoCoQk0bFbibots66FMnR/Gyl62aLFnLlJEbXor3mUkfKstFjp3JDHM4hGZ+ncAvtsqjQK1SEFa MIME-Version: 1.0 X-Received: by 10.195.13.114 with SMTP id ex18mr5286504wjd.111.1413399537748; Wed, 15 Oct 2014 11:58:57 -0700 (PDT) Received: by 10.194.184.180 with HTTP; Wed, 15 Oct 2014 11:58:57 -0700 (PDT) In-Reply-To: References: Date: Wed, 15 Oct 2014 14:58:57 -0400 Message-ID: From: Cory Fields To: Wladimir Content-Type: text/plain; charset=UTF-8 X-Spam-Score: 0.0 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. X-Headers-End: 1XeUFQ-000880-MZ Cc: Bitcoin Dev , Amir Taaki Subject: Re: [Bitcoin-development] BIP process X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Oct 2014 19:28:41 -0000 Sounds like this is what you're after, it's a fairly new feature: https://github.com/blog/1375%0A-task-lists-in-gfm-issues-pulls-comments I've been meaning to use it in a PR to try it out. Cory On Wed, Oct 15, 2014 at 5:36 AM, Wladimir wrote: >> 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 > > ------------------------------------------------------------------------------ > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push notifications. > Take corrective actions from your mobile device. > http://p.sf.net/sfu/Zoho > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development