On 25 May 2013 07:46, Zooko Wilcox-OHearn wrote: > jgarzik wrote: > > 1) Rule changes. We don't want these. > > In general? What constitutes a rule change? > > For example, if I understand correctly (from what Gavin said at > Bitcoin 2013), there is a move afoot to lift the block size limit. > Although, when I went to confirm my understanding by reading the > bitcoin-development list archives, I don't see mention of this. Is > there another forum I should be reading if I want to follow Bitcoin > development? > > Anyway, I hope that there are some rule changes that you would > consider for Bitcoin, although I recognize there are vast classes of > such changes that you wouldn't. > > I'm trying to figure out what's the most productive way to show you, > and everyone, candidates for such changes. Things that are definitely > not suitable for merging to trunk tomorrow, but might be suitable in a > year or two, or "Next Time We Have A Hardfork". > > I don't think alternative bitcoin-clones are the best venue for those. > Although they are certainly good venues for changes which can never > make it into Bitcoin. > > Perhaps the best venue for such a thing is just to fork bitcoin.git on > github. > It might be an idea to have 'rule change' fixes and 'bug fix' releases go out separately > > Regards, > > Zooko Wilcox-O'Hearn > > Founder, CEO, and Customer Support Rep > > https://LeastAuthority.com > > > ------------------------------------------------------------------------------ > Try New Relic Now & We'll Send You this Cool Shirt > New Relic is the only SaaS-based application performance monitoring service > that delivers powerful full stack analytics. Optimize and monitor your > browser, app, & servers with just a few lines of code. Try New Relic > and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development >