Difference between revisions of "Free Software Directory:Features"

From Free Software Directory
Jump to: navigation, search
m (fix formatting (remove unintended line breaks resulting in pre-formatted sections))
Line 4: Line 4:
  
 
* [[Free_Software_Directory:Import | Debian/Trisquel import tool]]
 
* [[Free_Software_Directory:Import | Debian/Trisquel import tool]]
* [[Free_Software_Directory:Features/Entry form|Improvements to  
+
* [[Free_Software_Directory:Features/Entry form|Improvements to Form:Entry]]
Form:Entry]]
+
* Have each page be a nicely formatted [[FSD:Features/Flyer|printable flyer]].
* Have each page be a nicely formatted [[FSD:Features/Flyer|printable  
 
flyer]].
 
 
* Promote FSD Collections
 
* Promote FSD Collections
  
Line 13: Line 11:
 
== Existing Features ==
 
== Existing Features ==
  
* [[Free_Software_Directory:Features/Featured_project | Featured  
+
* [[Free_Software_Directory:Features/Featured_project | Featured Programs]]
Programs]]
 
  
 
== Proposed Features ==
 
== Proposed Features ==
  
* Import [[Free_Software_Directory:Features/IceCat_extensions|IceCat  
+
* Import [[Free_Software_Directory:Features/IceCat_extensions|IceCat extensions]] using a scraper
extensions]] using a scraper
+
* See [[FSD:Features/Properties]] for new fields/properties that have been proposed.  
* See [[FSD:Features/Properties]] for new fields/properties that have  
 
been proposed.  
 
  
 
Below are ideas for how we can improve the FSD in other ways. If you'd  
 
Below are ideas for how we can improve the FSD in other ways. If you'd  
Line 27: Line 22:
 
you can start adding to the directory.
 
you can start adding to the directory.
  
* [[Free_Software_Directory:Features/Installation_instructions |  
+
* [[Free_Software_Directory:Features/Installation_instructions | Installation instructions]] for [http://www.gnu.org/distros/free-distros.html free distros] of GNU/Linux.
Installation instructions]] for  
+
* [[Free_Software_Directory:Features/RSS_feeds | RSS feeds]] of developer blogs for each program in the directory
[http://www.gnu.org/distros/free-distros.html free distros] of  
+
* [[Free_Software_Directory:Features/Sample_projects | Sample Projects]] for many of the directory items, including screenshots, howtos, scripts, config files, etc., and a zip file containing the project file(s) that were used with the relevant program(s).
GNU/Linux.
+
* [[Free_Software_Directory:Features/Favorites | Favorites]] / “I use this” button
* [[Free_Software_Directory:Features/RSS_feeds | RSS feeds]] of  
 
developer blogs for each program in the directory
 
* [[Free_Software_Directory:Features/Sample_projects | Sample Projects]]
 
for many of the directory items, including screenshots, howtos,  
 
scripts, config files, etc., and a zip file containing the project  
 
file(s) that were used with the relevant program(s).
 
* [[Free_Software_Directory:Features/Favorites | Favorites]] / “I use  
 
this” button
 
 
* Internationalization of the Directory -- translations of entries.
 
* Internationalization of the Directory -- translations of entries.
* Brief description (one short sentence) in the list of categories (or  
+
* Brief description (one short sentence) in the list of categories (or make a separate list if needed)
make a separate list if needed)
+
* Fix the Entry templates so that instead of querying semantic values it uses the Template values. We can store the template values as arrays or other data structures we already have available to us.  
* Fix the Entry templates so that instead of querying semantic values it
+
* Organize packages implemented in programming languages, working with them, or extended in them: we currently have “Computer languages” single line field, programming language categories and prerequisites: it's not obvious when editing which field is used for which use.
uses the Template values. We can store the template values as arrays or
+
* Add a tab with information useful for building or developing a package.
other data structures we already have available to us.  
+
* Use short descriptions for all software listings: the listings should remain compact. This allows us to use wikicode to a greater extent in full descriptions, without “polluting” the listings.
* Organize packages implemented in programming languages, working with  
+
* Add optional screenshots, maybe from [http://screenshots.debian.net/ screenshots.debian.net].
them, or extended in them: we currently have “Computer languages” single
+
* Improve semantic ontology/RDF representation by [https://semantic-mediawiki.org/wiki/Help:Import_vocabulary importing or defining new vocabularies]
line field, programming language categories and prerequisites: it's not
+
* Perhaps look into [https://github.com/edumbill/doap/wiki DOAP] or [https://joinup.ec.europa.eu/asset/adms_foss/description ADMS.SW]
obvious when editing which field is used for which use.
+
* Add an [https://en.wikipedia.org/wiki/Wikipedia:Authority_control authority control system] to make software entries uniquely identifiable and easy for machines to process it enabling wikidata integration
* Add a tab with information useful for building or developing a  
+
* Import resources from [https://notabug.org/koz.ross/awesome-gamedev awesome-gamedev] and other aggregates
package.
 
* Use short descriptions for all software listings: the listings should  
 
remain compact. This allows us to use wikicode to a greater extent in  
 
full descriptions, without “polluting” the listings.
 
* Add optional screenshots, maybe from [http://screenshots.debian.net/  
 
screenshots.debian.net].
 
* Improve semantic ontology/RDF representation by  
 
[https://semantic-mediawiki.org/wiki/Help:Import_vocabulary importing or
 
defining new vocabularies]
 
* Perhaps look into [https://github.com/edumbill/doap/wiki DOAP] or  
 
[https://joinup.ec.europa.eu/asset/adms_foss/description ADMS.SW]
 
* Add an [https://en.wikipedia.org/wiki/Wikipedia:Authority_control  
 
authority control system] to make software entries uniquely identifiable
 
and easy for machines to process it enabling wikidata integration
 
* Import resources from [https://notabug.org/koz.ross/awesome-gamedev awesome-gamedev]
 
and other aggregates
 
  
 
== Completed Projects ==
 
== Completed Projects ==
  
* [[FSD:Features/Skin|Fix skin of FSD]]
+
* <strike>[[FSD:Features/Skin|Fix skin of FSD]]</strike>
* [[Free_Software_Directory:Features/Redesign | Main Page Redesign]]
+
* <strike>[[Free_Software_Directory:Features/Redesign | Main Page Redesign]]</strike>
  
  
 
== Places to discuss ideas ==  
 
== Places to discuss ideas ==  
  
Join the [https://lists.gnu.org/mailman/listinfo/directory-discuss  
+
Join the [https://lists.gnu.org/mailman/listinfo/directory-discuss mailing list] or hang out on IRC '''#fsf''' on '''chat.freenode.net'''.
mailing list] or hang out on IRC '''#fsf''' on '''chat.freenode.net'''.
 
  
 
[[Category:Documentation]]
 
[[Category:Documentation]]

Revision as of 14:11, 17 January 2017


Current Focus


Existing Features

Proposed Features

Below are ideas for how we can improve the FSD in other ways. If you'd like to help, get in touch! We can point you in the right direction so you can start adding to the directory.

  • Installation instructions for free distros of GNU/Linux.
  • RSS feeds of developer blogs for each program in the directory
  • Sample Projects for many of the directory items, including screenshots, howtos, scripts, config files, etc., and a zip file containing the project file(s) that were used with the relevant program(s).
  • Favorites / “I use this” button
  • Internationalization of the Directory -- translations of entries.
  • Brief description (one short sentence) in the list of categories (or make a separate list if needed)
  • Fix the Entry templates so that instead of querying semantic values it uses the Template values. We can store the template values as arrays or other data structures we already have available to us.
  • Organize packages implemented in programming languages, working with them, or extended in them: we currently have “Computer languages” single line field, programming language categories and prerequisites: it's not obvious when editing which field is used for which use.
  • Add a tab with information useful for building or developing a package.
  • Use short descriptions for all software listings: the listings should remain compact. This allows us to use wikicode to a greater extent in full descriptions, without “polluting” the listings.
  • Add optional screenshots, maybe from screenshots.debian.net.
  • Improve semantic ontology/RDF representation by importing or defining new vocabularies
  • Perhaps look into DOAP or ADMS.SW
  • Add an authority control system to make software entries uniquely identifiable and easy for machines to process it enabling wikidata integration
  • Import resources from awesome-gamedev and other aggregates

Completed Projects


Places to discuss ideas

Join the mailing list or hang out on IRC #fsf on chat.freenode.net.



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.