FAQ: Website Transition: User Actions
General Information
This FAQ contains questions and answers about user actions that will be changing due to the site transitions related to the transition to the Auth application, updates to the SCM console and the move to XWiki. Questions are grouped by topic.
If you would like a question added or an answer expanded or otherwise improved, please send email to website-discuss AT opensolaris DOT org with "User Action FAQ" in the subject line. And please be as specific as possible about a new question or what changes would make an existing question and answer more helpful.
Information about the website transition is also available in the Website Community Group, and there is an opensolaris.org Website Transition FAQ available as well.
NOTE: If you have questions about how your content looks on XWiki after the final content migration, please check the 'POST-MIGRATION' section of the content preparation page.
- General Information
- Roles & Collectives
- What is a collective?
- Why are we using the term 'collective'?
- How many collectives are there and what are they?
- Where does information about my collective relationships (i.e., my roles) appear on the website?
- Where do I manage my collective relationships (i.e., my roles)?
- How do I obtain a particular role?
- What privileges are associated with the Participant role?
- What are the roles specific to Community Groups?
- What are the roles specific to Projects?
- What are the roles specific to User Groups?
- How is role information used across the site?
- Account Management
- Where do I go to manage my profile?
- Do I have to update my profile?
- Do I have to provide my Contributor Agreement number or Sun employee information?
- How is my Contributor Agreement number entered if I file one after registering on the site?
- What do I do if I think I have a Contributor Agreement on file but the number is not listed in my account detail?
- Where do I report problems with CAPTCHA?
- Where do I report problems with confirming a new registration?
- Where do I report general problems with the Auth application?
- How do I change my password?
- How do I get an opensolaris.org email address?
- Source Code Repository Management
- Governance Roles & Privileges
- Administrative Tasks for Project and User Group Leaders
- How do I designate someone as a Participant in a Project or a User Group?
- How do I designate someone as a Developer in a Project?
- How do I give someone commit rights to a source code repository?
- How do I generally manage commit rights in a Project?
- How do I remove someone as a Developer in a Project?
- How do I designate someone as an Affiliate in a User Group?
- How do I remove someone as an Affiliate in a User Group?
Roles & Collectives
What is a collective?
Collective is the name we use to describe spaces on opensolaris.org that have groups of people organized to do something. There are three collective types built into the website: Community Groups, Projects, and User Groups. Community Groups are generally large groups of people who get together to discuss technology areas and who sponsor development Projects. Projects are smaller groups of people who need direct access to source repositories to get work done. And User Groups are geographically-based groups of people meeting locally and evangelizing about OpenSolaris around the world.
Why are we using the term 'collective'?
We chose the term collective because we needed a generic term for the bodies of people within the overall OpenSolaris community that was not already in use or overloaded (such as Community Group or 'group').
How many collectives are there and what are they?
There are three types of collectives:
- Community Group: Defined in the OpenSolaris Constitution. See the Communities page for a description of Community Groups, instructions about how to request a new one, and a list of the current Community Groups on the site.
- Project: Mentioned in the OpenSolaris Constitution. See the Projects page for a description of Projects, instructions about how to request and set up a new one, and a list of the current Projects on the site.
- User Group: Not mentioned in the OpenSolaris Constitution. Information about User Groups can be found in the Advocacy Community Group.
NOTE: Within the database, there is also an entity called an Electorate (i.e., the OpenSolaris Electorate). Within that entity, governance data (currently people with voting rights, grant data for Community Group Contributors and Community Group Core Contributors, and Community Group Facilitators) is stored for each Community Group Electorate.
Where does information about my collective relationships (i.e., my roles) appear on the website?
Your user account in the Auth app (http://auth.opensolaris.org) contains information about the collectives with which you are associated. Click on 'Collectives' in the Menu list on the left side of the page. The page that displays (http://auth.opensolaris.org/collectives.action) will show the roles you have in collectives on the site.
Where do I manage my collective relationships (i.e., my roles)?
Roles are managed via the Auth app: http://auth.opensolaris.org. Choose 'Collectives' from the menu on the left side of the page.
How do I obtain a particular role?
On August 3, 2009 privileges that a user already had, including voting rights, was migrated to the new system. See the Data Migration document for detail about how existing data was moved.
Moving forward, how a new role is obtained will vary depending on the collective and the role. Anyone who is registered on the site can self-assign the Participant role using the Auth app. This role can also be granted by a collective. Other roles are granted by collectives. Roles granted by collectives are input to the Auth application by a person in the collective that has the appropriate role/privileges. If you are interested in obtaining a role beyond Participant within a particular collective, you should subscribe to the mailing list(s) for that collective and start participating within the collective to get to know people and determine how you can best contribute to the collective.
What privileges are associated with the Participant role?
A Participant is someone who is registered on the site and who has declared an interest in a particular collective via the Auth app. A person can also be granted the role of Participant within a collective by someone in the collective who has the appropriate role/privileges. A Participant can comment on Project web pages. A Participant has no governance rights.
What are the roles specific to Community Groups?
Participant, Contributor, Core Contributor, Facilitator. See the Roles & Collectives document for more information about the roles.
What are the roles specific to Projects?
Participant, Developer, Leader. See the Roles & Collectives document for more information about the roles.
What are the roles specific to User Groups?
Participant, Affiliate, Leader. See the Roles & Collectives document for more information about the roles.
How is role information used across the site?
Applications running on the site will assign privileges to roles within a collective. For example, the SCM application (http://repo.opensolaris.org) gives Project Leaders commit rights to all of the Project's source code repositories and allows a Project Leader to grant commit rights to one or more of the Project's source code repositories to a Project Developer. As another example, the voting application (http://poll.opensolaris.org) will only allow Community Group Core Contributors with at least one current grant to vote in a community-wide election.
Account Management
Where do I go to manage my profile?
The Auth application (http://auth.opensolaris.org). You are free to edit your account details.
Do I have to update my profile?
The first time you log in to Auth after the August 3 website transition, you will need to validate the details of your account and add two security questions. Just follow the prompts.
Do I have to provide my Contributor Agreement number or Sun employee information?
No, regarding Contributor Agreement numbers. And not yet, regarding Sun employee information. Existing Contributor Agreement numbers will be migrated with other account data. Eventually, you will need to provide Sun employee information if you will want to commit to source code repositories on the site or to the internal ON source repository.
How is my Contributor Agreement number entered if I file one after registering on the site?
If you file a Contributor Agreement after August 3, the number assigned will be added to the database by a site administrator.
What do I do if I think I have a Contributor Agreement on file but the number is not listed in my account detail?
Send email to website-admin AT opensolaris DOT org and provide your full name as noted on the Contributor Agreement, when you filed the agreement, and what number you were assigned.
Where do I report problems with CAPTCHA?
Send email to website-admin AT opensolaris DOT org. Provide detail about the actions you performed and the error messages you saw.
Where do I report problems with confirming a new registration?
Send email to website-admin AT opensolaris DOT org. Provide detail about the actions you performed and the error messages you saw.
Where do I report general problems with the Auth application?
File bugs/RFEs for Auth at http://defect.opensolaris.org. Click on 'Enter a new bug report'. Choose the 'auth' Development product. Then choose the AuthWebapp component of auth.
How do I change my password?
Log in using the Auth application (http://auth.opensolaris.org). Type in a new password and confirm it, enter your current password, and save your changes.
How do I get an opensolaris.org email address?
Existing addresses will be migrated with account detail. Once the transition to Auth is complete, a user can check the box on his/her 'account edit' page that says he/she would like an opensolaris.org email address. The address will be username@opensolaris.org.
Source Code Repository Management
How do I create a source code repository?
NOTE: Only Project Leaders can create new source code repositories in a Project, and Project Leaders automatically have commit rights to all of the Project's source code repositories.
If you are a Project Leader, go to http://repo.opensolaris.org. Select the Project for which you wish to create a source code repository. Select the 'Create Repository' link on the left navigation bar. Complete the details and submit the form.
How do I populate a source code repository?
You can view details about a source code repository by selecting that repository on http://repo.opensolaris.org. Ensure that the source code repository is not locked and that the user is a Project Leader or a Project Developer. You can check role information by choosing 'Project > View Leaders' or 'Project > Repo > Manage Participants'.
Checkout/clone the content using the relevant command - repo_url is shown on the source code repository details page on http://repo.opensolaris.org:
- svn co
- hg clone
Add the content to the source code repository that you have checked out locally. Commit/push the local content to the source code repository on http://repo.opensolaris.org: - svn commit
- hg push
How do I delete a source code repository?
A source code repository can not currently be deleted via the SCM application. To delete a source code repository, send email to tonic-ops AT sun DOT com and provide the Project name and the name of the source repository to be deleted.
How do I get commit rights to a source code repository?
A person must have the role of Developer in a Project to get commit rights to one or more of the Project's source code repositories. A Leader of the Project can assign the role of Developer in the Auth application. The Project Leader will go to http://repo.opensolaris.org and select the source code repository to which someone should be added. Select 'Manage Participants' on the left navigation menu. Search for the particular user. Select the check box for the user. Be sure to save the updates.
Governance Roles & Privileges
How do know if I can vote?
You can check the grants listed on the poll application to see if you have the grants you think you should. Go to http://poll.opensolaris.org and click on the 'Grants' tab. You must have been granted and accepted at least one Core Contributor grant to vote in a community-wide election. You can vote in a Community Group-specific election if you have been granted and accepted Core Contributor status in that Community Group.
How do I vote?
Voting in community-wide elections takes place using the poll application: http://poll.opensolaris.org. See instructions in the Lead Reference.
How do I become a Contributor in a Community Group?
A person is granted Contributor status by one or more Community Groups as acknowledgment that the person has contributed substantively to accomplishing the tasks of the Community Group. A person can also be granted Contributor status by the OGB for at-large contributions. See the OpenSolaris Constitution for detail. Usually, within a Community Group, a person is nominated, other Contributors and Core Contributors approve, and the person accepts the nomination. If a person believes he/she should be nominated, he/she can nominate him/herself.
How do I become a Core Contributor in a Community Group?
Once someone has Contributor status within a Community Group, he/she obtains Core Contributor status by again being nominated, having that nomination approved by other Core Contributors and accepting the nomination. A Core Contributor is someone who has been an "active and sustained" contributor to the Community Group. See the OpenSolaris Constitution for detail.
Administrative Tasks for Project and User Group Leaders
How do I designate someone as a Participant in a Project or a User Group?
Participant is a role in each of the three collectives. A person can designate him/herself as a Participant in a collective using the Auth application (http://auth.opensolaris.org). A Leader in a Project or a User Group can also designate someone as a Participant using the Auth application. This action might be taken if someone is moved from the role of Developer in a Project or Affiliate in a User Group but is still participating in the collective.
How do I designate someone as a Developer in a Project?
Only a Project Leader can designate someone as a Developer in the Project. A Project Leader will go to the Auth application (http://auth.opensolaris.org) and select 'Collectives' on the left navigation menu. Select the Project, by clicking on the name, in which he/she wishes to designate a Developer. Select 'Add or modify a user's relationship' and search and add the specific person. Select the "Developer" role from the list. Be sure to save the changes.
How do I give someone commit rights to a source code repository?
A person must have the role of Developer in a Project to get commit rights to one or more of the Project's source code repositories. A Leader of the Project can assign the role of Developer in the Auth application. The Project Leader will go to http://repo.opensolaris.org and select the source code repository to which someone should be added. Select 'Manage Participants' on the left navigation menu. Search for the particular user. Select the check box for the specific user. Be sure to save the updates.
How do I generally manage commit rights in a Project?
See details in the Lead Reference.
How do I remove someone as a Developer in a Project?
Only a Project Leader can remove the designation of Developer for someone in the Project. A Project Leader will go to the Auth application (http://auth.opensolaris.org) and select 'Collectives' on the left navigation menu. Select the Project, by clicking the name, that they wish to remove a Developer from. Locate the developer in the table of relationships, and select 'Delete' to remove him/her from the project.
How do I designate someone as an Affiliate in a User Group?
Only a User Group Leader can designate someone as an Affiliate in the User Group. A User Group Leader will go to the Auth application (http://auth.opensolaris.org) and select 'Collectives' on the left navigation menu. Select the User Group, by clicking the name, in which he/she wishes to designate an Affiliate. Select 'Add or modify a user's relationship' and search and add the specific person. Select the "Affiliate" role from the list. Be sure to save the updates.
How do I remove someone as an Affiliate in a User Group?
Only a User Group Leader can remove the designation of an Affiliate for someone in the User Group. A User Group Leader will go to the Auth application (http://auth.opensolaris.org) and select 'Collectives' on the left navigation menu. Select the User Group, by clicking the name, in which he/she wishes to remove an Affiliate. Locate the Affiliate in the table of relationships, and select 'Delete' to remove him/her from the User Group.