|
|
Community and project lead site referenceEverytime we use the term "community" on this page, we mean "community or project". If we expanded all the substitutions, then the page's tediosity skyrockets. How to manage your communityIf you are the leader of a community, you should see your user name and your "real name" on your community's "View the leaders for this community" page (linked at the top of your community's main page). As a community leader you should be able to:
Note: TML versus HTML: We have created a wiki-like markup language called TML (Tonic Markup Language) to use in page creation, for users that prefer not to use HTML. HTML is also available for users that want to do more advanced layout and design. Within community, a community leader can put any valid HTML into a page, hence the need to carefully limit those you select as community leaders. How to manage your projectIn addition to the basic operations for communities above, projects also have support for managing source code repositories. There are site-specific user instructions for Mercurial and Subversion, courtesy of the Tools community. It is the responsibility of project Leaders to confirm that contributions to the project are coming either from community members who are Sun employees or who have a Sun Contributor Agreement on file. When project teams take contributions of whole pieces of technology (for example, a device driver) via Sun Contributor Agreement, the team should confirm with the contributor that he/she wrote all of the code. If third-party code was used, other approvals are required. As a project leader you should be able to:
It's worth noting that the opensolaris.org infrastructure automatically publishes a repository's contents at a publically available URL, if anonymous checkouts are permitted for that repository. The URL is based on the project and repository name and follows the pattern http://opensolaris.org/sc/src/[project]/[repository]/...This mechanism may be a useful alternative for projects wishing to publish dozens or hundreds of files, or to publish automatically. InstructionsHow To Add A Community Leader
How To Add A Page
How To Show A Hidden Page
How To Hide And Delete A Page
How To Re-Order Links
How To Manage Attachments
How To Use Attachments
How To Add A Blog
How To Add An Announcement
How To Endorse A ProjectThis operation is only available to Community Leaders.
How To Post Binaries and/or Source
How To Add a Page of Core/ContributorsThis operation is only available to Community Leaders.
myCommunity Formal name of community =========== ======================== advocacy Advocacy Community Group approachability Approachability arc Architecture Process and Tools brandz BrandZ desktop Desktop device_drivers Device Drivers documentation Documentation dtrace DTrace edu Academic and Research fm Fault Management ha-clusters HA Clusters install Installation and Packaging int_localization Internationalization and Localization laptop Laptop ldoms Logical Domains mdb Modular Debugger (MDB) networking Networking nfs NFS ogb OpenSolaris Governing Board (OGB) on OS/Net (ON) performance Performance power_pc PowerPC printing OpenSolaris Printing security Security smf Service Management Facility (smf(5)) storage Storage sysadmin Systems Administration Community Group testing Testing tools Tools x_win X Window System xen Xen zfs ZFS zones Zones How To Add a RepositoryThis operation is only available to Project Leaders.
To initialize a Mercurial repository, create a local clone of the empty repo that you just created. Initialize the local clone (e.g., pull from ssh://anon@hg.opensolaris.org/hg/onnv/onnv-gate), then push to the new repo. You might also want to review Dan Price's hints for setting up a repository. How To Manage CommittersThis operation is only available to Project Leaders.
How To handle missing Discussions pagesThis operation is only available to Project Leaders. Note: This procedure also applies to you if you are trying to get rid of a Jive forum that shows up automatically in the "Discussions Lists" table at the bottom of the "Discussions" child page. When setting up the Discussions "child" page, there's a work-around required that is related to the fact that the Mailman system and the website software are not tightly integrated. The symptom is that the following text shows up at the bottom of the Discussions page: "This project does not have any discussions yet." To correct this, hide the Discussions child page (deleting it, effectively). Then create a custom "child" page called mailing-lists, which will show up in the sidebar effectively replacing `Discussions' link that you just hid. Create a link to your mailing-list homepage in the new child page. Alternatively, you can just link to the mailing list somewhere in the body of your main page. Or you can do both. All project pages should clearly identify and provide a link to where project discussions take place. |