Your yellow pages of Free Software/Open Source Software Publishers, their products and success cases. View via http://www.afs.one
<h1>Why AFS.one?</h1>
\ No newline at end of file
<p>
We wanted to create a collaborative repository highlighting success cases of
Enterprise Free Software Publishers with a focus on those companies that actually
create it and a bias towards <b>real Free software</b> - software that users
can actually modify, fix, improve or share.
</p>
<p>
Target Audience are Enterprises willing to implement Free Software with all the
warranties and long term commitment provided by a Commercial Software Publisher.
</p>
<p>
The idea of <ahref="http://www.afs.one/"title="AFS | Awesome Free Software">AFS</a>
was not create yet another directory of Open Source/Free Software such as
<ahref="http://freecode.com/">freecode</a> or another guide of supposed
Open Source Software, that uses the term "Open Source" as a marketing
argument to promote proprietory software that cannot be modified, fixed, improved
or shared.
</p>
<p>
Our ultimate goal is to ensure that Enterprises can take control of their IT
through Free Software and reduce their risks thanks to this model of publishing.
</p>
<h1>How to contribute?</h1>
<p>Submit pull requests following the JSON scheme described below.</p>
<h1>JSON Schema</h1>
<p>All JSON text entries must use UTF-8 encoding.</p>
<p>
Each publisher has a single JSON file with straightforward properties. Notables:
</p>
<ul>
<li><code>country</code>: origin country of the publisher (<ahref="https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2">ISO 3166-1 alpha-2</a>)</li>
<li><code>presence</code>: countries the publisher has a presense (<ahref="https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2">ISO 3166-1 alpha-2</a>)</li>
<li><code>source_code_download</code>: link to an archive with all source code available under a Free Software license</li>
<li>
<code>commercial_support</code>: link to a resource/page describing the type of commerical support provided for the respective Free Software
(empty if commercial support is only available for another (version of the) software that can be downloaded using <code>source_code_download</code>).
</li>
<li>wikipedia_url: link to the wikipedia page of the Free Software</li>
<li>openhub_url: link to the openhub page of the Free Software</li>
<li>language: the language of a success case (<ahref="https://en.wikipedia.org/wiki/ISO_639-1">ISO 639-1</a>)</li>
</ul>
<p>
The full JSON schema is here:
</p>
<pre><code>
{
"title": [company title],
"logo": [url to company logo],
"country": [origin country of the publishe],
"presence": [countries the publisher has a presense, e.g. ["us", "gb"]],
"website": [url to company website],
"founded_year": [year company was founded],
"free_software_list": [{
"title": [software title],
"logo": [url to software logo],
"category_list": [list of categories, e.g. ["communication", "database"]],
"source_code_download": [link to an archive with all source code],
"commercial_support": [link to a resource/page describing the type of commerical support provided],
"wikipedia_url": [link to the wikipedia page of the Free Software],
"success_case_list": [{
"title": [title of success case],
"image": [url to screenshot of success case],
"customer": [name of client/customer],
"country": [country of origin of customer],
"language": [language of success case],
"url": [url to success case]
}, {
[...next success case...]
}]
}, {
[... next Free Software ...]
}]
}
</code></pre>
<h1>Software Categories</h1>
<p>
Free Software is categorized using the following terms:
