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
How about adding a dedicated page with all the information about how to become a contributor? There's a lot of knowledge common for all rom-* projects so it feels wrong to duplicate it in CONTRIBUTING file in each repo.
This page could cover things like:
Code style guidelines (probably boils down to "run rubocop" to get feedback however I'm worried that people might be pushed by rubocop to do silly refactorings like breaking down a method into 2 because some artificial limit is exceeded etc.)
Basic design principles (avoid mutation, how OO is done in ROM, functional tidbits etc.)
Support interface (Equalizer, ClassMacros, Options etc.)
Git guidelines (esp regarding squashing, when to, when not to, what to write in commit messages)
How to get help and support from core contributors
How to find what to work on (it would be freaking cool to dynamically list issues tagged "help-wanted" there!)
The text was updated successfully, but these errors were encountered:
How about adding a dedicated page with all the information about how to become a contributor? There's a lot of knowledge common for all rom-* projects so it feels wrong to duplicate it in CONTRIBUTING file in each repo.
This page could cover things like:
The text was updated successfully, but these errors were encountered: