THE SPDX WIKI IS NO LONGER ACTIVE. ALL CONTENT HAS BEEN MOVED TO https://github.com/spdx

Difference between revisions of "Wiki Conventions"

From SPDX Wiki
Jump to: navigation, search
(update link to mailing list)
Line 1: Line 1:
 
<h2>First:</h2>
 
<h2>First:</h2>
 
<ul>
 
<ul>
<li>You need an account in order to edit the wiki pages.  If you haven't created an account on FOSSBazaar or spdx.org yet, please <a href="/user/register">sign up</a> for one now.  If you already have a FOSSBazaar account, you can use it login here.</li><li>There are three separate SPDX teams (<a href="http://www.spdx.org/wiki/spdx/spec-development">Technical</a>, <a href="http://www.spdx.org/wiki/spdx/biz">Business</a> and <a href="http://www.spdx.org/wiki/spdx/legal">Legal</a>) each of which has its own meetings and mailing list. There is also a regular General Meeting and mailing list, the main purposes of which is to report out on team activities. Here you can subscribe to the<span style="font-size: 10.8px;">&nbsp;<a href="https://fossbazaar.org/mailman/listinfo/spdx">SPDX mailing list</a>&nbsp;which is a good way for anyone with casual interest to participate and be notified of general meetings.  To participate on the teams or get on the team mailing lists, go to their respective sections under the Participation tab.</span></li><li>A good starting point for understanding the spec is the <a href="http://www.linuxfoundation.org/sites/main/files/publications/lf_foss_compliance_spdx.pdf">SPDX whitepaper</a>. This <a href="http://www.blackducksoftware.com/files/spdx/intro_to_spdx.mov">3 minute webinar</a> provides a very concise introduction.</li><li>Another good resource is the <a title="SPDX mailing list archive" href="https://fossbazaar.org/pipermail/spdx/">mailing list archive</a>. </li>
+
<li>You need an account in order to edit the wiki pages.  If you haven't created an account on FOSSBazaar or spdx.org yet, please <a href="/user/register">sign up</a> for one now.  If you already have a FOSSBazaar account, you can use it login here.</li><li>There are three separate SPDX teams (<a href="http://www.spdx.org/wiki/spdx/spec-development">Technical</a>, <a href="http://www.spdx.org/wiki/spdx/biz">Business</a> and <a href="http://www.spdx.org/wiki/spdx/legal">Legal</a>) each of which has its own meetings and mailing list. There is also a regular General Meeting and mailing list, the main purposes of which is to report out on team activities. Here you can subscribe to the<span style="font-size: 10.8px;">&nbsp;<a href="http://lists.spdx.org/mailman/listinfo/spdx">SPDX mailing list</a>&nbsp;which is a good way for anyone with casual interest to participate and be notified of general meetings.  To participate on the teams or get on the team mailing lists, go to their respective sections under the Participation tab.</span></li><li>A good starting point for understanding the spec is the <a href="http://www.linuxfoundation.org/sites/main/files/publications/lf_foss_compliance_spdx.pdf">SPDX whitepaper</a>. This <a href="http://www.blackducksoftware.com/files/spdx/intro_to_spdx.mov">3 minute webinar</a> provides a very concise introduction.</li><li>Another good resource is the <a title="SPDX mailing list archive" href="https://fossbazaar.org/pipermail/spdx/">mailing list archive</a>. </li>
 
</ul>
 
</ul>
 
<h2>Wiki</h2>
 
<h2>Wiki</h2>

Revision as of 17:17, 16 March 2012

First:

Wiki

Here are some instructions for using the SPDX wiki. Every user who is logged into spdx.org can modify wiki pages. At the top of a page, you'll see an "Edit" option. You can then edit the page using the HTML editor. When you save the page, make sure to put in a message in "Log message" briefly explaining the change you've made. Then click on "Save" at the bottom of the page to save or on "Preview" or "Preview changes" to preview before saving.

If a page has been edited more than once, you'll see a "Revisions" link at the top of the page (next to "Edit"). Clicking on this link will allow you to see in detail which changes have been made to the page.

If you want to create a new page, click on "Add child page".

If you want to add a visible comment,  please start the comment by

indicating the source by your initials, bolded, surrounded by angle brackets.  Then put the comment itself in italics.  For example: <kes> this is a comment or a question?. 

The purpose of this is to make sure its clear that this is not part of 

the official text of the standard at this point, and provides localized

context for the discussion.