Difference between revisions of "U.s.oo.o/User Community Roles"

From Apache OpenOffice Wiki
Jump to: navigation, search
m (Service Administrator)
(Roles available to Volunteers)
 
(57 intermediate revisions by 4 users not shown)
Line 1: Line 1:
This page is a spin-off of the Constitution page and specifically aims to provide a collaboration vehicle to agree the OOo User Community Rolls for the users of the site (''Users'').
+
This page is a spin-off of the Constitution page and specifically aims to provide a collaboration vehicle to agree the OOo User Community Roles for the users of the site (''Users'').
 +
 
 +
== User ==
 +
a ''User'' is any person who enters or uses the web site in any way, even if that person only visited the home page of the web site.
  
 
== Guest ==
 
== Guest ==
  
''Guests'' are Users who can search and access the information provided by the site, but cannot post or modify its content.  No registration or validation is required to be a Guest.  The site is open to all. <sup>([[#Limitations_on_Site_Access|1]])</sup>.   
+
A ''Guest'' is a User who can search and access the information provided by the site, but cannot post or modify its content.  No registration or validation is required to be a Guest.  The site is open to all. <sup>([[#Limitations_on_Site_Access|1]])</sup>.   
  
 
== Member ==
 
== Member ==
  
''Member'' are Users who have completed the site registration process<sup>([[#Site_Registration_Process|2]])</sup>. Members can also post or modify the information content of the site, within the content rules of the site.
+
A ''Member'' is a User who has successfully completed the site registration process<sup>([[#Site_Registration_Process|2]])</sup>. A Member can also post or modify the information content of the site, within the content rules of the site.
  
 
== Volunteer ==
 
== Volunteer ==
  
Any Member who wishes to take on a more active part in the life of the site (and commit to defined responsibilities for any site role that the Member has accepted) can request to become a ''Volunteer''.  The site Volunteers are collectively referred to as the User Community Volunteers ('''''UCV''''').  There is no cap on the size of the UCV.
+
A ''Volunteer'' is a Member who takes an active part in the life of the site and commits to defined responsibilities for a site role. A Member can request to become a ''Volunteer''.  Volunteers are collectively referred to as the User Community Volunteers ('''''UCV''''').  There is no cap on the size of the UCV.
  
There are four precursors to being accepted as a Volunteer:
+
The Member must apply to become a Volunteer though the registration process<sup>([[#Site_Registration_Process|2]])</sup>, and, if successful, will be elected to Volunteer status within the UCV. For a Member to be successful, some evidence of sustained commitment will normally be required; for example, numerous postings and wiki contributions, or a number of material articles over a six month period.  An equivalent track record in an associated community will normally be acceptable, for example, one of the other active OpenOffice.org or Linux related forums.
* The Member must apply to become a Volunteer<sup>([[#Site_Registration_Process|2]])</sup>.
+
* The Member must have shown some evidence of sustained commitment to the site.  An example of such commitment could be say 100 postings and wiki contributions, or a number of material articles over a six month period.  A equivalent track record on an associated community (for example one of the other active OpenOffice.org or Linux related forums will normally be acceptable.
+
* The Member's request must be supported by two or more Volunteers, who have validated the Members application and are willing to endorse this membership.
+
* The application must be endorsed by a UCV Vote<sup>([[#UCV_Voting_Process|3]])</sup>.  The quorum for the vote is one third of the UCV, and a two-thirds majority must be obtained of votes cast.
+
  
Any Volunteer may propose the removal of Volunteer status for any Volunteer.   
+
The UCV is intended to comprise the community of the active Members within the site, Volunteers may, therefore, revert back to a normal Member.
 +
* A Volunteer may resign from Volunteer status.
 +
* A six month period with no activity will automatically propose removal of Volunteer status.
 +
* Any Volunteer may propose the removal of Volunteer status for any other Volunteer. Justification must be included with the request. For example, repeated abuse or disregard of the site, the membership, or standing instructions endorsed by the UCV.
 +
The removal of Volunteer status is also controlled through the registration process<sup>([[#Site_Registration_Process|2]])</sup>, and where this occurs the individual will revert to normal Member statusA Member can always reapply for Volunteer status.
  
In cases where the Volunteer is not simply resigning from Volunteer status, but is proposed for removal by a second Volunteer, there must be just cause for the proposal; such cause could include:
+
Volunteers are regarded as trusted members of the site and therefore have available elevated privileges associated with such trust:
*lapse of status since the Member concerned has been inactive on the site and in the Volunteer role for over six months; 
+
* Full voting privileges within the UCV.
*repeated abuse or disregard of the site, the membership or standing instructions endorsed by the UCV/
+
* Ability to upload images and attachments to the site.
+
* Ability to use HTML in posts; most forum packages allow HTML as an option, and the layout is easier than in BBcode-style mark-up languages.
In such a case, the proposal must be supporting by a seconding Volunteer, and the removal must then be endorsed by a UCV Vote<sup>([[#UCV_Voting_Process|3]])</sup>.  The quorum for the vote is one third of the UCV, and a two-thirds majority must be obtained of votes cast. (Once removed, a member can subsequently reapply for Volunteer status.)
+
* Ability to blog.
 +
* Eligibility for site roles.
  
 
== Roles available to Volunteers ==
 
== Roles available to Volunteers ==
  
(These need fleshed out an this is really just a place holder on this first version, but the basic principle is that the list and responsibilities of the site roles can evolve overtime under change control and endorsement through the UCV voting process.  
+
The following User Community Roles are available to Volunteers.  Notwithstanding this, the list of site roles and responsibilities may evolve over time under change control and endorsement through the UCV voting process.  
  
 
===Site Administrator===
 
===Site Administrator===
 
Individuals that are willing to take on the responsibilities necessary to perform a due diligence in the following areas:
 
Individuals that are willing to take on the responsibilities necessary to perform a due diligence in the following areas:
  
Help maintain the security of the host system by:
+
*Help maintain the security of the host system by:
*Maintaining good working relationship with designated network administration staff at Sun Microsystems, Hamburg Germany.
+
**Maintaining a good working relationship with designated network administration staff at Sun Microsystems, Hamburg Germany.
*Perform steps necessary to carry out agreed upon configuration control procedures on application level services running on the server. During modifications of the applications, application of patches, reconfigurations.
+
**Maintain contact with the vendor's / supplier's information service for any applications run on the server.
*Maintain contact with the vendor's / supplier's information service for any applications run on the server.
+
**Take agreed upon steps when a security announcement is made by the vendors / suppliers.
*Take agreed upon steps when any security announcement is made by the vendors / suppliers.
+
**Follow agreed upon steps if a security breach of any application on the server is suspected. For example: notified by a board user that they suspect a problem.
*Follow agreed upon steps should a security breach of any application on the server become suspected. For example: notified by a board user that they suspect a problem.
+
**Perform steps necessary to carry out agreed upon configuration control procedures on application level services running on the server. During modifications of the applications, application of patches, reconfigurations.
*Follow agreed upon steps / actions to implement and maintain a disaster recovery plan. ( off site storage of backups, off site storage of application modifications, included files and configuration settings, etc )
+
**Follow agreed upon steps / actions to implement and maintain a disaster recovery plan ( e.g. off-site storage of backups, off-site storage of application modifications, included files and configuration settings).
*Support the Service Administrators by performing the following tasks
+
*Support the Service Administrators and Content managers by performing the following tasks:
**Create or apply modifications to the applications source, configuration files as needed.
+
**Create or apply modifications to the applications source or configuration files as needed.
**Configure client communication settings for the service application
+
**Configure client communication settings for the service application.
**Configure server configuration settings for the service application
+
**Configure server settings for the service application.
***Database indexing
+
***Database indexing.
***Database backups ( working with network admins )
+
***Database backups ( working with network admins ).
 +
***Install / configure support packages ( php libs, caching systems, etc ).
 +
 
 +
These individuals must also comply with all Standard Operating and Security Procedures defined by the hosting provider ( SUN Microsystems ), and to take whatever reasonable actions that the hosting provider requires of them in order to receive necessary host computer access privileges.
  
 
===Service Administrator===
 
===Service Administrator===
  
Individuals that are willing to take on the responsibilities necessary to maintain an application level service.  
+
Individuals that are willing to take on the responsibilities necessary to maintain an application level service. For example the Forum service Administrator would perform the following, and other, functions:
For example the Forum service Administrator would perform the following functions:
+
 
*May add, edit, delete, and reorder the forums, categories, and links.
 
*May add, edit, delete, and reorder the forums, categories, and links.
 
*Manage User Accounts
 
*Manage User Accounts
 
*Manage Group Accounts
 
*Manage Group Accounts
 
*Manage Board Level Settings ( Email, Template, etc )
 
*Manage Board Level Settings ( Email, Template, etc )
 +
*Support the Service Moderator's
  
===Content Manager===
+
These individuals are selected by the UCV alone.  The service administrator role is enabled through and provided by the relevant service application.  No action is required by the hosting provider to grant these privileges.
  
 
===Service Moderator===
 
===Service Moderator===
 +
 +
Moderator is a supporting administration role supported by some application services.  For example in the case of forums, moderators have an elevated level of privilege which enables them to modify or delete user posts that violate site policy (e.g. SPAM or obscenity).  Service Moderators are selected by the UCV Voting Process.  No action is required by the hosting provider to grant these privileges.
 +
 +
===Content Manager===
 +
These individuals are selected by the UCV alone.  The Content Manager role is enabled through and provided by the relevant service application. Where required Content Manager's may be granted User Account Interactive Access and MySQL datadase access.
  
 
===Ombudsman===
 
===Ombudsman===
 +
 +
The Ombudsman's role and responsibilities include:
 +
* Administration and oversight of all polls
 +
** The ombudsman can mandate that any specific vote be opened to the general membership, where he or she feels that there is a reasonable case for doing so.
 +
* NON-Voting member of all change control boards to represent the general membership. (do we have a process for this?)
 +
* Management and arbitration of Membership complaints.
 +
To avoid conflict of interest the Ombudsman cannot hold any other User Community Role.
 +
 +
=== Chronicler &mdash; Tie-breaker, spokesperson ===
 +
 +
* Shall be the official spokesperson for the organization on issues related to the interests and purpose. 
 +
* This person is not to vote unless there is a tie that freezes the issue at hand.
 +
 +
=== The Projects Manager ===
 +
* Shall assist in infrastructural development so that documentation of projects is done to some extent.
 +
* Maintains the projects' wiki pages.
 +
* Shall take charge of post-mortems of projects so useful information can be amassed as to what structures worked and what didn't.
 +
 +
=== Group Publicity Person &mdash; OO.o Evangelist ===
 +
* Shall come up with fun and useful "virtual events" that promote the use of OO.o and the support forums.
 +
* Shall abide by all local regulations and group agreements when promoting the organization or its views,
  
 
== Footnotes ==
 
== Footnotes ==
  
 
===Limitations on Site Access===
 
===Limitations on Site Access===
Some transactional rate limiting mechanisms may apply to prevent robot users degrading the performance of the site for normal interactive users.  We also need to consider whether we bar certain users and / or IP address/domains.  
+
Some transactional rate limiting mechanisms may apply to prevent robot users from degrading the performance of the site for normal interactive users.  We also need to consider whether we bar certain users and / or IP address/domains (based on bots, spam, abuse, etc).
  
 
===Site Registration Process===
 
===Site Registration Process===
 
The Site Registration Process has two variants:
 
The Site Registration Process has two variants:
  
*The standard process is for Users who want to become a Member of the site. The main reason form this process is to assign an identity for purposes of tracking changes that the user wishes to make. The minimum content is correct response to a "Captcha" dialogue or equivalent to eliminate SPAMing bots, and the submission a valid contact email address and response to an email sent to that address. The email address is retained as confidential information and not published on the site without written authorisation by said Member. It is there is to ensure that the site has a means of contacting the member: the site will not permit contributions from users without a valid supporting contact address. There are various other optional fields that the User can specify.
+
*The standard process is for a Guest who wants to become a Member; a Member can post, a Guest can not. The main purpose for registration, is is to associate changes made by a user with an identity. For example, a common forum feature is to list posts by author. The registration process will minimize SPAM bots through use of tools such as a "Captcha" or equivalent. A valid contact email address is required along with a response to an email sent to the submitted address. The email address is retained as confidential and not published to general members without authorization by the Member. The email address provides a means of contacting the members, but is only available to the system (for automated requested contacts such as a forum topic has been updated) and to members with specific roles such as a system administrator or moderator. A Guest can not become a member without a valid, verified, contact address. There are various other optional fields that the User can specify.
  
*The stricter process is for Users who want to become a Volunteer. Since such Volunteers can be appointed to trusted roles within the site, the UCV needs to have some confidence in the provenance and credentials of the applicantIn this case the application must include an a public identity (name, country, work experience, etc.) and a short personal statement of why the candidate wishes to become a volunteer. These details will normally be validated by two existing volunteers. The applicant must agree that all such details can be made available to peer Volunteers, but not accessible by normal Guests and Members except at the Volunteer's own discretion.
+
*A stricter process controls the transition from Member to Volunteer, and from Volunteer to normal Member. Volunteers may be appointed to trusted roles, so the UCV must have confidence in the provenance and credentials of the Member.   
 +
** A forum exists for discussing the Registration Process. Although only Volunteers can post to this forum, all Members can view the forum<sup>('''+''')</sup>.
 +
** All applications for promotion to or removal from Volunteer status are posted to this forum as a new topic.  Any Member can make an application through a Volunteer (for example the ombudsman) which typically contains a brief identity (name, country, work experience, etc.) and a short personal statement of why the candidate wishes to become a Volunteer.
 +
** Any Volunteer may comment on the application.
 +
** Any Volunteer may explicitly designate approval.
 +
** Any Volunteer may explicitly designate a protest.
 +
** The application is open for [two] weeks.
 +
** If at the end of this period at least two approvals and no protest have been made then Volunteer status change is granted.
 +
** The change is declined if there are not at least two approvals.
 +
** If there are least two approvals and at least one protest, a vote of the UCV membership is performed under the standard UCV voting procedure.
 +
** Where the application is declined, reapplication can be made after [3] months.
 +
 
 +
('''+''') There are issues of disclosure that we need to think about here.  See the
 +
[[Talk:U.s.oo.o/User_Community_Roles#proposed_change_to_Process_of_becoming_a_volunteer|Talk page]] for further discussion on this.
  
 
===UCV Voting Process===
 
===UCV Voting Process===
  
Again another placeholderIn general the UCV will be the normal voting forumHopefully we can batch routine votes up to say once per month, so that we don't get bombarded by votes.
+
Members of the Volunteer site team may hold votes on topics within their areas of interest separate from those interests voiced by Registered or unregistered users of the siteTechnical issues of interest to Volunteers may include any topic, including which issues will be decided by general Registered Member votes.  Topics under consideration will be posted to a Forum category devoted to these issues and the results will be posted there as well.  Registered members may comment on these issues or raise questions.
 +
 
 +
==== Voting Guidelines ====
 +
General Voting on issues of importance to the members regarding the site or the management will take place quarterly on the first Tuesday of January, April, July, and OctoberA Forum category will be set up devoted to these issues and the results will be posted there as well.  Only registered site members will be able to vote in these quarterly events.  In most cases, a simple majority vote will suffice.  This means in the case of a stand-off, a vote will be rescheduled for the next quarter. 
 +
 
 +
''Please do not change the logical content of this page without first discussing this on the [[Talk:U.s.oo.o/User_Community_Roles|Talk Page]] and acknowledgement from the [[U.s.oo.o/Planning/User_services_Contact_list|UCV Contact list]].''
  
We also need to think about the when, what how of general Membership votes.
+
[[Category:UCV]]

Latest revision as of 04:58, 13 October 2007

This page is a spin-off of the Constitution page and specifically aims to provide a collaboration vehicle to agree the OOo User Community Roles for the users of the site (Users).

User

a User is any person who enters or uses the web site in any way, even if that person only visited the home page of the web site.

Guest

A Guest is a User who can search and access the information provided by the site, but cannot post or modify its content. No registration or validation is required to be a Guest. The site is open to all. (1).

Member

A Member is a User who has successfully completed the site registration process(2). A Member can also post or modify the information content of the site, within the content rules of the site.

Volunteer

A Volunteer is a Member who takes an active part in the life of the site and commits to defined responsibilities for a site role. A Member can request to become a Volunteer. Volunteers are collectively referred to as the User Community Volunteers (UCV). There is no cap on the size of the UCV.

The Member must apply to become a Volunteer though the registration process(2), and, if successful, will be elected to Volunteer status within the UCV. For a Member to be successful, some evidence of sustained commitment will normally be required; for example, numerous postings and wiki contributions, or a number of material articles over a six month period. An equivalent track record in an associated community will normally be acceptable, for example, one of the other active OpenOffice.org or Linux related forums.

The UCV is intended to comprise the community of the active Members within the site, Volunteers may, therefore, revert back to a normal Member.

  • A Volunteer may resign from Volunteer status.
  • A six month period with no activity will automatically propose removal of Volunteer status.
  • Any Volunteer may propose the removal of Volunteer status for any other Volunteer. Justification must be included with the request. For example, repeated abuse or disregard of the site, the membership, or standing instructions endorsed by the UCV.

The removal of Volunteer status is also controlled through the registration process(2), and where this occurs the individual will revert to normal Member status. A Member can always reapply for Volunteer status.

Volunteers are regarded as trusted members of the site and therefore have available elevated privileges associated with such trust:

  • Full voting privileges within the UCV.
  • Ability to upload images and attachments to the site.
  • Ability to use HTML in posts; most forum packages allow HTML as an option, and the layout is easier than in BBcode-style mark-up languages.
  • Ability to blog.
  • Eligibility for site roles.

Roles available to Volunteers

The following User Community Roles are available to Volunteers. Notwithstanding this, the list of site roles and responsibilities may evolve over time under change control and endorsement through the UCV voting process.

Site Administrator

Individuals that are willing to take on the responsibilities necessary to perform a due diligence in the following areas:

  • Help maintain the security of the host system by:
    • Maintaining a good working relationship with designated network administration staff at Sun Microsystems, Hamburg Germany.
    • Maintain contact with the vendor's / supplier's information service for any applications run on the server.
    • Take agreed upon steps when a security announcement is made by the vendors / suppliers.
    • Follow agreed upon steps if a security breach of any application on the server is suspected. For example: notified by a board user that they suspect a problem.
    • Perform steps necessary to carry out agreed upon configuration control procedures on application level services running on the server. During modifications of the applications, application of patches, reconfigurations.
    • Follow agreed upon steps / actions to implement and maintain a disaster recovery plan ( e.g. off-site storage of backups, off-site storage of application modifications, included files and configuration settings).
  • Support the Service Administrators and Content managers by performing the following tasks:
    • Create or apply modifications to the applications source or configuration files as needed.
    • Configure client communication settings for the service application.
    • Configure server settings for the service application.
      • Database indexing.
      • Database backups ( working with network admins ).
      • Install / configure support packages ( php libs, caching systems, etc ).

These individuals must also comply with all Standard Operating and Security Procedures defined by the hosting provider ( SUN Microsystems ), and to take whatever reasonable actions that the hosting provider requires of them in order to receive necessary host computer access privileges.

Service Administrator

Individuals that are willing to take on the responsibilities necessary to maintain an application level service. For example the Forum service Administrator would perform the following, and other, functions:

  • May add, edit, delete, and reorder the forums, categories, and links.
  • Manage User Accounts
  • Manage Group Accounts
  • Manage Board Level Settings ( Email, Template, etc )
  • Support the Service Moderator's

These individuals are selected by the UCV alone. The service administrator role is enabled through and provided by the relevant service application. No action is required by the hosting provider to grant these privileges.

Service Moderator

Moderator is a supporting administration role supported by some application services. For example in the case of forums, moderators have an elevated level of privilege which enables them to modify or delete user posts that violate site policy (e.g. SPAM or obscenity). Service Moderators are selected by the UCV Voting Process. No action is required by the hosting provider to grant these privileges.

Content Manager

These individuals are selected by the UCV alone. The Content Manager role is enabled through and provided by the relevant service application. Where required Content Manager's may be granted User Account Interactive Access and MySQL datadase access.

Ombudsman

The Ombudsman's role and responsibilities include:

  • Administration and oversight of all polls
    • The ombudsman can mandate that any specific vote be opened to the general membership, where he or she feels that there is a reasonable case for doing so.
  • NON-Voting member of all change control boards to represent the general membership. (do we have a process for this?)
  • Management and arbitration of Membership complaints.

To avoid conflict of interest the Ombudsman cannot hold any other User Community Role.

Chronicler — Tie-breaker, spokesperson

  • Shall be the official spokesperson for the organization on issues related to the interests and purpose.
  • This person is not to vote unless there is a tie that freezes the issue at hand.

The Projects Manager

  • Shall assist in infrastructural development so that documentation of projects is done to some extent.
  • Maintains the projects' wiki pages.
  • Shall take charge of post-mortems of projects so useful information can be amassed as to what structures worked and what didn't.

Group Publicity Person — OO.o Evangelist

  • Shall come up with fun and useful "virtual events" that promote the use of OO.o and the support forums.
  • Shall abide by all local regulations and group agreements when promoting the organization or its views,

Footnotes

Limitations on Site Access

Some transactional rate limiting mechanisms may apply to prevent robot users from degrading the performance of the site for normal interactive users. We also need to consider whether we bar certain users and / or IP address/domains (based on bots, spam, abuse, etc).

Site Registration Process

The Site Registration Process has two variants:

  • The standard process is for a Guest who wants to become a Member; a Member can post, a Guest can not. The main purpose for registration, is is to associate changes made by a user with an identity. For example, a common forum feature is to list posts by author. The registration process will minimize SPAM bots through use of tools such as a "Captcha" or equivalent. A valid contact email address is required along with a response to an email sent to the submitted address. The email address is retained as confidential and not published to general members without authorization by the Member. The email address provides a means of contacting the members, but is only available to the system (for automated requested contacts such as a forum topic has been updated) and to members with specific roles such as a system administrator or moderator. A Guest can not become a member without a valid, verified, contact address. There are various other optional fields that the User can specify.
  • A stricter process controls the transition from Member to Volunteer, and from Volunteer to normal Member. Volunteers may be appointed to trusted roles, so the UCV must have confidence in the provenance and credentials of the Member.
    • A forum exists for discussing the Registration Process. Although only Volunteers can post to this forum, all Members can view the forum(+).
    • All applications for promotion to or removal from Volunteer status are posted to this forum as a new topic. Any Member can make an application through a Volunteer (for example the ombudsman) which typically contains a brief identity (name, country, work experience, etc.) and a short personal statement of why the candidate wishes to become a Volunteer.
    • Any Volunteer may comment on the application.
    • Any Volunteer may explicitly designate approval.
    • Any Volunteer may explicitly designate a protest.
    • The application is open for [two] weeks.
    • If at the end of this period at least two approvals and no protest have been made then Volunteer status change is granted.
    • The change is declined if there are not at least two approvals.
    • If there are least two approvals and at least one protest, a vote of the UCV membership is performed under the standard UCV voting procedure.
    • Where the application is declined, reapplication can be made after [3] months.

(+) There are issues of disclosure that we need to think about here. See the Talk page for further discussion on this.

UCV Voting Process

Members of the Volunteer site team may hold votes on topics within their areas of interest separate from those interests voiced by Registered or unregistered users of the site. Technical issues of interest to Volunteers may include any topic, including which issues will be decided by general Registered Member votes. Topics under consideration will be posted to a Forum category devoted to these issues and the results will be posted there as well. Registered members may comment on these issues or raise questions.

Voting Guidelines

General Voting on issues of importance to the members regarding the site or the management will take place quarterly on the first Tuesday of January, April, July, and October. A Forum category will be set up devoted to these issues and the results will be posted there as well. Only registered site members will be able to vote in these quarterly events. In most cases, a simple majority vote will suffice. This means in the case of a stand-off, a vote will be rescheduled for the next quarter.

Please do not change the logical content of this page without first discussing this on the Talk Page and acknowledgement from the UCV Contact list.

Personal tools