Welcome to WikiProject Free Software, a subdivision of WikiProject Software. WikiProject Free Software is a seperate workgroup of WikiProject Software devoted to the improvement and creation of articles pertinent to free (as in freedom) software. WikiProject Free Software is intended to improve and maintain free software articles, bring such articles to good or featured article state, and to create new free software articles. The scope of this project extends to:
To edit ratings for articles tagged {{WikiProject Free Software}}, just add |class=|importance= inside the {{}} symbols, i.e. {{WikiProject Free Software|class=|importance=}}. The tag does not do this automatically, so by adding this you can rate the article.
Here are some tasks that have to be done constantly or to almost every article. Further down the page you'll find TODO lists with one-off tasks that need to be done.
Verifying the bare minimum
Each article about a free software project should:
Link to {{portal|Free software|Free Software Portal Logo.svg}}, usually in the "See also" section.
Provide a link to the projects licence for confirmation (probably best done as a reference for the sentence about which free software licence the project uses).
Add a {{fact}} tag to any unverified statements.
Adding references
If you want to use an external webpage as a reference for a statement, the best way to do this is with a "{{cite web}}" template inside <ref> tags. The "cite web" template can take many optional fields, but "title" and "url" are mandatory. So here's a minimal reference:
Or if the information isn't so obvious in the linked document, or if you can give more information, you can use some of the additional tags:
<ref>{{cite web
|title = POSIX® 1003.1 FAQ Version 1.12
|url = http://www.opengroup.org/austin/papers/posix_faq.html
|quote = The name POSIX was suggested by Richard Stallman.
|date = 2006-02-02
|accessdate = 2006-07-16
|}}</ref>
Participants
If you wish to join the project, please add your name below this sentence, by adding:
#~~~~
on a new line.
The Assessment department will focus on assessing the quality of Wikipedia's Free Software related articles. This will aid us in recognising excellent contributions and identifying topics in need of further work.
Assessment should be conducted following these guidelines.
A featured article exemplifies our very best work and features professional standards of writing and presentation. In addition to meeting the requirements for all Wikipedia articles, it has the following attributes.
It is—
(a) well-written: its prose is engaging, even brilliant, and of a professional standard;
(b) comprehensive: it neglects no major facts or details;
(c) factually accurate: claims are verifiable against reliable sources, accurately represent the relevant body of published knowledge, and are supported with specific evidence and external citations; this requires a "References" section in which sources are listed, complemented by inline citations where appropriate;
(e) stable: it is not subject to ongoing edit wars and its content does not change significantly from day to day, except in response to the featured article process.
(a) a lead—a concise lead section that summarizes the topic and prepares the reader for the detail in the subsequent sections;
(b) appropriate structure—a system of hierarchical headings and a substantial but not overwhelming table of contents (see section help); and
(c) consistent citations—where required by Criterion 1c, consistently formatted inline citations using either footnotes[1] or Harvard referencing (Smith 2007, p. 1) (see citing sources for suggestions on formatting references; for articles with footnotes, the meta:cite format is recommended).
Length. It stays focused on the main topic without going into unnecessary detail (see summary style).
Professional, outstanding, and thorough; a definitive source for encyclopedic information.
No further content additions should be necessary unless new information becomes available; further improvements to the prose quality are often possible.
Prose. It features professional standards of writing.
Lead. It has an engaging lead section that introduces the subject, and defines the scope and inclusion criteria of the list.
Comprehensiveness. It comprehensively covers the defined scope, providing a complete set of items where practical, or otherwise at least all of the major items; where appropriate, it has annotations that provide useful and appropriate information about entries.
Structure. It is easy to navigate, and includes—where helpful—section headings and table sort facilities.
Style. It complies with the Manual of Style and its supplementary pages.
Visual appeal. It makes suitable use of text layout, formatting, tables, and colour; it has images if they are appropriate to the subject, with succinct captions or "alt" text; and it has a minimal proportion of red links.
Stability. It is not the subject of ongoing edit wars and its content does not change significantly from day to day, except in response to the featured list process.
The article is well organized and essentially complete, having been reviewed by impartial reviewers from a WikiProject or elsewhere.
More detailed criteria
Provides a well-written, clear and complete description of the topic, as described in Wikipedia:How to write a great article. It should be of a length suitable for the subject, appropriately structured, and be well referenced by a broad array of reliable sources. It should be well illustrated, with no copyright problems. Only minor style issues and other details need to be addressed before submission as a featured article candidate. See the A-Class assessment departments of some of the larger WikiProjects (e.g. WikiProject Military history, WikiProject Films).
Very useful to readers. A fairly complete treatment of the subject. A non-expert in the subject matter would typically find nothing wanting.
Expert knowledge may be needed to tweak the article, and style issues may need addressing. Peer-review may help.
(a) it provides references to all sources of information, and at minimum contains a section dedicated to the attribution of those sources in accordance with the guide to layout;
(b) at minimum, it provides in-line citations from reliable sources for direct quotations, statistics, published opinion, counter-intuitive or controversial statements that are challenged or likely to be challenged, and contentious material relating to living persons; and
Useful to nearly all readers, with no obvious problems; approaching (although not equalling) the quality of a professional encyclopedia.
Some editing by subject and style experts is helpful; comparison with an existing featured article on a similar topic may highlight areas where content is weak or missing.
The article is mostly complete and without major issues, but requires some further work to reach Good Article standards. B-Class articles should meet the six B-Class criteria.
The article reasonably covers the topic, and does not contain obvious omissions or inaccuracies. It contains a large proportion of the material necessary for an A-Class article, although some sections may need expansion, and some less important topics may be missing.
The article has a defined structure. Content should be organized into groups of related material, including a lead section and all the sections that can reasonably be included in an article of its kind.
The article is reasonably well written. The prose contains no major grammatical errors and flows sensibly, but it certainly need not be "brilliant". The Manual of Style need not be followed rigorously.
The article contains supporting materials where appropriate. Illustrations are encouraged, though not required. Diagrams and an infobox etc. should be included where they are relevant and useful to the content.
No reader should be left wanting, although the content may not be complete enough to satisfy a serious student or researcher.
A few aspects of content and style need to be addressed, and expert knowledge is increasingly needed. The inclusion of supporting materials should also be considered if practical, and the article checked for general compliance with the manual of style and related style guidelines.
The article is substantial, but is still missing important content or contains a lot of irrelevant material. The article should have some references to reliable sources, but may still have significant issues or require substantial cleanup.
More detailed criteria
The article is better developed in style, structure and quality than Start-Class, but fails one or more of the criteria for B-Class. It may have some gaps or missing elements; need editing for clarity, balance or flow; or contain policy violations such as bias or original research. Articles on fictional topics are likely to be marked as C-Class if they are written from an in-universe perspective.
Useful to a casual reader, but would not provide a complete picture for even a moderately detailed study.
Considerable editing is needed to close gaps in content and address cleanup issues.
An article that is developing, but which is quite incomplete and, most notably, lacks adequate reliable sources.
More detailed criteria
The article has a usable amount of good content, but it is weak in many areas, usually in referencing. Quality of the prose may be distinctly unencyclopedic, and MoS compliance non-existent; but the article should satisfy fundamental content policies such as notability and BLP, and provide enough sources to establish verifiability. No Start-Class article should be in any danger of being speedily deleted.
Provides some meaningful content, but the majority of readers will need more.
Provision of references to reliable sources should be prioritised; the article will also need substantial improvements in content and organisation.
The article is either a very short article or a rough collection of information that will need much work to become a meaningful article. It is usually very short, but can be of any length if the material is irrelevant or incomprehensible.
Provides very little meaningful content; may be little more than a dictionary definition
Any editing or additional material can be helpful. The provision of meaningful content should be a priority.
Stub, Start, and B class assessments can be made by every editor (although it is generally regarded good behaviour not to assess an article in which you have had a major influence yourself)
A class assessment is made within this project
Good Article and Feature Article assessments require formal review procedures outside of this project.
Project selected article
When enough members have been gathered, weekly votes will be taken to determine a high-quality article to be placed here in a similar manner to the standard FA.
(2008-09-26) The OJS article is in real bad shape, and needs to be rewritten. It reads like an AD, and has no structure.
(2008-03-19) The article Hacker (free and open source software) has some sections which should be rewritten with a more "detached" style, and needs more references. Even the title is not perfect.
(2007-09-17) The GNU Compiler Collection article contains no information about how fast/slow or big/small the outputted programs are.
(2007-08-13) GPL linking exception - this article isn't yet linked to by the articles about projects that use this exception, and the article itself contains quite a few tags complaining about original research or mistakes. Care sought.
(2007-04-13) The Player Project needs expansion, particularly someone with knowledge of the project to write about its history, goals, features without turning it back into an advert.
(2007-04-11) The dual-licensing article needs some clean-up (this is half-done now)
(2007-03-22) The OpenMoko article is quite weak for such an interesting free software topic. Help sought.
(2007-03-03) Patents and free software is a consolidation of previous stubs - it's new, so it needs some help and some review
(2007-02-07) The History of free software article is new and seeks contributions, particularly if you have links to essays by old-times for info about free software in the 80s and 70s, as well as 90s and 60s.
(2006-12-18) Add a section on how to contribute to the opensource community. This should cover how to create a program from existing technologies, languages and other opensource programs, how to fix a bug, write documentation, etc.
(2006-06-15) add {{free-software-stub}} to free software related articles which are stubs
(2006-06-06) Work is being done to create useful sub-categories in Category:Free software. This requires help to move articles from Category:free software into the sub-categories.
(2006-04-12) Add the {{portal|Free software|Free Software Portal Logo.svg}} tag to articles about, or related to, free software.
(2005-12-30) The Copyleft article contains information duplicated elsewhere, a review would be good
On Wikipedia, "stubs" are articles that someone has started, but need help in their expansion. Free software related stubs can be found in Category:Free software stubs. There you will find free software articles-in-need.