[Neuroimaging] Fwd: [GitHub] Subscribed to nipy/staged-recipes notifications

[Ariel Rokem]

On Sat, Jun 25, 2016 at 3:19 PM, Satrajit Ghosh <satra at mit.edu> wrote:

> hi ariel,
>
> i didn't really know what i was doing, but felt that if i were to create
> some staging for feedstocks i might as well do it under the nipy repo. i
> was planning to make one for nipype and perhaps a few others.
>

Ah - I thought you were thinking of doing something clever where we would
somehow circumvent the limits on the Github API and on the CI servers, or
maybe you were starting a new conda channel :-)

if you think i should fork it elsewhere let me know.
>

I've been forking these to my own user account, and making PRs from there
into staged-recipes. You can add multiple maintainers by adding their GH
user names in the relevant section of the recipe, so you can share the
responsibility widely. The conda-forge elves (for lack of a better term;
"admins" perhaps?) are pretty pro-active in adding people related to a
project to the list of maintainers.


> cheers,
>
> satra
>
> On Sat, Jun 25, 2016 at 7:48 PM, Ariel Rokem <arokem at gmail.com> wrote:
>
>> Hey Satra,
>>
>> Just checking in about this: what is the plan for this? As you might
>> know, there are already a few conda-forge recipes for nipy packages:
>>
>> https://github.com/conda-forge/nibabel-feedstock/
>> https://github.com/conda-forge/nitime-feedstock/
>> https://github.com/conda-forge/pydicom-feedstock/
>> https://github.com/conda-forge/dipy-feedstock/
>> https://github.com/conda-forge/nilearn-feedstock/
>> https://github.com/conda-forge/dcmstack-feedstock/
>>
>> (and more that I don't know of?)
>>
>> Is there any advantage to creating a fork for the nipy org?
>>
>>
>> (BTW: I can't speak for the nilearn recipe, because I didn't create it,
>> but if anyone is interested in joining as a maintainer of any of the
>> others, feel free to add yourself in a PR to the relevant section of the
>> recipe yaml file).
>>
>> (BTBTW: If anyone is interested in help/guidance is setting up one of
>> these, let me know and I can share from my own experience; the conda-forg
>> org is super-helpful though, so they will also help shepherd you through
>> the process. A really great community!)
>>
>> Thanks!
>>
>> Ariel
>>
>>
>> ---------- Forwarded message ----------
>> From: GitHub <noreply at github.com>
>> Date: Sat, Jun 25, 2016 at 3:08 AM
>> Subject: [GitHub] Subscribed to nipy/staged-recipes notifications
>> To: arokem at gmail.com
>>
>>
>>
>> Hey there, we’re just writing to let you know that you’ve been
>> automatically subscribed to a repository on GitHub.
>>
>>     nipy/staged-recipes forked by satra from conda-forge/staged-recipes
>>     A place to submit conda recipes before they become fully fledged
>> conda-forge feedstocks
>>     https://github.com/nipy/staged-recipes
>>
>> You’ll receive notifications for all issues, pull requests, and comments
>> that happen inside the repository. If you would like to stop watching this
>> repository, you can manage your settings here:
>>
>>     https://github.com/nipy/staged-recipes/subscription
>>
>> You can unwatch this repository immediately by clicking here:
>>
>>
>> https://github.com/nipy/staged-recipes/unsubscribe_via_email/AAHPNpd6rPkNEoi4twlYrh2YpbcP_4nBks5qPP4FgaJpZM4DsRgl
>>
>> You were automatically subscribed because you’ve been given push access
>> to the repository.
>>
>> Thanks!
>>
>>
>> _______________________________________________
>> Neuroimaging mailing list
>> Neuroimaging at python.org
>> https://mail.python.org/mailman/listinfo/neuroimaging
>>
>>
>
> _______________________________________________
> Neuroimaging mailing list
> Neuroimaging at python.org
> https://mail.python.org/mailman/listinfo/neuroimaging
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/neuroimaging/attachments/20160625/0121ece7/attachment.html>