You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of the writing of this issue, this project shows 2 out of 9 green checkmarks on the iec63131 project compared to community standards page (screenshot below).
While that is one measure of completeness, it does not cover all aspects of a complete GitHub project setup.
The following tasks are proposed to close this issue (subject to discussion, revision and agreement)
leverage GitHub teams to control permissions in a role-based way, and give higher privileges to more stakeholder nominated contributors (counter the increased privileges with stricter PR policies, see item 3)
create pull request and issue templates
set stricter rules for pull requests to main (merge restrictions, mandatory issue links, minimum and/or specific reviewers)
write best practices (in README) for; commit message wording, pull request title and description, issue closure checklists
How this project compares with community standards as of 2023-09-25:
The text was updated successfully, but these errors were encountered:
As of the writing of this issue, this project shows 2 out of 9 green checkmarks on the iec63131 project compared to community standards page (screenshot below).
While that is one measure of completeness, it does not cover all aspects of a complete GitHub project setup.
The following tasks are proposed to close this issue (subject to discussion, revision and agreement)
main
(merge restrictions, mandatory issue links, minimum and/or specific reviewers)How this project compares with community standards as of 2023-09-25:
The text was updated successfully, but these errors were encountered: