Task #48344

Topic #48435: Implement new team structure

Define possible access rights and entitlements for Active Contributors

Added by Robert Lemke almost 6 years ago. Updated almost 6 years ago.

Status:
New
Priority:
Should have
Category:
Community
Target version:
-
Start date:
2013-05-17
Due date:
% Done:

0%


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 almost 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
  • 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 almost 6 years ago

  • Target version set to Meeting 06.06.2013

#3 Updated by Robert Lemke almost 6 years ago

  • Target version deleted (Meeting 06.06.2013)

#4 Updated by Robert Lemke almost 6 years ago

  • Parent task set to #48435

Also available in: Atom PDF