25 Core team participation

Thibaud Colas edited this page 2024-07-31 16:53:00 +01:00

Unescape Escape

Table of Contents

• Core team onboarding
• New member responsibilities
• Core team offboarding

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

Core team members may be volunteers, or may have varying priorities at work which make regular commitments difficult. Taking this into account, we suggest the following minimum levels of participation:

• joining at least one meeting a month
• let the team know that you can't attend a meeting, by declining the calendar invitation or posting to #core-team
• on a fortnightly basis, at least one of:
  • submitting a PR (to any repo in the Wagtail organisation)
  • answering a question on Stack Overflow
  • reviewing a PR
  • triaging 5 issues
  • supporting a user on Slack
  • blogging about Wagtail

Core team onboarding

• Slack
  • Invite to #core-team channel
  • Add to list of people able to post to #announcements
• Add to GitHub team
• Add to Core team listings (Check whether they want to be listed with an affiliation):
  • Core Team page on the GitHub wiki
  • In CONTRIBUTORS.md
  • Wagtail.org core team page
• Add to PyPI organisation as a manager
• Invite to the calendar events for core team meetings
• Optionally assign someone to pair with them to familiarize with being on the core team

New member responsibilities

• Write an introductory blog post
• Add information to Core Team page on the GitHub wiki
• Note whether you want to be listed with an affiliation in CONTRIBUTORS.rst (or just make the PR yourself)

Core team offboarding

• GitHub org admin – remove from the Core GitHub team
• Core team – message the person saying we’re removing them from the core team listings, why
• GitHub org admin – remove from any of the thematic teams they were on
• GitHub org admin – check team memberships for any other team as appropriate
• GitHub org admin – review potential projects to archive under github.com/wagtail
• GitHub org admin – remove from the GitHub organization if they aren’t involved with any active project
• GitHub core team – remove from the core team wiki page
• GitHub core team – move from the "core team" list to the "alumni" list in CONTRIBUTORS.rst
• Slack admin – remove from the Posting permissions on the #announcements Slack channel
• Slack admin – remove from #core-team channel
• Wagtail admin – set account to inactive on wagtail.org
• Wagtail admin – remove admin rights from madewithwagtail.org
• Wagtail admin – remove admin rights from guide.wagtail.org
• Wagtail admin – remove name from https://wagtail.org/core-team
• npm admin – remove from wagtail organisation on npm
• PyPI packages admin – remove from PyPI organization
• PyPI packages admin – remove from all relevant Wagtail PyPI packages
• npm packages admin – remove from wagtail organization on npm, and relevant packages
• Vercel admin – remove from wagtail organization on Vercel
• Read the Docs admin – remove from the Wagtail project maintainers on RTD
• Read the Docs admin – remove from the sphinx-wagtail-theme project maintainers on RTD
• Algolia admin – remove from our DocSearch application
• Google Calendar - remove from core team meeting calendar events
• Open Collective – remove from wagtail organization admins
• YouTube – remove access to the channel

Home

• Slack
• Release schedule
• Roadmap
• Google Summer of Code

Teams

• Wagtail core team
  • Core team participation
• Wagtail sub teams
  • Accessibility team
    • Accessible image model working group
  • Performance team
  • UI team
  • Security team
  • Packaging team
  • Developer relations team
  • Sustainability team

How To

• Creating a new Wagtail release
• Creating a new TWIW email shot
• Edit ephemeral Squash sites
• Managing Wagtail translations
• Nightly testing of official plugins
• PR triage
• Updating PRs for linting changes
• Python Package Maintenance Guidelines