3 ms·
> the last commit was in 2019 with a bunch of open PRs and issues I don’t see much of a problem with that. It’s a spec, and is probably considered complete by
by codetrotter 4y ago
> the last commit was in 2019 with a bunch of open PRs and issues
I don’t see much of a problem with that. It’s a spec, and is probably considered complete by its authors. The issues and PRs are mostly people wanting to add links to more implementations of the spec to the README. That’s understandable but also not really necessary.
- dwaite 4y agoPer the original comment, that doesn't really show stewardship though. If you do not believe a PR or issue to be valid, you close it. If you are literally not willing to accept any PRs or issues, turn the feature off.
- layer8 4y agoWhat does it matter, assuming the specification is clear and unambiguous?
- dwaite 4y agoif it was clear, unambiguous, and had proper stewardship, there wouldn't be open issues and PRs.
- codetrotter 4y agoI’m not sure if it’s even possible to turn off PR for a repo on GitHub. One of the replies at https://stackoverflow.com/questions/27957454/how-to-disable-pull-requests-in-github https://stackoverflow.com/questions/27957454/how-to-disable-... seems to indicate that it is now possible since quite recently, but the linked post does not seem directly about disabling PRs. Either way, we don’t know if they really don’t want any issues or PRs opened at all just because they have some old issues and PRs still open.