faas-rs/faas
1
0
Fork 0
mirror of https://github.com/openfaas/faas.git synced 2025-06-08 16:26:47 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update verbiage to remove core channel

Browse Source 
Signed-off-by: Alex Ellis (OpenFaaS Ltd) <alexellis2@gmail.com>
This commit is contained in:
Alex Ellis (OpenFaaS Ltd) 2020-12-09 09:50:57 +00:00
parent 9bbb25e3c7
commit 3170d97bb5
1 changed files with 12 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
CONTRIBUTING.md
View File

@ -238,22 +238,23 @@ In the OpenFaaS community there are four levels of structure or maintainership:
#### Core Team #### Core Team
The Core Team have the ear of the Project Lead. They help with strategy, project maintenance, community management, and make a regular commitment of time to the project on a weekly basis.
Each member will be responsible for, or be a subject-matter-expert (SME) for a sub-system of OpenFaaS and will be granted write (push) access to the related repositories.
The Core Team have the same responsibilities and perks of the Membership Team, in addition will need to keep in close contact with the rest of the Core Team and the Project Lead.
* Members are listed on the project homepage as being part of the Core group and are shown first.
* Members are expected to attend 1:1 Zoom calls with the Project Lead up to once per month
* Members will notify the Project Lead and Core Team of any leave of a week or more and set a status in Slack of "away".
Core Team attend all project meetings and calls. Allowances will be made for timezones and other commitments.
The Core Team includes: The Core Team includes:
- Alex Ellis (@alexellis) - Lead - Alex Ellis (@alexellis) - Lead
- Lucas Roesler (@LucasRoesler) - SME for logs, provider model and secrets - Lucas Roesler (@LucasRoesler) - SME for logs, provider model and secrets
The Core Team have the ear of the Project Lead. They help with strategy, project maintenance, community management, and make a regular commitment of time to the project on a weekly basis. The Core Team will usually be responsible for, or be a subject-matter-expert (SME) for a sub-system of OpenFaaS. Core Team may be granted write (push) access to one or more sub-systems.
The Core Team gain access to a private *core* channel and are required to participate on a regular basis.
The Core Team have the same responsibilities and perks of the Membership Team, in addition will need to keep in close contact with the rest of the Core Team and the Project Lead.
* Core Team are expected to attend 1:1 Zoom calls with the Project Lead up to once per month
* Core Team members will notify the Project Lead and Core Team of any leave of a week or more and set a status in Slack of "away".
Core Team attend all project meetings and calls. Allowances will be made for timezones and other commitments.
#### Members Team #### Members Team
The Members Team are contributors who are well-known to the community with a track record of: The Members Team are contributors who are well-known to the community with a track record of: