search

ACS-Community / ACS-Docker-Image

Docker context for official acs community docker images on https://hub.docker.com/u/acscommunity
MIT License
1 stars 1 forks source link

Decide on a Workflow and write a CONTRIBUTING.md #14

Closed dneise closed 4 years ago

dneise commented 4 years ago

I propose to go for a workflow, which is well known in the community, and light weight, so we loose not much time. So I propose the github flow. https://guides.github.com/introduction/flow/

In order to inform newcomers of or decision, we need to make it easy to find. Github does this by a special file called CONTROBUTING.md.

We should write one. To make our lives easy, we should actually copy one. I found this. https://gist.github.com/PurpleBooth/b24679402957c63ec426

dneise commented 4 years ago

So in Slack @emiliogq proposed this workflow:

https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow

dneise commented 4 years ago

While I was more inclined to use this one:

https://www.atlassian.com/git/tutorials/comparing-workflows/feature-branch-workflow

By the way .. both are really good summaries of workflows ... and CTA should decide to use either of them, instead of cooking up their own.

dneise commented 4 years ago

So we go for a simplified version of the GitFlow workflow ... I will write a document to explain what we wanna do .. and @emiliogq can review it, to make sure we understand what we want. Then we link this document in the README, so new people who want to help, immediately know the rules of the game :D

dneise commented 4 years ago

done in c9692e931767e2cbb266338fe53afafba6674cc1