From: odinn <odinn.cyberguerrilla@riseup.net>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] BIP process
Date: Mon, 20 Oct 2014 00:33:34 +0000 [thread overview]
Message-ID: <5444585E.5080600@riseup.net> (raw)
In-Reply-To: <2753630.UjohjSx8jx@1337h4x0r>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Earlier in the discussion I suggested Discourse so that the BIP page
would be able to look smoother and draw more input.
Unsystem forum is run on Discourse and has twitter, github, and e-mail
integration.
For those who haven't explored it, here is what that looks / feels like:
https://forum.unsystem.net/
I'm curious as to why this sort of solution should or should not be
considered from someone else's perspective. In the end, whatever
works best for all concerned, I'm fine with it, but I'd like to hear
more about people's thoughts on Discourse. (I kind of like the feel
of it.)
xor wrote:
> On Wednesday, October 15, 2014 10:29:43 AM Wladimir wrote:
>> B) I also think it makes sense to move the BIP discussion (both
>> about the BIP process and individual BIPs) to a separate mailing
>> list.
>>
>> bitcoin-development currently has a dual function: discussion of
>> Bitcoin Core implementation concerns, as well as global changes
>> to Bitcoin (in the form of BIPs).
>>
>> This makes the list too busy for some people, but it is critical
>> that everyone writing a Bitcoin node or client is up-to-date
>> with proposals and can comment on them.
>
> I joined the list when Bitcoin was already in the 10-billions of
> market capitalization, and it actually really surprised me how low
> the traffic is here given the importance of Bitcoin.
>
> So as a random stranger to the project, I would vote against that
> if I was allowed to. There really should be *more* discussion here,
> and splitting the list up won't help with that.
>
> Greetings
>
>
>
> ------------------------------------------------------------------------------
>
>
>
>
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
>
- --
http://abis.io ~
"a protocol concept to enable decentralization
and expansion of a giving economy, and a new social good"
https://keybase.io/odinn
-----BEGIN PGP SIGNATURE-----
iQEcBAEBCgAGBQJURFhXAAoJEGxwq/inSG8Cpc0H+wZauz7iOj4XZJSI3VBv+5WL
YAe8kDSOpa5ZprFntsFfKVU+cmSjXckPjCRI9+LsrfTR2L+VjAimjQTct1m6oRAo
+5ZQ8Tn2CLEVRJRUzd8zbW8QPMuQCdzvwjs1oq8anaAPdwseEC/QhTZY6Av1MB8y
nH+05mMu4YeF3RRIyjXgvxDiBBK3knoaBkbsORkVbIb7MojUBy7FnsS1JFmSs8wv
XwWnkmFjVlhC8wSQYohcTWdJablxjpKRFq1ZNgDtIoXEi0dsC+G9Gc+8xub4hA/Y
nDk85ihX17TBbB47SOJEAdpGrJjkb8OvdX2ubLnQPYth82wX/MWJTTdv2a4JGik=
=uYGH
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2014-10-20 0:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-15 8:29 [Bitcoin-development] BIP process Wladimir
2014-10-15 9:22 ` Gregory Maxwell
2014-10-15 9:36 ` Wladimir
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 [this message]
-- 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=5444585E.5080600@riseup.net \
--to=odinn.cyberguerrilla@riseup.net \
--cc=bitcoin-development@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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