search

bitcoin-core / bitcoincore.org

Bitcoin Core project website
https://bitcoincore.org/
MIT License
603 stars 470 forks source link

Remove roadmap from 2015 #848

Closed maflcko closed 2 years ago

maflcko commented 2 years ago

The roadmap has many issues:

Fix all issues by removing it.

I think in the future it might be better for contributor(s) to share roadmaps not on this project's website, but on the appropriate mailing list, a blog, or a GitHub gist, or somewhere else. Also, general bitcoin education content is better hosted on websites dedicated to hosting educational content.

katesalazar commented 2 years ago

Hi, please forgive me for stacking just a couple of small immediate thoughts

On Mon, Jan 17, 2022 at 12:32 PM MarcoFalke @.***> wrote:

The roadmap has many issues:

  • It is outdated and (obviously) does not reflect the current state.

Why not just append a text telling this?

  • It implies that there is a unique roadmap for the whole project. However, practically each contributor has their own roadmap.

Present this as a feature. Again, why not just append a text telling this?

  • The embedded video is likely a GDPR cookie violation.

Fix all issues by removing it.

I think in the future it might be better for contributor(s) to share roadmaps not on this project's website, but on the appropriate mailing list, a blog, or a GitHub gist, or somewhere else. Also, general bitcoin education content is better hosted on websites dedicated to hosting educational content.

You can view, comment on, or merge this pull request online at:

https://github.com/bitcoin-core/bitcoincore.org/pull/848 Commit Summary

File Changes

(5 files https://github.com/bitcoin-core/bitcoincore.org/pull/848/files)

Patch Links:

— Reply to this email directly, view it on GitHub https://github.com/bitcoin-core/bitcoincore.org/pull/848, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMRS4W7NTT7E3LCBYJALD33UWP453ANCNFSM5MEOJQAQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you are subscribed to this thread.Message ID: @.***>

katesalazar commented 2 years ago

Hi, please forgive me for stacking just a couple of small immediate thoughts

The roadmap has many issues:

  • It is outdated and (obviously) does not reflect the current state.

Why not just append a text telling this?

  • It implies that there is a unique roadmap for the whole project. However, practically each contributor has their own roadmap.

Present this as a feature. Again, why not just append a text telling this? better yet, write a new article telling how those articles are obsolete, and link it easily from a postscript in the old articles

  • The embedded video is likely a GDPR cookie violation.

Fix all issues by removing it.

I think in the future it might be better for contributor(s) to share roadmaps not on this project's website, but on the appropriate mailing list, a blog, or a GitHub gist, or somewhere else. Also, general bitcoin education content is better hosted on websites dedicated to hosting educational content.

michaelfolkson commented 2 years ago

ACK

It seems reasonable not to have historical bitcoin-dev mailing list posts also stored on the bitcoincore.org site.

The embedded video is likely a GDPR cookie violation.

Can you explain why embedded video links are likely a GDPR cookie violation? Do you have any further details on this?

maflcko commented 2 years ago

Can you explain why embedded video links are likely a GDPR cookie violation? Do you have any further details on this?

Links aren't an issue, but iframes might be.

TheBlueMatt commented 2 years ago

The website is not hosted in the EU, GDPR does not apply. It seems wasteful to break the many links to this post - maybe add an outdated warning instead?

maflcko commented 2 years ago

Not a lawyer, but I am pretty sure that GDPR applies based on the location of the individual that the data is collected from, not the location of the website server? Otherwise, Google LLC could trivially avoid their fines (https://www.cnil.fr/en/cnils-restricted-committee-imposes-financial-penalty-50-million-euros-against-google-llc, ...) by claiming that "us-east-1b" or so served the requests.

Happy to keep the sites and add a "Archived" note instead. I removed them because there are superior and more complete sources. (For example optech on tx fee savings, also taking into account taproot). If they are kept, I think at the very least they should be removed from the navigation bar. Currently it is the first item in the "FAQ" dropdown, implying that this is recommended reading material for users.

michaelfolkson commented 2 years ago

Happy to keep the sites and add a "Archived" note instead. I removed them because there are superior and more complete sources. (For example optech on tx fee savings, also taking into account taproot). If they are kept, I think at the very least they should be removed from the navigation bar. Currently it is the first item in the "FAQ" dropdown, implying that this is recommended reading material for users.

Agreed, the above sounds like a good approach. Definitely shouldn't be in the FAQ dropdown. I'm not sure how many links there are to this post on bitcoincore.org hence I'm unclear on the impact of removing it entirely. But attempting immutability of links seems like a good goal for this site.

TheBlueMatt commented 2 years ago

Not a lawyer, but I am pretty sure that GDPR applies based on the location of the individual that the data is collected from, not the location of the website server? Otherwise, Google LLC could trivially avoid their fines (https://www.cnil.fr/en/cnils-restricted-committee-imposes-financial-penalty-50-million-euros-against-google-llc, ...) by claiming that "us-east-1b" or so served the requests.

I'm tempted to reply with a Pirate-Bay-style "just because you write a law that says it applies to me does not mean it applies to me if I don't live in your country" response :) Part of the Google issue is they actually have corporate subsidiaries, operations, and generally do business in Europe. A random static site hosted in the US does not :p.

Happy to keep the sites and add a "Archived" note instead. I removed them because there are superior and more complete sources. (For example optech on tx fee savings, also taking into account taproot). If they are kept, I think at the very least they should be removed from the navigation bar. Currently it is the first item in the "FAQ" dropdown, implying that this is recommended reading material for users.

SGTM.

Sjors commented 2 years ago

For stuff with lots of inbound links, I also prefer not deleting it.

maflcko commented 2 years ago

lots of inbound links

There shouldn't be too many links: https://duckduckgo.com/?q=%22bitcoincore.org%2Fen%2F2015%2F12%2F23%2Fcapacity-increases-faq

static

Is it static if the content is <iframe> youtube.com/watch <...? I am actually hoping to see a GDPR lawsuit where the defendant isn't FAANG (is that called MAANG now?). If https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-January/019741.html is also covering the entity that hosts this website, it might be worth to eat the risk.

TheBlueMatt commented 2 years ago

lots of inbound links

There are various news articles and social media posts at the time covering the related ML post, and this document is rather historical.

maflcko commented 2 years ago

Created #850 for discussion