Contributing guidelines #58

Open
opened 2019-06-10 09:49:20 +00:00 by b3yond · 1 comment
Owner

Author: @b3yond Posted at: 18.10.2018 15:55

When you see this project and don't know the maintainers personally, it is hard to know where to start.

Other projects have contributing guidelines for this. A nice guide how to add them is here: https://help.github.com/articles/setting-guidelines-for-repository-contributors/

Against which branch should I make pull requests? How do I write an extension? ... I'm not sure if we have enough questions to answer to make this long, but short contribution guidelines are even better than long, and way better than none

Author: @b3yond Posted at: 18.10.2018 15:55 When you see this project and don't know the maintainers personally, it is hard to know where to start. Other projects have contributing guidelines for this. A nice guide how to add them is here: https://help.github.com/articles/setting-guidelines-for-repository-contributors/ Against which branch should I make pull requests? How do I write an extension? ... I'm not sure if we have enough questions to answer to make this long, but short contribution guidelines are even better than long, and way better than none
Author
Owner

Author: @git-sid Posted at: 19.10.2018 10:20

maybe we could use the git-flow model to organize our project. Here's a nice way of adding it to the user workflow https://github.com/petervanderdoes/gitflow-avh .
That way, new contributors can create a feature branch, develop the feature and create merge request when the feature is finished.

Author: @git-sid Posted at: 19.10.2018 10:20 maybe we could use the [git-flow](https://nvie.com/posts/a-successful-git-branching-model/) model to organize our project. Here's a nice way of adding it to the user workflow https://github.com/petervanderdoes/gitflow-avh . That way, new contributors can create a feature branch, develop the feature and create merge request when the feature is finished.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: b3yond/ticketfrei#58
No description provided.