[gimp-web/gimp-web-static] Added selling.md, testing building/index.fr.md translation nesting

[Pat David <patdavid src gnome org>]

commit c81d48a298d985c96c841df3fa28ccbc22936238
Author: Pat David <patdavid gmail com>
Date:   Thu Aug 13 13:26:41 2015 -0500

    Added selling.md, testing building/index.fr.md translation nesting

 content/about/meta/building/index.fr.md |  207 +++++++++++++++++++++++++++++++
 content/about/selling.md                |   43 +++++++
 2 files changed, 250 insertions(+), 0 deletions(-)
---
diff --git a/content/about/meta/building/index.fr.md b/content/about/meta/building/index.fr.md
new file mode 100644
index 0000000..93c185d
--- /dev/null
+++ b/content/about/meta/building/index.fr.md
@@ -0,0 +1,207 @@
+Title: Building WGO
+Date: 2015-08-11T11:56:58-05:00
+Modified: 2015-08-11T11:57:04-05:00
+Author: Pat David
+Summary: A page about the new site.
+lang: fr
+
+
+Donc, vous voulez contribuer? 
+Génial! 
+Voici les étapes à suivre pour obtenir votre propre copie du site Web!
+
+[TOC]
+
+## Building the Site
+
+### Get git
+
+You will need to get git: <https://git-scm.com/>
+
+The examples here will use git from the command line, but you may be more comfortable using a GUI.
+In that case, find one you're comfortable with.
+If you are going to be contributing and want commit access to the repository, [learn git][] also.
+
+[learn git]: https://git-scm.com/documentation
+
+You can still contribute without commit access to the repository.
+You'll be creating patches instead of pushing changes directly to the repository.
+We'll cover those steps a little later.
+
+
+
+### Get the Source
+
+The source for the GIMP websites can be found here: <https://git.gnome.org/browse/gimp-web/>
+
+At the bottom of that page you should see a section title **Clone**.
+It will provide some common means to clone the repository:
+
+[git://git.gnome.org/gimp-web](git://git.gnome.org/gimp-web)  
+<https://git.gnome.org/browse/gimp-web>
+<ssh://USERNAME git gnome org/git/gimp-web>
+
+From your shell, navigate to your desired location to hold the files.
+
+If you are only interested in the new site while it's being developed, you don't have to fetch the entire 
repository.
+You can tell git to clone a particular branch (only) into the sub-directory `gimp-web-static`:
+
+`git clone -b gimp-web-static --single-branch https://git.gnome.org/browse/gimp-web gimp-web-static`
+
+That is,  
+`git clone -b gimp-web-static`  
+clone the branch gimp-web-static
+
+`--single-branch`  
+just the branch, not the entire repository
+
+`https://git.gnome.org/browse/gimp-web/`  
+the repository we are cloning from
+
+`gimp-web-static`  
+into this sub-directory from where we are.
+
+Be patient.
+At the moment the total download size will be around 111MB.
+This is because the gimp-web-static branch is still referencing all of WGO.
+This may be fixed later *or not*.
+So just sit tight while it fetches everything... :)
+
+Once it finishes, you'll have a sub-directory called `gimp-web-static`.
+If you enter that directory and run `git status` you should see some information:
+
+    $cd gimp-web-static/
+    $git status
+        On branch gimp-web-static
+        Your branch is up-to-date with 'origin/gimp-web-static'.
+        nothing to commit, working directory clean
+
+Congratulations!
+You now have your very own copy of the site source code.
+Now we just need to get the rest of the tools in place for you to make use of it.
+
+
+
+### Get Python
+
+You will need to download and install Python 2.7.x.
+
+<https://www.python.org/downloads/>
+
+2.6.x is not supported by Pelican, and there is only rudimentary support for 3.x at the moment.
+
+
+
+### Get Pelican
+
+Install [Pelican](http://blog.getpelican.com/):
+
+<http://blog.getpelican.com/>
+
+The easiest way to get it after installing Python is to use pip:
+
+`pip install Pelican`
+
+
+
+#### Some Extras
+
+Some extra components that we use on the site are [Markdown][] and [typogrify][]:
+
+`pip install Markdown`  
+`pip install typogrify`
+
+[Markdown]: http://daringfireball.net/projects/markdown/
+[typogrify]: https://github.com/mintchaos/typogrify
+
+
+
+### Build the Site
+
+Once the requirements are installed building the site is straightforward.
+Enter the project directory and issue the `Pelican` command to build:
+
+    cd gimp-web-static/
+    pelican
+
+After a few moments, the command will finish, and the site files will be in the `output` directory.
+
+
+#### Auto Rebuild
+
+If you are developing the site or content and want pelican to automatically regenerate the site when files 
change then you can run the command with the `-r` switch to reload automatically (and will possibly want to 
ignore any caches as well):
+
+    pelican -r --ignore-cache
+
+
+
+### View the Site
+
+To accurately see the site it is best to access it through a web server.
+Python has one built in that can be used.
+Enter the output directory, and start the HTTP server:
+
+    cd output/
+    python -m SimpleHTTPServer
+
+The site will then be accessible to a web browser at:
+
+    http://localhost:8000
+
+Do note that the SimpleHTTPServer won't serve SVG elements as images correctly.
+See [this section][] for a solution
+
+[this section]: ../using-pelican/#python-simplehttpserver-svg
+
+
+
+## Writing for the Site
+
+This section will cover writing something for the site.
+In particular it will focus on writing page content (a tutorial, or page like this).
+News items are similar, but will be covered in a different place (not all users will be allowed
+to publish news items).
+
+The actual structure of the site and directory hierarchies are covered in the [Using Pelican][] page.
+For this page, we will stick to writing a tutorial for the site.
+[Using Pelican]: ../using-pelican/
+
+The directories of page sections will be nested just as they are in the source directories now.
+This means that new tutorials will be located in their own directories under the `content/tutorials/` 
directory.
+They will then be accessible on a url like `www.gimp.org/tutorials/NEW_TUTORIAL_NAME/`
+
+For this example, we will create a new tutorial called `GIMP-Test`.
+Create this new directory under the tutorials directory:
+
+    cd content/tutorials/
+    mkdir GIMP-Test
+
+Inside that directory, create a new `index.md` file.
+This will be the page content.
+
+
+### Markdown File
+
+The `index.md` [Markdown][] file requires that any metadata be located first in the file.
+To finish describing metadata, follow it with a blank line and then start the actual file contents.
+The minimum metadata for files should at least be *Title*, *Date*, and *Author*.
+A sample leading section of an `index.md` file might look like this:
+
+    :::Markdown
+    Title: GIMP Test Tutorial
+    Date: 2015-08-11T14:11:02-05:00
+    Author: Pat David
+
+    Welcome to a quick test of writing new content!
+
+The rest of the file will contain the actual tutorial content.
+There is a Markdown cheatsheet available [here]({filename}../markdown.md) for reference.
+There will also be a more detailed article for writing a tutorial coming soon...
+
+When finished, save the file.
+If the webserver is running, and pelican was run with the `-r` option, refreshing the browser page should 
reflect the changes.
+Otherwise run pelican in the base directory again to rebuild the site and show the latest changes.
+
+Due to the way the directories are nested, the above example can be found at:
+
+    localhost:8000/tutorials/GIMP-Test/
diff --git a/content/about/selling.md b/content/about/selling.md
new file mode 100644
index 0000000..daba759
--- /dev/null
+++ b/content/about/selling.md
@@ -0,0 +1,43 @@
+Title: Selling GIMP
+Date: 2015-08-13T13:02:14-05:00
+Modified: 2015-08-13T13:02:23-05:00
+Author: Pat David
+
+
+## Introduction
+
+From time to time, we get questions from users who are surprised to see some individuals or companies 
selling GIMP from their web site or as part of an auction. Sometimes the software is advertised as being GIMP 
but in some cases there is no mention of the fact that what is sold is GIMP, and GIMP is <span class="help" 
title="software that may be modified and distributed freely, as long
+as you do not deny other users these freedoms">Free Software</span>. This page tries to answer some of these 
questions and provides suggestions for those who would like to sell GIMP.
+
+## Is it legal to sell copies of GIMP?
+
+Yes. The terms and conditions for copying, distribution and modification of GIMP are clearly listed in the 
[GNU General Public License](/about/COPYING). Redistribution for free or for profit is specifically allowed, 
as long as the license is included and the source code is made available. See also [Selling Free 
Software](http://www.gnu.org/philosophy/selling.html) on the <span class="help" title="Free Software
+Foundation">FSF</span> site.
+
+Besides the rights and conditions given by the GPL, it would also be nice (but not required) to mention in 
any advertising that the product being sold is GIMP (or a bundle including GIMP) or is derived from it.
+
+## Are the developers associated with companies selling GIMP?
+
+No. The GIMP developers are not associated with the companies selling copies of GIMP. We may be in contact 
with some of them from time to time when they contribute some improvements to GIMP. Some of them have also 
made [donations](/donating/) to the GIMP developers (sponsoring for the GIMP developers' conference). But 
none of the developers has direct financial interest in these companies.
+
+## I bought GIMP without knowing that it was Free Software
+
+Unfortunately, some companies selling GIMP do not always mention in their advertising that the software that 
they are selling can also be obtained for free. Sometimes GIMP is combined with additional software or 
artwork that adds value to the package, but sometimes what you get is not much more than what could otherwise 
be downloaded for free. If you have purchased such a copy of GIMP and you feel cheated, then you should 
complain to the vendor.
+
+However, if the vendor did not make the complete corresponding source code for their version of GIMP 
available to you as required by the GPL, then the vendor may have violated the license and may be liable for 
copyright infringment. Please try to clarify the situation with the vendor _before_ reporting any GPL 
violation to the GIMP developers. In any case, you should refrain from making public statements about the 
potential GPL violation before you have contacted the vendor. Notifying the developers too early of making 
public statements about the potential GPL violation may limit the legal options available to the developers 
(copyright owners).
+
+## Where can I buy a copy of GIMP?
+
+We do not sell GIMP from this web site. However, the platfom-specific pages contain links to packages 
provided by several individuals or companies, and some of them are selling GIMP. Please have a look at the 
page related to the platform you are using (UNIX, Windows or MacOS) and see if you can find anything 
interesting there.
+
+## Recommendations for those who sell copies of GIMP
+
+If you or your company intend to sell GIMP, it would be nice to follow these guidelines:
+
+1.  **Be honest**. Do not try to hide the fact that the product that you are selling is or contains GIMP 
(the GNU Image Manipulation Program). Mention it in any advertisement.
+2.  **Add value**. Try to provide more than what can be found in the default GIMP package. Include a nice 
installer, additional plug-ins, some nice artwork, some custom brushes and textures, your own tutorials and 
documentation, printed copies of the documentation, etc. There are many ways to add value to GIMP and to make 
your customers happy.
+3.  **Respect the GPL**. The GPL requires you to make the source code available. The best solution is to 
include the source code on the same medium as the GIMP installation package, but you can also include a 
written offer to supply the source code on request. Note that you cannot simply give a link to the GIMP ftp 
mirrors: it should be the exact source code that was used to compile the binary package that you are selling 
and you have to cover the costs of redistribution yourself. If you sell and distribute the binaries online, 
the GPL requires you to make the source code available "from the same place" so giving a link to the GIMP 
mirrors is not sufficient (see also [this section of the GPL 
FAQ](http://www.gnu.org/copyleft/gpl-faq.html#SourceAndBinaryOnDifferentSites)).
+4.  **Support your users**. If the version of GIMP that you are selling is modified in any way, you should 
inform your users and try to handle the support requests related to that version. Providing good support is 
another way to make your customers happy.
+
+Finally, think about giving something back. If the software created by many volunteers helps your business, 
it would be nice to return the favor by helping the developers. You can contribute by sending some 
improvements to the code or by sponsoring some events such as the GIMP developer's conference. This is not 
required, but happy developers are more likely to create a better product that you can sell later...
+