Roles: Difference between revisions

From My Wiki
Jump to navigation Jump to search
imported>Isaac
desc
imported>Bnewbold
style
 
(4 intermediate revisions by 2 users not shown)
Line 1: Line 1:
In building out the ldap infrastructure, the ops team has come up with these functional roles. On a technological level, they will be used to permission access to enterprise information systems. On a human level, they will shape the way we think about our relations. As such, we wanted to share this proposal, and request your feedback. We enumerated five roles:
In building out the ldap infrastructure, the technical operations team has come up with these functional roles.  


On a technological level, they will be used to provide different permission levels/access to FNF enterprise information systems.


*Participant
On a human level, they will shape the way we think about our relations. As such, we wanted to share this proposal, and request your feedback.
Someone who is following the project, can read everything, and write to the forum and wiki


*Contributor
We have enumerated several roles, based on existing levels of privilege/access.
Someone who is contributing to discussion, can read everything, write to the forum, wiki, kb, and chili.


*Builder
=== Guest ===
Someone who is contributing to development, can read everything, write to the forum, wiki, kb, chili, git, lab.


*TechnicalOps
'''Quick Description/overview of role:'''
This is the base level of access. It can be created by anyone (through a yet as undetermined provisioning  interface).
 
'''Abilities:'''
Read only access to everything.
 
=== Participant ===
 
'''Quick Description/overview of role:'''
Someone who is following the project at a more casual level.
 
'''Abilities: '''
Read everything, and perform the following write operations:
 
# Create/edit wiki pages
# Post to the forum
# Vote in a poll or other light/quick activity (such as comment on the blog)
 
=== Contributor ===
 
 
'''Quick Description/overview of role:'''
Someone who is actively contributing to the project.
 
'''Abilities:'''
 
# read everything
# write to the forum, wiki, kb, and chili.
 
===Builder===
 
 
'''Quick Description/overview of role:'''
Someone who is contributing to development,
 
'''Abilities:'''
 
# can read everything
# write to the forum, wiki, kb, chili, git, lab.
 
===TechnicalOps===
 
 
'''Quick Description/overview of role:'''
Someone who is maintaining the enterprise infrastructure. Has administrative access to servers, cpanel, applications.
Someone who is maintaining the enterprise infrastructure. Has administrative access to servers, cpanel, applications.


*BusinessAdministration
===BusinessAdministrator===
Someone who is contributing to the operations of the foundation. Can write to CRM/Dolibar.
 
'''Quick Description/overview of role:'''
Someone who is contributing to the operations of the foundation.  
 
'''Abilities:'''
Can write to CRM/Dolibar.

Latest revision as of 03:10, 27 June 2012

In building out the ldap infrastructure, the technical operations team has come up with these functional roles.

On a technological level, they will be used to provide different permission levels/access to FNF enterprise information systems.

On a human level, they will shape the way we think about our relations. As such, we wanted to share this proposal, and request your feedback.

We have enumerated several roles, based on existing levels of privilege/access.

Guest

Quick Description/overview of role: This is the base level of access. It can be created by anyone (through a yet as undetermined provisioning interface).

Abilities: Read only access to everything.

Participant

Quick Description/overview of role: Someone who is following the project at a more casual level.

Abilities: Read everything, and perform the following write operations:

  1. Create/edit wiki pages
  2. Post to the forum
  3. Vote in a poll or other light/quick activity (such as comment on the blog)

Contributor

Quick Description/overview of role: Someone who is actively contributing to the project.

Abilities:

  1. read everything
  2. write to the forum, wiki, kb, and chili.

Builder

Quick Description/overview of role: Someone who is contributing to development,

Abilities:

  1. can read everything
  2. write to the forum, wiki, kb, chili, git, lab.

TechnicalOps

Quick Description/overview of role: Someone who is maintaining the enterprise infrastructure. Has administrative access to servers, cpanel, applications.

BusinessAdministrator

Quick Description/overview of role: Someone who is contributing to the operations of the foundation.

Abilities: Can write to CRM/Dolibar.