Proposal: Codeless Contributions with GitHub Issue Forms

[hugosenari]

tl;dr: Issues 'templates' (forms) -> GH Actions -> PR

Objective: reduce contribution friction

https://stefanbuck.com/blog/codeless-contributions-with-github-issue-forms

[cyntheticfox]

Contribution friction is... Kinda part of the point -- it's necessarily what makes it a "curation" instead of an exhaustive list.

Sure, there are checks that could be better automated, like checking per-section alphabetization and even enforcing proper-noun capitalization, but there are parts like ensuring the description is both accurate and useful and that the project is sufficiently developed where the criteria isn't so easy to pin down (how do you measure how developed a project is? How do you measure how useful a description is?), let alone turn into code -- if subjective opinions and biases should be codified at all (not a fan of doing that).

Otherwise, that's the purpose of our existing checks via lychee action and awesome-lint.

Do you see some particular addition of an action that would add value?

[hugosenari]

Happy flow today:
Someone found something nice
Someone create a PR (fork, edit, commit, open the PR)
Someone else curate it
If is good accept the merge

Sad flow today:
Someone found something nice
Someone create... nah too much work

The proposal:
Someone found something nice
Someone create a issue (with a form)
Someone else curate it
If is good add a tag to it
Bot prepare the PR (fork, edit, commit, open the PR)