1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
|
= Teams and Internal Organization
Alpine is organized into various teams.
Teams help with delegating work.
Delegating work requires people to be available and get the necessary permissions to do their work.
Teams also make it easier for people to join specific teams, rather than the entirety of the project and all that entails.
Finally, this organizational structure gives more transparency as to how work is divided, and aids collaboration with outside entities.
This section describes the status quo of how Alpine is organized.
[glossary]
== Glossary
[glossary]
Team:: A group of people with a specific purpose/scope that they tend to.
Team Member:: A registered member of a team, given access to that team's workspaces.
Team Leads::
Team members that are allowed to vote in various organizational meetings and can appoint new team members.
Team Leads are marked in *bold* in official team listings.
== Becoming a Member
To become a team member, start by contributing to items under the team's jurisdiction.
Once you have shown some staying power, you may ask a team lead to appoint you as a member.
[TIP]
====
Do not worry if your request is denied!
That just means you aren't known enough to the team, or need to take the project more seriously.
The team lead should give you a reason as to why you've been denied.
====
== Becoming a Team Lead
Existing team leads, collectively, decide to appoint or demote other team leads.
A proposed team lead should already be part of the team.
If the proposal is to create a new team, the process is identical, except that the proposed team lead should be part of an existing team.
NOTE: Teams may have multiple, or one team lead - they may not have zero team leads.
== Being a Member/Lead
Being in a team grants grants you the things you need to work on whatever the scope of the team is.
You should know your fellow team members well, and cooperate with them (and potentially other teams) to achieve tasks.
As a team, you may request various workspaces, such as a separate irc channel, git namespace, dedicated host, and more.
As a team, it is up to you how you manage yourselves internally, but the contents of this document should serve as guidelines.
// TODO: specify what specific access each team has
== Current Team Listing
=== Core
Core team members have oversight over the entire project.
They also have the final say on packaging and security matters, and are the sole arbiters of the `main` repository.
|===
| Name | Nick | Email
| Carlo Landmeter | clandmeter | clandmeter@alpinelinux.org
| Francesco Colista | fcolista | fcolista@alpinelinux.org
| Jakub Jirutka | jirutka | jakub@jirutka.cz
| Kaarle Ritvanen | kunkku | kaarle.ritvanen@datakunkku.fi
| Kevin Daudt | \_ikke_ | kdaudt@alpinelinux.org
| Leonardo Arena | rnalrd | rnalrd@gmail.com
| Nathan Angelacos | nangel | nangel@alpinelinux.org
| *Natanael Copa* | *ncopa* | ncopa@alpinelinux.org
| Soeren Tempel | nmeum | soeren@soeren-tempel.net
| Timo Teräs | fabled | timo.teras@iki.fi
| William Pitcock | kaniini | nenolod@dereferenced.org
|===
=== Infrastructure
The infrastructure team takes care of the Alpine Linux infrastructure - maintaining the servers and services needed to keep everything running.
|===
| Name | Nick | Email
| *Carlo Landmeter* | *clandmeter* | clandmeter@alpinelinux.org
| Daniel Isaksen | danieli | d@duniel.no
| Kevin Daudt | \_ikke_ | kdaudt@alpinelinux.org
|===
=== Documentation
The documentation team creates and maintains all official documentation for Alpine Linux.
// TODO: once toast@toastin.space is recognized as an email, simplify entry
|===
| Name | Nick | Email
| *Chloe Kudryavtsev* | *SpaceToast* | link:mailto:toast@toastin.space[toast@toastin.space]
|===
=== Security
The security team takes care of communication with vulnerability reporters, maintaining an Alpine security advisory program, and information sharing with other projects.
|===
| Name | Nick | Email
| *Natanael Copa* | *ncopa* | ncopa@alpinelinux.org
|===
=== Packaging
Packaging team members have (limited) access to aports, take care of maintaining and creating packages, as well as accepting PRs and patches from the community.
|===
| Name | Nick | Email
| A. Wilcox | awilfox | awilcox@wilcox-tech.com
| Andy Postnikov | andypost | apostnikov@gmail.com
| Breno Leitao | leitao | breno.leitao@gmail.com
| Christian Kampka | ckampka | christian@kampka.net
| Daniel Sabogal | dsabogal | dsabogalcc@gmail.com
| Henrik Riomar | HRio | henrik.riomar@gmail.com
| *Natanael Copa* | *ncopa* | ncopa@alpinelinux.org
| Roberto Oliveira | rdutra | robertoguimaraes8@gmail.com
| N/A | Shiz | hi@shiz.me
|===
|
