public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Eric Lombrozo <elombrozo@gmail.com>
To: Nicolas Dorier <nicolas.dorier@gmail.com>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Core Devs : can you share your thoughts about all BIPs on this website ?
Date: Thu, 20 Aug 2015 20:45:56 -0700	[thread overview]
Message-ID: <3C185967-B56C-4A4E-AEBD-55436FC560D1@gmail.com> (raw)
In-Reply-To: <CA+1nnr=gMkwse5s8u+dDWfB4V7uswU8c-R7dRKQ=7j8P5w0mgQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3209 bytes --]

I think everyone who has contributed any commits to the Bitcoin Core project should have a say in this.


> On Aug 20, 2015, at 8:38 PM, Nicolas Dorier via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org <mailto:bitcoin-dev@lists.linuxfoundation.org>> wrote:
> 
> Thanks, btcdrak, I just added the column and you in the list. (looks nicer)
> 
> What I am calling "core devs" in the website is only "commit access people", should I rename this group ?
> I just want a way to improve readability of the website by grouping, I am open to all subjection on different way of grouping. 
> 
> I'm good for adding Mike Hearn, Adam Back, Mark Friedenback, Jorge Timons, Nick Szabo, Meni Rosenfeld, Charlee Lee.
> 
> If some of you are reading this list, please send me your PGP public key.
> For the others, any idea where I can hunt their PGP public keys ?
> 
> On Fri, Aug 21, 2015 at 12:10 PM, Btc Drak <btcdrak@gmail.com <mailto:btcdrak@gmail.com>> wrote:
> I was looking at this site recently and it's not very clear that by
> clicking the name you get their opinion. I would make that a separate
> column stated, Technical Opinion.
> 
> I think you need to include more of the developers/technical people,
> Adam Back, Mark Friedenback, Jorge Timons, (all of who are core
> developers). You need
> Peter Todd is a core dev btw, as is thebluematt.
> 
> You need other experts, I would include Nick Szabo, Meni Rosenfeld,
> Charlie Lee might be a good one. You should get the pools on there
> too.
> 
> You're missing Mike Hearn of course.
> 
> My key is 0xE5D138F5E73A1AF2
> 
> 
> On Wed, Aug 19, 2015 at 5:57 AM, Nicolas Dorier via bitcoin-dev
> <bitcoin-dev@lists.linuxfoundation.org <mailto:bitcoin-dev@lists.linuxfoundation.org>> wrote:
> > I created a small website which show a chart of your approvals about various
> > BIPs (which you must fill by yourself with a signed pgp message)
> >
> > For each BIP, you can fill if you approve or not, and give comments. (HTML
> > accepted, so you can link stuff you your posts)
> >
> > It would help the community a lot, so I hope you will do it !
> > I'm open to add other important devs, big miners, or other proposal that I
> > missed.
> >
> > Please, respond on BTC Talk or github. (I don't read the mailing anymore
> > because of the spam :( )
> >
> > Link : http://bipsxdevs.azurewebsites.net/ <http://bipsxdevs.azurewebsites.net/>
> > BtcTalk Topic : https://bitcointalk.org/index.php?topic=1156164 <https://bitcointalk.org/index.php?topic=1156164>
> > Github : https://github.com/NicolasDorier/BIPxDevs <https://github.com/NicolasDorier/BIPxDevs>
> >
> > _______________________________________________
> > bitcoin-dev mailing list
> > bitcoin-dev@lists.linuxfoundation.org <mailto:bitcoin-dev@lists.linuxfoundation.org>
> > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>
> >
> 
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org <mailto:bitcoin-dev@lists.linuxfoundation.org>
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev


[-- Attachment #2: Type: text/html, Size: 5699 bytes --]

  reply	other threads:[~2015-08-21  3:45 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-21  3:38 [bitcoin-dev] Core Devs : can you share your thoughts about all BIPs on this website ? Nicolas Dorier
2015-08-21  3:45 ` Eric Lombrozo [this message]
2015-08-21  3:54   ` Nicolas Dorier
  -- strict thread matches above, loose matches on Subject: below --
2015-08-19  4:57 Nicolas Dorier
2015-08-21  3:10 ` Btc Drak
2015-08-21  4:45 ` Gregory Maxwell
2015-08-21  5:10   ` Nicolas Dorier
2015-08-21  9:09     ` Btc Drak
2015-08-21  9:32       ` Peter Todd
2015-08-21  9:29   ` Peter Todd
2015-08-21  9:31     ` Btc Drak
2015-08-21  9:35       ` Peter Todd
2015-08-21 10:55         ` Yifu Guo
2015-08-21 11:28           ` Btc Drak
2015-08-21 12:28             ` Yifu Guo
2015-08-21 13:18               ` Oliver Egginger
2015-08-21 13:34                 ` Will Madden
2015-08-21 17:31                   ` Oliver Egginger
2015-08-21 18:07                     ` Will Madden
2015-08-22  3:02             ` odinn
2015-08-21 16:58         ` Nicolas Dorier

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=3C185967-B56C-4A4E-AEBD-55436FC560D1@gmail.com \
    --to=elombrozo@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=nicolas.dorier@gmail.com \
    /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