Add contributing guidelines #148
Conversation
|
This is an excellent start, thank you. There are a few items in the original issue that aren't addressed with this patch, so we should either migrate those to a new issue or keep the issue open. |
|
Something I was debating with myself was if it should only be contributors to the website ? How about the persons doing community work but not website related? That page should that about page work with #121 ? Or perhaps we want to highlight contributors (with their actions in https://taiwangoldcard.com/community ?) Edit: this aimed to be in #149 |
|
Are you on the right issue, Eric ? :) Maybe #149 ? I think we'll end up with two documents:
|
|
@fifieldt 🤦 my hundred tabs opened that got me |
| @@ -0,0 +1,60 @@ | |||
| ## Communication | |||
|
|
|||
| We use [slack](https://goldcardcommunity.slack.com/) for talking about all `#website` matters. | |||
There was a problem hiding this comment.
If we list that one, we should be aware that this will be public.
Will guest be allowed to that channel? Someone at g0v just asked me where things get coordinated. I think having "guests" to that channel might be great?
The chat might be better for quick feedbacks loop than github issues, and keep the interest of outsider contributors
There was a problem hiding this comment.
By default they need an invite until we let them in if I'm not wrong.
I like the guest model, it could be a good taste of what it's like to be in the gold card community.
|
Yep still missing things like collaboration principles. What should I fill for that? |
|
Open a new PR that's not on my fork's master branch. #154 |
Fixes #41
Added some guidelines and the flow for CMS too. Intending to publish a message in our line group to get content contributors.