Free Software Directory:Bugs
Bugs and suggestions
- Proposed features for the FSD
- Category browsing
Set up RT for bug tracking and tiket making(Probably won't happen)
- need to create "Category:Review-triaged" once RT has been set up.
fix the program tagging, so all programs are included in the main page redesign.This issue has been worked around.
Then update the pages in the Category:Bug_report name-space to visibly contain the category tag.
Then update Template:Bug_report to not include it automatically.
Should Category:Alert be changed like this as well, so we can distinguish new alerts from old ones? Done: one can change the "Nonfree" template field to "completed".
property that can identify a project as a High Priority Project. Ideally with a graphic, like for GNU projects.
- 'new messages' text overlays the red FSF links bar, so you can't click it. Still, you can just click your 'talk' page link instead.
Fix links to licensesI've make entries of 'GPLv3' redirect to 'License:GPLv3', etc. by using templates for displaying license query results. At the time of writing, pages should be going through the automatic update process.
Export all entries in XML format.
- Create cron job to do this
- Create cron job to update CSV output page of GNU all projects
- Pages incorrectly created with Form:Bug_update (without the "Review:" namespace prefix) are queryable. If they are then moved to the Review: namespace, then they remain queryable. I'm not sure if a non-admin can edit the page, which could let them create a false entry in the directory.
- Update the queries on GNU/Export to make sure the second column is the GNU package name property
- Update each GNU project with the GNU package name
- Remove edit links in Search results
- Fix links (multimedia, etc) at top of search results
- Autopopulate License verified date field if it is empty.
- Both the user name and the current date should be used for the "submitted by" fields -- they should not be user selectable.
- GNU Head goes away when you view "further results" in table of results.
- Make sorting case-insensitive. (See this SMW bug response.)
- We can use the autoedit links for things like allow admins to do things like confirm that they have reviewed an entry or as a way for "voting-up" etc. Or any number of things. See autoedit section at bottom of Semantic Forms page.
proprietary program search
When a person searches for a proprietary program, a list of free software replacements for that program should appear in the search results, *however*, the proprietary program and its name should not appear anywhere on the wiki. To achieve this functionality, we may want to use the Enhanced Retrieval extension.
When doing license verification, we need to ensure two things:
- More than one person checks a license
- We have a system in place for training volunteers (via some sort of mentorship) on how to properly check a project's license.
Point system and mentoring
Some ideas we have discussed is that we might have some sort of scoring system, so that more experienced individuals who check a license have more "points" than people less experienced. Let's say we have three tiers: level-1, level-2, level-3; with level-1 being the most experienced. A check by a level-1 person might be worth 15 points, a level-2 might be worth 10 points, and a check by a level-3 person might be worth 5 points. It might be that a license is properly "checked" if it has a score of at least 25 points. To coordinate this work we might consider using an extension such as Semantic Tasks.
But, more important than the point system is ensuring that level-3 individuals are not only verified by level-1 individuals, but, that some 1-on-1 guidance and help/mentoring is provided to level-3 individuals from level-1 individuals.
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.