<div><div dir="auto">Hey Yarik,</div></div><div dir="auto"><br></div><div dir="auto">Good to hear from you too. If we are only going to meet in person every 15-20 years I think we need to wear those badges like high school reunions with pictures of our younger, more idealistic selves:) Sorry for the delay but living in the UK as foreign residents has its ups and downs with my wife finishing grad school. </div><div dir="auto"><br></div><div dir="auto">To your points. Well if you don’t mind me sometimes mailing the list about upstream issues, I have a couple people working on neurodebian packages too so it will be mostly relevant. For dsiStudio for instance, I am wondering what we should do about the data that he doesn’t have bundled in his main source project. It will be mostly things like that. I am still very interested in the current status of a independent FreeSurfer build BTW. </div><div dir="auto"><br></div><div dir="auto">I will definitely make datalad a priority. I think Igor will approve:) My friend Simon has been running an IPFS node BTW. I will checkout popcon for sure. I think mricron, mrtrix3, AFNI, MNI tools and ANTs cover a lot of ground in terms of broad coverage with GPL/BSD tools. Interesting but not surprising on the top results. Curious how much you de-emphasize Python tools (NiPy projects), not denying their awesome merits, but just because everyone pushes Anaconda and/or pip installable generic packaging. </div><div dir="auto"><br></div><div dir="auto">Love to hear more about your FOSDEM plans. Happy to volunteer to help. I think there are some HBP software/standards projects they would like to also see more outside adoption too. I know at MozFest there are non-scientists interested and motivated to help in ways they can with projects. That’s certainly what I am trying to learn from Mozilla Fellows. If we can find the right engagement, I think there are people out there interested. Separately from NeuroFedora, I am trying to do more with make/hackaday hardware crowd and find projects that solve their problems like LSL that might get them more engaged. Still digging. </div><div dir="auto"><br></div><div dir="auto">Talk more soon. Hope to see you again soon (maybe January in Florida this time?)</div><div dir="auto"><br></div><div dir="auto">Cheers,</div><div dir="auto"><br></div><div dir="auto">-Morgan </div><div><br><div class="gmail_quote"><div dir="ltr">On Tue, Nov 13, 2018 at 5:09 AM Yaroslav Halchenko <<a href="mailto:debian@onerussian.com">debian@onerussian.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
On Sun, 11 Nov 2018, Morgan Hough wrote:<br>
<br>
> Hi Yarik/Michael/All,<br>
<br>
Hi Morgan! Long time no hear!<br>
<br>
> Ankur Sinha recently resurrected NeuroFedora and as he is a computational<br>
> neuroscientist, he has been focused on packaging NEST, Brian, etc. Igor<br>
> Gnatenko and I previous used a shared Google Doc with packages drawn from<br>
> NeuroDebian and the web that seemed to fit the criteria for inclusion but<br>
> it needs to be updated and before I did that I wanted to get in touch<br>
> about a couple of things. <br>
> 1) Is there still neurodebian-upstream list that would maybe be<br>
> appropriate for sharing info on common upstream packaging/licensing<br>
> problems?<br>
<br>
With the migration of the "non-official" lists server in Debian, we<br>
didn't bother moving -upstream and -devel since they were too low volume<br>
thus I think ATM we have only neurodebian-users:<br>
<a href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo" rel="noreferrer" target="_blank">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo</a><br>
<br>
> 2) Is there an up-to-date list of the most widely installed packages from<br>
> NeuroDebian that we can use to prioritize our RPM packaging efforts with<br>
> sought after neuroimaging packages?<br>
<br>
DataLad (and datalad-containers and datalad-neuroimaging) should go<br>
first! ;) would need fresh git-annex<br>
<br>
on a (more) serious note: I guess checkout neurodebian popcon<br>
<a href="http://neuro.debian.net/popcon/" rel="noreferrer" target="_blank">http://neuro.debian.net/popcon/</a><br>
so you could get e.g. those pkgs which we provide sorted by installation<br>
count:<br>
<br>
$> wget -O - -q <a href="http://neuro.debian.net/popcon/by_inst" rel="noreferrer" target="_blank">http://neuro.debian.net/popcon/by_inst</a> | grep -v 'Not in sid' | head -n 40<br>
#Format<br>
# <br>
#<name> is the package name;<br>
#<inst> is the number of people who installed this package;<br>
#<vote> is the number of people who use this package regularly;<br>
#<old> is the number of people who installed, but don't use this package<br>
# regularly;<br>
#<recent> is the number of people who upgraded this package recently;<br>
#<no-files> is the number of people whose entry didn't contain enough<br>
# information (atime and ctime were 0).<br>
#rank name inst vote old recent no-files (maintainer)<br>
116 neurodebian-popularity-contest 932 742 146 44 0 (Neurodebian Maintainers) <br>
224 python-pkg-resources 886 350 498 32 6 (Neurodebian Maintainers) <br>
392 libjs-jquery 812 134 251 34 393 (Debian Javascript Maintainers) <br>
404 init-system-helpers 806 392 393 19 2 (Neurodebian Maintainers) <br>
455 python-six 791 174 488 118 11 (Neurodebian Maintainers) <br>
569 p7zip-full 757 289 447 21 0 (Neurodebian Maintainers) <br>
627 python3-pkg-resources 745 273 441 31 0 (Neurodebian Maintainers) <br>
692 python-setuptools 730 250 442 31 7 (Neurodebian Maintainers) <br>
722 python3-six 723 126 524 69 4 (Neurodebian Maintainers) <br>
815 python-tz 698 58 611 28 1 (Neurodebian Maintainers) <br>
1012 p7zip 643 266 357 20 0 (Neurodebian Maintainers) <br>
1027 python-urllib3 639 66 512 56 5 (Neurodebian Maintainers) <br>
...<br>
<br>
which shows that "most popular" aren't neuroscience ones, but you could<br>
find the ones of interest below in there.<br>
<br>
<br>
> 3) I would certainly be interested in learning about venues that have been<br>
> useful to present NeuroDebian to those outside the neuroimaging community<br>
> (FOSDEM, MozFest, etc.) as well as any interest in sharing booth<br>
> space/fees/costs/resources/labor for such opportunities. As a regular<br>
> neurodebian user myself, I would be very proud to represent NeuroDebian at<br>
> some of the most recent open source/open science conferences I have<br>
> attended.<br>
<br>
Well -- we kinda suck at promotion outside of the field. We are contemplating<br>
though presence at the next FOSDEM but primarily not for NeuroDebian but for<br>
DataLad project, which although with the roots in neuroscience, has little to<br>
nothing neuroscience specific in it. So we really need to promote it beyond<br>
neuroimaging and neuroscience community. <br>
<br>
Promoting NeuroDebian outside of Neuroscience community might be a bit futile I<br>
guess ;-) After all it is NEURO Debian, even though we indeed package/support<br>
some generic projects, accent is neuro- stuff, and those generic ones are<br>
probably largely from python land, and that is where ppl often just resort to<br>
conda.<br>
<br>
> Finally, I don't know what support NeuroDebian currently receives for<br>
> efforts outside neuroimaging research but if it is within my budget I<br>
> would match that to include NeuroFedora. Happy to do that through/with<br>
> INCF or however others see fit. I only want this to be a contribution and<br>
> net benefit in terms of relations with other projects such as NeuroDebian.<br>
> I would certainly like to learn how I can help NeuroFedora perhaps benefit<br>
> from research funding as well but as the new kid on the block mainly just<br>
> looking for advice to get started providing a service that others will<br>
> benefit from now.<br>
<br>
Eh... we scored 3 "non awarded" proposals to both NIH and NSF where we sought<br>
for direct support/development for NeuroDebian. It was always a matter of 1<br>
reviewer saying smth like "oh well, this packaging stuff is not as important as<br>
development of new methodologies!" which kills the average score. So we gave<br>
up looking for dedicated funds for sustained funding... ATM we sustain<br>
NeuroDebian only via side-efforts within e.g. DataLad (funding is over),<br>
ReproNim projects, and also thanks to support via consulting agreement with the<br>
NIH funded NITRC. Also placing packages under joint maintenance with Debian<br>
Med and Science (and other) teams helps at times, although at other times<br>
involves just fixing up packaging so it backports easily, but I think it mostly<br>
helps ;-)<br>
<br>
<br>
> Thanks for your time, and as always, thank you for your inspiring project<br>
> and community.<br>
<br>
Thank you Morgan for your kind words and good luck with NeuroFedora effort!<br>
-- <br>
Yaroslav O. Halchenko<br>
Center for Open Neuroscience <a href="http://centerforopenneuroscience.org" rel="noreferrer" target="_blank">http://centerforopenneuroscience.org</a><br>
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755<br>
Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419<br>
WWW: <a href="http://www.linkedin.com/in/yarik" rel="noreferrer" target="_blank">http://www.linkedin.com/in/yarik</a> <br>
</blockquote></div></div>