Re: [Bitcoin-development] Proposed BIP status changes
Shouldn't we be doing this in a GitHub PR rather than spamming up the ML? Not really. BIP changes should be discussed on the mailing list, that's the way to get community consensus (as specified in BIP1). 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
Re: [Bitcoin-development] Proposed BIP status changes
On Thursday, October 16, 2014 6:22:04 AM Wladimir wrote: Shouldn't we be doing this in a GitHub PR rather than spamming up the ML? Not really. BIP changes should be discussed on the mailing list, that's the way to get community consensus (as specified in BIP1). Wladimir Discussion vs simple ACKing. -- 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
Re: [Bitcoin-development] BIP process
On Wednesday 15. October 2014 11.36.58 Wladimir wrote: 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. I have been part of both the OSI (NEN) and the OASIS standards committees for a while, working on standards as a technical adviser. There I learned a lot about how to manage this process, maybe some ideas from such committees can be useful. The idea that one person owns a BIP makes total sense, (s)he is the only one that should be putting forward the BIP when its mature enough for making it final. Note that this can be already after its been implemented once or twice. So you have a phase where you have random people propose changes, which should all go in the public mailinglist, and they can be accepted by the owner without discussion. If anyone that sees that change has an objection to the change, (s)he speaks up and you follow group consensus. This means (and this is actually in an ISO standard ;) that consensus is reached when nobody is left objecting to the change. At some point the BIP is mature enough to vote on, at the discretion of the owner, and the owner puts it forward and requests a vote. If the above process was handled cleanly there is a very small chance of it being down-voted so an actual vote may not be needed (its hard to decide who gets a vote..). You obviously need a deadline for this and afterwards you mark the proposal final. Or you close it as needs more work. -- Thomas Zander -- 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
Re: [Bitcoin-development] BIP process
On Wednesday 15. October 2014 20.13.11 Mike Hearn wrote: Plus its moderation features suck, its mail archiving features suck, etc. It essentially has no redeeming features at all. Other than it being open source, an open platform with no lock-in 'features' and it works with everyone that uses the standards properly. Naturally, if an old version fails to function with Yahoo, I'm all for finding a different provider. Thats what open platforms, like Mailman, are about. -- Thomas Zander -- 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
Re: [Bitcoin-development] BIP process
15.10.2014 at 20:13 Mike Hearn wrote: For a project that is based on digital signatures, it's really bad that the mailing list is incompatible with Yahoo's mail signatures must be valid policy. # Mailman: Do not break existing DKIM signatures DEFAULT_SUBJECT_PREFIX = DEFAULT_MSG_HEADER = DEFAULT_MSG_FOOTER = Maybe you should remove these settings. They make little sense and cause apparently problems for some recipients. Also the mail body must not be altered through advertising or something else. - oliver -- 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