The discussion was brought up during this weeks Tech. Governance session about ways to solidify RChips that are in the works (from draft to final) and how other open source projects do it (namely Ethereum). As of right now anyone can create an RChip and it's considered automatically approved if it meets some criteria. This RChip is about quantifying that criteria with some automation tools.
Describe the solution you'd like
One solution would be to let the submission process be as is, and as issue receives a specific tag, it will be processed by a bot/tool that retreives issue body, parses it, checks if it meets certain criteria, such as:
Correct pronunciation.
Includes all the necessary fields.
Does not use html tags but rather github flavored markdown.
If all the criteria are met, then the RChip can receive a unique identifier and be recorded in the repository (or maybe pushed to Rchain network itself, because why not). Storing them as files also allows us to generate static pages with something like Jekyllrb to make RChips viewable outside of Github.
Ethereum Foundation also has a tool called eip_validator that goes through markdown files and makes sure they all meet certain criteria. If possible rewrite it for Node.js rather than using Ruby as a dependency.
Describe alternatives you've considered
The alternative would be to force everyone to submit pull requests with a draft but that process is too manual and would discourage participation, or we can leave everything as is and check for criteria manually.
TheoXD
commented
4 years ago
Is your feature request related to a problem?
The discussion was brought up during this weeks Tech. Governance session about ways to solidify RChips that are in the works (from draft to final) and how other open source projects do it (namely Ethereum). As of right now anyone can create an RChip and it's considered automatically approved if it meets some criteria. This RChip is about quantifying that criteria with some automation tools.
Describe the solution you'd like
One solution would be to let the submission process be as is, and as issue receives a specific tag, it will be processed by a bot/tool that retreives issue body, parses it, checks if it meets certain criteria, such as:
If all the criteria are met, then the RChip can receive a unique identifier and be recorded in the repository (or maybe pushed to Rchain network itself, because why not). Storing them as files also allows us to generate static pages with something like Jekyllrb to make RChips viewable outside of Github.
Ethereum Foundation also has a tool called eip_validator that goes through markdown files and makes sure they all meet certain criteria. If possible rewrite it for Node.js rather than using Ruby as a dependency.
Describe alternatives you've considered
The alternative would be to force everyone to submit pull requests with a draft but that process is too manual and would discourage participation, or we can leave everything as is and check for criteria manually.