Task #48344
Topic #48435: Implement new team structure
Define possible access rights and entitlements for Active Contributors
Status: | New | Start date: | 2013-05-17 | |
---|---|---|---|---|
Priority: | Should have | Due date: | ||
Assigned To: | Christian Müller | % Done: | 0% |
|
Category: | Community | |||
Target version: | - |
Description
We need to create a list of accounts, access rights and other benefits (typo3.org email address) each Active Contributor is entitled to. This can later be used as a check list.
History
#1 Updated by Christian Müller about 2 years ago
- Neos and Flow website admin account
- Gerrit commit rights
- Github Flow / Neos / Flowpack organizations -> also needs guideline of what should go where
- typo3.org email address
- team calendar
- social media accounts
- Sourceforge
- CI server
- Ohloh?
- Forge projects (probably impossible?)
- buzz.typo3.org account (if wished)
- Core Internals?
- Shared cloud data store (which would need to be created then) (I imagine a shared google drive account or something like that)
- Packagist account?
#2 Updated by Robert Lemke about 2 years ago
- Target version set to Meeting 06.06.2013
#3 Updated by Robert Lemke about 2 years ago
- Target version deleted (
Meeting 06.06.2013)
#4 Updated by Robert Lemke about 2 years ago
- Parent task set to #48435