Site Infrastructure

Website Infrastructure Life Cycles

Introduction

This document outlines the policies and procedures for managing community website infrastructure on opensolaris.org.

The website supports three types of community infrastructure -- Community Groups, Projects, and User Groups. During regular operations, members of the community propose and manage their own groups on the site as per the OpenSolaris Constitution. But the processes for actually activating, deactivating, reactivating, transitioning, and terminating the infrastructure are managed by administrators from the Website Engineering Team ^[1]. In the sections below, the interactions between the community and the website administrators are described, and the materials community members need to properly manage their groups are documented.

Contacts

For questions concerning the implementation of community infrastructure, post to website-admin AT opensolaris DOT org.

Life Cycles

The policies for approving Community Groups, Projects, and User Groups are the same, and the implementation procedures are largely the same as well. Any distinctions or exceptions involving implementation are are called out in the text below.

Activation

Community Groups, Projects, and User Groups are approved via processes outlined in the OpenSolaris Governing Board's "Lifecycle Administrative Procedures" document, which is part of the OpenSolaris Constitution. To engage the implementation procedures after a group is approved, send mail to website-admin requesting that the group be set up on the site. All communication from that point forward will take place on website-admin. Note that the website-admin list is private, and the following information is required:

The bug ID and link to the bug report documenting the original request and approval.
The full title ^[2] of the group and the abbreviation name ^[2] for the group's URL (For example: Full title: Installation and Packaging. Abbreviation name for URL: install). Do not use "Solaris" or "OpenSolaris" in the name of a Community Group or Project. Solaris and OpenSolaris are trademarks ^[3] of Oracle Corporation and will not be used without Oracle legal approval. Use a generic name instead. Although "OpenSolaris" is a trademark, it is considered fair use to use OpenSolaris in the name of a User Group, such as Tokyo OpenSolaris User Group. We encourage this format.
A brief public description of the group.
The opensolaris.org user names and email addresses of the group's Facilitator and Leaders.
If the group requires a mailing list, the name of the list ^[2], and the names of Leaders who will administer the list. Names for group lists should be in the following format:
- For Community Groups: [name]-discuss AT opensolaris DOT org
- For Projects: [name]-dev AT opensolaris DOT org
- For Projects: [name]-discuss AT opensolaris DOT org
- For Projects: [name]-notify AT opensolaris DOT org
- For User Groups: ug-[name]osug AT opensolaris DOT org

If everything is in order, a space will be set up on the site and Leaders will be added to the group in the Auth database. The OGB Secretary will add the Facilitator to the group's Electorate in Auth since that is a governance role (NOTE: Currently, governance roles will only be added to Community Group Electorates]. Leaders of all groups are expected to populate their pages with content and announce their new group on opensolaris-announce AT opensolaris DOT org (subscribe here). To properly maintain their website infrastructure, all group Leaders are also responsible for following these website policies:

Deactivation and/or Termination

There are two ways a group's website infrastructure can be deactivated and/or terminated:

The Website Team can deactivate and/or terminate website infrastructure if it is not well maintained (filled with spam or violations of the TOU, etc) or abandoned for 3 months based on the OpenSolaris Website Guidelines.
Group Leaders can request that their group be deactivated and/or terminated.

In these cases, the procedures below will be followed:

If the Website Team initiates this action, the team will post mail to the group's list requesting that action be taken to maintain the site's infrastructure properly. If a group's website infrastructure becomes completely abandoned, the Website Team will post mail to the OGB requesting that action be taken to replace the Leaders and/or deactivate/terminate the group. If a decision is not made within 3 months, the Website Team can deactivate and/or terminate the group.
- In the case of deactivation, mailing lists and forums will be reset to disable new subscriptions and new postings but archives will be saved. If there has been no activity to archive, the lists and forums will be deleted. In the case of termination instructions the group's Leaders, the mailing list infrastructure will be deleted.
- In the case of deactivation, the group's web pages will be tagged with text indicating that the group is no longer active, and the members of the group who have website edit privileges will no longer have the ability to edit the group's web pages unless the group is reactivated. However, any governance privileges among group members will remain unless the OGB specifies otherwise. In the case of termination instructions the group's Leaders, the group space on the site will be deleted.
If Community Group Leaders initiate the process, they will follow the Lifecycle Administrative Procedures" document.
Source Code Management for Projects
- Access to SCM repositories will be disabled if a Project is deactivated. SCM repositories will be deleted if a Project is terminated.
- To request that repositories be deleted on active Projects, the Leaders should post to tonic-ops AT sun DOT com and/or website-admin AT opensolaris DOT org and the Website Team will delete the repos. In the future, this feature will be added to the SCM Console so Leaders can delete repositories themselves.

Reactivation and/or Transition

To reactivate an inactive group or transition a group to a different type, follow the OGB's the Lifecycle Administrative Procedures document and send mail to website-admin with the following information:

The names of the group and mailing list.
The opensolaris.org user names and email addresses of the group's Facilitator and Leaders.
The opensolaris.org user names and email addresses of the Leaders who will administer the mailing list.

References

Website Documents

Notes

^[1] The Website Engineering Team, which is part of Oracle's OpenSolaris Open Development Engineering Team, builds and supports opensolaris.org on behalf of Oracle Corporation and the OpenSolaris Community. The team also leads the Website Community Group and updates the Infrastructure Life Cycle Documentation regularly to reflect changes in the OpenSolaris community and/or program.

^[2] The "title" of any Collective on the site is the text appearing at the top of a group's home page and also in the left drop-down navigation bar. That text can be edited. The "name" of any Collective on the site is the text that appears at the end of the URL. That text can not be edited once chosen and it must be unique to all the Collectives on the site. Also, regarding names for mailing lists, most groups choose to name their lists using the same name as as they use for their Collectives. This is not required but it is highly recommended for consistency.

^[3] OpenSolaris Trademarks Policy

Tags:

Created by Jim Grisanzio on 2009/12/18 15:44

Last modified by Jim Grisanzio on 2010/10/28 06:31