-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Suggest removing DappTools #5985
Comments
Hey @devtooligan, thanks for raising this. I support removing dapptools. Would you be interested in putting up a PR for this? If not, I can get to it this week. |
I'm happy to make the pr. Is it just a matter of going through and deleting all references to DappTools? Or is there something to be done with Gatsby? @minimalsm |
Yup just deleting the call-outs to dappnode. They'll be in a few non-English languages too but you should be able to search the codebase for them pretty easily. |
@minimalsm 👍🏽 on it! |
Closed by #6000 |
Anyone who would use the ethereum.org site to choose a development tool or framework is most likely a new or inexperienced user. Because DappTools is no longer supported, it could be difficult or even frustrating if a new dev chose DappTools based on its presence on the ethereum.org site, and then subsequently ran into a bug and couldn't get any support on the dapp.tools.chat after investing some time with it.
In reviewing the ethereum-org-website Add a developer tool guidelines:
Aside from the "free as a puppy" update to the README, there have not been any significant updates in months.
There are 135 open issues (not that that number is really that meaningful tbh) including bug fix requests like this one.
As a former (and current) DappTools user I can sincerely say that the Ethereum ecosystem owes a deep debt of gratitude to the core DappTools team for all they have done. And so, it is with heavy heart that I propose removing DappTools as a suggested developer tool and framework from ethereum.org
The text was updated successfully, but these errors were encountered: