search

pyladies / global-organizing

Repository to track global organizing
46 stars 14 forks source link

Issue 49: So you've started a project team tips. #51

Closed BethanyG closed 4 years ago

BethanyG commented 4 years ago

https://github.com/pyladies/global-organizing/issues/49
Added the following to pyladies-projects-overview.md:

So a project's been started - now what?

We recommend making a few up front "administrative" decisions around membership, communication, & contributions. Documenting how the project team will be "run" helps volunteers understand where & how they can best contribute. These agreements can be added to the team project issue, the project repo README.md, or any other place that's accessible to all team members:

  • How will members ask/apply to join your project team? Are there expectations and/or qualifications you'd like to articulate?
  • What will be the process for onboarding new project members?
  • How will the group communicate with one another? How will members stay informed & coordinated?
  • What will be the workflow for contributions coming into the group? What will be the review process for issues & suggestions?
  • How will the issues / units of work / project areas be managed? How will you track progress & challenges?

Any of the global-organizing admins or existing project leads can also help you with tools & processes that have worked for them, or with any repo ,project board, or wiki setup needed for your team. Just reach out on Slack, or open an issue in this repository.

BethanyG commented 4 years ago

We can also add some of this to the issue template, if that's a better place for it.

lorenanicole commented 4 years ago

This is awesome, thanks @BethanyG !