Teams and Organization at #alpine-meetings, 2019-03-17 14:03
Meeting started by _ikke_
Roll Call
- Present: SpaceToast danieli fcolista _ikke_
Goal of the meeting
- DRAFT - Alpine Linux SIGs - Google Docs
- Burning Rubber Paste
- agenda: https://brpaste.xyz/y4fTUg?asciidoc
- Teams help with delegating work. This does require people to be available and get the necessary permissions to do their work
- It's also easier for people to join specific subteams
- Teams give more transparency to how the work is divided
- Question: how can we properly delegate access to specific systems?
Current team structure
- Current documented teams: 1. Core, 2. Infrastructure, 3. Developers
- Proposed teams: Core developers, infrastructure, documentation, security, packaging
- For future, discuss QA team for aports
- Agreed: No QA team for now
- Suggested team leads: core: ncopa, infra: clandmeter, documentation: spacetoast, security: ncopa, packaging: ncopa
- Core team: Core members, have oversight over project and takes lead over packaging and security
- Infra team: Takes care of the Alpine Linux infrastructure (maintaining servers and services)
- Packaging team: Members with (limited) access to aports, take care of packaging and accepting PRs / patches from the community
- Security team: Takes care of communication with vulnerability reporters, maintaining an Alpine security advisory program, and information sharing with other projects.
- Documentation team: Create and maintain official documentation for Alpine Linux
- alpine-devel: [alpine-devel] a release engineering team?
- Potential team: Release engineering. Need to find team members / people who want to contribute
Documentation of teams
- Current documentation has a single page with one table per team. Initially this format can be copied, but later we might opt to have one page per team
- cross-team communication should be stimulated. Therefore, we should opt to not have automatic separate communication channels per team.
- Teams can request separate workspaces (namespaces) for collaboration
- Each team may have multiple team leads
Team membership
- Team membership requirement: The team lead can decide to add team members. It's expected that a new team member has already contributed to the team and has shown to stay with the project.
- Team leads are decided by existing team leads. A proposed team lead should be already part of the specific team or in case of a new team, be member of another team.
- Action: provide a list of members to SpaceToast (documentation)
Open Floor
Meeting ended at 15:40:46 UTC
Full log