X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=sphinx%2Ffaq.rst;h=4757ecad9b27e12ddf04a6b7c5721ab33d5238c1;hb=174e51c626068499274f6afc51359b80beb49f1e;hp=956de0ea133552ffe6fb4c70db2bdf95165e401d;hpb=8bb724db8558e66f76112e8ba53a1f9cce99b502;p=neurodebian.git diff --git a/sphinx/faq.rst b/sphinx/faq.rst index 956de0e..4757eca 100644 --- a/sphinx/faq.rst +++ b/sphinx/faq.rst @@ -13,12 +13,12 @@ Why NeuroDebian? In the course of our own research endeavors |we| have joined forces to develop `PyMVPA -- a Python framework for multivariate pattern analysis of - neural data `_. To conveniently deployment PyMVPA for + neural data `_. To conveniently deploy PyMVPA for anyone using Debian-derived distributions this package repository was created initially. Besides the PyMVPA_ project |we| collaborate with the `NiPy team `_ on various projects, such as NiBabel_ and NiPype_. Quickly NeuroDebian_ became the ultimate integrated environment for - all these projects. We are now constantly working on enriching this + all these projects -- and we are constantly working on enriching this environment with as many additional relevant software as possible. @@ -43,7 +43,7 @@ Why is NeuroDebian not a Pure Blend? NeuroDebian aims to be a platform that provides a staging area for neuroscience software packages on their way into Debian. All packages are - properly registered with the relevant `Debian Pure Blends`_, e.g. + properly registered in the relevant `Debian Pure Blends`_, e.g. `Debian Science Cognitive Neuroscience`_ or `Debian Med Imaging`_. Inside Debian these efforts already provide a suitable framework for this purpose, and hence there is no need to establish yet another one. @@ -53,6 +53,18 @@ Why is NeuroDebian not a Pure Blend? .. _Debian Med Imaging: http://debian-med.alioth.debian.org/tasks/imaging +I want to help. How do I get involved? +-------------------------------------- + + We always need people to help maintaining existing packages. If you need + some additional software packaged and you want to try it on your own, we would + be happy to mentor you. We also have a :ref:`list of ongoing and planned + projects `, each listing a number of tasks that need to be done. + + If you found something you are interested in, please email the + neurodebian-devel_ mailing list and let us know about it. Thanks! + + When does a package migrate from NeuroDebian into Debian proper? ---------------------------------------------------------------- @@ -118,8 +130,8 @@ I have heard that some packages are non-free. Will you charge me for them? -------------------------------------------------------------------------- No. The term :term:`non-free` refers to an archive section. NeuroDebian uses - exactly the same :ref:`archive sections as Debian proper - `. The *non-free* + exactly the same `archive sections as Debian proper + `_. The *non-free* section contains packages that have certain restrictions regarding **your freedom** to employ them for a particular purpose. In contrast, for packages in the *main* section your are completely free to do whatever and in whatever @@ -162,5 +174,16 @@ package that is available from the NeuroDebian repository. Alternatively: as root or use sudo). +How can I cite NeuroDebian? +--------------------------- + +Please cite the following paper: + + Halchenko, Y. O. & Hanke, M. (2012). `Open is not enough. Let’s take the + next step: An integrated, community-driven computing platform for neuroscience + `_. + *Frontiers in Neuroinformatics*, 6:22. + + .. include:: link_names.txt .. include:: substitutions.txt