Free Software Directory:Workflow

License concerns

Please note: When publishing a new entry to the Free Software Directory, please make sure that it meets our requirements. If the license is not a free software license, then it should not be added to the directory. Therefore, check the license first! If you have questions about whether a program should be added, you can ask the directory-discuss@gnu.org mailing list.

• If you conclude that we can't admit a entry into the Directory, then change the status of relevant submissions to "reviewed" and add your (nice) comments explaining why above the template. See Review:0_A.D.-REV-ID-1 for an example.

When updating an existing entry

• When updating license info for a package, please make sure it meets the FSF's requirements, and ask another FSD administrator to review your work. (Either click the right checkbox on a bug report's "Edit with form" tab, or file a bug report with "Problem with this listing?" at the bottom of the project's page). Also, if you update the license info or confirm 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 report, or create a new bug report that states the license info needs to be checked and updated. Note that this applies to updating a license, not adding a new project to the directory.

Bugs and suggestions

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

• Category:Bug_report

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

• Category:Bug_report-done

If you edit a bug report using "edit with form", you can mark the it as having been reviewed. This changes the category automatically.

Viewing submissions (requests)

New entry requests are created with "Form:Submit":

• Form:Submit

Submissions are categorized as Review:

• Category:Review

When review is complete the category is changed to Reviewed.

• Category:Reviewed

If you edit the "Finished review=No" field to say "Yes," then this will happen automatically.

About editing with 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

At the top of pages in the Review: namespace is a link that will allow you to create or edit entries without typing URLs or entering a name into Form:Entry. Currently, to make changes to an entry's content you must type in your own sentences, and copy and paste basic info. To avoid copyright infringement, please use your own wording for program descriptions.

When you want to edit 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, allowing you to edit current values.

Entry editing tips and guidelines

• 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.

Organization of FSD

Here are some pages that an admin will find useful:

Categories mentioned above

• Category:Review: Submissions for (usually) new packages
• Category:Reviewed: Submissions that have been processed
• Category:Bug report: User submitted bugs and suggestions
• Category:Bug_report-done: Processed bug reports

Not mentioned above

• Category:Alert: Packages that have been marked as containing non-free software or using non-free documentation
• Category:Alert-done: Packages marked as non-free that have been processed
• Category:GNU_review: Submissions marked as GNU
• Category:GNU_review-done: GNU submissions that have been processed
• Category:Review_license: Packages whose license details require double-checking by an experienced administrator
• Category:Documentation: All documentation pages
• Category:Test: Test pages

Site development

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

• FSD:Hack: Tutorial links
• FSD:Bugs: Triaged bugs
• FSD:Features: Potential site improvements
• FSD:Trisquel: Trisquel packages that should be added to the FSD