> • I propose that BIPs be wiki pages, with a social convention that the > Author gets final word if any editing wars break out.
That's a good idea. What about using GitHub's Wiki feature for BIPs? They support MarkDown which is easy to read in text editors so we could someday create a repo with all finalized BIPs. That's a lot easier than importing a mediawiki dump. The last time en.bitcoin.it went down I tried to setup a static mirror and that was nearly impossible without a full LAMP stack. Also, BIPs should only contain images when absolutely necessary. > • If he's willing, I propose that Amir take the role of BIP editor. ack > • I think bitcoin is still too small to have a specialized > "bitcoin-ideas" mailing list; I propose that new potential BIPs be > discussed either here or on the bitcoin-dev mailing list. ack ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct _______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
