Topic #48435: Implement new team structure
Define possible access rights and entitlements for Active Contributors
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.
#1 Updated by Christian Müller over 6 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
- CI server
- 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?