Rooba
/
wagtail
mirror of https://github.com/wagtail/wagtail.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Updated Packaging Team (markdown)

Vince Salvino 2022-10-21 16:34:36 -04:00
parent 93e8e3bbd0
commit 62c970af31
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
Packaging-Team.md

@ -6,17 +6,17 @@ NOTE: Packaging team is in DRAFT status.
> To improve the experience of discovering, using, and creating Wagtail packages.
A Wagtail package is usually a 3rd-party (i.e. not part of Wagtail core) Python `pip` package which provides additional functionality to Wagtail. This team will take on the work, whether technical or marketing oriented, to improve the state of the packaging ecosystem. By growing the quantity and quality of 3rd-party Wagtail packages, we hope to grow the adoption of Wagtail as a whole.
A *Wagtail package* is usually a 3rd-party (i.e. not part of Wagtail core) `pip` package which provides additional functionality to Wagtail. This team will take on the work, whether technical or marketing oriented, to improve the state of the packaging ecosystem. By growing the quantity and quality of 3rd-party Wagtail packages, we hope to grow the adoption of Wagtail as a whole.
This team is not a package maintenance service. Instead we hope to create tools and resources for package maintainers.
### Membership
The team’s membership is open to all, introduce yourself in [#package-maintainers](https://app.slack.com/client/T0K33F93J/C032RLK62PQ) if you’re interested in joining. This channel is also used as an open forum for packaging-related topics.
The team’s membership is open to all: introduce yourself in [#package-maintainers](https://app.slack.com/client/T0K33F93J/C032RLK62PQ) if you’re interested in joining. This channel is also used as an open forum for packaging-related topics.
Membership terms are 6 months. The team lead will be assigned by the Wagtail Core Team with consultation from the Packaging Team.
The team lead will be assigned by the Wagtail Core Team, and will be responsible for reporting progress back to the Core Team.
We meet every two weeks to discuss everyone’s recent progress and next steps. At the end of each meeting, all participants should each have volunteered for an action, which they must strive to complete before the next meeting. Meeting notes and actions are public for future and past meetings.
We meet every two weeks to brainstorm, and discuss everyone’s recent progress and next steps. At the end of each meeting, all participants should each have volunteered for an action, which they must strive to complete before the next meeting. Meeting notes and actions are public for future and past meetings.
In-between meetings, we collaborate via Slack using the channel as an open forum, GitHub to keep track of actions, and collaborate on specific issues & pull requests.