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

Add a ways of working document #26

Closed
2 of 3 tasks
annakrystalli opened this issue Nov 22, 2018 · 9 comments
Closed
2 of 3 tasks

Add a ways of working document #26

annakrystalli opened this issue Nov 22, 2018 · 9 comments
Assignees
Labels
community issues releated to building a healthy community

Comments

@annakrystalli
Copy link
Collaborator

annakrystalli commented Nov 22, 2018

To detail the levels of involvement of official members so that expectations of their time are reasonable.


Update

This should be closed soon - requires #74 to close

Outstanding things to add

@pherterich
Copy link
Collaborator

pherterich commented Nov 22, 2018

  • preferred comms for individuals
  • percentage allocated to project
  • expectations on asynchronous response time
  • basic rules for when to use which comms tool

@pherterich
Copy link
Collaborator

pherterich commented Nov 22, 2018

  • commitment to make the implicit explicit and dedicate time to add to contributing guidelines etc.

@sgibson91
Copy link
Member

Guidelines on good commit messages: https://chris.beams.io/posts/git-commit/

@KirstieJane
Copy link
Collaborator

@sgibson91 - I'm going to move that blog post to #16 - I think it should be in contributing guidelines

@KirstieJane
Copy link
Collaborator

KirstieJane commented Nov 23, 2018

  • If we find errors or omissions in other packages we'll open an issue in those open source packages and try to fix them (including documentation)

@KirstieJane KirstieJane added the community issues releated to building a healthy community label Nov 23, 2018
@KirstieJane
Copy link
Collaborator

KirstieJane commented Nov 23, 2018

  • Triage in weekly meetings
  • Close issues when they're completed
  • Review often

@KirstieJane
Copy link
Collaborator

KirstieJane commented Nov 28, 2018

  • Try not to use "request changes" as only that member of the team can then merge the PR

@pherterich
Copy link
Collaborator

@KirstieJane @r-j-arnold with the cleaning up branches outstanding until we have a conversation at the next sprint (and covered by reminders such as #177 ), are we okay closing this issue and start a new one for anything else that comes up?

@r-j-arnold
Copy link
Collaborator

Yeah sure, closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community issues releated to building a healthy community
Development

No branches or pull requests

5 participants