[SciPy-Dev] mwavepy scikit

[alex arsenovic]

  i have been browsing the scikit-image and git docs,  trying to feel 
out the community and workflow. i have a couple quesitons:

     scikits:
     i was originally reading these directions.
      http://projects.scipy.org/scikits/wiki/ScikitsForDevelopers
     then i looked over the directions linked in previous email from 
gael, and i am a bit confused.  it doesnt appear that the scikit-image 
and scikit-learn share a common svn repo or use the 'namespace_packages` 
in its disutils setup. so i am unclear as to the meaning of a scikit, in 
practice.

     git:
     currently my project is hosted at google code, using svn. i see 
that git is the accepted version control system for scipy, scikit-image, 
and many others. being that i am sole developer, i dont see much 
advantage of using git for now, but it appears that it is being adopted, 
so moving to git is the correct decision. is moving to github from 
google code recommended or advantageous for scikits?

     naming:
     @gael, let me rephrase my understanding of your advice. i can 
create a git repository that has a name scikit-mwavepy, and the actual 
python module directory can have an arbitrary name, such as simply 
mwavepy. is this correct?
     this brings up the question of naming. are there suggestions as to 
changing the name mwavepy to something meaningful but also follows some 
convention for scikits? as a standalone package the name `mwavepy` made 
sense but as a scikit, it seems as somthing more to the point is 
appropriate such as skrf, or similar.

    sphinx/numpydoc:
     i have some technical questions about documentation concerning 
sphinx using the numpydoc extensions, is this a correct venue for these 
or should i post to sphinx mailing lists?

thanks

alex






On 01/16/2012 01:31 AM, Gael Varoquaux wrote:
> On Mon, Jan 16, 2012 at 12:16:17AM -0600, Travis Oliphant wrote:
>> I'm not an expert on this, but I believe you just need to upload your
>> package to PyPI with a scikits.<name>   and it will become part of the
>> index.
> Actually, the 'name' of the package just needs to start with 'scikit',
> the import name doesn't even have too anymore. Scikits.image and
> scikit-learn now have import names 'skimage' and 'sklearn'.
>
>> Gael V. wrote a nice example about how to get started, but I don't have
>> the link handy.  Perhaps he will post it again.
> You might be refeering to https://gist.github.com/1433151
>
> Gael
>
> _______________________________________________
> SciPy-Dev mailing list
> SciPy-Dev at scipy.org
> http://mail.scipy.org/mailman/listinfo/scipy-dev