X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=sphinx%2Ffaq.rst;h=4757ecad9b27e12ddf04a6b7c5721ab33d5238c1;hb=b0b5ac02bb33740df593706ce8eb16ae05a6eaac;hp=d2427dcadf7cb62f74f69721ea648b0aa982e5ee;hpb=636ac2caee75a8ad43e37235a2d0acd6224b1162;p=neurodebian.git diff --git a/sphinx/faq.rst b/sphinx/faq.rst index d2427dc..4757eca 100644 --- a/sphinx/faq.rst +++ b/sphinx/faq.rst @@ -1,11 +1,5 @@ .. -*- mode: rst; fill-column: 78 -*- .. ex: set sts=4 ts=4 sw=4 et tw=79: - ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### - # - # See COPYING file distributed along with the PyMVPA package for the - # copyright and license terms. - # - ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### .. _faq: @@ -19,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. @@ -49,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. @@ -59,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? ---------------------------------------------------------------- @@ -107,13 +113,77 @@ How to create a mirror of the repository? How do I get a new neuroscience-related FOSS into (Neuro)Debian? ---------------------------------------------------------------- - * You can approach packaging it yourself (file an ITP_ (Intent to package) - bugreport) and `ask us `_ to mentor your upload to - Debian_ if you are not a Debian developer. +The goal of NeuroDebian is to package neuroscience software for Debian. Hence +getting software into NeuroDebian means trying to get it into Debian. There are +at least two possibilities to achieve that: + +* You can approach packaging it yourself. Start by filing an ITP_ (Intent to + package) bugreport) and `ask us `_ to mentor your + upload to Debian_, if you are not a Debian developer. + +* `Contact us `_ -- but then it might take a little + longer, depending on our current workload and interest in a particular + software. + + +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 `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 + context you like. Regardless of the actual license or archive section, all + packages in NeuroDebian are provided free of charge and under the licensing + terms of the original developers. + +.. _sec_pkg_authentication: + +What means "The following signatures couldn't be verified..."? +-------------------------------------------------------------- + +When you start using this repository, you probably get warning messages +like this:: + + The following signatures couldn't be verified because + the public key is not available. + +Or you will be asked questions like this over and over:: + + WARNING: The following packages cannot be authenticated! + ... + Install these packages without verification [y/N]? + +This is because your APT installation initially does not know the GPG +key that is used to sign the release files of this repository. It is easy to +make APT happy again. The simplest way is to install the ``neurodebian-keyring`` +package that is available from the NeuroDebian repository. Alternatively: + +1. Get the key. Either download the `repository key from here + <_static/neuro.debian.net.asc>`_ + or fetch it from http://wwwkeys.pgp.net (2649A5A9). + +2. Now feed the key into APT by invoking:: + + apt-key add #file# + + Where `#file#` has to be replaced with the location of the key file you just + downloaded. You need to have superuser-privileges to do this (either do it + as root or use sudo). + + +How can I cite NeuroDebian? +--------------------------- + +Please cite the following paper: - * `Contact us `_, but then it might take longer - depending on our workload and interest to the particular software. + 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:: links_names.rst -.. include:: substitutions.rst +.. include:: link_names.txt +.. include:: substitutions.txt