-
-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Contributing guideline #124
Comments
In the contributing guide, will commits need to have I'm not sure if enforcing this would need to deploy specific bot accounts, I've never enforced this kind of setup for a GH repository. |
Maybe we can also scrap some documentation from here : Or even link it, I'm not sure if it's relevant but from what I see for PR names, it might be. There would also be the following benefits according to the "specification" of conventional commits :
|
No, I don't think we need to bother ourselves with GPG nonsense, neither with developer certificate of origins.
This is not relevant. For the conventional stuff, I feel like you are trying to solve a technical problem. |
Are these technical problems, something we should actively try to solve in order to have lesser friction for handling new contributions/reviewing and release maintenance ? Or this is not a key focus right now, as other things needs to be polished, first ? |
We should create a contributing guideline. This should include our commit conventions (following nixpkgs) and a logging policy (as mentioned in #121). Ideally, we would have a
CONTRIBUTING.md
file that is linked from the README.The text was updated successfully, but these errors were encountered: