The Admins Team is responsible for governance, overall coordination and all the rest that falls between the cracks . The group was previously known as TAG (Tiki Admin Group)
Admins are knowledgeable for all aspects of Tiki but each one has a special strength - even if they can do a little bit of everything. Admins rarely need to vote because decisions are usually consensual and it's a doOcracy. When a vote is required, these are the people. This is the list on Sourceforge & Freshmeat and at WhoWhat. Admins are by default in the Security team. Admins are voted in by other admins. Admins typically also participate in the Tiki Software Community Association as members of the Board of Directors.
- Add/remove SVN access for new contributors
- Formal letters/interactions with other organizations
- Make sure all Teams have a leader and are active and jump in for anything important that doesn't get done.
- Vote as a last resort or if necessary for legal/political reasons (ex.: formal motion needed for external needs)
- For example, they act as a safe guard, as a last resort to deal with Difficult People.
- Maintain Where and SWOT analysis for Tiki. The whole community is invited to participate but it's the type of high-level stuff the Admin group should be particularly concerned with.
Here is a list of things that mostly should be handled by the various teams, but if things fall through, the Admins need to help.
- Respect our word. Whatever is written on info.tiki.org is respected so "Make it happen" or "lower expectations".
- ex.: Version Lifecycle
- Releases (make sure to have release coordinator, being late is OK, but never more than 2 months late as this would disrupt the whole schedule and reduce confidence)
- Bugs are a fact of life, but regressions should be rare
- All items reported to security team need a conclusion (even if it's "invalid" or "won't fix")
- Pay the bills (server, domain name, etc.)
- Make sure people can join & help (get commit access, register to tiki.org)
- Keep *.tiki.org sites up & running
- Make sure our SourceForge.net space is working OK
- Address threats / changes that cause issues. Ex.: A slowdown of activity in a team can't be let to become a bottleneck for the rest of the community. Quality Team - How to reduce the workload
- Respond to requests from partners. If we don't have time / resources, at least indicate, "sorry, we can't do". A Partnership Team has been set up.
- Work on getting Teams to the next level (some are good, but some are inactive)
- to all existing Team members to ask to reconfirm
- to Mailing Lists/forums to invite people to join teams
- Get each team to start meetings/planning, etc.
- 2012 Year in Review (Marc and looking for help)
- Set up a Tiki Software and Community Dashboard.