Deployment wiki access control

This topic outlines the different levels of access control to the wiki, with supporting guidance on when and how to change the levels for specific topic pages.

Levels of access control to the Deployment wiki

Read access to the Deployment wiki is unrestricted. You do not even need to log in with your Jazz.net user ID for full read access, which facilitates external search engine indexing and search, such as Google.

Three groups are used to control write access to all topic pages:

• Technical leaders and senior editors: This group consists of deployment experts nominated from customers, partners and Rational. Membership of this group is based on nominations submitted for consideration to the community technical leaders and senior editors using the web-based nomination process. This group is enabled by TWikiDeploymentAuthorsGroup for all members.

• Deployment practitioners: This group consists of Deployment practitioners nominated from customer and partners, and members of Rational teams. Membership of this group customers and partners is based on nominations submitted for consideration to the community technical leaders and senior editors using the web-based nomination process. Anyone from a Rational team can request membership of this group (see Deployment wiki request write access for IBMers). This group is enabled by a combination of TWikiExternalAuthorsGroup for customers and partners, and TWikiAuthorsGroup for IBMers,

• Jazz.net users: All Jazz.net users have write access to open community topic pages using their existing Jazz.net user ID and password. This group is enabled by the Jazz.net users LDAP group.

By default, write access to all wiki pages is restricted to the TWikiDeploymentAuthorsGroup. Subsequently the community or section technical leaders and senior editors can open a page for wider write access to the Deployment practitioners (TWikiAuthorsGroup and TWikiExternalAuthorsGroup) or Jazz.net users (Jazz.net LDAP group). The granting of wider write access must occur on a page-by-page basis.

Many topic pages will be initially created by the technical leaders and senior editors, and then opened for wider write access to the Deployment practitioners or Jazz.net users. However, some core pages that contain fundamental or critical guidance and best practices will only ever be editable by the technical leaders and senior editors. It is important to strike the right balance between core pages that are only editable by experts to maintain a high quality versus community pages that allow the full community to contribute. Many of the core pages allow comments and questions to be raised to enable wider community contribution.

Changing the level of write access control for a topic page

The color of the title box at the top of each page denotes the level of write access. This will give a clear visual cue as to who can edit a page, and the provenance and quality of the guidance on that page. Below are illustrations of the three title box colors and the verbatim Twiki mark-up, with access control required for each:

 
<div id="header-title" style="padding: 10px 15px; border-width:1px; border-style:solid; border-color:#FFD28C; background-image: url(<nop>https://jazz.net/wiki/pub/Deployment/WebPreferences/TLASE.jpg); background-size: cover; font-size:120%">
---+!! Technical leaders and senior editors
%DKGRAY% Authors: Main.StevenBeard <br>
Build basis: None
%ENDCOLOR%</div></sticky>

 
<!--
   * Set ALLOWTOPICCHANGE = Main.TWikiDeploymentAuthorsGroup, Main.TWikiAuthorsGroup, Main.TWikiExternalAuthorsGroup
-->
<div id="header-title" style="padding: 10px 15px; border-width:1px; border-style:solid; border-color:#A8CEE4; background-image: url(<nop>https://jazz.net/wiki/pub/Deployment/WebPreferences/DP.jpg); background-size: cover; font-size:120%">
---+!! Deployment practitioners
%DKGRAY% Authors: Main.StevenBeard <br>
Build basis: None
%ENDCOLOR%</div></sticky>

 
<!--
   * Set ALLOWTOPICCHANGE = 
-->
<sticky><div id="container" >
<div id="header-title" style="padding: 10px 15px; border-width:1px; border-style:solid; border-color:#A8CEE4; background-image: url(<nop>https://jazz.net/wiki/pub/Deployment/WebPreferences/DP.jpg); background-size: cover; font-size:120%">
---+!! Deployment practitioners
%DKGRAY% Authors: Main.StevenBeard <br>
Build basis: None
%ENDCOLOR%</div></sticky>

Note: Please be very careful when setting the write access for a topic (ALLOWTOPICCHANGE) because it is very easy to get it wrong and remove write access for yourself and others!

Detailed steps required to gain different levels of write access

Open community topic page write access for Jazz.net users

There are no additional steps required other than to register as a Jazz.net user for this level of write access. It will be enabled for all existing Jazz.net users and any newly registered Jazz.net users go forward. You must login with your Jazz.net credentials to edit an open community topic page.

Deployment practitioner topic page write access for IBMers

IBMers just need to follow the steps to [[RequestWriteAccessForIBMers][Request write access for IBMers]. There are no additional approval steps required and write access to deployment practitioner topic pages and membership of the Deployment wiki RTC project should be enabled within a couple of days.

This will result in the user being added to:

1. The jazzwriter's LDAP group
2. The TWikiUsers list
3. The TWikiAuthorsGroup
4. The membership of the [https://jazz.net/jazz02/web/projects/Deployment%20Wiki#action=com.ibm.team.dashboard.viewDashboard][Deployment wiki RTC project]]

Deployment practitioner topic page write access for customers and partners

All customers and partners should follow the deployment practitioner nomination process to request this level of write access. This nomination will then be approved or rejected by a combination of the IBM sponsor for the nomination and one of the community technical leaders and senior editors.

If approved, the user will be added to the:

1. The jazzwriter's LDAP group
2. The TWikiUsers list
3. The TWikiExternalAuthorsGroup
4. The membership of the [https://jazz.net/jazz02/web/projects/Deployment%20Wiki#action=com.ibm.team.dashboard.viewDashboard][Deployment wiki RTC project]]

Finally, the user will be emailed to notify them that their nomination has been accepted and they have been set-up for this level of write access.

Technical leader and senior editor topic page write access for IBMers

Note: IBMers should first request Deployment practitioner topic page write access.

Secondly, IBMers should should follow the deployment technical leaders and senior editors nomination process to request this level of write access. This nomination will then be approved or rejected by the full community technical leaders and senior editors.

If approved, the user will be additionally added to the TWikiDeploymentAuthorsGroup.

Technical leader and senior editor topic page write access for customers and partners

Customers and partners should follow the deployment technical leaders and senior editors nomination process to request this level of write access. This nomination will then be approved or rejected by a combination of the IBM sponsor for the nomination and the full community technical leaders and senior editors.

If approved, the user will be added to:

1. The jazzwriter's LDAP group
2. The TWikiUsers list
3. The TWikiExternalAuthorsGroup
4. The TWikiDeploymentAuthorsGroup
5. The membership of the [https://jazz.net/jazz02/web/projects/Deployment%20Wiki#action=com.ibm.team.dashboard.viewDashboard][Deployment wiki RTC project]]

Finally, the user will be emailed to notify them that their nomination has been accepted and they have been set-up for this level of write access.

Related topics: Deployment Wiki Request Write Access for IBMers, Deployment technical leaders and senior editors nomination process, Deployment practitioners nomination process

External links:

• None

Additional contributors: None