OpenSolaris Community: Advocacy Community Group
View the leaders for this community
Community Observers
The Advocacy Community
Group (CG) exists to help people around the world get involved in the
OpenSolaris community. We welcome participation from people of all
languages and cultures and people with all levels of technical and
non-technical skills.
Everyone
has something to
contribute.
In our community you will find
user
group projects,
presentations,
news,
articles,
newsletters,
blogs (
here,
here,
here), technical &
non-technical content, videos and podcasts,
events
and conferences,
community
metrics, swag,
badges
& buttons, and a variety of other promotional projects. And
if we don't have it, we'll try to link to it. Over time the Advocacy CG
will
sponsor both technical and non-technical projects but our focus will
remain on engaging users. Also over time, the editing of the Advocacy
CG pages will become easier to manage as opensolaris.org grows to
support customized wiki functionality. Currently, we
sponsor all the user group projects, the BeleniX development
discussion list, the trademark project, the mentoring project, the
OpenSolaris DevCon lists, and the OpenSolaris community awards program
list. Pretty much everything in that mix is geared toward users.
We are just getting started, though. We grew out of the
merger of three previous OpenSolaris communities -- marketing, user
groups, and immigrants. Links to the entire discussion about that
merger (including links to former list
archives) and the creation of the Advocacy CG can be found on the
Advocacy
merger archive page. Also, our hope is to work closely with all the
OpenSolaris distributions as they mature and as we all build a global
user community around various OpenSolaris
technologies.
Join the Advocacy CG: 3 Steps
- Register on opensolaris.org: https://www.opensolaris.org/register.jspa
- Sign up to the advocacy-discuss mail list: sign
up, archives,
web
forum
- Participate
Values & Governance
Our defining values
are simple: We embrace and promote the
OpenSolaris
Principles (
multi
lingual), and we are a community group in good standing under the
OpenSolaris
Constitution.
Facilitator
Jim Grisanzio
(jim
dot
grisanzio at sun dot com). The Advocacy facilitator is
responsible for managing any voting issues and notifying the secretary
of the OGB regarding changes to the contributor and/or core
contributors
lists. The facilitator also reports to the OGB when needed and
communicates back to Advocacy about any OGB-related issues. The role of
CG facilitators is outlined in
section
7.5 of the OpenSolaris Constitution.
Contributors,
Core Contributors, & Leaders
The Advocacy CG contributors and core contributors
are
all listed here. You can also search/sort under the
“grants” tab at
http://vote.opensolaris.org/
for a list of Advocacy contributors as well as all the OpenSolaris
contributors. For an
explanation of contributors and core contributors and voting
procedures, see the
OpenSolaris
Constitution. To make matters a bit confusing, there is also a set
of "
leaders"
that have edit rights to the Advocacy CG pages, and they may or may not
also be contributors and core contributors. That's a governance-website
bug. We'll get it fixed. Also, when the opensolaris.org infrastructure
expands to support wiki functionality (
see
restructuring of opensolaris.org), the various site roles will be
much easier to explain and track.
Current projects
and/or lists/pages sponsored by the Advocacy CG
We sponsor many projects, and we are interested in sponsoring many
more. Here is a current list:
Voting Procedures, User Group Proposals, Project Proposals
The Advocacy CG voting procedures are based on the
OpenSolaris
Constitution and the OpenSolaris Governing Board's
Project
Instantiation Policy and cover the following areas: Participant,
Contributor, Core Contributor, User Group Proposals, Project Proposals.
If any of this is confusing -- and it most certainly is -- just ask on
advocacy-discuss (
sign
up,
archives,
forum).
- Participant:
Register on
opensolaris.org and advocacy-discuss and participate in community
conversations and events.
- Contributor:
To earn contributor status you need to be nominated by a contributor or
core contributor. You also need a total of two +1 votes and no -1
votes.
Only core contributors can vote, and voting is open on advocacy-discuss
for five days. The initial nomination is considered a +1 vote. After
the voting, the new contributor must respond to the thread and accept
his or her grant.
- Core Contributor:
To earn core contributor status you need to be nominated by a core
contributor.
You also need a total of three +1 votes with no -1 votes. Only core
contributors can vote, and voting is open on advocacy-discuss for five
days. The initial nomination is considered a +1 vote. After the voting,
the new core contributor must respond to the thread and accept his or
her grant.
- User Groups:
To get user
group infrastructure (a project space and mailing list) on
opensolaris.org, you need to send a proposal to advocacy-discuss for
approval. You need one +1 vote and no -1 votes. Only Core Contributors
can vote, and voting is open on advocacy-discuss for five days. Write
your proposal in the following format:
- Name of user group
- Two or more initial participants listed with their OpenSolaris
user IDs
- A one paragraph description of the group -- including location,
activities planned, related organizations, etc.
- Projects:
Project
proposals follow the OGB's Project
Instantiation Policy. Voting follows the Constitution (Section
8.4). You need three +1 votes and no -1 votes. Only core
contributors
can vote, and voting is open on advocacy-discuss for five days. Write
your proposal in the following format (which is edited slightly from
the OGB's instantiation policy):
- A short synopsis of the project's purpose.
- A list of community groups sponsoring the project.
- A list of participants (with their OpenSolaris
user IDs) constituting the initial project team, including a single
individual who will serve as the preferred point of contact.
- A one paragraph description of the project for an audience of
participants who may not be familiar with the area in which work is
proposed. This should contain a brief description of the problem(s) the
project is expected to solve, and of the manner in which it will do so.
- A listing of related ongoing or proposed projects, including
information about any dependencies on or by this project and any
duplication of purpose or overlap with other ongoing work. This
listing should also include the name of the consolidation the project
team is targeting, if applicable.
- Optionally, additional information which may be of interest to
prospective project team members and/or consumers of the project's
output.
If your user group or project proposal is approved, the Advocacy
facilitator will set
up a project space and mail list. The project will be hidden until it
is ready to open with at least a minimum level of content (examples
include a welcome message, contact info, meeting location, list and
leader info, etc). Only the Advocacy facilitator can actually open a
project, so you will be working closely with Jim to get your project
and list set up.
As a leader of your
new user group or project, it is expected that you will maintain your
project space and mail list (filter spam, add/remove names,
communicate with the OpenSolaris webmaster and other community members,
etc)
just as all the other project leads in the OpenSolaris community.
Please review the
OpenSolaris
Website Guidelines and
Sun
trademarks policy so you are clear about various site issues --
especially the policy around mail list management. For instance, if
lists are not used and properly maintained, they can be deleted. Also,
please review the
Community/Project
lead reference so you are familiar with how to manage your
project – especially if you will be taking contributions from
non-Sun members of the community. And, of course, we all expect that
projects
within the Advocacy CG follow the open source spirit of transparency
and the governing rules specified by the OpenSolaris Constitution.
Page Updated: 5/1/08,
Jim
Grisanzio
OpenSolaris Developer Summit Graphic: Alex Seibert