Skip to content
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

docs: add CONTRIBUTING.md #37

Closed
fexolm opened this issue May 9, 2018 · 7 comments · Fixed by #142
Closed

docs: add CONTRIBUTING.md #37

fexolm opened this issue May 9, 2018 · 7 comments · Fixed by #142
Labels
discussion Discussion and planning prior to implementation is needed release blocker

Comments

@fexolm
Copy link
Contributor

fexolm commented May 9, 2018

We may need to add smth like contribution guideline which would formalize our workflow.
For example: we may add label "in progress" if someone currently working on task and remove it when switch on the other task.
It could save a lot of time if every team member would follow that rules.

@fexolm fexolm added the discussion Discussion and planning prior to implementation is needed label May 9, 2018
@quasilyte
Copy link
Member

Ok, makes sense.
We need CONTRIBUTING.md for sure.

@quasilyte quasilyte changed the title all: create contribution guideline CONTRIBUTING.md: create contribution guideline May 9, 2018
@quasilyte quasilyte changed the title CONTRIBUTING.md: create contribution guideline docs: add CONTRIBUTING.md May 9, 2018
@quasilyte
Copy link
Member

We also need to formalize how we tag issues and most commit messages.
It's not 100% precise and I have doubts sometimes (like in situation with this issue title),
but if we end up with exact rules, it'll be easier.

quasilyte pushed a commit that referenced this issue May 10, 2018
@fexolm
Copy link
Contributor Author

fexolm commented May 14, 2018

@quasilyte, closing?

@quasilyte
Copy link
Member

It lacks info about labels and workflow you bound to them.

@quasilyte
Copy link
Member

quasilyte commented May 14, 2018

You can close this and open more specific issues, if you like it more this way.
But in it's current state, the document is not good enough.

@quasilyte
Copy link
Member

@tengufromsky, if you have any issues figuring out how to contribute to this project,
feel free to leave your questions here.

@quasilyte
Copy link
Member

Related: #116.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion Discussion and planning prior to implementation is needed release blocker
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants