Website for gathering the thoughts of core devs

[Nicolas Dorier]

Today I worked on a small website so core devs can upload easily their thoughts about the block size and present it to the community.

Core devs, please submit your thoughts (or at least what BIP you approve/disapprove) for each of those BIPs.
You need to submit a formatted message signed with your PGP key to edit your profile, I am using PGP pubkeys I found in bitcoin.org github.

Please let me know of any dev participants to add in this matrix, as well as other complete proposal I forgot.

If you are a dev in the list:

• Click on your name in the main page
• Click on Edit
• Submit a PGP signed, formatted message (HTML accepted) with your approval/disapproval and opinion on each BIP as in the example

If you don't have time, at least tell us what you reject completely and what would you be ready to approve.

Url : http://bipsxdevs.azurewebsites.net/
Github : https://github.com/NicolasDorier/BIPxDevs
Sample of message signed : https://aois.blob.core.windows.net/public/BlockSize/DevsPost/zsample.sig

Hope it help,
(Let me know if it breaks, I am using a small free website of Azure with quota limits )

[1714466998]

1714466998

[1714466998]

1714466998

[unamis76]

This is pretty good work! Most devs have already posted their opinions but on several sites, on different posts, scattered around. It would be nice if devs noticed this and posted their opinions in the same place.

[Nicolas Dorier]

This is pretty good work! Most devs have already posted their opinions but on several sites, on different posts, scattered around. It would be nice if devs noticed this and posted their opinions in the same place.

Yes their thoughts are scattered everywhere, and we don't even know what they approve or completely disapprove. It will bring some clarity, I hope.

[hdbuck]

+1 that would be quite nice, for a start.

hope the devs would give this a chance.

[ashour]

Today I worked on a small website so core devs can upload easily their thoughts about the block size and present it to the community.

Core devs, please submit your thoughts (or at least what BIP you approve/disapprove) for each of those BIPs.
You need to submit a formatted message signed with your PGP key to edit your profile, I am using PGP pubkeys I found in bitcoin.org github.

Please let me know of any dev participants to add in this matrix, as well as other complete proposal I forgot.

If you are a dev in the list:

• Click on your name in the main page
• Click on Edit
• Submit a PGP signed, formatted message (HTML accepted) with your approval/disapproval and opinion on each BIP as in the example

If you don't have time, at least tell us what you reject completely and what would you be ready to approve.

Url : http://bipsxdevs.azurewebsites.net/
Github : https://github.com/NicolasDorier/BIPxDevs
Sample of message signed : https://aois.blob.core.windows.net/public/BlockSize/DevsPost/zsample.sig

Hope it help,
(Let me know if it breaks, I am using a small free website of Azure with quota limits )

Nice and useful website, but you should change the design a bit. And get a cpanel hosting with a domain and the site could get some good traffic.

[hexafraction]

Nice and useful website, but you should change the design a bit. And get a cpanel hosting with a domain and the site could get some good traffic.

Why would the OP necessarily want cPanel hosting? What tangible benefit to the user does having cPanel have that simply hosting as it is (with a higher quota) doesn't? I agree however, that the design could be tweaked a bit.

[Nicolas Dorier]

I accept github PR, I did this website in one day, it is just a utility website for getting the job done and present nicely to the user. (a quick & dirty site which does the job)
Design is not my thing

I don't plan gathering traffic, I just want it to serve its temporary purpose : Inform users and gather thoughts of core devs.

[CounterEntropy]

I accept github PR, I did this website in one day, it is just a utility website for getting the job done and present nicely to the user. (a quick & dirty site which does the job)
Design is not my thing

I don't plan gathering traffic, I just want it to serve its temporary purpose : Inform users and gather thoughts of core devs.

Not sure if it is for core devs only or any proposal with merit can get in here. If the later is true, then you might like to include this one - https://bitcointalk.org/index.php?topic=1154536.0

[Nicolas Dorier]

I accept github PR, I did this website in one day, it is just a utility website for getting the job done and present nicely to the user. (a quick & dirty site which does the job)
Design is not my thing

I don't plan gathering traffic, I just want it to serve its temporary purpose : Inform users and gather thoughts of core devs.

Not sure if it is for core devs only or any proposal with merit can get in here. If the later is true, then you might like to include this one - https://bitcointalk.org/index.php?topic=1154536.0

To keep the table readable, I will just mention informatively and if a voter wants to get it included, I will add it.
I added other devs in the list as well.

[jl2012]

Does it mean Luke is neutral to other proposals?

[Nicolas Dorier]

It means that he did not responded to other BIP, so we can interpret as either neutral or "I have not read it", which are basically the same.

[dexX7]

I'd consider Meni's proposal actually more as an extension: it could be applied on 1 MB blocks, but also on 8 MB blocks. And the mechanism seems to be soft-forkable. (edit: just to clarify: this shouldn't imply I don't consider it as valuable item on the list!)

[Nicolas Dorier]

I'd consider Meni's proposal actually more as an extension: it could be applied on 1 MB blocks, but also on 8 MB blocks. And the mechanism seems to be soft-forkable. (edit: just to clarify: this shouldn't imply I don't consider it as valuable item on the list!)

Those BIP are not mutually exclusive, several of them can be implemented if they reach consensus. I don't think it as a competition between all of them, but as a way to see which one can be fork planned without blood.