Difference between revisions of "Free Software Directory:Features"

From Free Software Directory
Jump to: navigation, search
(Add awesome-gamedev note)
Line 1: Line 1:
 
__NOTOC__
 
__NOTOC__
  
== Current Focus ==
+
==
 +
Current Focus ==
  
 
* [[Free_Software_Directory:Import | Debian/Trisquel import tool]]
 
* [[Free_Software_Directory:Import | Debian/Trisquel import tool]]
* [[Free_Software_Directory:Features/Entry form|Improvements to Form:Entry]]
+
* [[Free_Software_Directory:Features/Entry form|Improvements to  
* Have each page be a nicely formatted [[FSD:Features/Flyer|printable flyer]].
+
Form:Entry]]
 +
* Have each page be a nicely formatted [[FSD:Features/Flyer|printable  
 +
flyer]].
 
* Promote FSD Collections
 
* Promote FSD Collections
  
Line 11: Line 14:
 
== Existing Features ==
 
== Existing Features ==
  
* [[Free_Software_Directory:Features/Featured_project | Featured Programs]]
+
* [[Free_Software_Directory:Features/Featured_project | Featured  
 +
Programs]]
  
 
== Proposed Features ==
 
== Proposed Features ==
  
* Import [[Free_Software_Directory:Features/IceCat_extensions|IceCat extensions]] using a scraper
+
* Import [[Free_Software_Directory:Features/IceCat_extensions|IceCat  
* See [[FSD:Features/Properties]] for new fields/properties that have been proposed.  
+
extensions]] using a scraper
 +
* 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 like to help, get in touch! We can point you in the right direction so you can start adding to the directory.
+
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.
  
* [[Free_Software_Directory:Features/Installation_instructions | Installation instructions]] for [http://www.gnu.org/distros/free-distros.html free distros] of GNU/Linux.
+
* [[Free_Software_Directory:Features/Installation_instructions |  
* [[Free_Software_Directory:Features/RSS_feeds | RSS feeds]] of developer blogs for each program in the directory
+
Installation instructions]] for  
* [[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).
+
[http://www.gnu.org/distros/free-distros.html free distros] of  
* [[Free_Software_Directory:Features/Favorites | Favorites]] / “I use this” button
+
GNU/Linux.
 +
* [[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 make a separate list if needed)
+
* Brief description (one short sentence) in the list of categories (or  
* 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.  
+
make a separate list if needed)
* 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.
+
* Fix the Entry templates so that instead of querying semantic values it
* Add a tab with information useful for building or developing a package.
+
uses the Template values. We can store the template values as arrays or
* 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.
+
other data structures we already have available to us.  
* Add optional screenshots, maybe from [http://screenshots.debian.net/ screenshots.debian.net].
+
* Organize packages implemented in programming languages, working with  
* Improve semantic ontology/RDF representation by [https://semantic-mediawiki.org/wiki/Help:Import_vocabulary importing or defining new vocabularies]
+
them, or extended in them: we currently have “Computer languages” single
  * Perhaps look into [https://github.com/edumbill/doap/wiki DOAP] or [https://joinup.ec.europa.eu/asset/adms_foss/description ADMS.SW]
+
line field, programming language categories and prerequisites: it's not
* 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
+
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 [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 ==
Line 43: Line 76:
 
== Places to discuss ideas ==  
 
== Places to discuss ideas ==  
  
Join the [https://lists.gnu.org/mailman/listinfo/directory-discuss mailing list] or hang out on IRC '''#fsf''' on '''chat.freenode.net'''.
+
Join the [https://lists.gnu.org/mailman/listinfo/directory-discuss  
 +
mailing list] or hang out on IRC '''#fsf''' on '''chat.freenode.net'''.
  
 
[[Category:Documentation]]
 
[[Category:Documentation]]

Revision as of 11:47, 21 August 2015


==

Current Focus ==


Existing Features

Proposed Features

been proposed.

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.

free distros of GNU/Linux.

developer blogs for each program in the directory

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

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.

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 DOAP or 

ADMS.SW

authority control system] to make software entries uniquely identifiable

and easy for machines to process it enabling wikidata integration

and other aggregates

Completed Projects


Places to discuss ideas

Join the [https://lists.gnu.org/mailman/listinfo/directory-discuss 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.