User:AngelinaBelle/SMF team manual/Team roles: Difference between revisions From Online Manual

Jump to: navigation, search
(Censord name infobox -> project manager)
No edit summary
 
(35 intermediate revisions by 4 users not shown)
Line 1: Line 1:
{{PolicyDisclaimer}}
{{PolicyDisclaimer}}
__TOC__
__TOC__
The SimpleMachines Forum (SMF) project is a project team under the umbrella of the Simple Machines NPO.  
The Simple Machines Forum (SMF) project is a project under the umbrella of the Simple Machines NPO.  
==The SMF team==
==The SMF project structure==
The SMF project has a project manager and several sub-teams.  The heads of these teams, along with the project manager, constitute the projects's steering committee, which is responsible for developing plans for the project and leading the project toward achieving its goals.
The SMF project has a project manager and several sub-teams.  The heads of these teams, along with the project manager, constitute the projects's steering committee, which is responsible for developing plans for the project and leading the project toward achieving its goals.


===Moderation Duties===
===Project Manager===
It is the duty of every SimpleMachines team member to patrol every publicly-viewable boards, review every post for inappropriate content, and move, remove, or lock topics as required to maintain civility and good order. Language Moderators (not members of the SMF team) are responsible for patrolling non-English language boards.
The SMF Project Manager (PM) is responsible for representing the SMF project to the non-profit organization, the Board of Directors and to the SMF community. The PM leads the team, maintaining the vision and spirit of the project. The PM encourages and supports team members, works with the steering committee to set goals for the project.
 
The PM's responsibilities are:
#To help the SMF team set goals.
#To lead the SMF team toward meeting the team's goals, help solve problems
#To help the teams collaborate, stay informed of the effect they have on one another, and work together effectively.
#To mediate conflict between team members, or between team members and community members, in order to help the parties reach an agreement.
# When authorized by the SC, to speak on behalf of the steering committee.
# To serve as team figurehead -- representing the team to the community, answering general inquiries, turning some questions over to other experts on the team.
# To identify areas for improvement within the project.
#*Inform or advise the responsible parties, bring it to the attention of the SC, or appoint someone to handle it.
#*The SC must be notified of all such appointments.
 
In order to carry out these duties,
# The PM should have administrative access to simplemachines.org, and related sites.
# The PM should have root access to the servers/VMs holding the infrastructure of the SMF project, in order to be able to help in case of emergency.


===Project Manager===
The PM is empowered to:
{{Did you know|above=One Censored Name
# Perform administrative duties necessary for the team, such as changing groups (set as Friend, apprentice, etc.).
|text=We have one forum user whose name was censored from the site. The reason for his ban and subsequent censoring was that he aggressively broke the site rules and abused team members verbally and in writing.}}<!--
# Intervene and make project decisions, in case of emergency, when the respective person responsible is not available. These situations include, but are not limited to:
#* The responsible team lead or member is inactive or otherwise unavailable, and immediate action needs to be taken.
#* The project is seriously endangered, as when immediate removal of a team member is necessary.


-->
Restrictions on the powers of the PM are:
* Arbiters and negotiators for community/user issues
# When the PM takes administrative action to change member access, removal of team members, or other emergency actions, he must inform the SMF leadership or the team.
* High-level representation
# The PM must provide an explanation for any decision or action, at the request of the SMF leadership.
* Reviewing license issues
# The SMF leadership can reverse any decision or action of the PM. The SMF leaderhip may make a decision without taking a formal poll. If any member of the SC (including the PM) requests a poll on the matter, a poll may be taken.
* Maintaining the vision & spirit
# The SMF team can reverse any decision or action of the PM.
** set goals and direction for the future
** Provide leadership to the team
** encourage and support Team Members
* Running meetings


===Team Leads===
===Team Leads===
* Keeping their team motivated & on task
Each of the teams within the SMF project has a team lead. The team lead are responsible for:
* Helping team members stay involved
* Reporting progress during team meetings.
* Watching for new team members and recruiting them
* Participating in Steering Committee discussions.
* Mentoring new team members
* Keeping the other teams informed of important changes or events.
* Reporting progress during team meetings
* Keeping their team motivated & on task.
* Participating in Steering Committee discussions
* Helping team members stay involved.
* Keep the other teams informed of important changes or events
* Giving team members the recognition and credit they merit for their successes and accomplishments.
* Supporting the personal and professional growth of each and every member of the team
* Watching for new team members and recruiting them.
* Making sure apprentice members and new team members have a mentor, that the mentor works as closely with the new member as necessary, and that apprentices makes appropriate progress during the apprenticeship period.


===Developers===
===Developers===
{{Did you know|above=Did you know?
{{Did you know|above=Did you know?
|text=The “SE” is YaBB SE stood
|text=The “SE” in YaBB SE stood for “Splinter Edition” after Splinter from the Teenage Mutant Ninja Turtles. Ninjas are cool, and YaBB SE was designed to be cool, too. And it was a developed by a small splinter group of the original YaBB Team.}}<!--
for “Splinter Edition” after
Splinter from the Teenage
Mutant Ninja Turtles.
Ninjas are cool, and we
wanted YaBB SE to be so
as well. Additionally, it
was a developed by a
small splinter group from
the original YaBB Team.}}


* Maintaining the development roadmap and plan
-->Developers create the software. Without them, there is no software community. For the SMF community to remain vital, the software must remain vital. The developers must lead in decisions about where technology is going, and where SMF needs to go to stay current. They need to consider everything from what the users want, to making the features run efficiently, to making sure all the pieces get tested properly.
* Develop SMF applications
 
* Maintaining the changelog
For information and ways to contribute, please refer to the [http://wiki.simplemachines.org/smf/User:Norv/dev/team Development pages].
* Monitoring the bug trackers
* Fixing bugs
* Assisting with support in special circumstances
* Reviewing & selecting features for inclusion
* Liaising with the beta testers
* Address all security reports and CC info@simplemachines.org
* Ensure other teams have sufficient information to perform their duties (ie: Doc Team should know about new features so they can be documented)
* Manage CVS (including user accounts)
* Review current and coming technology and make sure SMF stays current
* Provide leadership to the team and to the community as a whole


===Support Specialists===
===Support Specialists===
* Helping our users have an exceptional SMF experience
* Helping our users have an exceptional SMF experience.
* Providing special attention to the Charter Members
* Providing special attention to the Charter Members.
* Monitoring the help desk & getting tickets to a “closed”  state
* Monitoring the help desk & getting tickets to a “closed”  state.
** Check HD first
** Check Help Desk first.
** Check CM boards
** Check Charter Member boards.
** Check Support boards
** Check Support boards.
* Revisit your old posts and mark as solved when they are.
* Revisit your old posts and mark as solved when appropriate.
* Perform upgrades and installs for CM’s
* Perform upgrades and installs for Charter Members.
* Support the core software by answering questions, suggesting fixes, etc
* Support the core software by answering questions, suggesting fixes, etc.
* Act as a filter for bug reports, reporting legitimate ones to the bug tracker
* Act as a filter for bug reports, reporting legitimate ones to the bug tracker.
* Look for common problems/errors and suggest documentation or code changes to reduce them
* Look for common problems/errors and suggest documentation or code changes to reduce them.
* Assume nothing. Always ask questions, no matter how tedious that can get. If a post is unclear, don't make assumptions. Ask for clarification.
* Some posts may seem trivial, to you. Remember that they aren't trivial to our users. Always strive to be friendly and helpful. You are SMF's "Front line". The way you are perceived will reflect on SMF, not just you.
* Always try to remember to tell users to backup, before attempting anything. If you don't remind them, they'll almost certainly forget.
* If you begin helping, on a certain topic, try to maintain an interest in that topic; don't just leave it if you're stuck. There's a "Support Helpers" board. Use that to alert other support team members of your plight.
* If you're going to be away from the boards, whilst you're helping someone, try to let other members of the team know, so that they can take that topic over for you, rather than letting the person you're helping just "Hang".


===Customizers===
===Customizers===
* Watching for feature ideas that should be put into mods
Customizers are developers who can provide mods and/or themes for SMF. They review and approve mods and themes submitted by the community, and they maintain the customization site. Their duties include:
* Updating SMF's official mods as necessary to maintain compatibility
 
* Designing new themes
* Watching for feature ideas that should be put into mods.
* Updating SMF's official themes as necessary to maintain compatibility
* Updating SMF's official mods as necessary to maintain compatibility.
* Theme Site maintenance
* Updating SMF's official themes as necessary to maintain compatibility.
** Approving community-created themes
* Designing new themes.
* Mod Site maintenance
* Theme Site maintenance.
** Approving community-created mods
** Approving community-created themes.
* Graphics images (i.e. Buttons &  smileys)
* Mod Site maintenance.
* Other graphics as requested/required
** Approving community-created mods.
* Give support to people trying to create themes and modifications
* Graphics images (i.e. Buttons &  smileys).
* Suggest changes to make theme and modification create easier and more powerful
* Other graphics as requested/required.
* Give support to people trying to create themes and modifications.
* Suggest changes to make theme and modification creation easier and more powerful.
* Write mods that follow the coding guidelines and as though they were writing a default SMF feature.
* Write mods that follow the coding guidelines and as though they were writing a default SMF feature.
* Provide support in the Coding Discussion and Graphics boards
* Provide support in the Coding Discussion and Graphics boards.


===Doc Writers===
===Doc Writers===
* Maintaining the Online Manual
Documentation Writers write and maintain the online documentation at simplemachines.org. They may be called upon to write and maintain any documentation within the forum software itself. They may work with and recruit [b]Doc Helpers[/b] from the community to help out.  Their responsibilities.
** Write clear, accurate, and easy to understand documentation
* Maintaining the Online Manual.
** Review and update update text as needed
** Write clear, accurate, and easy to understand documentation.
* Work with localizers, site, and dev teams to enable document translations
** Review and update update text as needed.
* Review/proof other SMF team publications
* Work with localizers, site, and dev teams to enable document translations.
* Spelling/Grammar checks on the site and in our public postings
* Write, review, or proofread other SMF team publications, including our news announcement postings.
* Maintain Team Manual
* Maintain the SMF Team Manual


===Localizers===
===Localizers===
Line 105: Line 109:


==Others who contribute to the SMF project==
==Others who contribute to the SMF project==
These individuals also volunteer their time on behalf of the project, but are not members of the team.
These individuals also volunteer their time on behalf of the project, but are not members of the SMF project.
===NPO teams===
 
The SMF project depends on the Simple Machines NPO for Marketing, and to maintain its site and its servers. These teams are not part of the SMF project. The site team is responsible for upgrading SimpleMachines.org and re-installing necessary modifications. The server team is responsible for specifying, configuring, and maintaining all of the NPO's servers.
===Simple Machines organizational teams===
The SMF project depends on teams from the Simple Machines corporate organization for Marketing and to maintain its site and its servers. These teams are not officially part of the SMF project. The site team is responsible for maintaining and upgrading SimpleMachines.org and the software on it. The server team is responsible for specifying, configuring and maintaining the organization's servers and other hardware. The marketing team is responsible for planning press releases, attendance to conferences and other public relations details. Additionally, the marketing team works on acquiring sponsorships as well as maintaining and supporting the advertisements and advertisers on the simplemachines.org site.
 
===Forum Administrators===
Forum administrators take care of routine tasks like banning and deleting accounts, as well as less-common tasks like creating membergroups and adjusting membergroup permissions. These tasks are generally handled by site and server team members, by the SMF project manager and by other SMF team members.


===Friends===
===Friends===
Former members of the SMF team, some of whom are still members of the NPO, often share their experience with the team. Some Friends may re-join the team when they again have time to commit to the SMF project.
Former members of the SMF team, some of whom are still members of the Simple Machines organization. They often share their experiences with the team. Some Friends may re-join the team when they again have time to commit to the SMF project.
 
===Community Helpers===
===Community Helpers===
Many members of the community contribute in one way or another without holding any title at all.
Some community members have been invited to join special-purpose membergroups. They do not have access to SMF team-only boards, but do have some permissions that other members of the community do not have.
Others may join, or be invited to join, community support groups. These include
*Consulting Developers
*Language Moderators -- moderate and provide support on non-English language boards
*Beta Testers.
*Beta Testers
*Language Moderators -- moderate and provide support on non-English language boards.
*Documentation Helpers
*Support Helpers
*Translators -- with their work SMF is available for [http://download.simplemachines.org/?smflanguages many languages].
*Translators -- with their work SMF is available for [http://download.simplemachines.org/?smflanguages many languages].


Anyone who wishes may join these membergroups right from their own profile
*Doc Helpers.
*Community Support Helpers.


{{mbox|text=The following describes the organization of the LLC in 2006}}
Many other members of the community contribute in one way or another without holding any title at all. They are important to keeping things going at simplemachines.org
 
==Organizational Chart==
When someone joins the Simple Machines team, one of the most important pieces of information
they must assimilate is where they fit in to the grand scheme of things. The Simple Machines
LLC Org Chart can be seen in Figure 1 below.
[[File:LLCorg.GIF|600px|Figure 1 -- Simple Machines LLC Org Chart, circa November 2006]]
 
On the chart above, the connecting lines represent the paths of formal communication, and the
vertical placement of roles within the chart typically represents the level of access they have
within the community.
 
In consideration of the above Org Chart though, a critical differentiator is that although a
“higher” position may provide increased access, it does not inherently provide increased
authority. We have elected to use a hierarchical structure because of the communications and
organizational benefits it provides, not because any team member is superior to another. We are
a team of equals.  We need to trust each other to do our jobs correctly, and we need to trust each
other to provide constructive feedback regardless of position within the org chart.
 
As the project grows, team members retire, and our needs change, openings for team members
become available.  While it is desirable to always have a complete team and to quickly fill
openings, we must take our time and be very selective when recruiting new team members.  This
will ensure we maintain a dedicated and efficient team.  Every team members is encouraged to
be on the lookout for community members who demonstrate the qualities necessary to become a
team member.  These qualities include, but are not limited too, loyalty to the community,
willingness to help others, and strong knowledge in a particular area.  The use of the team boardsto discuss prospective team members is encouraged.
 
In order to maintain a productive environment as well as a happy team, it is essential to maintain
good spirit between team members.  The key to this is maintaining a positive environment by
providing constructive criticism as well as being able to accept criticism from others.  For
example, “I think this would be better if done differently” is always better than “You screwed
this all up”.  While both positive and negative feedback is essential, it is also essential to always
convey feedback in a positive manner.
 
Team members are given moderator permissions on every board.  While you aren’t expected to
read every post or catch every topic requiring moderation, all team members are encouraged to
keep an eye out for and remove or move as appropriate any inappropriate content, topics posted
in the wrong board, and spam.
 
As with any project of this nature, copyright and intellectual property issues will occasionally
arise.  As a team, we should maintain an awareness of how our software is being used in order to
pinpoint copyright violations.  Such violations might include illegal copyright removal and
illegal redistribution.  Any copyright violations should be added to the copyright topic in Full
Team Chat so that follow-up action may be taken by the appropriate team member.
Even though each team group has its own specific areas of focus, we must also maintain an
awareness of the other teams.  Particularly, it is very important to stay informed about
development progress.  Ultimately, development is the driving force behind everything we do at
Simple Machines. For example, it is important for the Development and Doc teams to interact toinsure that no software features go undocumented, while Support Team members should be
aware of changes, new features, and common problems that are to be expected.
Periodic team meetings are scheduled in order to ensure each team knows the status of the other
teams’ efforts and we are all on the “same page”.  Every effort is made to schedule meetings at
such times where the most team members are available to attend.  Each team member is
encouraged to visit the Meeting Availability page and enter the times during which you are
available.
 
 
 
==Project Managers==
- Arbiters and negotiators for community/user issues
- High-level representation
- Reviewing license issues
- Maintaining the vision & spirit
o set goals and direction for the future
o Provide leadership to the team
o encourage and support Team Members
- Running meetings
 
==Assistant Project Managers==
- Handling general emails
- Running meetings when PM’s absent
- Following up on initiatives
- Helping to coordinate “special” member groups – i.e. charter members, beta testers, etc.
- advertising campaigns on the site
- create email for Team Members
- Admin stuff on the board
o  bans
o  maintenance
o  reorganize boards
o  permissions
==Team Leads==
- Keeping their team motivated & on task
- Helping team members stay involved
- Watching for new team members and recruiting them
- Mentoring new team members
- Reporting progress during team meetings
- Participating in “Leadership Team” discussions
- Keep the other teams informed of important changes or events
==Developers==
- Maintaining the development roadmap and plan
- Develop SMF applications
- Maintaining the changelog
- Monitoring the bug trackers
- Fixing bugs
- Assisting with support in special circumstances
- Reviewing & selecting features for inclusion
- Liaising with the beta testers
- Address all security reports and CC info@simplemachines.org
- Ensure other teams have sufficient information to perform their duties (ie: Doc Team
should know about new features so they can be documented)
- Manage CVS (including user accounts)
- Review current and coming technology and make sure SM stays current
- Provide leadership to the team and to the community as a whole
- Upgrading SimpleMachines.org and re-installing necessary modifications
 
{{mbox|text=Did you know?
The “SE” is YaBB SE stood
for “Splinter Edition” after
Splinter from the Teenage
Mutant Ninja Turtles.
Ninjas are cool, and we
wanted YaBB SE to be so
as well. Additionally, it
was a developed by a
small splinter group from
the original YaBB Team.}}
==Support Specialists==
- Helping our users have an exceptional SMF experience
- Providing special attention to the Charter Members
- Monitoring the help desk & getting tickets to a “closed”
state
o Check HD first
o Check CM boards
o Check Support boards
- Revisit your old posts and mark as solved when they are.
- Perform upgrades and installs for CM’s
- Support the core software by answering questions,
suggesting fixes, etc
- Act as a filter for bug reports, reporting legitimate ones to
the bug tracker
- Look for common problems/errors and suggest
documentation or code changes to reduce them
 
==Customizers==
- Watching for feature ideas that should be put into mods
- Updating mods as necessary to maintain compatibility
- Designing new themes
- Updating themes as necessary to maintain compatibility
- Theme Site maintenance
- Creating & approving themes
- Mod Site maintenance
- Creating and approving mods
- Graphics images (i.e. Buttons &  smileys)
- Other graphics as requested/required
- Give support to people trying to create themes and modifications
- Suggest changes to make theme and modification create easier and more powerful
- Write mods that follow the coding guidelines and as though they were writing a default
feature.
- Provide support in the Coding Discussion and Graphics boards
 
==Doc Writers==
- Maintaining the Online Manual
o update text as needed
o Flash tutorials
- Language translations
- review/proof publications
- Maintaining Team Manual
- Spelling/Grammar checks on the site and in our public postings
- Write clear, accurate, and easy to understand documentation
- Review the in source documentation and suggest/make fixes
 
==Marketing==
- Watching for awards and PR opportunities
- Speaking about SMF on other forums/websites
- Prepare ads that are posted on other sites
- sourcing out new redistributors
- maintaining redistributors relationships
o ensure redistributors receive copies of our agreement
o ensuring redistributors keep things up to date
o helping redistributors support *their* marketing efforts of SMF
- GET OUR NAME OUT THERE
- Promote the use of SMF to forum owners
- Promote the sale of Charter Memberships
- Promote the sale site advertising
- Suggest ways to improve our name recognition
- Publish articles that would be of professional news worthy level.
- Find articles mentioning SM and inform the community of them
- Identify advertising opportunities for SMF
 
==Moderators==
o Review all posts on assigned board for inappropriate content
o Move, remove, or lock topics as appropriate
 
{{mbox|text=One Censored Name
We have one forum user
whose name was
censored from the site.
The reason for his ban
and subsequent censoring
was that he aggressively
broke the site rules and
abused team members
verbally and in writing.}}
 
==Other Roles==
- Server Admin
- Newsletter writer
- Language coordinator
- Team interviewers
- Beta Testers
- Security Advisors

Latest revision as of 17:51, 8 December 2011

The Simple Machines Forum (SMF) project is a project under the umbrella of the Simple Machines NPO.

The SMF project structure

The SMF project has a project manager and several sub-teams. The heads of these teams, along with the project manager, constitute the projects's steering committee, which is responsible for developing plans for the project and leading the project toward achieving its goals.

Project Manager

The SMF Project Manager (PM) is responsible for representing the SMF project to the non-profit organization, the Board of Directors and to the SMF community. The PM leads the team, maintaining the vision and spirit of the project. The PM encourages and supports team members, works with the steering committee to set goals for the project.

The PM's responsibilities are:

  1. To help the SMF team set goals.
  2. To lead the SMF team toward meeting the team's goals, help solve problems
  3. To help the teams collaborate, stay informed of the effect they have on one another, and work together effectively.
  4. To mediate conflict between team members, or between team members and community members, in order to help the parties reach an agreement.
  5. When authorized by the SC, to speak on behalf of the steering committee.
  6. To serve as team figurehead -- representing the team to the community, answering general inquiries, turning some questions over to other experts on the team.
  7. To identify areas for improvement within the project.
    • Inform or advise the responsible parties, bring it to the attention of the SC, or appoint someone to handle it.
    • The SC must be notified of all such appointments.

In order to carry out these duties,

  1. The PM should have administrative access to simplemachines.org, and related sites.
  2. The PM should have root access to the servers/VMs holding the infrastructure of the SMF project, in order to be able to help in case of emergency.

The PM is empowered to:

  1. Perform administrative duties necessary for the team, such as changing groups (set as Friend, apprentice, etc.).
  2. Intervene and make project decisions, in case of emergency, when the respective person responsible is not available. These situations include, but are not limited to:
    • The responsible team lead or member is inactive or otherwise unavailable, and immediate action needs to be taken.
    • The project is seriously endangered, as when immediate removal of a team member is necessary.

Restrictions on the powers of the PM are:

  1. When the PM takes administrative action to change member access, removal of team members, or other emergency actions, he must inform the SMF leadership or the team.
  2. The PM must provide an explanation for any decision or action, at the request of the SMF leadership.
  3. The SMF leadership can reverse any decision or action of the PM. The SMF leaderhip may make a decision without taking a formal poll. If any member of the SC (including the PM) requests a poll on the matter, a poll may be taken.
  4. The SMF team can reverse any decision or action of the PM.

Team Leads

Each of the teams within the SMF project has a team lead. The team lead are responsible for:

  • Reporting progress during team meetings.
  • Participating in Steering Committee discussions.
  • Keeping the other teams informed of important changes or events.
  • Keeping their team motivated & on task.
  • Helping team members stay involved.
  • Giving team members the recognition and credit they merit for their successes and accomplishments.
  • Supporting the personal and professional growth of each and every member of the team
  • Watching for new team members and recruiting them.
  • Making sure apprentice members and new team members have a mentor, that the mentor works as closely with the new member as necessary, and that apprentices makes appropriate progress during the apprenticeship period.

Developers

Did you know?
The “SE” in YaBB SE stood for “Splinter Edition” after Splinter from the Teenage Mutant Ninja Turtles. Ninjas are cool, and YaBB SE was designed to be cool, too. And it was a developed by a small splinter group of the original YaBB Team.

Developers create the software. Without them, there is no software community. For the SMF community to remain vital, the software must remain vital. The developers must lead in decisions about where technology is going, and where SMF needs to go to stay current. They need to consider everything from what the users want, to making the features run efficiently, to making sure all the pieces get tested properly.

For information and ways to contribute, please refer to the Development pages.

Support Specialists

  • Helping our users have an exceptional SMF experience.
  • Providing special attention to the Charter Members.
  • Monitoring the help desk & getting tickets to a “closed” state.
    • Check Help Desk first.
    • Check Charter Member boards.
    • Check Support boards.
  • Revisit your old posts and mark as solved when appropriate.
  • Perform upgrades and installs for Charter Members.
  • Support the core software by answering questions, suggesting fixes, etc.
  • Act as a filter for bug reports, reporting legitimate ones to the bug tracker.
  • Look for common problems/errors and suggest documentation or code changes to reduce them.
  • Assume nothing. Always ask questions, no matter how tedious that can get. If a post is unclear, don't make assumptions. Ask for clarification.
  • Some posts may seem trivial, to you. Remember that they aren't trivial to our users. Always strive to be friendly and helpful. You are SMF's "Front line". The way you are perceived will reflect on SMF, not just you.
  • Always try to remember to tell users to backup, before attempting anything. If you don't remind them, they'll almost certainly forget.
  • If you begin helping, on a certain topic, try to maintain an interest in that topic; don't just leave it if you're stuck. There's a "Support Helpers" board. Use that to alert other support team members of your plight.
  • If you're going to be away from the boards, whilst you're helping someone, try to let other members of the team know, so that they can take that topic over for you, rather than letting the person you're helping just "Hang".

Customizers

Customizers are developers who can provide mods and/or themes for SMF. They review and approve mods and themes submitted by the community, and they maintain the customization site. Their duties include:

  • Watching for feature ideas that should be put into mods.
  • Updating SMF's official mods as necessary to maintain compatibility.
  • Updating SMF's official themes as necessary to maintain compatibility.
  • Designing new themes.
  • Theme Site maintenance.
    • Approving community-created themes.
  • Mod Site maintenance.
    • Approving community-created mods.
  • Graphics images (i.e. Buttons & smileys).
  • Other graphics as requested/required.
  • Give support to people trying to create themes and modifications.
  • Suggest changes to make theme and modification creation easier and more powerful.
  • Write mods that follow the coding guidelines and as though they were writing a default SMF feature.
  • Provide support in the Coding Discussion and Graphics boards.

Doc Writers

Documentation Writers write and maintain the online documentation at simplemachines.org. They may be called upon to write and maintain any documentation within the forum software itself. They may work with and recruit [b]Doc Helpers[/b] from the community to help out. Their responsibilities.

  • Maintaining the Online Manual.
    • Write clear, accurate, and easy to understand documentation.
    • Review and update update text as needed.
  • Work with localizers, site, and dev teams to enable document translations.
  • Write, review, or proofread other SMF team publications, including our news announcement postings.
  • Maintain the SMF Team Manual

Localizers

  • Coordinate the activity of Translators and Language Moderators.
  • Validate new translation team applications.
  • Manage the [email protected] correspondence.
  • Add /remove new translators.
  • Enhance accessibility to translate the wiki docs.
  • Informing community regarding language related topics of interest.

Others who contribute to the SMF project

These individuals also volunteer their time on behalf of the project, but are not members of the SMF project.

Simple Machines organizational teams

The SMF project depends on teams from the Simple Machines corporate organization for Marketing and to maintain its site and its servers. These teams are not officially part of the SMF project. The site team is responsible for maintaining and upgrading SimpleMachines.org and the software on it. The server team is responsible for specifying, configuring and maintaining the organization's servers and other hardware. The marketing team is responsible for planning press releases, attendance to conferences and other public relations details. Additionally, the marketing team works on acquiring sponsorships as well as maintaining and supporting the advertisements and advertisers on the simplemachines.org site.

Forum Administrators

Forum administrators take care of routine tasks like banning and deleting accounts, as well as less-common tasks like creating membergroups and adjusting membergroup permissions. These tasks are generally handled by site and server team members, by the SMF project manager and by other SMF team members.

Friends

Former members of the SMF team, some of whom are still members of the Simple Machines organization. They often share their experiences with the team. Some Friends may re-join the team when they again have time to commit to the SMF project.

Community Helpers

Some community members have been invited to join special-purpose membergroups. They do not have access to SMF team-only boards, but do have some permissions that other members of the community do not have.

  • Consulting Developers
  • Beta Testers.
  • Language Moderators -- moderate and provide support on non-English language boards.
  • Translators -- with their work SMF is available for many languages.

Anyone who wishes may join these membergroups right from their own profile

  • Doc Helpers.
  • Community Support Helpers.

Many other members of the community contribute in one way or another without holding any title at all. They are important to keeping things going at simplemachines.org



Advertisement: