Organization Structure

Development Team

Development Manager (Gordon Rowell)

• Release Leaders {RL} - (The RL is a non-technical, proj. mgr. position that works with the DM to determine feature prioritization/importance/support/funding)

1. 7.0 (Gordon Rowell)
2. 7.1 ( __ )
3. Future ( __ )

Team Leaders

(The team leaders are meant to be project management oriented, but can be technical people also. Many leader positions are opportunities for the less technically oriented to volunteer!)

• Updates Team Leader (Ian Wells)
• Security Team Leader (Ian Wells)
• Test Team Leader ( _ )
• Tools Team Leader ( _ )

Development Teams

Updates Team (6 to N people, should be technical, intermediate to expert)

• Members ( Gordon Rowell , Charlie Brady , Shad Lords, ... )
• Handles all updates after Gold release
• Potentially could handle all updates from RC to Gold
• Six or more active volunteers required here

Security Team (should be technical, expert)

• Members ( _ , _ , ... )
• Closed group, volunteers selected by existing group
• Handles all security updates for Gold releases, and ensure that the fixes are in any pre-release versions
• DM is ex-officio member

Test Team (6 to N people) (may be technical, beginner to expert)

• Members ( _ , _ , ... )
• Responsible for gathering testers, pushing bugs to Resolved or Reopened as quickly as possible
• Responsible for chasing reporters and closing off bugs without follow-up
• Bugzilla maintenance (new categories, versions, etc.)
• Maintain technical part of SME Server FAQ
• Six or more active volunteers required here

Tools Team (6 to N people) (should be technical, beginner to expert)

• Members ( _ , _ , ... )
• Build tools
• Release tools
• Build server setup and maintenance
• Mirror liaison

Communications Team

Communications Manager (Greg Swallow)

Team Leaders

• Web Team Leader (Ron Mc New)
• Manual Team Leader
• Publications / Marketing Leader?
• Graphics Team Leader?
• Wiki / Forum Team Leader?
• Translations Team Leader ( _ ) {The TTL is unique in that this person will accept, prioritise and assign tasks from all three primary areas to the team members.}

Communication Teams

• Web Team Members ( _ , _ , ... )
• Manual Team
• Wiki Team

• Translation Team (6 to N people, non-technical to technical) {The translations team is shared primarily between SME Server translations, and documentation/website translations. They would also help out with translations of contribs, where required. This team would accept requests from all three Managers (Development, Communications or Administrative)}.

  • English maintainer(s) {Per the constitution, English is the base language that should be translated to/from}
  • French maintainer(s) (Franck Pierre)
  • Spanish maintainer(s) ( _ )
  • Italian maintainer(s) (Filippo Carletti)
  • German maintainer(s) (Dietmar Berteld)
  • Your language here!

Administrative Team

Business Agent (Paul Dahlman)

Administrative Positions

• Accounting Assistant (someone that is familiar with US accounting and tax requirements)
• Legal Assistant (someone that may be a lawyer | paralegal | business owner with contract, etc. experience)
• EU Region Assistant ( _ ) (Regional Assistants help with business affairs in the languages and customs of the particular region)
• African Region Assistant ( _ )
• Asian/Pacific Region Assistant ( _ )
• North American Region --> Currently the BA
• Central/South American Region Assistant ( _ )
• License Adhearence Team Leader ( _ ) {This person will screen and assign tasks to the team, and escalate continual or flagrant violations to the BA and Legal Assistant}.
• Marketing Statistics Assistant(s) ( _ ) {This person will work with the BA and Regional Assistants to assess our own / external information to determine our market penetration in each region, develop customer profiles, identify and rank the features that are most/least important to the typical enduser, keep current statistics of which SME versions are in service and report these results to the leadership}
• Bounty Program Team Leader ( _ ) {This person will oversee the development and operation of the Bounty Program for SME Server Inc. It is likely that this person will interact with the Development Manager with regard to developing criteria and executing bounty submission evaluations}.

Administration Teams

• License Adhearence Team (2 to N people, non to technical) {This team will review code included in the SME base for licensing violations, investigate reports of SME 'brand' lifting or GPL violations, and potentially review contribution code (at least those hosted by contribs) for licensing violations)
• Administrative Assistants Team {This team will handle small administrative 'projects' as they become available. Examples might include oversight of the bounty program, interfacing with other OSS project teams, etc.}