-
Notifications
You must be signed in to change notification settings - Fork 351
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Should This Repository Be Archived? #267
Comments
The repo's README should specifically state that it requires Yarn 3.x not Yarn 1.x for starters, and provide some guidance on configuring it, not just a link to the Yarn website, since Yarn 3 setup even caught me by surprise. That's the cause of some of the open issues where users encountered Yarn errors and might have even given up on bothering to try to use Substrate all together. It's a show-stopper for some. I'd hate to think of how many users don't get passed that step but don't spend the time digging through the open issues for the solution, or just notice how long it's been since it was last updated and just walk away immediately. I tried to created a PR to Dockerise it here #261 since that way users are less likely to get stumped during installation steps too, but it doesn't seem like anyone was available or interested in reviewing it, so I haven't touched the repo since. Even the Substrate repo itself has a Docker installation option and README https://github.com/paritytech/substrate/tree/master/docker The original intention was to tackle the issues tagged 'good first issue' and 'help wanted' next but I those issues are probably stale and need to be closed too. There are numerous open PRs and issues that have been open for more than 6 months often with simple fixes and should have been closed months ago, maybe those should be fixed before archiving it. This is all surprising given that this repo would likely be the goto repo for any user wanting to create a dapp on the Polkadot network that either interacts with smart contracts or directly with a one or more chains. |
I don't think this repo should be archive for the reasons @ltfschoen provides above. I'm working on getting it updated. Thanks for all your help @ltfschoen - it's very appreciated. It's unfortunate that this repo hasn't been a priority to be actively maintained and I'm sorry some of your PRs have been ignored for so long. I'll make sure the repo gets more attention. Your active involvement is much appreciated. |
The main branch has not seen a commit in over a year, it seems.
The text was updated successfully, but these errors were encountered: