Free Software Foundation!

Join now

Difference between revisions of "Free Software Directory:Workflow"

From Free Software Directory
Jump to: navigation,
(Added some initial licensing notes from Josh)
Line 18: Line 18:
 
* In the ''Documentation note'' and ''Version comment'' fields, make sure all URLs are formatted as external links. Simply pasting the URL is bad because it does not create a clickable link and because long URLs create formatting errors due to poor line wrap support.  
 
* In the ''Documentation note'' and ''Version comment'' fields, make sure all URLs are formatted as external links. Simply pasting the URL is bad because it does not create a clickable link and because long URLs create formatting errors due to poor line wrap support.  
 
* Make sure IRC channels are formatted as URIs in the formatted like such: ''irc://irc.gnu.org/channelname'' — notice that the hash tag of the channelname is optional.  
 
* Make sure IRC channels are formatted as URIs in the formatted like such: ''irc://irc.gnu.org/channelname'' — notice that the hash tag of the channelname is optional.  
* The "Submitted by" and "Submitted date" should only be edited the first time a project is submitted.   
+
* The ''Submitted by'' and ''Submitted date'' should only be edited the first time a project is submitted.   
* If you are making a very minor change, do not bother updating the "last reviewed" fields. However, if you are updating the software to indicate a new version has been released or have improved it in other substantial and interesting ways, make sure you updated the last reviewed by and last reviewed date. This will add it to an RSS feed of recent updates.  
+
* If you are making a very minor change, do not bother updating the ''Last reviewed'' fields. However, if you are updating the software to indicate a new version has been released or have improved it in other substantial and interesting ways, make sure you updated the ''Last reviewed by'' and ''Last reviewed date''. This will add it to an RSS feed of recent updates.  
* The licensing section deserves its own wiki page, but for now, make sure you have another experienced administrator review your work to help ensure the licensing information is correct.  
+
* The licensing section deserves its own wiki page, but for now:
 +
** When updating license info for a package, please ask another FSD administrator to review your work. Also, if you do update the license info or have confirmed that it is correct in a newer version, be sure to update the ''License reviewed by'' and ''License reviewed date'' fields for that package.
 +
** When updating an existing package in the Directory, if you suspect the package has changed and become proprietary software, then this should be flagged for urgent review immediately. Also, contact another administrator letting them know about the situation.
 +
** If you are having trouble updating or checking the license for a package, don't let this halt updating other aspects of the package's information. Simply update the information you can and then either update the existing Bug in the ''Review:'' namespace or create a new Bug that states the package license info needs to be checked and updated.
  
 
== Reviewing new submissions ==
 
== Reviewing new submissions ==

Revision as of 00:42, 17 March 2012


Bugs and suggestions

Requested updates to existing submissions get categorized as "Bug report":

When completed, the category gets changed to "Bug report-done"

Updating existing submissions

To update an existing submission, go to the page and click edit with form.

Some important things to do when updating a submission:

  • In the Documentation note and Version comment fields, make sure all URLs are formatted as external links. Simply pasting the URL is bad because it does not create a clickable link and because long URLs create formatting errors due to poor line wrap support.
  • Make sure IRC channels are formatted as URIs in the formatted like such: irc://irc.gnu.org/channelname — notice that the hash tag of the channelname is optional.
  • The Submitted by and Submitted date should only be edited the first time a project is submitted.
  • If you are making a very minor change, do not bother updating the Last reviewed fields. However, if you are updating the software to indicate a new version has been released or have improved it in other substantial and interesting ways, make sure you updated the Last reviewed by and Last reviewed date. This will add it to an RSS feed of recent updates.
  • The licensing section deserves its own wiki page, but for now:
    • When updating license info for a package, please ask another FSD administrator to review your work. Also, if you do update the license info or have confirmed that it is correct in a newer version, be sure to update the License reviewed by and License reviewed date fields for that package.
    • When updating an existing package in the Directory, if you suspect the package has changed and become proprietary software, then this should be flagged for urgent review immediately. Also, contact another administrator letting them know about the situation.
    • If you are having trouble updating or checking the license for a package, don't let this halt updating other aspects of the package's information. Simply update the information you can and then either update the existing Bug in the Review: namespace or create a new Bug that states the package license info needs to be checked and updated.

Reviewing new submissions

New submissions are done through the form "Form:Submit":

Submissions are moved into New submissions get categorized as Review:

When review is complete the category is changed to Reviewed

Publishing new submissions

Please note: When publishing a new entry to the Free Software Directory, please make sure that it meets our requirements, and that another administrator who is experienced in publishing new submissions to the directory reviews your work.

Moving from Reviewed to published

To move a page from being reviewed to being published, you should move the submission page to a new page within the Main namespace of our wiki (i.e., 'directory.fsf.org/wiki/').

Edit the new submission in the main namespace and make sure that the first template is named "Entry". If the page does not appear to be formatted correctly, you may have to change the line from "{{Entry2" to read "{{Entry". Once you have saved, you should be able to edit this page using the Edit with form tab. At this point you can go through and fill out any fields that were not available for editing through Form:Submit.

Publishing new submissions directly

If a new submission is not being moved from the Review namespace, you can create it through Form:Entry.

Organization of FSD

Here are some of the pages that an admin will find useful.

Categories

Forms

  • Form:Submit: Anyone with a user account can submit a package for review
  • Form:Entry: Admins can use this to create new project pages

When editing a page, you have the option of using "Edit" or "Edit with Form". The first allows you to see the source code of the page and offers more flexibility, whereas the second one presents you with a convenient form layout, displaying and allowing you to edit current values.

At the top of pages in the Review: namespace is a link that will allow you to create or edit pages without typing URLs. Currently, making changes on official entries involves manually typing in what you have found, or copying and pasting basic info from user-submissions. To avoid copyright infringement, and to allow us to release the directory under the FDL, please use your own wording for program descriptions.

Site development

These links are useful for people working on fixing and brining new features to the directory:




Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the page “GNU Free Documentation License”.

The copyright and license notices on this page only apply to the text on this page. Any software or copyright-licenses or other similar notices described in this text has its own copyright notice and license, which can usually be found in the distribution or license text itself.


Personal tools

Variants
Actions
Navigation
Contribute