[[Teams/DE|deutsch]] | '''english'''

= CAcert Teams =
The Community is structured around many teams doing various areas.  Each team generally has a team leader, who liaises with the Committee of CAcert Inc, a.k.a. the Board, ''the executive'' of the Community.  Teams also work to the policies, and are occasionally subject to Arbitrations.

Thus there are three centers of gravity in CAcert's community:  the board, the policy group and the arbitration forum.  These three centers are peers in power, all interlocked, and in some senses mirror the political structures found in some countries:  the executive ("presidency"), the parliament ("makers of laws") and the judiciary (courts).

Every team is defined by some service/task/product/[[Roles|role]] for CAcert services (the products) within and for the Community.  Currently there are:

 * systems
   * critical systems team
   * infrastructure systems team
 * arbitration forum
 * assurance team
   * organisation assurance team
   * events
 * education forum
 * comma
 * support team
 * software development
   * new software ''birdshack'' team and old software team.
 * finance team
 * Audit team

== Leaders ==
Every team will have several people sharing tasks. One of those will take or is acknowledged as the lead and is referred to as leader.

||'''''Name of Team''' '' ||'''''Description of TL's role''' '' ||'''''Short''' '' || Document || '''''Team Page''' '' ||'''''status''' '' ||'''''person''''' ||
||(Individual) Assurance ||AssuranceOfficer ||AO || AP || AssuranceTeam || vacant ||  ||
||Organisation Assurance ||OrganisationAssuranceOfficer || OAO || OAP ||OrganisationAssurance || vacant || ||
||Education ||EducationOfficer || EDU || HB? || EducationCampus ||filled ||[[BernhardFröhlich|Bernhard Fröhlich]] according to [[https://wiki.cacert.org/EmailBoardDecisions#m20071026.1|m20071026.1]] ||
||Assurance Events || [[EventOrganisationOfficer|Event Teams Leader]] ||EO? || HB? ||UpcomingEvents || vacant || ||
||Community (&) Communication  || to be defined || to be defined || || || vacant ||  ||
||Marketing Arsenal  || to be defined || to be defined || || || vacant ||  ||
||Privacy || ||PO || PP ||  || vacant ||  ||
||Dispute Resolution || [[ArbitrationForum]] || DRO || DRP || [[ArbitrationForum|Arbitration Forum]]<<BR>>[[Arbitrations|Pending Arbitrations]]|| vacant || ||
||Documentation || DocumentationOfficer || DocO || ? || (none) || vacant||  ||
||Policy || [[PolicyOfficer]] || PolO || PoP || [[https://lists.cacert.org/wws/arc/cacert-policy|Policy Group mailing list]]<<BR>>[[PolicyDecisions|Policy Decisions]] || vacant ||  ||
||application engineering || || AppEng || SP || SystemAdministration || obsolete according to SP  || area inactive, not filled ||
||Software-Assessment || ||SA || SP || [[Software/Assessment/Team|Software-Assessment Team]] || filled || Dirk Astrath according to [[https://community.cacert.org/board/motions.php?motion=m20170308.2|m20170308.2]] ||
||Support || [[Brain/Support/TeamLeader|Support Team Leader]] || SE || SP8 || [[Support/Team]] ||filled || Joost Steijlen  according to [[https://community.cacert.org/board/motions.php?motion=m20111120.3|m20111120.3]] ||
||Critical Services || || Crit? sysadm? || SP || SystemAdministration || filled || Dirk Astrath since Nov 1, 2019 ||
|| Infrastructure || || infra|| ? || SystemAdministration || filled || [[Jan Dittberner]] according to [[https://community.cacert.org/board/motions.php?motion=|m201?????.?]] ||
|| Access Engineers || provides access to secure site || AE || SP || ? || vacant || ||
|| Finance Team || to be defined || FO || ? || [[FinanceTeam]] || vacant || ||
|| PR || Public Relations || PR || ? || [[PublicRelations|PR]] || filled || [[AlexanderBahlo]] according to board meeting 2016-04-17 ||
|| Audit Team || Lead Auditor: Audit over CAcert || LA || -- || [[Audit/Team]] || vacant || ||
|| New Roots and Escrow Team || New Roots and Escrow || NRE || -- || [[Roots/EscrowAndRecovery/NRE]] || vacant ||  ||
Things that aren't picked up by people might be the responsibility of the board, but in general this means they are in danger of being done weakly or not at all:

 * Human Resources
   *  Please don't add new lines without consultation with board.  Adding a line doesn't make it so.
 * Quality
 * Security
 * policy

== FAQ ==
The following is some basic questions on how our teams work.


=== What does a Team Leader have to do? ===
 * Provide reports on request by the Board.
   *  '''NOTE:''' that team leaders have been requested to work on their reports for the upcoming AGM.  Something short, maybe 5 lines, because there are a lot of teams now :)
 * Keep their areas in the wiki up to date.
 * Look out for new team members and help them to contribute.
 * Share problems, ask for help.
 * Tell us when you can no longer do the job.
   * It is a responsibility to hand over.

=== How can I take part in a CAcert Team? ===
There is no special or guaranteed or written path. In general, help a lot and join the team informally.  Contact the team Officer as shown in the chart, and ask. If there is no team, do *something* in CAcert, help make it known (contact any Officer). Then suggest you try this and that on your area.  Finally, you can write to cacert-board@co and ask team-related questions.

Start informing yourself about the area. Read through the wiki on that area.  Look for the list of outstanding tasks. Help on the outstanding tasks. Subscribe yourself to any of the CAcert email lists and take part.

Also, join the [[CAcertIncorporated|Association]], as per [[TopMinutes-20070917|m20070917.8]] which says that ''"(Non-board operational) Officers of the project of the organization should be members of the association CAcert Inc.; the Board can make exceptions to this rule."''

=== How do I resign from being a role? ===
'''Please contact and inform everyone in your team, other leaders and the board'''.

There is of course a conflict here.  Everyone must put their life, family, job first.  But we also have a responsibility to hand over the task to others.  The minimum is to let us know, so we can pick it up.  Ideally, work with the team or someone else to help the transition.

If there are any critical assets then it is your responsibility to hand those over, and this requirement is independent of the circumstances.

=== Conflicts of Interest ===
To protect our community and to protect yourself, leader should:

 a. declare any potential conflicts of interest
 a. expect these to be reviewed, and
 a. possibly re-engaged in another area.

Especially security areas are sensitive to these restrictions. Each leader is expected to clearly describe any potential conflicts of interest.  This is as much to protect you as it is to protect the community;  your work boss may ask you to do things that you might have trouble refusing, and these things may cause a breach of CCA/SP, a breach of the law, or a breach of our principles.  We can much better deal with these conflicts if they are known about and thought about in advance.

=== Historical ===
In the period of 2006 to 2008, CAcert built out its organisation structure by appointing officers to various tasks.  This area was initially managed by [[Advisory]] then by ManagementSubCommittee (M-SC) and ultimately by [[Board]].

Every Office was defined by some service/task (a product) for CAcert services (the products) within and for the Community. Every Office would have certain persons from the Community taking up some task in the Office. One of those persons will take or is acknowledged as the lead and is referred to as Officer.  Historically, there was also some writing about ProductManagers, but this never worked out.

An old organigram is found here: [[http://svn.cacert.org/CAcert/organisation/CAcert-Organogram.jpg|Organization Structure Chart]] ([[http://svn.cacert.org/CAcert/organisation/CAcert-Organogram.pdf|PDF format]]).

As of 2009 there was general agreement at the board level that the Officers process was causing as many problems as it was solving, and the term was dropped from general management.  To some extent, we started using the term ''team leader'' to refer to the same thing.  The emphasis was changed from ''one person'' to ''one team''.

----

== Inputs & Thoughts ==

 . 20091205-hugi

 . {{{
Curious, to name persons and teams without common agreement about the project structure. Again 3 functional areas with various working sections (=teams) would make sense!

comma is just an area, consisting of community (&) communication, (marketing) arsenal with the strongest weapon or "front ends" the assurers or orga assurers, and campaigns as events or fundrising. identity is as well in comma as it is a marketing issue, but to give strong emphasize it is a separate section.

See overall wiki structure:
http://wiki.cacert.org/comma/Workbench/WikiCertLoginKnowHowMgmtTool
https://lists.cacert.org/wws/arc/cacert/2009-11/msg00077.html


  }}}

----

 . 20101009-UlrichSchroeter

 . {{{
Above list of teams is the historical result by processes and probably the Organisation Structure result of the Pirmasens Meeting end of 2007 [1]

Structure can be seen from different perspectives:
 * Audit will have to split into business areas Registration Authority (RA) and Certificate Authority (CA) only.
 * From Management perspective, above listed management areas makes sense, as they are the real existing working and business areas. From Boards view, these teams has to report to the Board and they'll reports directly (w/o addtl. management levels)
 * From Audit work practice: (RA): Arbitration, Policy Group, Assurance Area, Education (CATS), ATE (combined but separated area of Assurance and Education), Co-Audit, Systems (CA): Critical team, Access-Engineers, Infrastructure team, Software-Assessment, Software-Development are the working areas.
 * Community view: Policy Group (legislative), Board (Executive), Arbitration (judiciary) are the areas.
 * probably more views to add .....
  }}}

== Links ==
 *  [1] [[https://svn.cacert.org/CAcert/Education/Organization%20Structure.png]]
 * [[Roles]]

----
 . CategoryCommunity