From dimitri.papadopoulos at cea.fr Thu Oct 1 12:22:58 2015 From: dimitri.papadopoulos at cea.fr (Dimitri Papadopoulos Orfanos) Date: Thu, 1 Oct 2015 12:22:58 +0200 Subject: [Neuroimaging] [nibabel] reading corrupt *.nii.gz files In-Reply-To: References: <560BE520.9030205@cea.fr> Message-ID: <560D0982.6010708@cea.fr> Hi Matthew, Le 30/09/2015 21:29, Matthew Brett a ?crit : > [...] > Would the friendly error be much different from the unfriendly one > though? I guess it would just be something like 'Error reading > compressed image data : Error -3 while decompressing: invalid code > lengths set' ? > [...] I was thinking of intercepting this specific error -3 (Z_DATA_ERROR) and emitting a message such as: Error reading compressed image data: the compressed file is corrupted, most probably truncated (zlib reports: invalid code lengths set). The zlib documentation (http://www.zlib.net/manual.html) reads: inflate() returns [...] Z_DATA_ERROR if the input data was corrupted (input stream not conforming to the zlib format or incorrect check value) [...] If Z_DATA_ERROR is returned, the application may then call inflateSync() to look for a good compression block if a partial recovery of the data is desired. Best, Dimitri From j.davidgriffiths at gmail.com Thu Oct 1 19:33:55 2015 From: j.davidgriffiths at gmail.com (John Griffiths) Date: Thu, 1 Oct 2015 13:33:55 -0400 Subject: [Neuroimaging] visualize odfs on a slice with dipy fvtk Message-ID: Dear dipy experts, I'd like to visualize some ODFs on a slice with fvtk. Something like the example here http://nipy.sourceforge.net/dipy/examples_built/reconst_csd.html#example-reconst-csd ...but with additionally an FA or RGB map for the slice 'underneath' the ODFs. Is that possible? Ta, john -- Dr. John Griffiths Post-Doctoral Research Fellow Rotman Research Institute, Baycrest Toronto, Canada and Visiting Research Fellow School of Physics University of Sydney -------------- next part -------------- An HTML attachment was scrubbed... URL: From garyfallidis at gmail.com Thu Oct 1 20:00:02 2015 From: garyfallidis at gmail.com (Eleftherios Garyfallidis) Date: Thu, 1 Oct 2015 14:00:02 -0400 Subject: [Neuroimaging] visualize odfs on a slice with dipy fvtk In-Reply-To: References: Message-ID: Hi John, Yes, it is possible but the code is not yet merged in the development branch. Have a look here https://github.com/Garyfallidis/dipy/blob/fvtk_2.0_pr2/dipy/viz/tests/test_fvtk_actors.py#L212 Give me some feedback if you start using it. Have a look also at this tutorial it has many goodies :) https://github.com/Garyfallidis/dipy/blob/fvtk_2.0_pr2/doc/examples/viz_advanced.py Happy hacking! Cheers, Eleftherios On Thu, Oct 1, 2015 at 1:33 PM, John Griffiths wrote: > > Dear dipy experts, > > I'd like to visualize some ODFs on a slice with fvtk. > > Something like the example here > > > http://nipy.sourceforge.net/dipy/examples_built/reconst_csd.html#example-reconst-csd > > ...but with additionally an FA or RGB map for the slice 'underneath' the > ODFs. > > > Is that possible? > > > Ta, > > john > > > > -- > > Dr. John Griffiths > > Post-Doctoral Research Fellow > > Rotman Research Institute, Baycrest > > Toronto, Canada > > and > > Visiting Research Fellow > > School of Physics > > University of Sydney > > _______________________________________________ > Neuroimaging mailing list > Neuroimaging at python.org > https://mail.python.org/mailman/listinfo/neuroimaging > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jcohen at polymtl.ca Sun Oct 4 17:38:56 2015 From: jcohen at polymtl.ca (Julien Cohen-Adad) Date: Sun, 4 Oct 2015 11:38:56 -0400 Subject: [Neuroimaging] Installing dipy without compiling Message-ID: Hi, For the software we are distributing ( https://github.com/neuropoly/spinalcordtoolbox), we would like to include dipy. It's fairly easy to install it automatically via pip, however the OSX platform requires XCode (or other compilers). Since this is a problem for some of our users, I was wondering if there is a good way to precompile dipy and include it in our package. Currently we do include some binaries (e.g. ANTs) that work for OSX (>10.8) and most linux distributions therefore this solution is very easy to support. Thank you for your help, Julien -- Julien Cohen-Adad, PhD Assistant Professor, Polytechnique Montreal Associate Director, Functional Neuroimaging Unit, University of Montreal Phone: 514 340 5121 (office: 2264); Skype: jcohenadad Web: www.neuro.polymtl.ca -------------- next part -------------- An HTML attachment was scrubbed... URL: From garyfallidis at gmail.com Mon Oct 5 22:39:40 2015 From: garyfallidis at gmail.com (Eleftherios Garyfallidis) Date: Mon, 5 Oct 2015 16:39:40 -0400 Subject: [Neuroimaging] [Dipy] Next release scheduled for 19th of October Message-ID: Dear Dipy developers, We didn't release for a few months now. So, we discussed with Ariel and we are suggesting to release on the 19th of October. Ariel will lead this release because I need to finish some of my research work before the end of my postdoc which is soon and I need to prioritize this for now. So, I will help as much as I can but with limited time. So, please especially the core developers find some time and let's all try to review/merge nicely the latest PRs and have another successful release pushing the boundaries of dMRI. GGT!, Eleftherios -------------- next part -------------- An HTML attachment was scrubbed... URL: From katiesurrence at gmail.com Wed Oct 7 18:36:45 2015 From: katiesurrence at gmail.com (Katie Surrence) Date: Wed, 7 Oct 2015 12:36:45 -0400 Subject: [Neuroimaging] SpaceTimeRealigner doesn't write multiple output files Message-ID: Dear All, I'm reposting this question from Neurostars to see if anyone here might have insight. I'm trying to use SpaceTimeRealigner through NiPype. I had SpaceTimeRealigner running, but I realized that I was only realigning within run, and not between them. Referring to the reference article, it says that it realigns multiple runs by computing a mean image within run after 4D realignment, realigning those mean images to each other, and then composing that transform with the within run transforms. So far, so good. In the sample code in that article, it passes the realigner object multiple runs in a list. However, now I return to my original confusion (A: two questions about simultaneous realignment and slice timing in NiPype ) about how/where files are written. When I run SpaceTimeRealigner, the output corr_4D.nii.gz is written to the current working directory. When I was realigning one run at a time, I could just change the working directory in my script and the corrected file plopped into the right place. When I try to realign multiple runs at once, I can't do that, and the single file I get at the end (written into the current working directory) has the dimensions of a single run (I imagine it's the last run realigned) not a bunch of concatenated runs. Here is what I have right now: for sub in subjects.keys(): infiles = [] for run in subjects[sub]: infiles.append(os.path.join(root, sub, 'func', run, '4D.nii')) realigner = SpaceTimeRealigner() realigner.inputs.in_file = infiles realigner.inputs.tr = 2.2 step = 2.2/34. order = [x*step for x in range(0, 34)] realigner.inputs.slice_times = order realigner.inputs.slice_info = 2 newdir = os.path.join(root, sub, 'func', run, 'tmp') if not os.path.isdir(newdir): os.mkdir(newdir) os.chdir(newdir) res = realigner.run() How do I get SpaceTimeRealigner to both realign runs with each other, and write an individual corrected 4d file for each run into a distinct directory? Thanks very much for any help you can provide. Best, Katie -------------- next part -------------- An HTML attachment was scrubbed... URL: From arokem at gmail.com Thu Oct 8 18:09:51 2015 From: arokem at gmail.com (Ariel Rokem) Date: Thu, 8 Oct 2015 09:09:51 -0700 Subject: [Neuroimaging] Installing dipy without compiling In-Reply-To: References: Message-ID: Hi Julien, It should be possible for us to provide pre-compiled binaries for different platforms. Ideally, that's what we should have on pypi, so that a pip install doesn't require compilation. However, we are rather stretched as it is, so we don't usually do that. It would be good to hear what exactly are your needs: OSX would be easier to support (at least for machines that are fairly up-to-date, no Power PCs, please...); Windows might be a bit more challenging (though we do now have a few developers on the team who work on that platform). At the very least, I think that you should be able to compile dipy on your target machine, and distribute that together with your toolbox. I don't see any reason that wouldn't work. Cheers, Ariel On Sun, Oct 4, 2015 at 8:38 AM, Julien Cohen-Adad wrote: > Hi, > > For the software we are distributing ( > https://github.com/neuropoly/spinalcordtoolbox), we would like to include > dipy. > > It's fairly easy to install it automatically via pip, however the OSX > platform requires XCode (or other compilers). Since this is a problem for > some of our users, I was wondering if there is a good way to precompile > dipy and include it in our package. Currently we do include some binaries > (e.g. ANTs) that work for OSX (>10.8) and most linux distributions > therefore this solution is very easy to support. > > Thank you for your help, > > Julien > > -- > Julien Cohen-Adad, PhD > Assistant Professor, Polytechnique Montreal > Associate Director, Functional Neuroimaging Unit, University of Montreal > Phone: 514 340 5121 (office: 2264); Skype: jcohenadad > Web: www.neuro.polymtl.ca > > _______________________________________________ > Neuroimaging mailing list > Neuroimaging at python.org > https://mail.python.org/mailman/listinfo/neuroimaging > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From matthew.brett at gmail.com Thu Oct 8 18:13:16 2015 From: matthew.brett at gmail.com (Matthew Brett) Date: Thu, 8 Oct 2015 09:13:16 -0700 Subject: [Neuroimaging] Installing dipy without compiling In-Reply-To: References: Message-ID: Hi, On Sun, Oct 4, 2015 at 8:38 AM, Julien Cohen-Adad wrote: > Hi, > > For the software we are distributing > (https://github.com/neuropoly/spinalcordtoolbox), we would like to include > dipy. > > It's fairly easy to install it automatically via pip, however the OSX > platform requires XCode (or other compilers). Since this is a problem for > some of our users, I was wondering if there is a good way to precompile dipy > and include it in our package. Currently we do include some binaries (e.g. > ANTs) that work for OSX (>10.8) and most linux distributions therefore this > solution is very easy to support. Actually, a pip install of dipy should download the binary wheels, and not require a compiler. Is that not the case? You can always ship the default dipy wheel (from pypi) and install that with pip during your install phase. Cheers, Matthew From jcohen at polymtl.ca Thu Oct 8 22:03:18 2015 From: jcohen at polymtl.ca (Julien Cohen-Adad) Date: Thu, 8 Oct 2015 16:03:18 -0400 Subject: [Neuroimaging] Installing dipy without compiling In-Reply-To: References: Message-ID: OK, we created wheels for OSX and installation works smoothly with pip. Thank you very much for your help! Julien On Thu, Oct 8, 2015 at 12:13 PM, Matthew Brett wrote: > Hi, > > On Sun, Oct 4, 2015 at 8:38 AM, Julien Cohen-Adad > wrote: > > Hi, > > > > For the software we are distributing > > (https://github.com/neuropoly/spinalcordtoolbox), we would like to > include > > dipy. > > > > It's fairly easy to install it automatically via pip, however the OSX > > platform requires XCode (or other compilers). Since this is a problem for > > some of our users, I was wondering if there is a good way to precompile > dipy > > and include it in our package. Currently we do include some binaries > (e.g. > > ANTs) that work for OSX (>10.8) and most linux distributions therefore > this > > solution is very easy to support. > > Actually, a pip install of dipy should download the binary wheels, and > not require a compiler. Is that not the case? You can always ship > the default dipy wheel (from pypi) and install that with pip during > your install phase. > > Cheers, > > Matthew > _______________________________________________ > Neuroimaging mailing list > Neuroimaging at python.org > https://mail.python.org/mailman/listinfo/neuroimaging > -------------- next part -------------- An HTML attachment was scrubbed... URL: From matthew.brett at gmail.com Sun Oct 11 09:59:25 2015 From: matthew.brett at gmail.com (Matthew Brett) Date: Sun, 11 Oct 2015 00:59:25 -0700 Subject: [Neuroimaging] Upcoming nipy release In-Reply-To: References: <20150828135930.GR19455@onerussian.com> <20150925003033.GW30459@onerussian.com> Message-ID: Hi, On Fri, Sep 25, 2015 at 6:27 PM, Matthew Brett wrote: > Hi, > > I think we're nearly there now. I've reviewed all the PRs but one - > I think all the current nipy PRs should go into the release when > ready. > > The one I'm working on at the moment, that doesn't need input from > anyone yet, is https://github.com/nipy/nipy/pull/301 by Jonathan. > > Could y'all have a look at the remaining PRs over the next couple of > days, clear up the remaining comments? OK - we are very nearly there. I've finished work on top of Jonathan's stuff, I would be very grateful for a review: https://github.com/nipy/nipy/pull/366 A tiny PR fixing up a couple of examples: https://github.com/nipy/nipy/pull/371 A new travis error in empirical p value with Numpy 1.10: https://github.com/nipy/nipy/issues/369 An error in an example, on an automated test run: https://github.com/nipy/nipy/issues/370 Once these are cleared, I think, finally, we are ready to go. Onward and upward, Matthew From arokem at gmail.com Tue Oct 13 21:18:01 2015 From: arokem at gmail.com (Ariel Rokem) Date: Tue, 13 Oct 2015 12:18:01 -0700 Subject: [Neuroimaging] Bumping up minimal numpy version? Message-ID: Hi everyone, With numpy 1.10 now out, would it be draconic to bump up the minimal supported version up to 1.8? See also: https://github.com/nipy/dipy/pull/731 Cheers, Ariel -------------- next part -------------- An HTML attachment was scrubbed... URL: From matthew.brett at gmail.com Tue Oct 13 21:27:31 2015 From: matthew.brett at gmail.com (Matthew Brett) Date: Tue, 13 Oct 2015 12:27:31 -0700 Subject: [Neuroimaging] Bumping up minimal numpy version? In-Reply-To: References: Message-ID: Hi, On Tue, Oct 13, 2015 at 12:18 PM, Ariel Rokem wrote: > Hi everyone, > > With numpy 1.10 now out, would it be draconic to bump up the minimal > supported version up to 1.8? > > See also: https://github.com/nipy/dipy/pull/731 Can you avoid that? Standard minimum numpy requirement seems to be 1.7.1 - e.g Pandas, Scipy etc. Cheers, Matthew From arokem at gmail.com Tue Oct 13 21:40:01 2015 From: arokem at gmail.com (Ariel Rokem) Date: Tue, 13 Oct 2015 12:40:01 -0700 Subject: [Neuroimaging] Bumping up minimal numpy version? In-Reply-To: References: Message-ID: Hi Matthew, Thanks for the quick response! On Tue, Oct 13, 2015 at 12:27 PM, Matthew Brett wrote: > Hi, > > On Tue, Oct 13, 2015 at 12:18 PM, Ariel Rokem wrote: > > Hi everyone, > > > > With numpy 1.10 now out, would it be draconic to bump up the minimal > > supported version up to 1.8? > > > > See also: https://github.com/nipy/dipy/pull/731 > > Can you avoid that? Standard minimum numpy requirement seems to be > 1.7.1 - e.g Pandas, Scipy etc. > Probably. But there doesn't seem to be a wheel for that in the scikit-image wheelhouse: https://travis-ci.org/nipy/dipy/jobs/85177837#L171 Would it be much trouble to make that available? Thanks! Ariel > Cheers, > > Matthew > _______________________________________________ > Neuroimaging mailing list > Neuroimaging at python.org > https://mail.python.org/mailman/listinfo/neuroimaging > -------------- next part -------------- An HTML attachment was scrubbed... URL: From matthew.brett at gmail.com Tue Oct 13 21:39:48 2015 From: matthew.brett at gmail.com (Matthew Brett) Date: Tue, 13 Oct 2015 12:39:48 -0700 Subject: [Neuroimaging] Upcoming nipy release In-Reply-To: References: <20150828135930.GR19455@onerussian.com> <20150925003033.GW30459@onerussian.com> Message-ID: Hi, On Sun, Oct 11, 2015 at 12:59 AM, Matthew Brett wrote: > Hi, > > On Fri, Sep 25, 2015 at 6:27 PM, Matthew Brett wrote: >> Hi, >> >> I think we're nearly there now. I've reviewed all the PRs but one - >> I think all the current nipy PRs should go into the release when >> ready. >> >> The one I'm working on at the moment, that doesn't need input from >> anyone yet, is https://github.com/nipy/nipy/pull/301 by Jonathan. >> >> Could y'all have a look at the remaining PRs over the next couple of >> days, clear up the remaining comments? > > OK - we are very nearly there. > > I've finished work on top of Jonathan's stuff, I would be very > grateful for a review: > > https://github.com/nipy/nipy/pull/366 Any takers for this one? It's ready for merge after a review. > A tiny PR fixing up a couple of examples: > > https://github.com/nipy/nipy/pull/371 Merged, thanks to Chris Markiewicz for the review. > A new travis error in empirical p value with Numpy 1.10: > > https://github.com/nipy/nipy/issues/369 Proposed fix in https://github.com/nipy/nipy/pull/372 > An error in an example, on an automated test run: > > https://github.com/nipy/nipy/issues/370 Proposed fix in https://github.com/nipy/nipy/pull/373 - but I'm not sure if the fix is right. > Once these are cleared, I think, finally, we are ready to go. There is a small bit of work on pip installing to do - https://github.com/nipy/nipy/issues/320 - but then I think we're ready. Cheers, Matthew From matthew.brett at gmail.com Tue Oct 13 21:42:31 2015 From: matthew.brett at gmail.com (Matthew Brett) Date: Tue, 13 Oct 2015 12:42:31 -0700 Subject: [Neuroimaging] Bumping up minimal numpy version? In-Reply-To: References: Message-ID: Yo, On Tue, Oct 13, 2015 at 12:40 PM, Ariel Rokem wrote: > Hi Matthew, > > Thanks for the quick response! > > On Tue, Oct 13, 2015 at 12:27 PM, Matthew Brett > wrote: >> >> Hi, >> >> On Tue, Oct 13, 2015 at 12:18 PM, Ariel Rokem wrote: >> > Hi everyone, >> > >> > With numpy 1.10 now out, would it be draconic to bump up the minimal >> > supported version up to 1.8? >> > >> > See also: https://github.com/nipy/dipy/pull/731 >> >> Can you avoid that? Standard minimum numpy requirement seems to be >> 1.7.1 - e.g Pandas, Scipy etc. > > > Probably. But there doesn't seem to be a wheel for that in the scikit-image > wheelhouse: > > https://travis-ci.org/nipy/dipy/jobs/85177837#L171 > > Would it be much trouble to make that available? Not much trouble, but there is a wheel for 1.7.1 . I can't remember what the 1.7.1 was compared to 1.7.0 but it does seem to be standard to use 1.7.1. Matthew From bertrand.thirion at inria.fr Tue Oct 13 21:49:21 2015 From: bertrand.thirion at inria.fr (bthirion) Date: Tue, 13 Oct 2015 21:49:21 +0200 Subject: [Neuroimaging] Upcoming nipy release In-Reply-To: References: <20150828135930.GR19455@onerussian.com> <20150925003033.GW30459@onerussian.com> Message-ID: <561D6041.7050703@inria.fr> I'll try to take a look for the ones I am supposed to know better. My todolist is a bit messy atm. Best, Bertrand On 13/10/2015 21:39, Matthew Brett wrote: > Hi, > > On Sun, Oct 11, 2015 at 12:59 AM, Matthew Brett wrote: >> Hi, >> >> On Fri, Sep 25, 2015 at 6:27 PM, Matthew Brett wrote: >>> Hi, >>> >>> I think we're nearly there now. I've reviewed all the PRs but one - >>> I think all the current nipy PRs should go into the release when >>> ready. >>> >>> The one I'm working on at the moment, that doesn't need input from >>> anyone yet, is https://github.com/nipy/nipy/pull/301 by Jonathan. >>> >>> Could y'all have a look at the remaining PRs over the next couple of >>> days, clear up the remaining comments? >> OK - we are very nearly there. >> >> I've finished work on top of Jonathan's stuff, I would be very >> grateful for a review: >> >> https://github.com/nipy/nipy/pull/366 > Any takers for this one? It's ready for merge after a review. > >> A tiny PR fixing up a couple of examples: >> >> https://github.com/nipy/nipy/pull/371 > Merged, thanks to Chris Markiewicz for the review. > >> A new travis error in empirical p value with Numpy 1.10: >> >> https://github.com/nipy/nipy/issues/369 > Proposed fix in https://github.com/nipy/nipy/pull/372 > >> An error in an example, on an automated test run: >> >> https://github.com/nipy/nipy/issues/370 > Proposed fix in https://github.com/nipy/nipy/pull/373 - but I'm not > sure if the fix is right. > >> Once these are cleared, I think, finally, we are ready to go. > There is a small bit of work on pip installing to do - > https://github.com/nipy/nipy/issues/320 - but then I think we're > ready. > > Cheers, > > Matthew > _______________________________________________ > Neuroimaging mailing list > Neuroimaging at python.org > https://mail.python.org/mailman/listinfo/neuroimaging From angel.torrado at urjc.es Tue Oct 13 22:08:53 2015 From: angel.torrado at urjc.es (=?UTF-8?Q?=C3=81ngel_Torrado_Carvajal?=) Date: Tue, 13 Oct 2015 16:08:53 -0400 Subject: [Neuroimaging] Affine Matrix AttributeError Message-ID: Dear all, I am trying to execute my (already working) code, and I am getting an error: Traceback (most recent call last): File "PatchBasedSegmentation.py", line 158, in output_img = nb.Nifti1Image(output_matrix_0, input_img.affine, input_img.header) AttributeError: 'Nifti1Image' object has no attribute 'affine' where: input_img = nb.load(input_path + input_vol) What's the problem? From the *documentation * a 'Nifti1Image' object HAS attribute 'affine'. Actually, it is working in my laptop. How can I fix it in this computer? Thank you in advance, *--* * ?ngel Torrado Carvajal* * Research Assistant* Medical Image Analysis Laboratory Universidad Rey Juan Carlos Despacho 155 - Departamental II Calle Tulip?n s/n 28933 M?stoles - Madrid * Before printing this message, make sure it's necessary. Protecting the environment is in your hand.* * Antes de imprimir este mensaje, aseg?rate de que es necesario. Proteger el medio ambiente est? tambi?n en tu mano.* -------------- next part -------------- An HTML attachment was scrubbed... URL: From matthew.brett at gmail.com Tue Oct 13 22:12:02 2015 From: matthew.brett at gmail.com (Matthew Brett) Date: Tue, 13 Oct 2015 13:12:02 -0700 Subject: [Neuroimaging] Affine Matrix AttributeError In-Reply-To: References: Message-ID: Hi, On Tue, Oct 13, 2015 at 1:08 PM, ?ngel Torrado Carvajal wrote: > Dear all, > > I am trying to execute my (already working) code, and I am getting an error: > > Traceback (most recent call last): > File "PatchBasedSegmentation.py", line 158, in > output_img = nb.Nifti1Image(output_matrix_0, input_img.affine, > input_img.header) > AttributeError: 'Nifti1Image' object has no attribute 'affine' > > where: > > input_img = nb.load(input_path + input_vol) > > What's the problem? From the documentation a 'Nifti1Image' object HAS > attribute 'affine'. Actually, it is working in my laptop. How can I fix it > in this computer? I think you've got an older version of nibabel - pre 2.0. We introduced the `.affine` property in 2.0. If you want code compatible with older and newer nibabel, use `img.get_affine()` instead, HTH, Matthew From matthew.brett at gmail.com Tue Oct 13 22:13:14 2015 From: matthew.brett at gmail.com (Matthew Brett) Date: Tue, 13 Oct 2015 13:13:14 -0700 Subject: [Neuroimaging] Upcoming nipy release In-Reply-To: <561D6041.7050703@inria.fr> References: <20150828135930.GR19455@onerussian.com> <20150925003033.GW30459@onerussian.com> <561D6041.7050703@inria.fr> Message-ID: On Tue, Oct 13, 2015 at 12:49 PM, bthirion wrote: > I'll try to take a look for the ones I am supposed to know better. My > todolist is a bit messy atm. They should both be very quick... Cheers, Matthew From arokem at gmail.com Tue Oct 13 22:14:40 2015 From: arokem at gmail.com (Ariel Rokem) Date: Tue, 13 Oct 2015 13:14:40 -0700 Subject: [Neuroimaging] Bumping up minimal numpy version? In-Reply-To: References: Message-ID: On Tue, Oct 13, 2015 at 12:42 PM, Matthew Brett wrote: > Yo, > > On Tue, Oct 13, 2015 at 12:40 PM, Ariel Rokem wrote: > > Hi Matthew, > > > > Thanks for the quick response! > > > > On Tue, Oct 13, 2015 at 12:27 PM, Matthew Brett > > > wrote: > >> > >> Hi, > >> > >> On Tue, Oct 13, 2015 at 12:18 PM, Ariel Rokem wrote: > >> > Hi everyone, > >> > > >> > With numpy 1.10 now out, would it be draconic to bump up the minimal > >> > supported version up to 1.8? > >> > > >> > See also: https://github.com/nipy/dipy/pull/731 > >> > >> Can you avoid that? Standard minimum numpy requirement seems to be > >> 1.7.1 - e.g Pandas, Scipy etc. > > > > > > Probably. But there doesn't seem to be a wheel for that in the > scikit-image > > wheelhouse: > > > > https://travis-ci.org/nipy/dipy/jobs/85177837#L171 > > > > Would it be much trouble to make that available? > > Not much trouble, but there is a wheel for 1.7.1 . I can't remember > what the 1.7.1 was compared to 1.7.0 but it does seem to be standard > to use 1.7.1. Tried it, but I really don't think there's a wheel for 1.7.1: https://travis-ci.org/arokem/dipy/jobs/85194895#L164 > Matthew > _______________________________________________ > Neuroimaging mailing list > Neuroimaging at python.org > https://mail.python.org/mailman/listinfo/neuroimaging > -------------- next part -------------- An HTML attachment was scrubbed... URL: From matthew.brett at gmail.com Tue Oct 13 22:19:33 2015 From: matthew.brett at gmail.com (Matthew Brett) Date: Tue, 13 Oct 2015 13:19:33 -0700 Subject: [Neuroimaging] Bumping up minimal numpy version? In-Reply-To: References: Message-ID: Hi, On Tue, Oct 13, 2015 at 1:14 PM, Ariel Rokem wrote: > > > On Tue, Oct 13, 2015 at 12:42 PM, Matthew Brett > wrote: >> >> Yo, >> >> On Tue, Oct 13, 2015 at 12:40 PM, Ariel Rokem wrote: >> > Hi Matthew, >> > >> > Thanks for the quick response! >> > >> > On Tue, Oct 13, 2015 at 12:27 PM, Matthew Brett >> > >> > wrote: >> >> >> >> Hi, >> >> >> >> On Tue, Oct 13, 2015 at 12:18 PM, Ariel Rokem wrote: >> >> > Hi everyone, >> >> > >> >> > With numpy 1.10 now out, would it be draconic to bump up the minimal >> >> > supported version up to 1.8? >> >> > >> >> > See also: https://github.com/nipy/dipy/pull/731 >> >> >> >> Can you avoid that? Standard minimum numpy requirement seems to be >> >> 1.7.1 - e.g Pandas, Scipy etc. >> > >> > >> > Probably. But there doesn't seem to be a wheel for that in the >> > scikit-image >> > wheelhouse: >> > >> > https://travis-ci.org/nipy/dipy/jobs/85177837#L171 >> > >> > Would it be much trouble to make that available? >> >> Not much trouble, but there is a wheel for 1.7.1 . I can't remember >> what the 1.7.1 was compared to 1.7.0 but it does seem to be standard >> to use 1.7.1. > > > Tried it, but I really don't think there's a wheel for 1.7.1: > https://travis-ci.org/arokem/dipy/jobs/85194895#L164 Oops - I see that I didn't build one for Python 2.7 ... I'll do that now. Matthew From arokem at gmail.com Tue Oct 13 22:23:52 2015 From: arokem at gmail.com (Ariel Rokem) Date: Tue, 13 Oct 2015 13:23:52 -0700 Subject: [Neuroimaging] Bumping up minimal numpy version? In-Reply-To: References: Message-ID: On Tue, Oct 13, 2015 at 1:19 PM, Matthew Brett wrote: > Hi, > > On Tue, Oct 13, 2015 at 1:14 PM, Ariel Rokem wrote: > > > > > > On Tue, Oct 13, 2015 at 12:42 PM, Matthew Brett > > > wrote: > >> > >> Yo, > >> > >> On Tue, Oct 13, 2015 at 12:40 PM, Ariel Rokem wrote: > >> > Hi Matthew, > >> > > >> > Thanks for the quick response! > >> > > >> > On Tue, Oct 13, 2015 at 12:27 PM, Matthew Brett > >> > > >> > wrote: > >> >> > >> >> Hi, > >> >> > >> >> On Tue, Oct 13, 2015 at 12:18 PM, Ariel Rokem > wrote: > >> >> > Hi everyone, > >> >> > > >> >> > With numpy 1.10 now out, would it be draconic to bump up the > minimal > >> >> > supported version up to 1.8? > >> >> > > >> >> > See also: https://github.com/nipy/dipy/pull/731 > >> >> > >> >> Can you avoid that? Standard minimum numpy requirement seems to be > >> >> 1.7.1 - e.g Pandas, Scipy etc. > >> > > >> > > >> > Probably. But there doesn't seem to be a wheel for that in the > >> > scikit-image > >> > wheelhouse: > >> > > >> > https://travis-ci.org/nipy/dipy/jobs/85177837#L171 > >> > > >> > Would it be much trouble to make that available? > >> > >> Not much trouble, but there is a wheel for 1.7.1 . I can't remember > >> what the 1.7.1 was compared to 1.7.0 but it does seem to be standard > >> to use 1.7.1. > > > > > > Tried it, but I really don't think there's a wheel for 1.7.1: > > https://travis-ci.org/arokem/dipy/jobs/85194895#L164 > > Oops - I see that I didn't build one for Python 2.7 ... I'll do that now. That would be great. Let me know when you've done it, and I will retrigger that build on Travis. Thanks! > Matthew > _______________________________________________ > Neuroimaging mailing list > Neuroimaging at python.org > https://mail.python.org/mailman/listinfo/neuroimaging > -------------- next part -------------- An HTML attachment was scrubbed... URL: From matthew.brett at gmail.com Tue Oct 13 23:50:37 2015 From: matthew.brett at gmail.com (Matthew Brett) Date: Tue, 13 Oct 2015 14:50:37 -0700 Subject: [Neuroimaging] Bumping up minimal numpy version? In-Reply-To: References: Message-ID: On Tue, Oct 13, 2015 at 1:23 PM, Ariel Rokem wrote: > > On Tue, Oct 13, 2015 at 1:19 PM, Matthew Brett > wrote: >> >> Hi, >> >> On Tue, Oct 13, 2015 at 1:14 PM, Ariel Rokem wrote: >> > >> > >> > On Tue, Oct 13, 2015 at 12:42 PM, Matthew Brett >> > >> > wrote: >> >> >> >> Yo, >> >> >> >> On Tue, Oct 13, 2015 at 12:40 PM, Ariel Rokem wrote: >> >> > Hi Matthew, >> >> > >> >> > Thanks for the quick response! >> >> > >> >> > On Tue, Oct 13, 2015 at 12:27 PM, Matthew Brett >> >> > >> >> > wrote: >> >> >> >> >> >> Hi, >> >> >> >> >> >> On Tue, Oct 13, 2015 at 12:18 PM, Ariel Rokem >> >> >> wrote: >> >> >> > Hi everyone, >> >> >> > >> >> >> > With numpy 1.10 now out, would it be draconic to bump up the >> >> >> > minimal >> >> >> > supported version up to 1.8? >> >> >> > >> >> >> > See also: https://github.com/nipy/dipy/pull/731 >> >> >> >> >> >> Can you avoid that? Standard minimum numpy requirement seems to be >> >> >> 1.7.1 - e.g Pandas, Scipy etc. >> >> > >> >> > >> >> > Probably. But there doesn't seem to be a wheel for that in the >> >> > scikit-image >> >> > wheelhouse: >> >> > >> >> > https://travis-ci.org/nipy/dipy/jobs/85177837#L171 >> >> > >> >> > Would it be much trouble to make that available? >> >> >> >> Not much trouble, but there is a wheel for 1.7.1 . I can't remember >> >> what the 1.7.1 was compared to 1.7.0 but it does seem to be standard >> >> to use 1.7.1. >> > >> > >> > Tried it, but I really don't think there's a wheel for 1.7.1: >> > https://travis-ci.org/arokem/dipy/jobs/85194895#L164 >> >> Oops - I see that I didn't build one for Python 2.7 ... I'll do that now. > > > That would be great. Let me know when you've done it, and I will retrigger > that build on Travis. > > Thanks! There should be 1.7.1 wheels for Python 2.6 and 2.7 now... Matthew From binarybottle at gmail.com Wed Oct 14 14:16:06 2015 From: binarybottle at gmail.com (Arno Klein) Date: Wed, 14 Oct 2015 08:16:06 -0400 Subject: [Neuroimaging] Mindboggle as part of nipy? Message-ID: Hello! I am planning on an official release of the mindboggle package ( http://mindboggle.info) in the next few months and would like it to be more of a community project. Currently, the mindboggle github repository is under my personal username (https://github.com/binarybottle/mindboggle). Would the nipy developer community be interested in integrating mindboggle as part of nipy's github repository, https://github.com/nipy/mindboggle? Any suggestions for making mindboggle a better package that is easier to maintain by the community are most welcome! Cheers, @rno -------------- next part -------------- An HTML attachment was scrubbed... URL: From matthew.brett at gmail.com Wed Oct 14 17:46:26 2015 From: matthew.brett at gmail.com (Matthew Brett) Date: Wed, 14 Oct 2015 08:46:26 -0700 Subject: [Neuroimaging] Mindboggle as part of nipy? In-Reply-To: References: Message-ID: Hi Arno, On Wed, Oct 14, 2015 at 5:16 AM, Arno Klein wrote: > Hello! I am planning on an official release of the mindboggle package > (http://mindboggle.info) in the next few months and would like it to be more > of a community project. Currently, the mindboggle github repository is under > my personal username (https://github.com/binarybottle/mindboggle). Would > the nipy developer community be interested in integrating mindboggle as part > of nipy's github repository, https://github.com/nipy/mindboggle? > > Any suggestions for making mindboggle a better package that is easier to > maintain by the community are most welcome! Thanks for mailing. I'm afraid I don't know mindboggle, but scanning the front page, do I understand right, that mindboggle is an application building on top of nipype? Can the nipypers - er pype up here? I hope all's good, Matthew From satra at mit.edu Wed Oct 14 17:52:13 2015 From: satra at mit.edu (Satrajit Ghosh) Date: Wed, 14 Oct 2015 11:52:13 -0400 Subject: [Neuroimaging] Mindboggle as part of nipy? In-Reply-To: References: Message-ID: hi all, while mindboggle is built on top of nipype as an execution pipeline, at its core it is a collection of algorithms and standalone functions for structural analysis of brains based on piecewise correspondence. +1 from my side to include mindboggle in nipy. cheers, satra On Wed, Oct 14, 2015 at 11:46 AM, Matthew Brett wrote: > Hi Arno, > > On Wed, Oct 14, 2015 at 5:16 AM, Arno Klein > wrote: > > Hello! I am planning on an official release of the mindboggle package > > (http://mindboggle.info) in the next few months and would like it to be > more > > of a community project. Currently, the mindboggle github repository is > under > > my personal username (https://github.com/binarybottle/mindboggle). > Would > > the nipy developer community be interested in integrating mindboggle as > part > > of nipy's github repository, https://github.com/nipy/mindboggle? > > > > Any suggestions for making mindboggle a better package that is easier to > > maintain by the community are most welcome! > > Thanks for mailing. I'm afraid I don't know mindboggle, but scanning > the front page, do I understand right, that mindboggle is an > application building on top of nipype? Can the nipypers - er pype up > here? > > I hope all's good, > > Matthew > _______________________________________________ > Neuroimaging mailing list > Neuroimaging at python.org > https://mail.python.org/mailman/listinfo/neuroimaging > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jbpoline at gmail.com Wed Oct 14 17:55:43 2015 From: jbpoline at gmail.com (JB Poline) Date: Wed, 14 Oct 2015 08:55:43 -0700 Subject: [Neuroimaging] Mindboggle as part of nipy? In-Reply-To: References: Message-ID: +1 ! On Wed, Oct 14, 2015 at 8:52 AM, Satrajit Ghosh wrote: > hi all, > > while mindboggle is built on top of nipype as an execution pipeline, at its > core it is a collection of algorithms and standalone functions for > structural analysis of brains based on piecewise correspondence. > > +1 from my side to include mindboggle in nipy. > > cheers, > > satra > > On Wed, Oct 14, 2015 at 11:46 AM, Matthew Brett > wrote: >> >> Hi Arno, >> >> On Wed, Oct 14, 2015 at 5:16 AM, Arno Klein >> wrote: >> > Hello! I am planning on an official release of the mindboggle package >> > (http://mindboggle.info) in the next few months and would like it to be >> > more >> > of a community project. Currently, the mindboggle github repository is >> > under >> > my personal username (https://github.com/binarybottle/mindboggle). >> > Would >> > the nipy developer community be interested in integrating mindboggle as >> > part >> > of nipy's github repository, https://github.com/nipy/mindboggle? >> > >> > Any suggestions for making mindboggle a better package that is easier to >> > maintain by the community are most welcome! >> >> Thanks for mailing. I'm afraid I don't know mindboggle, but scanning >> the front page, do I understand right, that mindboggle is an >> application building on top of nipype? Can the nipypers - er pype up >> here? >> >> I hope all's good, >> >> Matthew >> _______________________________________________ >> 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 > From arokem at gmail.com Thu Oct 15 02:37:20 2015 From: arokem at gmail.com (Ariel Rokem) Date: Wed, 14 Oct 2015 17:37:20 -0700 Subject: [Neuroimaging] Mindboggle as part of nipy? In-Reply-To: References: Message-ID: +1 from here as well! And: https://github.com/nipy/nipy.github.com/pull/6 On Wed, Oct 14, 2015 at 8:55 AM, JB Poline wrote: > +1 ! > > On Wed, Oct 14, 2015 at 8:52 AM, Satrajit Ghosh wrote: > > hi all, > > > > while mindboggle is built on top of nipype as an execution pipeline, at > its > > core it is a collection of algorithms and standalone functions for > > structural analysis of brains based on piecewise correspondence. > > > > +1 from my side to include mindboggle in nipy. > > > > cheers, > > > > satra > > > > On Wed, Oct 14, 2015 at 11:46 AM, Matthew Brett > > > wrote: > >> > >> Hi Arno, > >> > >> On Wed, Oct 14, 2015 at 5:16 AM, Arno Klein > >> wrote: > >> > Hello! I am planning on an official release of the mindboggle package > >> > (http://mindboggle.info) in the next few months and would like it to > be > >> > more > >> > of a community project. Currently, the mindboggle github repository is > >> > under > >> > my personal username (https://github.com/binarybottle/mindboggle). > >> > Would > >> > the nipy developer community be interested in integrating mindboggle > as > >> > part > >> > of nipy's github repository, https://github.com/nipy/mindboggle? > >> > > >> > Any suggestions for making mindboggle a better package that is easier > to > >> > maintain by the community are most welcome! > >> > >> Thanks for mailing. I'm afraid I don't know mindboggle, but scanning > >> the front page, do I understand right, that mindboggle is an > >> application building on top of nipype? Can the nipypers - er pype up > >> here? > >> > >> I hope all's good, > >> > >> Matthew > >> _______________________________________________ > >> 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 > > > _______________________________________________ > Neuroimaging mailing list > Neuroimaging at python.org > https://mail.python.org/mailman/listinfo/neuroimaging > -------------- next part -------------- An HTML attachment was scrubbed... URL: From matthew.brett at gmail.com Thu Oct 15 02:44:22 2015 From: matthew.brett at gmail.com (Matthew Brett) Date: Wed, 14 Oct 2015 17:44:22 -0700 Subject: [Neuroimaging] Mindboggle as part of nipy? In-Reply-To: References: Message-ID: Hi, On Wed, Oct 14, 2015 at 5:37 PM, Ariel Rokem wrote: > +1 from here as well! > > And: https://github.com/nipy/nipy.github.com/pull/6 > > On Wed, Oct 14, 2015 at 8:55 AM, JB Poline wrote: >> >> +1 ! >> >> On Wed, Oct 14, 2015 at 8:52 AM, Satrajit Ghosh wrote: >> > hi all, >> > >> > while mindboggle is built on top of nipype as an execution pipeline, at >> > its >> > core it is a collection of algorithms and standalone functions for >> > structural analysis of brains based on piecewise correspondence. >> > >> > +1 from my side to include mindboggle in nipy. >> > >> > cheers, >> > >> > satra >> > >> > On Wed, Oct 14, 2015 at 11:46 AM, Matthew Brett >> > >> > wrote: >> >> >> >> Hi Arno, >> >> >> >> On Wed, Oct 14, 2015 at 5:16 AM, Arno Klein >> >> wrote: >> >> > Hello! I am planning on an official release of the mindboggle >> >> > package >> >> > (http://mindboggle.info) in the next few months and would like it to >> >> > be >> >> > more >> >> > of a community project. Currently, the mindboggle github repository >> >> > is >> >> > under >> >> > my personal username (https://github.com/binarybottle/mindboggle). >> >> > Would >> >> > the nipy developer community be interested in integrating mindboggle >> >> > as >> >> > part >> >> > of nipy's github repository, https://github.com/nipy/mindboggle? >> >> > >> >> > Any suggestions for making mindboggle a better package that is easier >> >> > to >> >> > maintain by the community are most welcome! >> >> >> >> Thanks for mailing. I'm afraid I don't know mindboggle, but scanning >> >> the front page, do I understand right, that mindboggle is an >> >> application building on top of nipype? Can the nipypers - er pype up >> >> here? I guess the next question is - who will be maintaining mindboggle? I don't think that it is likely that moving mindboggle to the nipy org will help much in attracting developers, although putting it on the project pages might (thanks for doing that Ariel). Has anyone got any other suggestions for keeping mindboggle in good health? It's always a difficult problem... Cheers, Matthew From arokem at gmail.com Thu Oct 15 02:51:19 2015 From: arokem at gmail.com (Ariel Rokem) Date: Wed, 14 Oct 2015 17:51:19 -0700 Subject: [Neuroimaging] Mindboggle as part of nipy? In-Reply-To: References: Message-ID: On Wed, Oct 14, 2015 at 5:44 PM, Matthew Brett wrote: > Hi, > > On Wed, Oct 14, 2015 at 5:37 PM, Ariel Rokem wrote: > > +1 from here as well! > > > > And: https://github.com/nipy/nipy.github.com/pull/6 > > > > On Wed, Oct 14, 2015 at 8:55 AM, JB Poline wrote: > >> > >> +1 ! > >> > >> On Wed, Oct 14, 2015 at 8:52 AM, Satrajit Ghosh wrote: > >> > hi all, > >> > > >> > while mindboggle is built on top of nipype as an execution pipeline, > at > >> > its > >> > core it is a collection of algorithms and standalone functions for > >> > structural analysis of brains based on piecewise correspondence. > >> > > >> > +1 from my side to include mindboggle in nipy. > >> > > >> > cheers, > >> > > >> > satra > >> > > >> > On Wed, Oct 14, 2015 at 11:46 AM, Matthew Brett > >> > > >> > wrote: > >> >> > >> >> Hi Arno, > >> >> > >> >> On Wed, Oct 14, 2015 at 5:16 AM, Arno Klein > >> >> wrote: > >> >> > Hello! I am planning on an official release of the mindboggle > >> >> > package > >> >> > (http://mindboggle.info) in the next few months and would like it > to > >> >> > be > >> >> > more > >> >> > of a community project. Currently, the mindboggle github repository > >> >> > is > >> >> > under > >> >> > my personal username (https://github.com/binarybottle/mindboggle). > >> >> > Would > >> >> > the nipy developer community be interested in integrating > mindboggle > >> >> > as > >> >> > part > >> >> > of nipy's github repository, https://github.com/nipy/mindboggle? > >> >> > > >> >> > Any suggestions for making mindboggle a better package that is > easier > >> >> > to > >> >> > maintain by the community are most welcome! > >> >> > >> >> Thanks for mailing. I'm afraid I don't know mindboggle, but scanning > >> >> the front page, do I understand right, that mindboggle is an > >> >> application building on top of nipype? Can the nipypers - er pype > up > >> >> here? > > I guess the next question is - who will be maintaining mindboggle? > I don't think that Arno was planning any change in the structure of the project, from that point of view. I think that someone with admin rights on the nipy github org could start a "mindboggle" 'team' and designate Arno to be a manager of this team with all rights on that repo. Arno - is that what you intended? > I don't think that it is likely that moving mindboggle to the nipy org > will help much in attracting developers, although putting it on the > project pages might (thanks for doing that Ariel). > > Has anyone got any other suggestions for keeping mindboggle in good > health? It's always a difficult problem... > > Cheers, > > Matthew > _______________________________________________ > Neuroimaging mailing list > Neuroimaging at python.org > https://mail.python.org/mailman/listinfo/neuroimaging > -------------- next part -------------- An HTML attachment was scrubbed... URL: From binarybottle at gmail.com Thu Oct 15 03:23:19 2015 From: binarybottle at gmail.com (Arno Klein) Date: Wed, 14 Oct 2015 21:23:19 -0400 Subject: [Neuroimaging] Mindboggle as part of nipy? Message-ID: That's right, Ariel -- I was hoping to transfer ownership of the mindboggle repo to nipy and continue to manage its development until I get hit by a bus (or lightning, or both). Cheers, @rno On Wed, Oct 14, 2015 at 8:51 PM, Ariel Rokem wrote: > > > On Wed, Oct 14, 2015 at 5:44 PM, Matthew Brett > wrote: > >> Hi, >> >> On Wed, Oct 14, 2015 at 5:37 PM, Ariel Rokem wrote: >> > +1 from here as well! >> > >> > And: https://github.com/nipy/nipy.github.com/pull/6 >> > >> > On Wed, Oct 14, 2015 at 8:55 AM, JB Poline wrote: >> >> >> >> +1 ! >> >> >> >> On Wed, Oct 14, 2015 at 8:52 AM, Satrajit Ghosh wrote: >> >> > hi all, >> >> > >> >> > while mindboggle is built on top of nipype as an execution pipeline, >> at >> >> > its >> >> > core it is a collection of algorithms and standalone functions for >> >> > structural analysis of brains based on piecewise correspondence. >> >> > >> >> > +1 from my side to include mindboggle in nipy. >> >> > >> >> > cheers, >> >> > >> >> > satra >> >> > >> >> > On Wed, Oct 14, 2015 at 11:46 AM, Matthew Brett >> >> > >> >> > wrote: >> >> >> >> >> >> Hi Arno, >> >> >> >> >> >> On Wed, Oct 14, 2015 at 5:16 AM, Arno Klein > > >> >> >> wrote: >> >> >> > Hello! I am planning on an official release of the mindboggle >> >> >> > package >> >> >> > (http://mindboggle.info) in the next few months and would like >> it to >> >> >> > be >> >> >> > more >> >> >> > of a community project. Currently, the mindboggle github >> repository >> >> >> > is >> >> >> > under >> >> >> > my personal username (https://github.com/binarybottle/mindboggle >> ). >> >> >> > Would >> >> >> > the nipy developer community be interested in integrating >> mindboggle >> >> >> > as >> >> >> > part >> >> >> > of nipy's github repository, https://github.com/nipy/mindboggle? >> >> >> > >> >> >> > Any suggestions for making mindboggle a better package that is >> easier >> >> >> > to >> >> >> > maintain by the community are most welcome! >> >> >> >> >> >> Thanks for mailing. I'm afraid I don't know mindboggle, but >> scanning >> >> >> the front page, do I understand right, that mindboggle is an >> >> >> application building on top of nipype? Can the nipypers - er pype >> up >> >> >> here? >> >> I guess the next question is - who will be maintaining mindboggle? >> > > I don't think that Arno was planning any change in the structure of the > project, from that point of view. I think that someone with admin rights on > the nipy github org could start a "mindboggle" 'team' and designate Arno to > be a manager of this team with all rights on that repo. > > Arno - is that what you intended? > > >> I don't think that it is likely that moving mindboggle to the nipy org >> will help much in attracting developers, although putting it on the >> project pages might (thanks for doing that Ariel). >> >> Has anyone got any other suggestions for keeping mindboggle in good >> health? It's always a difficult problem... >> >> Cheers, >> >> Matthew >> _______________________________________________ >> 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: From arokem at gmail.com Thu Oct 15 15:16:28 2015 From: arokem at gmail.com (Ariel Rokem) Date: Thu, 15 Oct 2015 06:16:28 -0700 Subject: [Neuroimaging] Mindboggle as part of nipy? In-Reply-To: References: Message-ID: As for how to go about development: if for the time being you are the only person writing and merging code on mindboggle, you can either make PRs and merge these yourself, or merge/push to master yourself on your machine, without PRs. In the longer run, hopefully others will join you, and then PRs will be the way to go. In that stage, you will certainly still want a fork of the project under your user account, so that you can use the git workflow for PRs and so on. One way to go about creating the right structure would be to ask the github support team to reverse the forking relationship between nipy/mindboggle and binarybottle/mindboggle. They can do that kind of thing - I've seen it done! This is important, because otherwise PRs will still be done relative to the 'root node' of the forking relationship, which at the moment is binarybottle/mindboggle. On Wed, Oct 14, 2015 at 6:23 PM, Arno Klein wrote: > That's right, Ariel -- I was hoping to transfer ownership of the > mindboggle repo to nipy and continue to manage its development until I get > hit by a bus (or lightning, or both). > > Cheers, > @rno > > On Wed, Oct 14, 2015 at 8:51 PM, Ariel Rokem wrote: > >> >> >> On Wed, Oct 14, 2015 at 5:44 PM, Matthew Brett >> wrote: >> >>> Hi, >>> >>> On Wed, Oct 14, 2015 at 5:37 PM, Ariel Rokem wrote: >>> > +1 from here as well! >>> > >>> > And: https://github.com/nipy/nipy.github.com/pull/6 >>> > >>> > On Wed, Oct 14, 2015 at 8:55 AM, JB Poline wrote: >>> >> >>> >> +1 ! >>> >> >>> >> On Wed, Oct 14, 2015 at 8:52 AM, Satrajit Ghosh >>> wrote: >>> >> > hi all, >>> >> > >>> >> > while mindboggle is built on top of nipype as an execution >>> pipeline, at >>> >> > its >>> >> > core it is a collection of algorithms and standalone functions for >>> >> > structural analysis of brains based on piecewise correspondence. >>> >> > >>> >> > +1 from my side to include mindboggle in nipy. >>> >> > >>> >> > cheers, >>> >> > >>> >> > satra >>> >> > >>> >> > On Wed, Oct 14, 2015 at 11:46 AM, Matthew Brett >>> >> > >>> >> > wrote: >>> >> >> >>> >> >> Hi Arno, >>> >> >> >>> >> >> On Wed, Oct 14, 2015 at 5:16 AM, Arno Klein < >>> binarybottle at gmail.com> >>> >> >> wrote: >>> >> >> > Hello! I am planning on an official release of the mindboggle >>> >> >> > package >>> >> >> > (http://mindboggle.info) in the next few months and would like >>> it to >>> >> >> > be >>> >> >> > more >>> >> >> > of a community project. Currently, the mindboggle github >>> repository >>> >> >> > is >>> >> >> > under >>> >> >> > my personal username (https://github.com/binarybottle/mindboggle >>> ). >>> >> >> > Would >>> >> >> > the nipy developer community be interested in integrating >>> mindboggle >>> >> >> > as >>> >> >> > part >>> >> >> > of nipy's github repository, https://github.com/nipy/mindboggle? >>> >> >> > >>> >> >> > Any suggestions for making mindboggle a better package that is >>> easier >>> >> >> > to >>> >> >> > maintain by the community are most welcome! >>> >> >> >>> >> >> Thanks for mailing. I'm afraid I don't know mindboggle, but >>> scanning >>> >> >> the front page, do I understand right, that mindboggle is an >>> >> >> application building on top of nipype? Can the nipypers - er >>> pype up >>> >> >> here? >>> >>> I guess the next question is - who will be maintaining mindboggle? >>> >> >> I don't think that Arno was planning any change in the structure of the >> project, from that point of view. I think that someone with admin rights on >> the nipy github org could start a "mindboggle" 'team' and designate Arno to >> be a manager of this team with all rights on that repo. >> >> Arno - is that what you intended? >> >> >>> I don't think that it is likely that moving mindboggle to the nipy org >>> will help much in attracting developers, although putting it on the >>> project pages might (thanks for doing that Ariel). >>> >>> Has anyone got any other suggestions for keeping mindboggle in good >>> health? It's always a difficult problem... >>> >>> Cheers, >>> >>> Matthew >>> _______________________________________________ >>> 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 >> >> > > _______________________________________________ > Neuroimaging mailing list > Neuroimaging at python.org > https://mail.python.org/mailman/listinfo/neuroimaging > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From moiein2000 at gmail.com Fri Oct 16 00:15:13 2015 From: moiein2000 at gmail.com (Matthew Einhorn) Date: Thu, 15 Oct 2015 18:15:13 -0400 Subject: [Neuroimaging] Mindboggle as part of nipy? In-Reply-To: References: Message-ID: On Thu, Oct 15, 2015 at 9:16 AM, Ariel Rokem wrote: > As for how to go about development: if for the time being you are the only > person writing and merging code on mindboggle, you can either make PRs and > merge these yourself, or merge/push to master yourself on your machine, > without PRs. In the longer run, hopefully others will join you, and then > PRs will be the way to go. In that stage, you will certainly still want a > fork of the project under your user account, so that you can use the git > workflow for PRs and so on. > > One way to go about creating the right structure would be to ask the > github support team to reverse the forking relationship between > nipy/mindboggle and binarybottle/mindboggle. They can do that kind of thing > - I've seen it done! > I'm not sure if you're aware that you can transfer a repo: https://help.github.com/articles/transferring-a-repository/#transferring-from-a-user-to-an-organization. Transferring to nipy would make it the "root" from which others can fork. But you'd probably have to delete the exiting fork in nipy. Matt -------------- next part -------------- An HTML attachment was scrubbed... URL: From matthew.brett at gmail.com Fri Oct 16 00:20:29 2015 From: matthew.brett at gmail.com (Matthew Brett) Date: Thu, 15 Oct 2015 15:20:29 -0700 Subject: [Neuroimaging] Mindboggle as part of nipy? In-Reply-To: References: Message-ID: On Thu, Oct 15, 2015 at 3:15 PM, Matthew Einhorn wrote: > On Thu, Oct 15, 2015 at 9:16 AM, Ariel Rokem wrote: >> >> As for how to go about development: if for the time being you are the only >> person writing and merging code on mindboggle, you can either make PRs and >> merge these yourself, or merge/push to master yourself on your machine, >> without PRs. In the longer run, hopefully others will join you, and then PRs >> will be the way to go. In that stage, you will certainly still want a fork >> of the project under your user account, so that you can use the git workflow >> for PRs and so on. >> >> One way to go about creating the right structure would be to ask the >> github support team to reverse the forking relationship between >> nipy/mindboggle and binarybottle/mindboggle. They can do that kind of thing >> - I've seen it done! > > > > I'm not sure if you're aware that you can transfer a repo: > https://help.github.com/articles/transferring-a-repository/#transferring-from-a-user-to-an-organization. > Transferring to nipy would make it the "root" from which others can fork. > But you'd probably have to delete the exiting fork in nipy. Thanks, yes, that what what I was going to suggest. Cheers, Matthew From satra at mit.edu Fri Oct 16 00:36:30 2015 From: satra at mit.edu (Satrajit Ghosh) Date: Thu, 15 Oct 2015 17:36:30 -0500 Subject: [Neuroimaging] Mindboggle as part of nipy? In-Reply-To: References: Message-ID: arno: i've deleted the forked repo. if matthew has already enabled you within the nipy organization you should be able to transfer the repo to nipy. cheers, satra On Thu, Oct 15, 2015 at 5:20 PM, Matthew Brett wrote: > On Thu, Oct 15, 2015 at 3:15 PM, Matthew Einhorn > wrote: > > On Thu, Oct 15, 2015 at 9:16 AM, Ariel Rokem wrote: > >> > >> As for how to go about development: if for the time being you are the > only > >> person writing and merging code on mindboggle, you can either make PRs > and > >> merge these yourself, or merge/push to master yourself on your machine, > >> without PRs. In the longer run, hopefully others will join you, and > then PRs > >> will be the way to go. In that stage, you will certainly still want a > fork > >> of the project under your user account, so that you can use the git > workflow > >> for PRs and so on. > >> > >> One way to go about creating the right structure would be to ask the > >> github support team to reverse the forking relationship between > >> nipy/mindboggle and binarybottle/mindboggle. They can do that kind of > thing > >> - I've seen it done! > > > > > > > > I'm not sure if you're aware that you can transfer a repo: > > > https://help.github.com/articles/transferring-a-repository/#transferring-from-a-user-to-an-organization > . > > Transferring to nipy would make it the "root" from which others can fork. > > But you'd probably have to delete the exiting fork in nipy. > > Thanks, yes, that what what I was going to suggest. > > Cheers, > > Matthew > _______________________________________________ > Neuroimaging mailing list > Neuroimaging at python.org > https://mail.python.org/mailman/listinfo/neuroimaging > -------------- next part -------------- An HTML attachment was scrubbed... URL: From spilgrim at umail.iu.edu Wed Oct 14 23:21:05 2015 From: spilgrim at umail.iu.edu (Samuel Pilgrim) Date: Wed, 14 Oct 2015 17:21:05 -0400 Subject: [Neuroimaging] Reconstruction of the diffusion signal with the Tensor model after de-noising Message-ID: Neuroimaging mailing list, I'm an undergraduate experimenting with dipy and am currently working on a project that would combine a few of the examples given in the documentation. In particular, I'd like to be able to take one of the sample data-sets, apply the de-noising procedure described in the documentation under "Denoise images using Non-Local Means" and then use the tensor model to reconstruct the diffusion signal using the de-noised data. I have scripts that do each of these things separately, but when I try to do reconstruction with de-noised data, I get an alignment error on the line that reads " tenfit = tenmodel.fit(maskdata) ". I believe the issue is caused by a command in the de-noising part of the script that goes " data = data[..., 1] ". After this line, the dimension of the object data has been reduced by one, (i.e. the command print(data.shape) returns a tuple of 3 integers instead of 4. I think this is what's causing the alignment issue later, but I also can't get it to run without this line. Any assistance would be greatly appreciated. Best, Sam -------------- next part -------------- An HTML attachment was scrubbed... URL: From arokem at gmail.com Fri Oct 16 08:46:11 2015 From: arokem at gmail.com (Ariel Rokem) Date: Thu, 15 Oct 2015 23:46:11 -0700 Subject: [Neuroimaging] Reconstruction of the diffusion signal with the Tensor model after de-noising In-Reply-To: References: Message-ID: Hi Sam, You might be able to draw inspiration from the new DKI example, in which denoising is first applied: https://github.com/nipy/dipy/blob/master/doc/examples/reconst_dki.py#L124 And then a model is fit (in this case the DKI model, but the TensorModel would look very similar): https://github.com/nipy/dipy/blob/master/doc/examples/reconst_dki.py#L124 https://github.com/nipy/dipy/blob/master/doc/examples/reconst_dki.py#L145 Does that work for you? Cheers, Ariel On Wed, Oct 14, 2015 at 2:21 PM, Samuel Pilgrim wrote: > Neuroimaging mailing list, > > I'm an undergraduate experimenting with dipy and am currently working on > a project that would combine a few of the examples given in the > documentation. In particular, I'd like to be able to take one of the > sample data-sets, apply the de-noising procedure described in the > documentation under "Denoise images using Non-Local Means" and then use > the tensor model to reconstruct the diffusion signal using the de-noised > data. I have scripts that do each of these things separately, but when I > try to do reconstruction with de-noised data, I get an alignment error on > the line that reads " tenfit = tenmodel.fit(maskdata) ". I believe the > issue is caused by a command in the de-noising part of the script that goes > " data = data[..., 1] ". After this line, the dimension of the object > data has been reduced by one, (i.e. the command print(data.shape) returns a > tuple of 3 integers instead of 4. I think this is what's causing the > alignment issue later, but I also can't get it to run without this line. > Any assistance would be greatly appreciated. > > Best, > Sam > > _______________________________________________ > Neuroimaging mailing list > Neuroimaging at python.org > https://mail.python.org/mailman/listinfo/neuroimaging > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From stjeansam at gmail.com Fri Oct 16 10:24:35 2015 From: stjeansam at gmail.com (Samuel St-Jean) Date: Fri, 16 Oct 2015 10:24:35 +0200 Subject: [Neuroimaging] Reconstruction of the diffusion signal with the Tensor model after de-noising In-Reply-To: References: Message-ID: That's right, your problem comes from this line. To keep the example runnable in a reasonable time, only a single diffusion weighted volume is selected, hence why your tensor fitting does not work anymore. You can simply remove this single line and run the rest as is, that should process your 4D block on each volume separately and them you can fit the tensor model on the denoised version. I'll guess I'll add a small comment that this line is for example purposes only. 2015-10-14 23:21 GMT+02:00 Samuel Pilgrim : > Neuroimaging mailing list, > > I'm an undergraduate experimenting with dipy and am currently working on > a project that would combine a few of the examples given in the > documentation. In particular, I'd like to be able to take one of the > sample data-sets, apply the de-noising procedure described in the > documentation under "Denoise images using Non-Local Means" and then use > the tensor model to reconstruct the diffusion signal using the de-noised > data. I have scripts that do each of these things separately, but when I > try to do reconstruction with de-noised data, I get an alignment error on > the line that reads " tenfit = tenmodel.fit(maskdata) ". I believe the > issue is caused by a command in the de-noising part of the script that goes > " data = data[..., 1] ". After this line, the dimension of the object > data has been reduced by one, (i.e. the command print(data.shape) returns a > tuple of 3 integers instead of 4. I think this is what's causing the > alignment issue later, but I also can't get it to run without this line. > Any assistance would be greatly appreciated. > > Best, > Sam > > _______________________________________________ > Neuroimaging mailing list > Neuroimaging at python.org > https://mail.python.org/mailman/listinfo/neuroimaging > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From spilgrim at umail.iu.edu Fri Oct 16 15:28:22 2015 From: spilgrim at umail.iu.edu (Samuel Pilgrim) Date: Fri, 16 Oct 2015 09:28:22 -0400 Subject: [Neuroimaging] Reconstruction of the diffusion signal with the Tensor model after de-noising In-Reply-To: References: Message-ID: Ariel, Thanks a lot. I'll try that out today/tomorrow and get back to you. Best, Sam On Fri, Oct 16, 2015 at 2:46 AM, Ariel Rokem wrote: > Hi Sam, > > You might be able to draw inspiration from the new DKI example, in which > denoising is first applied: > > https://github.com/nipy/dipy/blob/master/doc/examples/reconst_dki.py#L124 > > And then a model is fit (in this case the DKI model, but the TensorModel > would look very similar): > > https://github.com/nipy/dipy/blob/master/doc/examples/reconst_dki.py#L124 > https://github.com/nipy/dipy/blob/master/doc/examples/reconst_dki.py#L145 > > Does that work for you? > > Cheers, > > Ariel > > > > On Wed, Oct 14, 2015 at 2:21 PM, Samuel Pilgrim > wrote: > >> Neuroimaging mailing list, >> >> I'm an undergraduate experimenting with dipy and am currently working on >> a project that would combine a few of the examples given in the >> documentation. In particular, I'd like to be able to take one of the >> sample data-sets, apply the de-noising procedure described in the >> documentation under "Denoise images using Non-Local Means" and then use >> the tensor model to reconstruct the diffusion signal using the de-noised >> data. I have scripts that do each of these things separately, but when I >> try to do reconstruction with de-noised data, I get an alignment error on >> the line that reads " tenfit = tenmodel.fit(maskdata) ". I believe >> the issue is caused by a command in the de-noising part of the script that >> goes " data = data[..., 1] ". After this line, the dimension of the >> object data has been reduced by one, (i.e. the command print(data.shape) >> returns a tuple of 3 integers instead of 4. I think this is what's causing >> the alignment issue later, but I also can't get it to run without this >> line. Any assistance would be greatly appreciated. >> >> Best, >> Sam >> >> _______________________________________________ >> 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: From matthew.brett at gmail.com Sat Oct 17 22:57:31 2015 From: matthew.brett at gmail.com (Matthew Brett) Date: Sat, 17 Oct 2015 13:57:31 -0700 Subject: [Neuroimaging] Upcoming nipy release In-Reply-To: References: <20150828135930.GR19455@onerussian.com> <20150925003033.GW30459@onerussian.com> <561D6041.7050703@inria.fr> Message-ID: Hi, On Tue, Oct 13, 2015 at 1:13 PM, Matthew Brett wrote: > On Tue, Oct 13, 2015 at 12:49 PM, bthirion wrote: >> I'll try to take a look for the ones I am supposed to know better. My >> todolist is a bit messy atm. Planning to release today, barring any emergencies. Would love a review of any of the pending pull requests (there are 4 new ones), but especially: https://github.com/nipy/nipy/pull/377 Cheers, Matthew From matthew.brett at gmail.com Sun Oct 18 00:33:54 2015 From: matthew.brett at gmail.com (Matthew Brett) Date: Sat, 17 Oct 2015 15:33:54 -0700 Subject: [Neuroimaging] Upcoming nipy release In-Reply-To: References: <20150828135930.GR19455@onerussian.com> <20150925003033.GW30459@onerussian.com> <561D6041.7050703@inria.fr> Message-ID: Hi, On Sat, Oct 17, 2015 at 1:57 PM, Matthew Brett wrote: > Hi, > > On Tue, Oct 13, 2015 at 1:13 PM, Matthew Brett wrote: >> On Tue, Oct 13, 2015 at 12:49 PM, bthirion wrote: >>> I'll try to take a look for the ones I am supposed to know better. My >>> todolist is a bit messy atm. > > Planning to release today, barring any emergencies. > > Would love a review of any of the pending pull requests (there are 4 > new ones), but especially: > > https://github.com/nipy/nipy/pull/377 Also - I would love some feedback on the Changelog: https://github.com/nipy/nipy/pull/378 Cheers2, Matthew From matthew.brett at gmail.com Sun Oct 18 07:20:41 2015 From: matthew.brett at gmail.com (Matthew Brett) Date: Sat, 17 Oct 2015 22:20:41 -0700 Subject: [Neuroimaging] Nipy 0.4.0, finally Message-ID: Hi, I am pleased and relieved to announce the 0.4.0 release of nipy. Here's the changelog: Abbreviated authors are: * MB - Matthew Brett * BT - Bertrand Thirion * AR - Alexis Roche * YH - Yarik Halchenko * JBP - Jean-Baptiste Poline * JT - Jonathan Taylor * 0.4.0 (Saturday 18 October 2015) * Bugfix, refactoring and compatibility release; * Full port to Python 3 using single code-base; * Various fixes for modern numpy, scipy, sympy, nibabel compatibility; * Refactor space-time realignment (AR); * Change in interface for slice-timing options in space-time realign (AR+MB); * New ``nipy_4d_realign`` script to run space-time realign (Ariel Rokem); * Drop requirement for BLAS / LAPACK external library at build-time (AR); * Move much code out of nipy.labs into main tree (AR, BT); * Deprecate remaining code in nipy.labs (AR, BT); * Updates to landmark learning code including API (BT); * Various fixes to design matrix machinery (BT, Michael Waskom); * Fix to two-sample permutation test suggested by github user jwirsich (BF); * Refactoring and fixes to design matrix drift calculations (JBP); * Extending API of resampling code to allow more ndimage kwargs (JBP); * Start of new example on OpenFMRI ds105 dataset (JT); * New ``block_design`` function for designs with specified onsets (JT); * New ``show_contrast`` function for reviewing contrasts (JT); * Fix for bug in ``nipy_diagnose`` script / ``screens`` module giving incorrect PCA output; * Added SPM HRF to other HRF options; * Redesign concept of an image "space" with new image space modules, functions, classes; * Various fixes for correct installation provided or suggested by YH; * Some visualization changes by Elvis Dohmatob; The latest source and wheels should be up on pypi in in : https://pypi.python.org/pypi/nipy Thanks to everyone who contributed to this release: Alexis Roche Bertrand Thirion Ariel Rokem Elvis Dohmatob Jean-Baptiste Poline Yaroslav Halchenko Jonathan Taylor Ben Cipollini Gael Varoquaux Fabian Pedregosa Endolith Michael Waskom And of course - your noble selves for discussion and advice, Cheers, Matthew From satra at mit.edu Sun Oct 18 16:57:22 2015 From: satra at mit.edu (Satrajit Ghosh) Date: Sun, 18 Oct 2015 09:57:22 -0500 Subject: [Neuroimaging] Nipy 0.4.0, finally In-Reply-To: References: Message-ID: congratulations! cheers, satra On Sun, Oct 18, 2015 at 12:20 AM, Matthew Brett wrote: > Hi, > > I am pleased and relieved to announce the 0.4.0 release of nipy. > > Here's the changelog: > > Abbreviated authors are: > > * MB - Matthew Brett > * BT - Bertrand Thirion > * AR - Alexis Roche > * YH - Yarik Halchenko > * JBP - Jean-Baptiste Poline > * JT - Jonathan Taylor > > * 0.4.0 (Saturday 18 October 2015) > > * Bugfix, refactoring and compatibility release; > * Full port to Python 3 using single code-base; > * Various fixes for modern numpy, scipy, sympy, nibabel compatibility; > * Refactor space-time realignment (AR); > * Change in interface for slice-timing options in space-time realign > (AR+MB); > * New ``nipy_4d_realign`` script to run space-time realign (Ariel Rokem); > * Drop requirement for BLAS / LAPACK external library at build-time (AR); > * Move much code out of nipy.labs into main tree (AR, BT); > * Deprecate remaining code in nipy.labs (AR, BT); > * Updates to landmark learning code including API (BT); > * Various fixes to design matrix machinery (BT, Michael Waskom); > * Fix to two-sample permutation test suggested by github user jwirsich > (BF); > * Refactoring and fixes to design matrix drift calculations (JBP); > * Extending API of resampling code to allow more ndimage kwargs (JBP); > * Start of new example on OpenFMRI ds105 dataset (JT); > * New ``block_design`` function for designs with specified onsets (JT); > * New ``show_contrast`` function for reviewing contrasts (JT); > * Fix for bug in ``nipy_diagnose`` script / ``screens`` module giving > incorrect PCA output; > * Added SPM HRF to other HRF options; > * Redesign concept of an image "space" with new image space modules, > functions, classes; > * Various fixes for correct installation provided or suggested by YH; > * Some visualization changes by Elvis Dohmatob; > > The latest source and wheels should be up on pypi in in : > > https://pypi.python.org/pypi/nipy > > Thanks to everyone who contributed to this release: > > Alexis Roche > Bertrand Thirion > Ariel Rokem > Elvis Dohmatob > Jean-Baptiste Poline > Yaroslav Halchenko > Jonathan Taylor > Ben Cipollini > Gael Varoquaux > Fabian Pedregosa > Endolith > Michael Waskom > > And of course - your noble selves for discussion and advice, > > Cheers, > > Matthew > _______________________________________________ > Neuroimaging mailing list > Neuroimaging at python.org > https://mail.python.org/mailman/listinfo/neuroimaging > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bcipolli at ucsd.edu Sun Oct 18 17:04:15 2015 From: bcipolli at ucsd.edu (Ben Cipollini) Date: Sun, 18 Oct 2015 10:04:15 -0500 Subject: [Neuroimaging] Nipy 0.4.0, finally In-Reply-To: References: Message-ID: Yes, great to see. Thanks for driving that forward @matthew-brett ! Ben On Sun, Oct 18, 2015 at 12:20 AM, Matthew Brett wrote: > Hi, > > I am pleased and relieved to announce the 0.4.0 release of nipy. > > Here's the changelog: > > Abbreviated authors are: > > * MB - Matthew Brett > * BT - Bertrand Thirion > * AR - Alexis Roche > * YH - Yarik Halchenko > * JBP - Jean-Baptiste Poline > * JT - Jonathan Taylor > > * 0.4.0 (Saturday 18 October 2015) > > * Bugfix, refactoring and compatibility release; > * Full port to Python 3 using single code-base; > * Various fixes for modern numpy, scipy, sympy, nibabel compatibility; > * Refactor space-time realignment (AR); > * Change in interface for slice-timing options in space-time realign > (AR+MB); > * New ``nipy_4d_realign`` script to run space-time realign (Ariel Rokem); > * Drop requirement for BLAS / LAPACK external library at build-time (AR); > * Move much code out of nipy.labs into main tree (AR, BT); > * Deprecate remaining code in nipy.labs (AR, BT); > * Updates to landmark learning code including API (BT); > * Various fixes to design matrix machinery (BT, Michael Waskom); > * Fix to two-sample permutation test suggested by github user jwirsich > (BF); > * Refactoring and fixes to design matrix drift calculations (JBP); > * Extending API of resampling code to allow more ndimage kwargs (JBP); > * Start of new example on OpenFMRI ds105 dataset (JT); > * New ``block_design`` function for designs with specified onsets (JT); > * New ``show_contrast`` function for reviewing contrasts (JT); > * Fix for bug in ``nipy_diagnose`` script / ``screens`` module giving > incorrect PCA output; > * Added SPM HRF to other HRF options; > * Redesign concept of an image "space" with new image space modules, > functions, classes; > * Various fixes for correct installation provided or suggested by YH; > * Some visualization changes by Elvis Dohmatob; > > The latest source and wheels should be up on pypi in in : > > https://pypi.python.org/pypi/nipy > > Thanks to everyone who contributed to this release: > > Alexis Roche > Bertrand Thirion > Ariel Rokem > Elvis Dohmatob > Jean-Baptiste Poline > Yaroslav Halchenko > Jonathan Taylor > Ben Cipollini > Gael Varoquaux > Fabian Pedregosa > Endolith > Michael Waskom > > And of course - your noble selves for discussion and advice, > > Cheers, > > Matthew > _______________________________________________ > Neuroimaging mailing list > Neuroimaging at python.org > https://mail.python.org/mailman/listinfo/neuroimaging > -------------- next part -------------- An HTML attachment was scrubbed... URL: From krzysztof.gorgolewski at gmail.com Sun Oct 18 19:15:53 2015 From: krzysztof.gorgolewski at gmail.com (Chris Filo Gorgolewski) Date: Sun, 18 Oct 2015 12:15:53 -0500 Subject: [Neuroimaging] Nipy 0.4.0, finally In-Reply-To: References: Message-ID: Well done everyone! On Oct 18, 2015 00:21, "Matthew Brett" wrote: > Hi, > > I am pleased and relieved to announce the 0.4.0 release of nipy. > > Here's the changelog: > > Abbreviated authors are: > > * MB - Matthew Brett > * BT - Bertrand Thirion > * AR - Alexis Roche > * YH - Yarik Halchenko > * JBP - Jean-Baptiste Poline > * JT - Jonathan Taylor > > * 0.4.0 (Saturday 18 October 2015) > > * Bugfix, refactoring and compatibility release; > * Full port to Python 3 using single code-base; > * Various fixes for modern numpy, scipy, sympy, nibabel compatibility; > * Refactor space-time realignment (AR); > * Change in interface for slice-timing options in space-time realign > (AR+MB); > * New ``nipy_4d_realign`` script to run space-time realign (Ariel Rokem); > * Drop requirement for BLAS / LAPACK external library at build-time (AR); > * Move much code out of nipy.labs into main tree (AR, BT); > * Deprecate remaining code in nipy.labs (AR, BT); > * Updates to landmark learning code including API (BT); > * Various fixes to design matrix machinery (BT, Michael Waskom); > * Fix to two-sample permutation test suggested by github user jwirsich > (BF); > * Refactoring and fixes to design matrix drift calculations (JBP); > * Extending API of resampling code to allow more ndimage kwargs (JBP); > * Start of new example on OpenFMRI ds105 dataset (JT); > * New ``block_design`` function for designs with specified onsets (JT); > * New ``show_contrast`` function for reviewing contrasts (JT); > * Fix for bug in ``nipy_diagnose`` script / ``screens`` module giving > incorrect PCA output; > * Added SPM HRF to other HRF options; > * Redesign concept of an image "space" with new image space modules, > functions, classes; > * Various fixes for correct installation provided or suggested by YH; > * Some visualization changes by Elvis Dohmatob; > > The latest source and wheels should be up on pypi in in : > > https://pypi.python.org/pypi/nipy > > Thanks to everyone who contributed to this release: > > Alexis Roche > Bertrand Thirion > Ariel Rokem > Elvis Dohmatob > Jean-Baptiste Poline > Yaroslav Halchenko > Jonathan Taylor > Ben Cipollini > Gael Varoquaux > Fabian Pedregosa > Endolith > Michael Waskom > > And of course - your noble selves for discussion and advice, > > Cheers, > > Matthew > _______________________________________________ > Neuroimaging mailing list > Neuroimaging at python.org > https://mail.python.org/mailman/listinfo/neuroimaging > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bertrand.thirion at inria.fr Sun Oct 18 20:06:46 2015 From: bertrand.thirion at inria.fr (bthirion) Date: Sun, 18 Oct 2015 20:06:46 +0200 Subject: [Neuroimaging] Nipy 0.4.0, finally In-Reply-To: References: Message-ID: <5623DFB6.1020908@inria.fr> Hi Matthew, Thank you for this last release. Best, Bertrand On 18/10/2015 07:20, Matthew Brett wrote: > Hi, > > I am pleased and relieved to announce the 0.4.0 release of nipy. > > Here's the changelog: > > Abbreviated authors are: > > * MB - Matthew Brett > * BT - Bertrand Thirion > * AR - Alexis Roche > * YH - Yarik Halchenko > * JBP - Jean-Baptiste Poline > * JT - Jonathan Taylor > > * 0.4.0 (Saturday 18 October 2015) > > * Bugfix, refactoring and compatibility release; > * Full port to Python 3 using single code-base; > * Various fixes for modern numpy, scipy, sympy, nibabel compatibility; > * Refactor space-time realignment (AR); > * Change in interface for slice-timing options in space-time realign > (AR+MB); > * New ``nipy_4d_realign`` script to run space-time realign (Ariel Rokem); > * Drop requirement for BLAS / LAPACK external library at build-time (AR); > * Move much code out of nipy.labs into main tree (AR, BT); > * Deprecate remaining code in nipy.labs (AR, BT); > * Updates to landmark learning code including API (BT); > * Various fixes to design matrix machinery (BT, Michael Waskom); > * Fix to two-sample permutation test suggested by github user jwirsich (BF); > * Refactoring and fixes to design matrix drift calculations (JBP); > * Extending API of resampling code to allow more ndimage kwargs (JBP); > * Start of new example on OpenFMRI ds105 dataset (JT); > * New ``block_design`` function for designs with specified onsets (JT); > * New ``show_contrast`` function for reviewing contrasts (JT); > * Fix for bug in ``nipy_diagnose`` script / ``screens`` module giving > incorrect PCA output; > * Added SPM HRF to other HRF options; > * Redesign concept of an image "space" with new image space modules, > functions, classes; > * Various fixes for correct installation provided or suggested by YH; > * Some visualization changes by Elvis Dohmatob; > > The latest source and wheels should be up on pypi in in : > > https://pypi.python.org/pypi/nipy > > Thanks to everyone who contributed to this release: > > Alexis Roche > Bertrand Thirion > Ariel Rokem > Elvis Dohmatob > Jean-Baptiste Poline > Yaroslav Halchenko > Jonathan Taylor > Ben Cipollini > Gael Varoquaux > Fabian Pedregosa > Endolith > Michael Waskom > > And of course - your noble selves for discussion and advice, > > Cheers, > > Matthew > _______________________________________________ > Neuroimaging mailing list > Neuroimaging at python.org > https://mail.python.org/mailman/listinfo/neuroimaging From garyfallidis at gmail.com Sun Oct 18 23:25:34 2015 From: garyfallidis at gmail.com (Eleftherios Garyfallidis) Date: Sun, 18 Oct 2015 17:25:34 -0400 Subject: [Neuroimaging] Nipy 0.4.0, finally In-Reply-To: <5623DFB6.1020908@inria.fr> References: <5623DFB6.1020908@inria.fr> Message-ID: Keep it up guys! Good job! :) On Sun, Oct 18, 2015 at 2:06 PM, bthirion wrote: > Hi Matthew, > > Thank you for this last release. > Best, > > Bertrand > > > On 18/10/2015 07:20, Matthew Brett wrote: > >> Hi, >> >> I am pleased and relieved to announce the 0.4.0 release of nipy. >> >> Here's the changelog: >> >> Abbreviated authors are: >> >> * MB - Matthew Brett >> * BT - Bertrand Thirion >> * AR - Alexis Roche >> * YH - Yarik Halchenko >> * JBP - Jean-Baptiste Poline >> * JT - Jonathan Taylor >> >> * 0.4.0 (Saturday 18 October 2015) >> >> * Bugfix, refactoring and compatibility release; >> * Full port to Python 3 using single code-base; >> * Various fixes for modern numpy, scipy, sympy, nibabel compatibility; >> * Refactor space-time realignment (AR); >> * Change in interface for slice-timing options in space-time realign >> (AR+MB); >> * New ``nipy_4d_realign`` script to run space-time realign (Ariel >> Rokem); >> * Drop requirement for BLAS / LAPACK external library at build-time >> (AR); >> * Move much code out of nipy.labs into main tree (AR, BT); >> * Deprecate remaining code in nipy.labs (AR, BT); >> * Updates to landmark learning code including API (BT); >> * Various fixes to design matrix machinery (BT, Michael Waskom); >> * Fix to two-sample permutation test suggested by github user jwirsich >> (BF); >> * Refactoring and fixes to design matrix drift calculations (JBP); >> * Extending API of resampling code to allow more ndimage kwargs (JBP); >> * Start of new example on OpenFMRI ds105 dataset (JT); >> * New ``block_design`` function for designs with specified onsets (JT); >> * New ``show_contrast`` function for reviewing contrasts (JT); >> * Fix for bug in ``nipy_diagnose`` script / ``screens`` module giving >> incorrect PCA output; >> * Added SPM HRF to other HRF options; >> * Redesign concept of an image "space" with new image space modules, >> functions, classes; >> * Various fixes for correct installation provided or suggested by YH; >> * Some visualization changes by Elvis Dohmatob; >> >> The latest source and wheels should be up on pypi in in : >> >> https://pypi.python.org/pypi/nipy >> >> Thanks to everyone who contributed to this release: >> >> Alexis Roche >> Bertrand Thirion >> Ariel Rokem >> Elvis Dohmatob >> Jean-Baptiste Poline >> Yaroslav Halchenko >> Jonathan Taylor >> Ben Cipollini >> Gael Varoquaux >> Fabian Pedregosa >> Endolith >> Michael Waskom >> >> And of course - your noble selves for discussion and advice, >> >> Cheers, >> >> Matthew >> _______________________________________________ >> 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: From charest.ian at gmail.com Mon Oct 19 07:55:36 2015 From: charest.ian at gmail.com (Ian Charest) Date: Mon, 19 Oct 2015 05:55:36 +0000 Subject: [Neuroimaging] Nipy 0.4.0, finally In-Reply-To: References: <5623DFB6.1020908@inria.fr> Message-ID: Congratulations! On Sun, 18 Oct 2015 22:25 Eleftherios Garyfallidis wrote: > Keep it up guys! Good job! :) > > On Sun, Oct 18, 2015 at 2:06 PM, bthirion > wrote: > >> Hi Matthew, >> >> Thank you for this last release. >> Best, >> >> Bertrand >> >> >> On 18/10/2015 07:20, Matthew Brett wrote: >> >>> Hi, >>> >>> I am pleased and relieved to announce the 0.4.0 release of nipy. >>> >>> Here's the changelog: >>> >>> Abbreviated authors are: >>> >>> * MB - Matthew Brett >>> * BT - Bertrand Thirion >>> * AR - Alexis Roche >>> * YH - Yarik Halchenko >>> * JBP - Jean-Baptiste Poline >>> * JT - Jonathan Taylor >>> >>> * 0.4.0 (Saturday 18 October 2015) >>> >>> * Bugfix, refactoring and compatibility release; >>> * Full port to Python 3 using single code-base; >>> * Various fixes for modern numpy, scipy, sympy, nibabel compatibility; >>> * Refactor space-time realignment (AR); >>> * Change in interface for slice-timing options in space-time realign >>> (AR+MB); >>> * New ``nipy_4d_realign`` script to run space-time realign (Ariel >>> Rokem); >>> * Drop requirement for BLAS / LAPACK external library at build-time >>> (AR); >>> * Move much code out of nipy.labs into main tree (AR, BT); >>> * Deprecate remaining code in nipy.labs (AR, BT); >>> * Updates to landmark learning code including API (BT); >>> * Various fixes to design matrix machinery (BT, Michael Waskom); >>> * Fix to two-sample permutation test suggested by github user >>> jwirsich (BF); >>> * Refactoring and fixes to design matrix drift calculations (JBP); >>> * Extending API of resampling code to allow more ndimage kwargs (JBP); >>> * Start of new example on OpenFMRI ds105 dataset (JT); >>> * New ``block_design`` function for designs with specified onsets >>> (JT); >>> * New ``show_contrast`` function for reviewing contrasts (JT); >>> * Fix for bug in ``nipy_diagnose`` script / ``screens`` module giving >>> incorrect PCA output; >>> * Added SPM HRF to other HRF options; >>> * Redesign concept of an image "space" with new image space modules, >>> functions, classes; >>> * Various fixes for correct installation provided or suggested by YH; >>> * Some visualization changes by Elvis Dohmatob; >>> >>> The latest source and wheels should be up on pypi in in : >>> >>> https://pypi.python.org/pypi/nipy >>> >>> Thanks to everyone who contributed to this release: >>> >>> Alexis Roche >>> Bertrand Thirion >>> Ariel Rokem >>> Elvis Dohmatob >>> Jean-Baptiste Poline >>> Yaroslav Halchenko >>> Jonathan Taylor >>> Ben Cipollini >>> Gael Varoquaux >>> Fabian Pedregosa >>> Endolith >>> Michael Waskom >>> >>> And of course - your noble selves for discussion and advice, >>> >>> Cheers, >>> >>> Matthew >>> _______________________________________________ >>> 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 >> > > _______________________________________________ > Neuroimaging mailing list > Neuroimaging at python.org > https://mail.python.org/mailman/listinfo/neuroimaging > -------------- next part -------------- An HTML attachment was scrubbed... URL: From pellman.john at gmail.com Tue Oct 20 15:36:23 2015 From: pellman.john at gmail.com (John Pellman) Date: Tue, 20 Oct 2015 09:36:23 -0400 Subject: [Neuroimaging] Nipype at Pycon India Message-ID: Looks like y'all have a fan. :) https://www.youtube.com/watch?v=dOWVKtZynas -------------- next part -------------- An HTML attachment was scrubbed... URL: From garyfallidis at gmail.com Tue Oct 20 15:38:03 2015 From: garyfallidis at gmail.com (Eleftherios Garyfallidis) Date: Tue, 20 Oct 2015 09:38:03 -0400 Subject: [Neuroimaging] Nipype at Pycon India In-Reply-To: References: Message-ID: :) On Tue, Oct 20, 2015 at 9:36 AM, John Pellman wrote: > Looks like y'all have a fan. :) > > https://www.youtube.com/watch?v=dOWVKtZynas > > _______________________________________________ > Neuroimaging mailing list > Neuroimaging at python.org > https://mail.python.org/mailman/listinfo/neuroimaging > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From satra at mit.edu Tue Oct 20 15:45:13 2015 From: satra at mit.edu (Satrajit Ghosh) Date: Tue, 20 Oct 2015 09:45:13 -0400 Subject: [Neuroimaging] Nipype at Pycon India In-Reply-To: References: Message-ID: thanks for sharing! cheers, satra On Tue, Oct 20, 2015 at 9:36 AM, John Pellman wrote: > Looks like y'all have a fan. :) > > https://www.youtube.com/watch?v=dOWVKtZynas > > _______________________________________________ > Neuroimaging mailing list > Neuroimaging at python.org > https://mail.python.org/mailman/listinfo/neuroimaging > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From garyfallidis at gmail.com Mon Oct 26 15:34:20 2015 From: garyfallidis at gmail.com (Eleftherios Garyfallidis) Date: Mon, 26 Oct 2015 15:34:20 -0400 Subject: [Neuroimaging] Site Contributions In-Reply-To: References: Message-ID: Hi Vanessa and all, Would it be possible to switch to your much nicer new website? I still see the older version being up. Do you have a plan for this? Or you waiting for some feedback on our side? Best regards, Eleftherios On Wed, Sep 2, 2015 at 12:57 PM, Ben Cipollini wrote: > I think they're good for mobile sites. I think they're generally expanded > by default on full screens, and compacted on mobile. So I suggest to keep > it, but have a regular menu that's showing on full screens and hidden on > mobile. > > On Wed, Sep 2, 2015 at 9:51 AM, vanessa sochat > wrote: > >> That's a good suggestion, and I'll add as an issue so I can find it >> easily when the next round of changes comes around. Generally, these >> "hamburger" menu things are useless functionality wise, and only serve to >> aesthetically "get rid of the navigation" to have a clean looking site. In >> our case, it is probably just annoying to have the extra clicks. >> >> On Wed, Sep 2, 2015 at 8:50 AM, Ben Cipollini wrote: >> >>> This looks great. It's also cool to see "ask a question" integrated into >>> the website, though we'll still have to hash things out for that. >>> >>> Rather than open a github issue (which few may see), I'll make a >>> suggestion here: can we have the menu expanded by default when accessing >>> via a full-size screen? >>> >>> It feels odd to me to have to expand the menu in order to navigate >>> anywhere, by default. To me, navigation options should be obvious, unless >>> pressed for space. >>> >>> >>> >>> On Sun, Aug 30, 2015 at 1:14 PM, vanessa sochat >>> wrote: >>> >>>> Hi Everyone, >>>> >>>> I've finished work on the "contribute" page with my thinking for how to >>>> contribute various content: >>>> >>>> http://vsoch.github.io/nipy-jekyll/contribute.html >>>> >>>> and as an example, put up a quick blog post: >>>> >>>> http://neuroimaging.tumblr.com/ >>>> >>>> The old "example" blog posts are hidden (private) and can be viewed if >>>> you are a contributor. I'd like to add anyone and everyone interested to >>>> contribute as "official" contributors via tumblr - if you are interested >>>> please send me your email address. I've already invited some of you for >>>> which I know the email. >>>> >>>> Best, >>>> >>>> Vanessa >>>> >>>> >>>> -- >>>> Vanessa Villamia Sochat >>>> Stanford University >>>> (603) 321-0676 >>>> >>>> _______________________________________________ >>>> 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 >>> >>> >> >> >> -- >> Vanessa Villamia Sochat >> Stanford University >> (603) 321-0676 >> >> _______________________________________________ >> 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: From vsochat at stanford.edu Mon Oct 26 15:56:55 2015 From: vsochat at stanford.edu (vanessa sochat) Date: Mon, 26 Oct 2015 12:56:55 -0700 Subject: [Neuroimaging] Site Contributions In-Reply-To: References: Message-ID: Hi Eleftherios, It definitely would be possible! I'm not any sort of admin in the nipy space, so the farthest I could take it is having the repo for someone to deploy on nipy.github.io. The code is here: https://github.com/vsoch/nipy-jekyll and deployment on my github pages: http://vsoch.github.io/nipy-jekyll/ I mostly stopped working on it because I accomplished all the things that I set out to do (jekyll site, preview on continuous integration with circle, standard ways to add new content, and an easy way to multiple ways to add content a la github , or for those who aren't comfortable with pushing and pulling, la social media ). I think I had suggested moving forward for people to try out tumblr (and start contributing content!), and if people were happy, to move it over to the nipy repo. If the outcome of the work was not a desired solution, I was content to just let it be. However if there is interest, that is definitely still a possibility. Best, Vanessa On Mon, Oct 26, 2015 at 12:34 PM, Eleftherios Garyfallidis < garyfallidis at gmail.com> wrote: > Hi Vanessa and all, > > Would it be possible to switch to your much nicer new website? I still see > the older version being up. > > Do you have a plan for this? Or you waiting for some feedback on our side? > > Best regards, > Eleftherios > > On Wed, Sep 2, 2015 at 12:57 PM, Ben Cipollini wrote: > >> I think they're good for mobile sites. I think they're generally expanded >> by default on full screens, and compacted on mobile. So I suggest to keep >> it, but have a regular menu that's showing on full screens and hidden on >> mobile. >> >> On Wed, Sep 2, 2015 at 9:51 AM, vanessa sochat >> wrote: >> >>> That's a good suggestion, and I'll add as an issue so I can find it >>> easily when the next round of changes comes around. Generally, these >>> "hamburger" menu things are useless functionality wise, and only serve to >>> aesthetically "get rid of the navigation" to have a clean looking site. In >>> our case, it is probably just annoying to have the extra clicks. >>> >>> On Wed, Sep 2, 2015 at 8:50 AM, Ben Cipollini wrote: >>> >>>> This looks great. It's also cool to see "ask a question" integrated >>>> into the website, though we'll still have to hash things out for that. >>>> >>>> Rather than open a github issue (which few may see), I'll make a >>>> suggestion here: can we have the menu expanded by default when accessing >>>> via a full-size screen? >>>> >>>> It feels odd to me to have to expand the menu in order to navigate >>>> anywhere, by default. To me, navigation options should be obvious, unless >>>> pressed for space. >>>> >>>> >>>> >>>> On Sun, Aug 30, 2015 at 1:14 PM, vanessa sochat >>>> wrote: >>>> >>>>> Hi Everyone, >>>>> >>>>> I've finished work on the "contribute" page with my thinking for how >>>>> to contribute various content: >>>>> >>>>> http://vsoch.github.io/nipy-jekyll/contribute.html >>>>> >>>>> and as an example, put up a quick blog post: >>>>> >>>>> http://neuroimaging.tumblr.com/ >>>>> >>>>> The old "example" blog posts are hidden (private) and can be viewed if >>>>> you are a contributor. I'd like to add anyone and everyone interested to >>>>> contribute as "official" contributors via tumblr - if you are interested >>>>> please send me your email address. I've already invited some of you for >>>>> which I know the email. >>>>> >>>>> Best, >>>>> >>>>> Vanessa >>>>> >>>>> >>>>> -- >>>>> Vanessa Villamia Sochat >>>>> Stanford University >>>>> (603) 321-0676 >>>>> >>>>> _______________________________________________ >>>>> 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 >>>> >>>> >>> >>> >>> -- >>> Vanessa Villamia Sochat >>> Stanford University >>> (603) 321-0676 >>> >>> _______________________________________________ >>> 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 >> >> > > _______________________________________________ > Neuroimaging mailing list > Neuroimaging at python.org > https://mail.python.org/mailman/listinfo/neuroimaging > > -- Vanessa Villamia Sochat Stanford University (603) 321-0676 -------------- next part -------------- An HTML attachment was scrubbed... URL: From arokem at gmail.com Tue Oct 27 09:40:08 2015 From: arokem at gmail.com (Ariel Rokem) Date: Tue, 27 Oct 2015 06:40:08 -0700 Subject: [Neuroimaging] Site Contributions In-Reply-To: References: Message-ID: Hi Vanessa, I have a few comments/suggestions: 1. I would rather not have the front page be the project directory. In my opinion, the front page should instead explain briefly what this is, and lead visitors to the various other parts of the website. 2. There are a few issues with formatting in the Code of Conduct page (bullet points appear as continued lines) Other than these two, I think this is ready to be introduced as a PR against the nipy/nipy.github.com repository (you don't need any admin rights to do that, but I also just added you to "team blog" on the github nipy org, so you can even do the merge yourself, if you want). Cheers, Ariel On Mon, Oct 26, 2015 at 12:56 PM, vanessa sochat wrote: > Hi Eleftherios, > > It definitely would be possible! I'm not any sort of admin in the nipy > space, so the farthest I could take it is having the repo for someone to > deploy on nipy.github.io. The code is here: > > https://github.com/vsoch/nipy-jekyll > > and deployment on my github pages: > > http://vsoch.github.io/nipy-jekyll/ > > I mostly stopped working on it because I accomplished all the things that > I set out to do (jekyll site, preview on continuous integration with > circle, standard ways to add new content, and an easy way to multiple > ways to add content a la github > , or for those who > aren't comfortable with pushing and pulling, la social media > ). I think I had suggested moving forward > for people to try out tumblr (and start contributing content!), and if > people were happy, to move it over to the nipy repo. If the outcome of the > work was not a desired solution, I was content to just let it be. However > if there is interest, that is definitely still a possibility. > > Best, > > Vanessa > > > > On Mon, Oct 26, 2015 at 12:34 PM, Eleftherios Garyfallidis < > garyfallidis at gmail.com> wrote: > >> Hi Vanessa and all, >> >> Would it be possible to switch to your much nicer new website? I still >> see the older version being up. >> >> Do you have a plan for this? Or you waiting for some feedback on our side? >> >> Best regards, >> Eleftherios >> >> On Wed, Sep 2, 2015 at 12:57 PM, Ben Cipollini wrote: >> >>> I think they're good for mobile sites. I think they're generally >>> expanded by default on full screens, and compacted on mobile. So I suggest >>> to keep it, but have a regular menu that's showing on full screens and >>> hidden on mobile. >>> >>> On Wed, Sep 2, 2015 at 9:51 AM, vanessa sochat >>> wrote: >>> >>>> That's a good suggestion, and I'll add as an issue so I can find it >>>> easily when the next round of changes comes around. Generally, these >>>> "hamburger" menu things are useless functionality wise, and only serve to >>>> aesthetically "get rid of the navigation" to have a clean looking site. In >>>> our case, it is probably just annoying to have the extra clicks. >>>> >>>> On Wed, Sep 2, 2015 at 8:50 AM, Ben Cipollini >>>> wrote: >>>> >>>>> This looks great. It's also cool to see "ask a question" integrated >>>>> into the website, though we'll still have to hash things out for that. >>>>> >>>>> Rather than open a github issue (which few may see), I'll make a >>>>> suggestion here: can we have the menu expanded by default when accessing >>>>> via a full-size screen? >>>>> >>>>> It feels odd to me to have to expand the menu in order to navigate >>>>> anywhere, by default. To me, navigation options should be obvious, unless >>>>> pressed for space. >>>>> >>>>> >>>>> >>>>> On Sun, Aug 30, 2015 at 1:14 PM, vanessa sochat >>>>> wrote: >>>>> >>>>>> Hi Everyone, >>>>>> >>>>>> I've finished work on the "contribute" page with my thinking for how >>>>>> to contribute various content: >>>>>> >>>>>> http://vsoch.github.io/nipy-jekyll/contribute.html >>>>>> >>>>>> and as an example, put up a quick blog post: >>>>>> >>>>>> http://neuroimaging.tumblr.com/ >>>>>> >>>>>> The old "example" blog posts are hidden (private) and can be viewed >>>>>> if you are a contributor. I'd like to add anyone and everyone interested to >>>>>> contribute as "official" contributors via tumblr - if you are interested >>>>>> please send me your email address. I've already invited some of you for >>>>>> which I know the email. >>>>>> >>>>>> Best, >>>>>> >>>>>> Vanessa >>>>>> >>>>>> >>>>>> -- >>>>>> Vanessa Villamia Sochat >>>>>> Stanford University >>>>>> (603) 321-0676 >>>>>> >>>>>> _______________________________________________ >>>>>> 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 >>>>> >>>>> >>>> >>>> >>>> -- >>>> Vanessa Villamia Sochat >>>> Stanford University >>>> (603) 321-0676 >>>> >>>> _______________________________________________ >>>> 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 >>> >>> >> >> _______________________________________________ >> Neuroimaging mailing list >> Neuroimaging at python.org >> https://mail.python.org/mailman/listinfo/neuroimaging >> >> > > > -- > Vanessa Villamia Sochat > Stanford University > (603) 321-0676 > > _______________________________________________ > Neuroimaging mailing list > Neuroimaging at python.org > https://mail.python.org/mailman/listinfo/neuroimaging > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From arokem at gmail.com Tue Oct 27 09:48:15 2015 From: arokem at gmail.com (Ariel Rokem) Date: Tue, 27 Oct 2015 06:48:15 -0700 Subject: [Neuroimaging] Site Contributions In-Reply-To: References: Message-ID: Oh, one more: On Tue, Oct 27, 2015 at 6:40 AM, Ariel Rokem wrote: > Hi Vanessa, > > I have a few comments/suggestions: > > 1. I would rather not have the front page be the project directory. In my > opinion, the front page should instead explain briefly what this is, and > lead visitors to the various other parts of the website. > > 2. There are a few issues with formatting in the Code of Conduct page > (bullet points appear as continued lines) > 3. Please include mindboggle in the project directory (it's been recently added!). > Other than these two, I think this is ready to be introduced as a PR > against the nipy/nipy.github.com repository (you don't need any admin > rights to do that, but I also just added you to "team blog" on the github > nipy org, so you can even do the merge yourself, if you want). > > Cheers, > > Ariel > > On Mon, Oct 26, 2015 at 12:56 PM, vanessa sochat > wrote: > >> Hi Eleftherios, >> >> It definitely would be possible! I'm not any sort of admin in the nipy >> space, so the farthest I could take it is having the repo for someone to >> deploy on nipy.github.io. The code is here: >> >> https://github.com/vsoch/nipy-jekyll >> >> and deployment on my github pages: >> >> http://vsoch.github.io/nipy-jekyll/ >> >> I mostly stopped working on it because I accomplished all the things that >> I set out to do (jekyll site, preview on continuous integration with >> circle, standard ways to add new content, and an easy way to multiple >> ways to add content a la github >> , or for those who >> aren't comfortable with pushing and pulling, la social media >> ). I think I had suggested moving >> forward for people to try out tumblr (and start contributing content!), and >> if people were happy, to move it over to the nipy repo. If the outcome of >> the work was not a desired solution, I was content to just let it be. >> However if there is interest, that is definitely still a possibility. >> >> Best, >> >> Vanessa >> >> >> >> On Mon, Oct 26, 2015 at 12:34 PM, Eleftherios Garyfallidis < >> garyfallidis at gmail.com> wrote: >> >>> Hi Vanessa and all, >>> >>> Would it be possible to switch to your much nicer new website? I still >>> see the older version being up. >>> >>> Do you have a plan for this? Or you waiting for some feedback on our >>> side? >>> >>> Best regards, >>> Eleftherios >>> >>> On Wed, Sep 2, 2015 at 12:57 PM, Ben Cipollini >>> wrote: >>> >>>> I think they're good for mobile sites. I think they're generally >>>> expanded by default on full screens, and compacted on mobile. So I suggest >>>> to keep it, but have a regular menu that's showing on full screens and >>>> hidden on mobile. >>>> >>>> On Wed, Sep 2, 2015 at 9:51 AM, vanessa sochat >>>> wrote: >>>> >>>>> That's a good suggestion, and I'll add as an issue so I can find it >>>>> easily when the next round of changes comes around. Generally, these >>>>> "hamburger" menu things are useless functionality wise, and only serve to >>>>> aesthetically "get rid of the navigation" to have a clean looking site. In >>>>> our case, it is probably just annoying to have the extra clicks. >>>>> >>>>> On Wed, Sep 2, 2015 at 8:50 AM, Ben Cipollini >>>>> wrote: >>>>> >>>>>> This looks great. It's also cool to see "ask a question" integrated >>>>>> into the website, though we'll still have to hash things out for that. >>>>>> >>>>>> Rather than open a github issue (which few may see), I'll make a >>>>>> suggestion here: can we have the menu expanded by default when accessing >>>>>> via a full-size screen? >>>>>> >>>>>> It feels odd to me to have to expand the menu in order to navigate >>>>>> anywhere, by default. To me, navigation options should be obvious, unless >>>>>> pressed for space. >>>>>> >>>>>> >>>>>> >>>>>> On Sun, Aug 30, 2015 at 1:14 PM, vanessa sochat >>>>> > wrote: >>>>>> >>>>>>> Hi Everyone, >>>>>>> >>>>>>> I've finished work on the "contribute" page with my thinking for how >>>>>>> to contribute various content: >>>>>>> >>>>>>> http://vsoch.github.io/nipy-jekyll/contribute.html >>>>>>> >>>>>>> and as an example, put up a quick blog post: >>>>>>> >>>>>>> http://neuroimaging.tumblr.com/ >>>>>>> >>>>>>> The old "example" blog posts are hidden (private) and can be viewed >>>>>>> if you are a contributor. I'd like to add anyone and everyone interested to >>>>>>> contribute as "official" contributors via tumblr - if you are interested >>>>>>> please send me your email address. I've already invited some of you for >>>>>>> which I know the email. >>>>>>> >>>>>>> Best, >>>>>>> >>>>>>> Vanessa >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Vanessa Villamia Sochat >>>>>>> Stanford University >>>>>>> (603) 321-0676 >>>>>>> >>>>>>> _______________________________________________ >>>>>>> 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 >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Vanessa Villamia Sochat >>>>> Stanford University >>>>> (603) 321-0676 >>>>> >>>>> _______________________________________________ >>>>> 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 >>>> >>>> >>> >>> _______________________________________________ >>> Neuroimaging mailing list >>> Neuroimaging at python.org >>> https://mail.python.org/mailman/listinfo/neuroimaging >>> >>> >> >> >> -- >> Vanessa Villamia Sochat >> Stanford University >> (603) 321-0676 >> >> _______________________________________________ >> Neuroimaging mailing list >> Neuroimaging at python.org >> https://mail.python.org/mailman/listinfo/neuroimaging >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From vsochat at stanford.edu Tue Oct 27 13:35:11 2015 From: vsochat at stanford.edu (vanessa sochat) Date: Tue, 27 Oct 2015 10:35:11 -0700 Subject: [Neuroimaging] Site Contributions In-Reply-To: References: Message-ID: I will do some tweaks and get the site working. There will be a change for the URL so there might be some bugs with my initial release, but I'll get it fixed asap. Will send an update later. On Tue, Oct 27, 2015 at 6:48 AM, Ariel Rokem wrote: > Oh, one more: > > On Tue, Oct 27, 2015 at 6:40 AM, Ariel Rokem wrote: > >> Hi Vanessa, >> >> I have a few comments/suggestions: >> >> 1. I would rather not have the front page be the project directory. In my >> opinion, the front page should instead explain briefly what this is, and >> lead visitors to the various other parts of the website. >> >> 2. There are a few issues with formatting in the Code of Conduct page >> (bullet points appear as continued lines) >> > > > 3. Please include mindboggle in the project directory (it's been recently > added!). > > >> Other than these two, I think this is ready to be introduced as a PR >> against the nipy/nipy.github.com repository (you don't need any admin >> rights to do that, but I also just added you to "team blog" on the github >> nipy org, so you can even do the merge yourself, if you want). >> >> Cheers, >> >> Ariel >> >> On Mon, Oct 26, 2015 at 12:56 PM, vanessa sochat >> wrote: >> >>> Hi Eleftherios, >>> >>> It definitely would be possible! I'm not any sort of admin in the nipy >>> space, so the farthest I could take it is having the repo for someone to >>> deploy on nipy.github.io. The code is here: >>> >>> https://github.com/vsoch/nipy-jekyll >>> >>> and deployment on my github pages: >>> >>> http://vsoch.github.io/nipy-jekyll/ >>> >>> I mostly stopped working on it because I accomplished all the things >>> that I set out to do (jekyll site, preview on continuous integration with >>> circle, standard ways to add new content, and an easy way to multiple >>> ways to add content a la github >>> , or for those who >>> aren't comfortable with pushing and pulling, la social media >>> ). I think I had suggested moving >>> forward for people to try out tumblr (and start contributing content!), and >>> if people were happy, to move it over to the nipy repo. If the outcome of >>> the work was not a desired solution, I was content to just let it be. >>> However if there is interest, that is definitely still a possibility. >>> >>> Best, >>> >>> Vanessa >>> >>> >>> >>> On Mon, Oct 26, 2015 at 12:34 PM, Eleftherios Garyfallidis < >>> garyfallidis at gmail.com> wrote: >>> >>>> Hi Vanessa and all, >>>> >>>> Would it be possible to switch to your much nicer new website? I still >>>> see the older version being up. >>>> >>>> Do you have a plan for this? Or you waiting for some feedback on our >>>> side? >>>> >>>> Best regards, >>>> Eleftherios >>>> >>>> On Wed, Sep 2, 2015 at 12:57 PM, Ben Cipollini >>>> wrote: >>>> >>>>> I think they're good for mobile sites. I think they're generally >>>>> expanded by default on full screens, and compacted on mobile. So I suggest >>>>> to keep it, but have a regular menu that's showing on full screens and >>>>> hidden on mobile. >>>>> >>>>> On Wed, Sep 2, 2015 at 9:51 AM, vanessa sochat >>>>> wrote: >>>>> >>>>>> That's a good suggestion, and I'll add as an issue so I can find it >>>>>> easily when the next round of changes comes around. Generally, these >>>>>> "hamburger" menu things are useless functionality wise, and only serve to >>>>>> aesthetically "get rid of the navigation" to have a clean looking site. In >>>>>> our case, it is probably just annoying to have the extra clicks. >>>>>> >>>>>> On Wed, Sep 2, 2015 at 8:50 AM, Ben Cipollini >>>>>> wrote: >>>>>> >>>>>>> This looks great. It's also cool to see "ask a question" integrated >>>>>>> into the website, though we'll still have to hash things out for that. >>>>>>> >>>>>>> Rather than open a github issue (which few may see), I'll make a >>>>>>> suggestion here: can we have the menu expanded by default when accessing >>>>>>> via a full-size screen? >>>>>>> >>>>>>> It feels odd to me to have to expand the menu in order to navigate >>>>>>> anywhere, by default. To me, navigation options should be obvious, unless >>>>>>> pressed for space. >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Sun, Aug 30, 2015 at 1:14 PM, vanessa sochat < >>>>>>> vsochat at stanford.edu> wrote: >>>>>>> >>>>>>>> Hi Everyone, >>>>>>>> >>>>>>>> I've finished work on the "contribute" page with my thinking for >>>>>>>> how to contribute various content: >>>>>>>> >>>>>>>> http://vsoch.github.io/nipy-jekyll/contribute.html >>>>>>>> >>>>>>>> and as an example, put up a quick blog post: >>>>>>>> >>>>>>>> http://neuroimaging.tumblr.com/ >>>>>>>> >>>>>>>> The old "example" blog posts are hidden (private) and can be viewed >>>>>>>> if you are a contributor. I'd like to add anyone and everyone interested to >>>>>>>> contribute as "official" contributors via tumblr - if you are interested >>>>>>>> please send me your email address. I've already invited some of you for >>>>>>>> which I know the email. >>>>>>>> >>>>>>>> Best, >>>>>>>> >>>>>>>> Vanessa >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Vanessa Villamia Sochat >>>>>>>> Stanford University >>>>>>>> (603) 321-0676 >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> 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 >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Vanessa Villamia Sochat >>>>>> Stanford University >>>>>> (603) 321-0676 >>>>>> >>>>>> _______________________________________________ >>>>>> 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 >>>>> >>>>> >>>> >>>> _______________________________________________ >>>> Neuroimaging mailing list >>>> Neuroimaging at python.org >>>> https://mail.python.org/mailman/listinfo/neuroimaging >>>> >>>> >>> >>> >>> -- >>> Vanessa Villamia Sochat >>> Stanford University >>> (603) 321-0676 >>> >>> _______________________________________________ >>> 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 > > -- Vanessa Villamia Sochat Stanford University (603) 321-0676 -------------- next part -------------- An HTML attachment was scrubbed... URL: From bcipolli at ucsd.edu Tue Oct 27 13:36:06 2015 From: bcipolli at ucsd.edu (Ben Cipollini) Date: Tue, 27 Oct 2015 10:36:06 -0700 Subject: [Neuroimaging] Site Contributions In-Reply-To: References: Message-ID: Thanks Vanessa! On Tue, Oct 27, 2015 at 10:35 AM, vanessa sochat wrote: > I will do some tweaks and get the site working. There will be a change for > the URL so there might be some bugs with my initial release, but I'll get > it fixed asap. Will send an update later. > > On Tue, Oct 27, 2015 at 6:48 AM, Ariel Rokem wrote: > >> Oh, one more: >> >> On Tue, Oct 27, 2015 at 6:40 AM, Ariel Rokem wrote: >> >>> Hi Vanessa, >>> >>> I have a few comments/suggestions: >>> >>> 1. I would rather not have the front page be the project directory. In >>> my opinion, the front page should instead explain briefly what this is, and >>> lead visitors to the various other parts of the website. >>> >>> 2. There are a few issues with formatting in the Code of Conduct page >>> (bullet points appear as continued lines) >>> >> >> >> 3. Please include mindboggle in the project directory (it's been recently >> added!). >> >> >>> Other than these two, I think this is ready to be introduced as a PR >>> against the nipy/nipy.github.com repository (you don't need any admin >>> rights to do that, but I also just added you to "team blog" on the github >>> nipy org, so you can even do the merge yourself, if you want). >>> >>> Cheers, >>> >>> Ariel >>> >>> On Mon, Oct 26, 2015 at 12:56 PM, vanessa sochat >>> wrote: >>> >>>> Hi Eleftherios, >>>> >>>> It definitely would be possible! I'm not any sort of admin in the nipy >>>> space, so the farthest I could take it is having the repo for someone to >>>> deploy on nipy.github.io. The code is here: >>>> >>>> https://github.com/vsoch/nipy-jekyll >>>> >>>> and deployment on my github pages: >>>> >>>> http://vsoch.github.io/nipy-jekyll/ >>>> >>>> I mostly stopped working on it because I accomplished all the things >>>> that I set out to do (jekyll site, preview on continuous integration with >>>> circle, standard ways to add new content, and an easy way to multiple >>>> ways to add content a la github >>>> , or for those who >>>> aren't comfortable with pushing and pulling, la social media >>>> ). I think I had suggested moving >>>> forward for people to try out tumblr (and start contributing content!), and >>>> if people were happy, to move it over to the nipy repo. If the outcome of >>>> the work was not a desired solution, I was content to just let it be. >>>> However if there is interest, that is definitely still a possibility. >>>> >>>> Best, >>>> >>>> Vanessa >>>> >>>> >>>> >>>> On Mon, Oct 26, 2015 at 12:34 PM, Eleftherios Garyfallidis < >>>> garyfallidis at gmail.com> wrote: >>>> >>>>> Hi Vanessa and all, >>>>> >>>>> Would it be possible to switch to your much nicer new website? I still >>>>> see the older version being up. >>>>> >>>>> Do you have a plan for this? Or you waiting for some feedback on our >>>>> side? >>>>> >>>>> Best regards, >>>>> Eleftherios >>>>> >>>>> On Wed, Sep 2, 2015 at 12:57 PM, Ben Cipollini >>>>> wrote: >>>>> >>>>>> I think they're good for mobile sites. I think they're generally >>>>>> expanded by default on full screens, and compacted on mobile. So I suggest >>>>>> to keep it, but have a regular menu that's showing on full screens and >>>>>> hidden on mobile. >>>>>> >>>>>> On Wed, Sep 2, 2015 at 9:51 AM, vanessa sochat >>>>>> wrote: >>>>>> >>>>>>> That's a good suggestion, and I'll add as an issue so I can find it >>>>>>> easily when the next round of changes comes around. Generally, these >>>>>>> "hamburger" menu things are useless functionality wise, and only serve to >>>>>>> aesthetically "get rid of the navigation" to have a clean looking site. In >>>>>>> our case, it is probably just annoying to have the extra clicks. >>>>>>> >>>>>>> On Wed, Sep 2, 2015 at 8:50 AM, Ben Cipollini >>>>>>> wrote: >>>>>>> >>>>>>>> This looks great. It's also cool to see "ask a question" integrated >>>>>>>> into the website, though we'll still have to hash things out for that. >>>>>>>> >>>>>>>> Rather than open a github issue (which few may see), I'll make a >>>>>>>> suggestion here: can we have the menu expanded by default when accessing >>>>>>>> via a full-size screen? >>>>>>>> >>>>>>>> It feels odd to me to have to expand the menu in order to navigate >>>>>>>> anywhere, by default. To me, navigation options should be obvious, unless >>>>>>>> pressed for space. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Sun, Aug 30, 2015 at 1:14 PM, vanessa sochat < >>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>> >>>>>>>>> Hi Everyone, >>>>>>>>> >>>>>>>>> I've finished work on the "contribute" page with my thinking for >>>>>>>>> how to contribute various content: >>>>>>>>> >>>>>>>>> http://vsoch.github.io/nipy-jekyll/contribute.html >>>>>>>>> >>>>>>>>> and as an example, put up a quick blog post: >>>>>>>>> >>>>>>>>> http://neuroimaging.tumblr.com/ >>>>>>>>> >>>>>>>>> The old "example" blog posts are hidden (private) and can be >>>>>>>>> viewed if you are a contributor. I'd like to add anyone and everyone >>>>>>>>> interested to contribute as "official" contributors via tumblr - if you are >>>>>>>>> interested please send me your email address. I've already invited some of >>>>>>>>> you for which I know the email. >>>>>>>>> >>>>>>>>> Best, >>>>>>>>> >>>>>>>>> Vanessa >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Vanessa Villamia Sochat >>>>>>>>> Stanford University >>>>>>>>> (603) 321-0676 >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> 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 >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Vanessa Villamia Sochat >>>>>>> Stanford University >>>>>>> (603) 321-0676 >>>>>>> >>>>>>> _______________________________________________ >>>>>>> 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 >>>>>> >>>>>> >>>>> >>>>> _______________________________________________ >>>>> Neuroimaging mailing list >>>>> Neuroimaging at python.org >>>>> https://mail.python.org/mailman/listinfo/neuroimaging >>>>> >>>>> >>>> >>>> >>>> -- >>>> Vanessa Villamia Sochat >>>> Stanford University >>>> (603) 321-0676 >>>> >>>> _______________________________________________ >>>> 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 >> >> > > > -- > Vanessa Villamia Sochat > Stanford University > (603) 321-0676 > > _______________________________________________ > Neuroimaging mailing list > Neuroimaging at python.org > https://mail.python.org/mailman/listinfo/neuroimaging > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From vsochat at stanford.edu Tue Oct 27 13:42:54 2015 From: vsochat at stanford.edu (vanessa sochat) Date: Tue, 27 Oct 2015 10:42:54 -0700 Subject: [Neuroimaging] Site Contributions In-Reply-To: References: Message-ID: Just as a proof of concept for adding a project - I just added a new entry to the data file (copy pasting basically), copied one file, and the entire process took me like, 48 seconds :) On Tue, Oct 27, 2015 at 10:36 AM, Ben Cipollini wrote: > Thanks Vanessa! > > On Tue, Oct 27, 2015 at 10:35 AM, vanessa sochat > wrote: > >> I will do some tweaks and get the site working. There will be a change >> for the URL so there might be some bugs with my initial release, but I'll >> get it fixed asap. Will send an update later. >> >> On Tue, Oct 27, 2015 at 6:48 AM, Ariel Rokem wrote: >> >>> Oh, one more: >>> >>> On Tue, Oct 27, 2015 at 6:40 AM, Ariel Rokem wrote: >>> >>>> Hi Vanessa, >>>> >>>> I have a few comments/suggestions: >>>> >>>> 1. I would rather not have the front page be the project directory. In >>>> my opinion, the front page should instead explain briefly what this is, and >>>> lead visitors to the various other parts of the website. >>>> >>>> 2. There are a few issues with formatting in the Code of Conduct page >>>> (bullet points appear as continued lines) >>>> >>> >>> >>> 3. Please include mindboggle in the project directory (it's been >>> recently added!). >>> >>> >>>> Other than these two, I think this is ready to be introduced as a PR >>>> against the nipy/nipy.github.com repository (you don't need any admin >>>> rights to do that, but I also just added you to "team blog" on the github >>>> nipy org, so you can even do the merge yourself, if you want). >>>> >>>> Cheers, >>>> >>>> Ariel >>>> >>>> On Mon, Oct 26, 2015 at 12:56 PM, vanessa sochat >>>> wrote: >>>> >>>>> Hi Eleftherios, >>>>> >>>>> It definitely would be possible! I'm not any sort of admin in the nipy >>>>> space, so the farthest I could take it is having the repo for someone to >>>>> deploy on nipy.github.io. The code is here: >>>>> >>>>> https://github.com/vsoch/nipy-jekyll >>>>> >>>>> and deployment on my github pages: >>>>> >>>>> http://vsoch.github.io/nipy-jekyll/ >>>>> >>>>> I mostly stopped working on it because I accomplished all the things >>>>> that I set out to do (jekyll site, preview on continuous integration with >>>>> circle, standard ways to add new content, and an easy way to multiple >>>>> ways to add content a la github >>>>> , or for those >>>>> who aren't comfortable with pushing and pulling, la social media >>>>> ). I think I had suggested moving >>>>> forward for people to try out tumblr (and start contributing content!), and >>>>> if people were happy, to move it over to the nipy repo. If the outcome of >>>>> the work was not a desired solution, I was content to just let it be. >>>>> However if there is interest, that is definitely still a possibility. >>>>> >>>>> Best, >>>>> >>>>> Vanessa >>>>> >>>>> >>>>> >>>>> On Mon, Oct 26, 2015 at 12:34 PM, Eleftherios Garyfallidis < >>>>> garyfallidis at gmail.com> wrote: >>>>> >>>>>> Hi Vanessa and all, >>>>>> >>>>>> Would it be possible to switch to your much nicer new website? I >>>>>> still see the older version being up. >>>>>> >>>>>> Do you have a plan for this? Or you waiting for some feedback on our >>>>>> side? >>>>>> >>>>>> Best regards, >>>>>> Eleftherios >>>>>> >>>>>> On Wed, Sep 2, 2015 at 12:57 PM, Ben Cipollini >>>>>> wrote: >>>>>> >>>>>>> I think they're good for mobile sites. I think they're generally >>>>>>> expanded by default on full screens, and compacted on mobile. So I suggest >>>>>>> to keep it, but have a regular menu that's showing on full screens and >>>>>>> hidden on mobile. >>>>>>> >>>>>>> On Wed, Sep 2, 2015 at 9:51 AM, vanessa sochat >>>>>> > wrote: >>>>>>> >>>>>>>> That's a good suggestion, and I'll add as an issue so I can find it >>>>>>>> easily when the next round of changes comes around. Generally, these >>>>>>>> "hamburger" menu things are useless functionality wise, and only serve to >>>>>>>> aesthetically "get rid of the navigation" to have a clean looking site. In >>>>>>>> our case, it is probably just annoying to have the extra clicks. >>>>>>>> >>>>>>>> On Wed, Sep 2, 2015 at 8:50 AM, Ben Cipollini >>>>>>>> wrote: >>>>>>>> >>>>>>>>> This looks great. It's also cool to see "ask a question" >>>>>>>>> integrated into the website, though we'll still have to hash things out for >>>>>>>>> that. >>>>>>>>> >>>>>>>>> Rather than open a github issue (which few may see), I'll make a >>>>>>>>> suggestion here: can we have the menu expanded by default when accessing >>>>>>>>> via a full-size screen? >>>>>>>>> >>>>>>>>> It feels odd to me to have to expand the menu in order to navigate >>>>>>>>> anywhere, by default. To me, navigation options should be obvious, unless >>>>>>>>> pressed for space. >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On Sun, Aug 30, 2015 at 1:14 PM, vanessa sochat < >>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>> >>>>>>>>>> Hi Everyone, >>>>>>>>>> >>>>>>>>>> I've finished work on the "contribute" page with my thinking for >>>>>>>>>> how to contribute various content: >>>>>>>>>> >>>>>>>>>> http://vsoch.github.io/nipy-jekyll/contribute.html >>>>>>>>>> >>>>>>>>>> and as an example, put up a quick blog post: >>>>>>>>>> >>>>>>>>>> http://neuroimaging.tumblr.com/ >>>>>>>>>> >>>>>>>>>> The old "example" blog posts are hidden (private) and can be >>>>>>>>>> viewed if you are a contributor. I'd like to add anyone and everyone >>>>>>>>>> interested to contribute as "official" contributors via tumblr - if you are >>>>>>>>>> interested please send me your email address. I've already invited some of >>>>>>>>>> you for which I know the email. >>>>>>>>>> >>>>>>>>>> Best, >>>>>>>>>> >>>>>>>>>> Vanessa >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>> Stanford University >>>>>>>>>> (603) 321-0676 >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> 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 >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Vanessa Villamia Sochat >>>>>>>> Stanford University >>>>>>>> (603) 321-0676 >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> 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 >>>>>>> >>>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Neuroimaging mailing list >>>>>> Neuroimaging at python.org >>>>>> https://mail.python.org/mailman/listinfo/neuroimaging >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Vanessa Villamia Sochat >>>>> Stanford University >>>>> (603) 321-0676 >>>>> >>>>> _______________________________________________ >>>>> 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 >>> >>> >> >> >> -- >> Vanessa Villamia Sochat >> Stanford University >> (603) 321-0676 >> >> _______________________________________________ >> 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 > > -- Vanessa Villamia Sochat Stanford University (603) 321-0676 -------------- next part -------------- An HTML attachment was scrubbed... URL: From vsochat at stanford.edu Tue Oct 27 13:56:30 2015 From: vsochat at stanford.edu (vanessa sochat) Date: Tue, 27 Oct 2015 10:56:30 -0700 Subject: [Neuroimaging] Site Contributions In-Reply-To: References: Message-ID: Hi Ariel, Please add me as an admin to nipy.github.io, so I can set up circle for CI. Thanks! Best, Vanessa On Tue, Oct 27, 2015 at 10:42 AM, vanessa sochat wrote: > Just as a proof of concept for adding a project - I just added a new entry > to the data file (copy pasting basically), copied one file, and the entire > process took me like, 48 seconds :) > > On Tue, Oct 27, 2015 at 10:36 AM, Ben Cipollini wrote: > >> Thanks Vanessa! >> >> On Tue, Oct 27, 2015 at 10:35 AM, vanessa sochat >> wrote: >> >>> I will do some tweaks and get the site working. There will be a change >>> for the URL so there might be some bugs with my initial release, but I'll >>> get it fixed asap. Will send an update later. >>> >>> On Tue, Oct 27, 2015 at 6:48 AM, Ariel Rokem wrote: >>> >>>> Oh, one more: >>>> >>>> On Tue, Oct 27, 2015 at 6:40 AM, Ariel Rokem wrote: >>>> >>>>> Hi Vanessa, >>>>> >>>>> I have a few comments/suggestions: >>>>> >>>>> 1. I would rather not have the front page be the project directory. In >>>>> my opinion, the front page should instead explain briefly what this is, and >>>>> lead visitors to the various other parts of the website. >>>>> >>>>> 2. There are a few issues with formatting in the Code of Conduct page >>>>> (bullet points appear as continued lines) >>>>> >>>> >>>> >>>> 3. Please include mindboggle in the project directory (it's been >>>> recently added!). >>>> >>>> >>>>> Other than these two, I think this is ready to be introduced as a PR >>>>> against the nipy/nipy.github.com repository (you don't need any admin >>>>> rights to do that, but I also just added you to "team blog" on the github >>>>> nipy org, so you can even do the merge yourself, if you want). >>>>> >>>>> Cheers, >>>>> >>>>> Ariel >>>>> >>>>> On Mon, Oct 26, 2015 at 12:56 PM, vanessa sochat >>>> > wrote: >>>>> >>>>>> Hi Eleftherios, >>>>>> >>>>>> It definitely would be possible! I'm not any sort of admin in the >>>>>> nipy space, so the farthest I could take it is having the repo for someone >>>>>> to deploy on nipy.github.io. The code is here: >>>>>> >>>>>> https://github.com/vsoch/nipy-jekyll >>>>>> >>>>>> and deployment on my github pages: >>>>>> >>>>>> http://vsoch.github.io/nipy-jekyll/ >>>>>> >>>>>> I mostly stopped working on it because I accomplished all the things >>>>>> that I set out to do (jekyll site, preview on continuous integration with >>>>>> circle, standard ways to add new content, and an easy way to multiple >>>>>> ways to add content a la github >>>>>> , or for those >>>>>> who aren't comfortable with pushing and pulling, la social media >>>>>> ). I think I had suggested moving >>>>>> forward for people to try out tumblr (and start contributing content!), and >>>>>> if people were happy, to move it over to the nipy repo. If the outcome of >>>>>> the work was not a desired solution, I was content to just let it be. >>>>>> However if there is interest, that is definitely still a possibility. >>>>>> >>>>>> Best, >>>>>> >>>>>> Vanessa >>>>>> >>>>>> >>>>>> >>>>>> On Mon, Oct 26, 2015 at 12:34 PM, Eleftherios Garyfallidis < >>>>>> garyfallidis at gmail.com> wrote: >>>>>> >>>>>>> Hi Vanessa and all, >>>>>>> >>>>>>> Would it be possible to switch to your much nicer new website? I >>>>>>> still see the older version being up. >>>>>>> >>>>>>> Do you have a plan for this? Or you waiting for some feedback on our >>>>>>> side? >>>>>>> >>>>>>> Best regards, >>>>>>> Eleftherios >>>>>>> >>>>>>> On Wed, Sep 2, 2015 at 12:57 PM, Ben Cipollini >>>>>>> wrote: >>>>>>> >>>>>>>> I think they're good for mobile sites. I think they're generally >>>>>>>> expanded by default on full screens, and compacted on mobile. So I suggest >>>>>>>> to keep it, but have a regular menu that's showing on full screens and >>>>>>>> hidden on mobile. >>>>>>>> >>>>>>>> On Wed, Sep 2, 2015 at 9:51 AM, vanessa sochat < >>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>> >>>>>>>>> That's a good suggestion, and I'll add as an issue so I can find >>>>>>>>> it easily when the next round of changes comes around. Generally, these >>>>>>>>> "hamburger" menu things are useless functionality wise, and only serve to >>>>>>>>> aesthetically "get rid of the navigation" to have a clean looking site. In >>>>>>>>> our case, it is probably just annoying to have the extra clicks. >>>>>>>>> >>>>>>>>> On Wed, Sep 2, 2015 at 8:50 AM, Ben Cipollini >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> This looks great. It's also cool to see "ask a question" >>>>>>>>>> integrated into the website, though we'll still have to hash things out for >>>>>>>>>> that. >>>>>>>>>> >>>>>>>>>> Rather than open a github issue (which few may see), I'll make a >>>>>>>>>> suggestion here: can we have the menu expanded by default when accessing >>>>>>>>>> via a full-size screen? >>>>>>>>>> >>>>>>>>>> It feels odd to me to have to expand the menu in order to >>>>>>>>>> navigate anywhere, by default. To me, navigation options should be obvious, >>>>>>>>>> unless pressed for space. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Sun, Aug 30, 2015 at 1:14 PM, vanessa sochat < >>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>> >>>>>>>>>>> Hi Everyone, >>>>>>>>>>> >>>>>>>>>>> I've finished work on the "contribute" page with my thinking for >>>>>>>>>>> how to contribute various content: >>>>>>>>>>> >>>>>>>>>>> http://vsoch.github.io/nipy-jekyll/contribute.html >>>>>>>>>>> >>>>>>>>>>> and as an example, put up a quick blog post: >>>>>>>>>>> >>>>>>>>>>> http://neuroimaging.tumblr.com/ >>>>>>>>>>> >>>>>>>>>>> The old "example" blog posts are hidden (private) and can be >>>>>>>>>>> viewed if you are a contributor. I'd like to add anyone and everyone >>>>>>>>>>> interested to contribute as "official" contributors via tumblr - if you are >>>>>>>>>>> interested please send me your email address. I've already invited some of >>>>>>>>>>> you for which I know the email. >>>>>>>>>>> >>>>>>>>>>> Best, >>>>>>>>>>> >>>>>>>>>>> Vanessa >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>> Stanford University >>>>>>>>>>> (603) 321-0676 >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> 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 >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Vanessa Villamia Sochat >>>>>>>>> Stanford University >>>>>>>>> (603) 321-0676 >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> 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 >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Neuroimaging mailing list >>>>>>> Neuroimaging at python.org >>>>>>> https://mail.python.org/mailman/listinfo/neuroimaging >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Vanessa Villamia Sochat >>>>>> Stanford University >>>>>> (603) 321-0676 >>>>>> >>>>>> _______________________________________________ >>>>>> 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 >>>> >>>> >>> >>> >>> -- >>> Vanessa Villamia Sochat >>> Stanford University >>> (603) 321-0676 >>> >>> _______________________________________________ >>> 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 >> >> > > > -- > Vanessa Villamia Sochat > Stanford University > (603) 321-0676 > -- Vanessa Villamia Sochat Stanford University (603) 321-0676 -------------- next part -------------- An HTML attachment was scrubbed... URL: From arokem at gmail.com Tue Oct 27 14:07:13 2015 From: arokem at gmail.com (Ariel Rokem) Date: Tue, 27 Oct 2015 11:07:13 -0700 Subject: [Neuroimaging] Site Contributions In-Reply-To: References: Message-ID: Hi, On Tue, Oct 27, 2015 at 10:56 AM, vanessa sochat wrote: > Hi Ariel, > > Please add me as an admin to nipy.github.io, so I can set up circle for > CI. Thanks! > > I believe I just did that. Let me know how you get on. > Best, > > Vanessa > > On Tue, Oct 27, 2015 at 10:42 AM, vanessa sochat > wrote: > >> Just as a proof of concept for adding a project - I just added a new >> entry to the data file (copy pasting basically), copied one file, and the >> entire process took me like, 48 seconds :) >> >> On Tue, Oct 27, 2015 at 10:36 AM, Ben Cipollini >> wrote: >> >>> Thanks Vanessa! >>> >>> On Tue, Oct 27, 2015 at 10:35 AM, vanessa sochat >>> wrote: >>> >>>> I will do some tweaks and get the site working. There will be a change >>>> for the URL so there might be some bugs with my initial release, but I'll >>>> get it fixed asap. Will send an update later. >>>> >>>> On Tue, Oct 27, 2015 at 6:48 AM, Ariel Rokem wrote: >>>> >>>>> Oh, one more: >>>>> >>>>> On Tue, Oct 27, 2015 at 6:40 AM, Ariel Rokem wrote: >>>>> >>>>>> Hi Vanessa, >>>>>> >>>>>> I have a few comments/suggestions: >>>>>> >>>>>> 1. I would rather not have the front page be the project directory. >>>>>> In my opinion, the front page should instead explain briefly what this is, >>>>>> and lead visitors to the various other parts of the website. >>>>>> >>>>>> 2. There are a few issues with formatting in the Code of Conduct page >>>>>> (bullet points appear as continued lines) >>>>>> >>>>> >>>>> >>>>> 3. Please include mindboggle in the project directory (it's been >>>>> recently added!). >>>>> >>>>> >>>>>> Other than these two, I think this is ready to be introduced as a PR >>>>>> against the nipy/nipy.github.com repository (you don't need any >>>>>> admin rights to do that, but I also just added you to "team blog" on the >>>>>> github nipy org, so you can even do the merge yourself, if you want). >>>>>> >>>>>> Cheers, >>>>>> >>>>>> Ariel >>>>>> >>>>>> On Mon, Oct 26, 2015 at 12:56 PM, vanessa sochat < >>>>>> vsochat at stanford.edu> wrote: >>>>>> >>>>>>> Hi Eleftherios, >>>>>>> >>>>>>> It definitely would be possible! I'm not any sort of admin in the >>>>>>> nipy space, so the farthest I could take it is having the repo for someone >>>>>>> to deploy on nipy.github.io. The code is here: >>>>>>> >>>>>>> https://github.com/vsoch/nipy-jekyll >>>>>>> >>>>>>> and deployment on my github pages: >>>>>>> >>>>>>> http://vsoch.github.io/nipy-jekyll/ >>>>>>> >>>>>>> I mostly stopped working on it because I accomplished all the things >>>>>>> that I set out to do (jekyll site, preview on continuous integration with >>>>>>> circle, standard ways to add new content, and an easy way to multiple >>>>>>> ways to add content a la github >>>>>>> , or for those >>>>>>> who aren't comfortable with pushing and pulling, la social media >>>>>>> ). I think I had suggested moving >>>>>>> forward for people to try out tumblr (and start contributing content!), and >>>>>>> if people were happy, to move it over to the nipy repo. If the outcome of >>>>>>> the work was not a desired solution, I was content to just let it be. >>>>>>> However if there is interest, that is definitely still a possibility. >>>>>>> >>>>>>> Best, >>>>>>> >>>>>>> Vanessa >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Mon, Oct 26, 2015 at 12:34 PM, Eleftherios Garyfallidis < >>>>>>> garyfallidis at gmail.com> wrote: >>>>>>> >>>>>>>> Hi Vanessa and all, >>>>>>>> >>>>>>>> Would it be possible to switch to your much nicer new website? I >>>>>>>> still see the older version being up. >>>>>>>> >>>>>>>> Do you have a plan for this? Or you waiting for some feedback on >>>>>>>> our side? >>>>>>>> >>>>>>>> Best regards, >>>>>>>> Eleftherios >>>>>>>> >>>>>>>> On Wed, Sep 2, 2015 at 12:57 PM, Ben Cipollini >>>>>>>> wrote: >>>>>>>> >>>>>>>>> I think they're good for mobile sites. I think they're generally >>>>>>>>> expanded by default on full screens, and compacted on mobile. So I suggest >>>>>>>>> to keep it, but have a regular menu that's showing on full screens and >>>>>>>>> hidden on mobile. >>>>>>>>> >>>>>>>>> On Wed, Sep 2, 2015 at 9:51 AM, vanessa sochat < >>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>> >>>>>>>>>> That's a good suggestion, and I'll add as an issue so I can find >>>>>>>>>> it easily when the next round of changes comes around. Generally, these >>>>>>>>>> "hamburger" menu things are useless functionality wise, and only serve to >>>>>>>>>> aesthetically "get rid of the navigation" to have a clean looking site. In >>>>>>>>>> our case, it is probably just annoying to have the extra clicks. >>>>>>>>>> >>>>>>>>>> On Wed, Sep 2, 2015 at 8:50 AM, Ben Cipollini >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>>> This looks great. It's also cool to see "ask a question" >>>>>>>>>>> integrated into the website, though we'll still have to hash things out for >>>>>>>>>>> that. >>>>>>>>>>> >>>>>>>>>>> Rather than open a github issue (which few may see), I'll make a >>>>>>>>>>> suggestion here: can we have the menu expanded by default when accessing >>>>>>>>>>> via a full-size screen? >>>>>>>>>>> >>>>>>>>>>> It feels odd to me to have to expand the menu in order to >>>>>>>>>>> navigate anywhere, by default. To me, navigation options should be obvious, >>>>>>>>>>> unless pressed for space. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Sun, Aug 30, 2015 at 1:14 PM, vanessa sochat < >>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>> >>>>>>>>>>>> Hi Everyone, >>>>>>>>>>>> >>>>>>>>>>>> I've finished work on the "contribute" page with my thinking >>>>>>>>>>>> for how to contribute various content: >>>>>>>>>>>> >>>>>>>>>>>> http://vsoch.github.io/nipy-jekyll/contribute.html >>>>>>>>>>>> >>>>>>>>>>>> and as an example, put up a quick blog post: >>>>>>>>>>>> >>>>>>>>>>>> http://neuroimaging.tumblr.com/ >>>>>>>>>>>> >>>>>>>>>>>> The old "example" blog posts are hidden (private) and can be >>>>>>>>>>>> viewed if you are a contributor. I'd like to add anyone and everyone >>>>>>>>>>>> interested to contribute as "official" contributors via tumblr - if you are >>>>>>>>>>>> interested please send me your email address. I've already invited some of >>>>>>>>>>>> you for which I know the email. >>>>>>>>>>>> >>>>>>>>>>>> Best, >>>>>>>>>>>> >>>>>>>>>>>> Vanessa >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>> Stanford University >>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> 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 >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>> Stanford University >>>>>>>>>> (603) 321-0676 >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> 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 >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Neuroimaging mailing list >>>>>>>> Neuroimaging at python.org >>>>>>>> https://mail.python.org/mailman/listinfo/neuroimaging >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Vanessa Villamia Sochat >>>>>>> Stanford University >>>>>>> (603) 321-0676 >>>>>>> >>>>>>> _______________________________________________ >>>>>>> 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 >>>>> >>>>> >>>> >>>> >>>> -- >>>> Vanessa Villamia Sochat >>>> Stanford University >>>> (603) 321-0676 >>>> >>>> _______________________________________________ >>>> 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 >>> >>> >> >> >> -- >> Vanessa Villamia Sochat >> Stanford University >> (603) 321-0676 >> > > > > -- > Vanessa Villamia Sochat > Stanford University > (603) 321-0676 > > _______________________________________________ > Neuroimaging mailing list > Neuroimaging at python.org > https://mail.python.org/mailman/listinfo/neuroimaging > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From vsochat at stanford.edu Tue Oct 27 14:10:10 2015 From: vsochat at stanford.edu (vanessa sochat) Date: Tue, 27 Oct 2015 11:10:10 -0700 Subject: [Neuroimaging] Site Contributions In-Reply-To: References: Message-ID: Got it! Thanks! :) On Tue, Oct 27, 2015 at 11:07 AM, Ariel Rokem wrote: > Hi, > On Tue, Oct 27, 2015 at 10:56 AM, vanessa sochat > wrote: > >> Hi Ariel, >> >> Please add me as an admin to nipy.github.io, so I can set up circle for >> CI. Thanks! >> >> > I believe I just did that. Let me know how you get on. > > >> Best, >> >> Vanessa >> >> On Tue, Oct 27, 2015 at 10:42 AM, vanessa sochat >> wrote: >> >>> Just as a proof of concept for adding a project - I just added a new >>> entry to the data file (copy pasting basically), copied one file, and the >>> entire process took me like, 48 seconds :) >>> >>> On Tue, Oct 27, 2015 at 10:36 AM, Ben Cipollini >>> wrote: >>> >>>> Thanks Vanessa! >>>> >>>> On Tue, Oct 27, 2015 at 10:35 AM, vanessa sochat >>>> wrote: >>>> >>>>> I will do some tweaks and get the site working. There will be a change >>>>> for the URL so there might be some bugs with my initial release, but I'll >>>>> get it fixed asap. Will send an update later. >>>>> >>>>> On Tue, Oct 27, 2015 at 6:48 AM, Ariel Rokem wrote: >>>>> >>>>>> Oh, one more: >>>>>> >>>>>> On Tue, Oct 27, 2015 at 6:40 AM, Ariel Rokem >>>>>> wrote: >>>>>> >>>>>>> Hi Vanessa, >>>>>>> >>>>>>> I have a few comments/suggestions: >>>>>>> >>>>>>> 1. I would rather not have the front page be the project directory. >>>>>>> In my opinion, the front page should instead explain briefly what this is, >>>>>>> and lead visitors to the various other parts of the website. >>>>>>> >>>>>>> 2. There are a few issues with formatting in the Code of Conduct >>>>>>> page (bullet points appear as continued lines) >>>>>>> >>>>>> >>>>>> >>>>>> 3. Please include mindboggle in the project directory (it's been >>>>>> recently added!). >>>>>> >>>>>> >>>>>>> Other than these two, I think this is ready to be introduced as a PR >>>>>>> against the nipy/nipy.github.com repository (you don't need any >>>>>>> admin rights to do that, but I also just added you to "team blog" on the >>>>>>> github nipy org, so you can even do the merge yourself, if you want). >>>>>>> >>>>>>> Cheers, >>>>>>> >>>>>>> Ariel >>>>>>> >>>>>>> On Mon, Oct 26, 2015 at 12:56 PM, vanessa sochat < >>>>>>> vsochat at stanford.edu> wrote: >>>>>>> >>>>>>>> Hi Eleftherios, >>>>>>>> >>>>>>>> It definitely would be possible! I'm not any sort of admin in the >>>>>>>> nipy space, so the farthest I could take it is having the repo for someone >>>>>>>> to deploy on nipy.github.io. The code is here: >>>>>>>> >>>>>>>> https://github.com/vsoch/nipy-jekyll >>>>>>>> >>>>>>>> and deployment on my github pages: >>>>>>>> >>>>>>>> http://vsoch.github.io/nipy-jekyll/ >>>>>>>> >>>>>>>> I mostly stopped working on it because I accomplished all the >>>>>>>> things that I set out to do (jekyll site, preview on continuous integration >>>>>>>> with circle, standard ways to add new content, and an easy way to multiple >>>>>>>> ways to add content a la github >>>>>>>> , or for those >>>>>>>> who aren't comfortable with pushing and pulling, la social media >>>>>>>> ). I think I had suggested moving >>>>>>>> forward for people to try out tumblr (and start contributing content!), and >>>>>>>> if people were happy, to move it over to the nipy repo. If the outcome of >>>>>>>> the work was not a desired solution, I was content to just let it be. >>>>>>>> However if there is interest, that is definitely still a possibility. >>>>>>>> >>>>>>>> Best, >>>>>>>> >>>>>>>> Vanessa >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Mon, Oct 26, 2015 at 12:34 PM, Eleftherios Garyfallidis < >>>>>>>> garyfallidis at gmail.com> wrote: >>>>>>>> >>>>>>>>> Hi Vanessa and all, >>>>>>>>> >>>>>>>>> Would it be possible to switch to your much nicer new website? I >>>>>>>>> still see the older version being up. >>>>>>>>> >>>>>>>>> Do you have a plan for this? Or you waiting for some feedback on >>>>>>>>> our side? >>>>>>>>> >>>>>>>>> Best regards, >>>>>>>>> Eleftherios >>>>>>>>> >>>>>>>>> On Wed, Sep 2, 2015 at 12:57 PM, Ben Cipollini >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> I think they're good for mobile sites. I think they're generally >>>>>>>>>> expanded by default on full screens, and compacted on mobile. So I suggest >>>>>>>>>> to keep it, but have a regular menu that's showing on full screens and >>>>>>>>>> hidden on mobile. >>>>>>>>>> >>>>>>>>>> On Wed, Sep 2, 2015 at 9:51 AM, vanessa sochat < >>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>> >>>>>>>>>>> That's a good suggestion, and I'll add as an issue so I can find >>>>>>>>>>> it easily when the next round of changes comes around. Generally, these >>>>>>>>>>> "hamburger" menu things are useless functionality wise, and only serve to >>>>>>>>>>> aesthetically "get rid of the navigation" to have a clean looking site. In >>>>>>>>>>> our case, it is probably just annoying to have the extra clicks. >>>>>>>>>>> >>>>>>>>>>> On Wed, Sep 2, 2015 at 8:50 AM, Ben Cipollini >>>>>>>>>> > wrote: >>>>>>>>>>> >>>>>>>>>>>> This looks great. It's also cool to see "ask a question" >>>>>>>>>>>> integrated into the website, though we'll still have to hash things out for >>>>>>>>>>>> that. >>>>>>>>>>>> >>>>>>>>>>>> Rather than open a github issue (which few may see), I'll make >>>>>>>>>>>> a suggestion here: can we have the menu expanded by default when accessing >>>>>>>>>>>> via a full-size screen? >>>>>>>>>>>> >>>>>>>>>>>> It feels odd to me to have to expand the menu in order to >>>>>>>>>>>> navigate anywhere, by default. To me, navigation options should be obvious, >>>>>>>>>>>> unless pressed for space. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Sun, Aug 30, 2015 at 1:14 PM, vanessa sochat < >>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Hi Everyone, >>>>>>>>>>>>> >>>>>>>>>>>>> I've finished work on the "contribute" page with my thinking >>>>>>>>>>>>> for how to contribute various content: >>>>>>>>>>>>> >>>>>>>>>>>>> http://vsoch.github.io/nipy-jekyll/contribute.html >>>>>>>>>>>>> >>>>>>>>>>>>> and as an example, put up a quick blog post: >>>>>>>>>>>>> >>>>>>>>>>>>> http://neuroimaging.tumblr.com/ >>>>>>>>>>>>> >>>>>>>>>>>>> The old "example" blog posts are hidden (private) and can be >>>>>>>>>>>>> viewed if you are a contributor. I'd like to add anyone and everyone >>>>>>>>>>>>> interested to contribute as "official" contributors via tumblr - if you are >>>>>>>>>>>>> interested please send me your email address. I've already invited some of >>>>>>>>>>>>> you for which I know the email. >>>>>>>>>>>>> >>>>>>>>>>>>> Best, >>>>>>>>>>>>> >>>>>>>>>>>>> Vanessa >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>> Stanford University >>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>> >>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>> 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 >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>> Stanford University >>>>>>>>>>> (603) 321-0676 >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> 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 >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Neuroimaging mailing list >>>>>>>>> Neuroimaging at python.org >>>>>>>>> https://mail.python.org/mailman/listinfo/neuroimaging >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Vanessa Villamia Sochat >>>>>>>> Stanford University >>>>>>>> (603) 321-0676 >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> 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 >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Vanessa Villamia Sochat >>>>> Stanford University >>>>> (603) 321-0676 >>>>> >>>>> _______________________________________________ >>>>> 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 >>>> >>>> >>> >>> >>> -- >>> Vanessa Villamia Sochat >>> Stanford University >>> (603) 321-0676 >>> >> >> >> >> -- >> Vanessa Villamia Sochat >> Stanford University >> (603) 321-0676 >> >> _______________________________________________ >> 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 > > -- Vanessa Villamia Sochat Stanford University (603) 321-0676 -------------- next part -------------- An HTML attachment was scrubbed... URL: From vsochat at stanford.edu Tue Oct 27 14:30:06 2015 From: vsochat at stanford.edu (vanessa sochat) Date: Tue, 27 Oct 2015 11:30:06 -0700 Subject: [Neuroimaging] Site Contributions In-Reply-To: References: Message-ID: Hi Everyone, Site is live! https://nipy.github.io/ Ariel - I'm not sure how to set up the nipy.org. Would you mind taking a look and fixing that up? Circle is having some bugs with the artifact generation, I think I can probably fix it, but not during the work week. Ben - I added your contribution to the README but didn't get the other comment in time. The good news is now anyone and everyone can submit changes as PR. I encourage everyone to familiarize yourself with tumblr, and start contributing content, PRs to tweak it. Best, Vanessa On Tue, Oct 27, 2015 at 11:10 AM, vanessa sochat wrote: > Got it! Thanks! :) > > On Tue, Oct 27, 2015 at 11:07 AM, Ariel Rokem wrote: > >> Hi, >> On Tue, Oct 27, 2015 at 10:56 AM, vanessa sochat >> wrote: >> >>> Hi Ariel, >>> >>> Please add me as an admin to nipy.github.io, so I can set up circle for >>> CI. Thanks! >>> >>> >> I believe I just did that. Let me know how you get on. >> >> >>> Best, >>> >>> Vanessa >>> >>> On Tue, Oct 27, 2015 at 10:42 AM, vanessa sochat >>> wrote: >>> >>>> Just as a proof of concept for adding a project - I just added a new >>>> entry to the data file (copy pasting basically), copied one file, and the >>>> entire process took me like, 48 seconds :) >>>> >>>> On Tue, Oct 27, 2015 at 10:36 AM, Ben Cipollini >>>> wrote: >>>> >>>>> Thanks Vanessa! >>>>> >>>>> On Tue, Oct 27, 2015 at 10:35 AM, vanessa sochat >>>> > wrote: >>>>> >>>>>> I will do some tweaks and get the site working. There will be a >>>>>> change for the URL so there might be some bugs with my initial release, but >>>>>> I'll get it fixed asap. Will send an update later. >>>>>> >>>>>> On Tue, Oct 27, 2015 at 6:48 AM, Ariel Rokem >>>>>> wrote: >>>>>> >>>>>>> Oh, one more: >>>>>>> >>>>>>> On Tue, Oct 27, 2015 at 6:40 AM, Ariel Rokem >>>>>>> wrote: >>>>>>> >>>>>>>> Hi Vanessa, >>>>>>>> >>>>>>>> I have a few comments/suggestions: >>>>>>>> >>>>>>>> 1. I would rather not have the front page be the project directory. >>>>>>>> In my opinion, the front page should instead explain briefly what this is, >>>>>>>> and lead visitors to the various other parts of the website. >>>>>>>> >>>>>>>> 2. There are a few issues with formatting in the Code of Conduct >>>>>>>> page (bullet points appear as continued lines) >>>>>>>> >>>>>>> >>>>>>> >>>>>>> 3. Please include mindboggle in the project directory (it's been >>>>>>> recently added!). >>>>>>> >>>>>>> >>>>>>>> Other than these two, I think this is ready to be introduced as a >>>>>>>> PR against the nipy/nipy.github.com repository (you don't need any >>>>>>>> admin rights to do that, but I also just added you to "team blog" on the >>>>>>>> github nipy org, so you can even do the merge yourself, if you want). >>>>>>>> >>>>>>>> Cheers, >>>>>>>> >>>>>>>> Ariel >>>>>>>> >>>>>>>> On Mon, Oct 26, 2015 at 12:56 PM, vanessa sochat < >>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>> >>>>>>>>> Hi Eleftherios, >>>>>>>>> >>>>>>>>> It definitely would be possible! I'm not any sort of admin in the >>>>>>>>> nipy space, so the farthest I could take it is having the repo for someone >>>>>>>>> to deploy on nipy.github.io. The code is here: >>>>>>>>> >>>>>>>>> https://github.com/vsoch/nipy-jekyll >>>>>>>>> >>>>>>>>> and deployment on my github pages: >>>>>>>>> >>>>>>>>> http://vsoch.github.io/nipy-jekyll/ >>>>>>>>> >>>>>>>>> I mostly stopped working on it because I accomplished all the >>>>>>>>> things that I set out to do (jekyll site, preview on continuous integration >>>>>>>>> with circle, standard ways to add new content, and an easy way to multiple >>>>>>>>> ways to add content a la github >>>>>>>>> , or for >>>>>>>>> those who aren't comfortable with pushing and pulling, la social >>>>>>>>> media ). I think I had suggested >>>>>>>>> moving forward for people to try out tumblr (and start contributing >>>>>>>>> content!), and if people were happy, to move it over to the nipy repo. If >>>>>>>>> the outcome of the work was not a desired solution, I was content to just >>>>>>>>> let it be. However if there is interest, that is definitely still a >>>>>>>>> possibility. >>>>>>>>> >>>>>>>>> Best, >>>>>>>>> >>>>>>>>> Vanessa >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On Mon, Oct 26, 2015 at 12:34 PM, Eleftherios Garyfallidis < >>>>>>>>> garyfallidis at gmail.com> wrote: >>>>>>>>> >>>>>>>>>> Hi Vanessa and all, >>>>>>>>>> >>>>>>>>>> Would it be possible to switch to your much nicer new website? I >>>>>>>>>> still see the older version being up. >>>>>>>>>> >>>>>>>>>> Do you have a plan for this? Or you waiting for some feedback on >>>>>>>>>> our side? >>>>>>>>>> >>>>>>>>>> Best regards, >>>>>>>>>> Eleftherios >>>>>>>>>> >>>>>>>>>> On Wed, Sep 2, 2015 at 12:57 PM, Ben Cipollini >>>>>>>>> > wrote: >>>>>>>>>> >>>>>>>>>>> I think they're good for mobile sites. I think they're generally >>>>>>>>>>> expanded by default on full screens, and compacted on mobile. So I suggest >>>>>>>>>>> to keep it, but have a regular menu that's showing on full screens and >>>>>>>>>>> hidden on mobile. >>>>>>>>>>> >>>>>>>>>>> On Wed, Sep 2, 2015 at 9:51 AM, vanessa sochat < >>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>> >>>>>>>>>>>> That's a good suggestion, and I'll add as an issue so I can >>>>>>>>>>>> find it easily when the next round of changes comes around. Generally, >>>>>>>>>>>> these "hamburger" menu things are useless functionality wise, and only >>>>>>>>>>>> serve to aesthetically "get rid of the navigation" to have a clean looking >>>>>>>>>>>> site. In our case, it is probably just annoying to have the extra clicks. >>>>>>>>>>>> >>>>>>>>>>>> On Wed, Sep 2, 2015 at 8:50 AM, Ben Cipollini < >>>>>>>>>>>> bcipolli at ucsd.edu> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> This looks great. It's also cool to see "ask a question" >>>>>>>>>>>>> integrated into the website, though we'll still have to hash things out for >>>>>>>>>>>>> that. >>>>>>>>>>>>> >>>>>>>>>>>>> Rather than open a github issue (which few may see), I'll make >>>>>>>>>>>>> a suggestion here: can we have the menu expanded by default when accessing >>>>>>>>>>>>> via a full-size screen? >>>>>>>>>>>>> >>>>>>>>>>>>> It feels odd to me to have to expand the menu in order to >>>>>>>>>>>>> navigate anywhere, by default. To me, navigation options should be obvious, >>>>>>>>>>>>> unless pressed for space. >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> On Sun, Aug 30, 2015 at 1:14 PM, vanessa sochat < >>>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Hi Everyone, >>>>>>>>>>>>>> >>>>>>>>>>>>>> I've finished work on the "contribute" page with my thinking >>>>>>>>>>>>>> for how to contribute various content: >>>>>>>>>>>>>> >>>>>>>>>>>>>> http://vsoch.github.io/nipy-jekyll/contribute.html >>>>>>>>>>>>>> >>>>>>>>>>>>>> and as an example, put up a quick blog post: >>>>>>>>>>>>>> >>>>>>>>>>>>>> http://neuroimaging.tumblr.com/ >>>>>>>>>>>>>> >>>>>>>>>>>>>> The old "example" blog posts are hidden (private) and can be >>>>>>>>>>>>>> viewed if you are a contributor. I'd like to add anyone and everyone >>>>>>>>>>>>>> interested to contribute as "official" contributors via tumblr - if you are >>>>>>>>>>>>>> interested please send me your email address. I've already invited some of >>>>>>>>>>>>>> you for which I know the email. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Best, >>>>>>>>>>>>>> >>>>>>>>>>>>>> Vanessa >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> -- >>>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>>> Stanford University >>>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>>> >>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>> 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 >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>> Stanford University >>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> 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 >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> Neuroimaging mailing list >>>>>>>>>> Neuroimaging at python.org >>>>>>>>>> https://mail.python.org/mailman/listinfo/neuroimaging >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Vanessa Villamia Sochat >>>>>>>>> Stanford University >>>>>>>>> (603) 321-0676 >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> 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 >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Vanessa Villamia Sochat >>>>>> Stanford University >>>>>> (603) 321-0676 >>>>>> >>>>>> _______________________________________________ >>>>>> 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 >>>>> >>>>> >>>> >>>> >>>> -- >>>> Vanessa Villamia Sochat >>>> Stanford University >>>> (603) 321-0676 >>>> >>> >>> >>> >>> -- >>> Vanessa Villamia Sochat >>> Stanford University >>> (603) 321-0676 >>> >>> _______________________________________________ >>> 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 >> >> > > > -- > Vanessa Villamia Sochat > Stanford University > (603) 321-0676 > -- Vanessa Villamia Sochat Stanford University (603) 321-0676 -------------- next part -------------- An HTML attachment was scrubbed... URL: From vsochat at stanford.edu Tue Oct 27 14:38:31 2015 From: vsochat at stanford.edu (vanessa sochat) Date: Tue, 27 Oct 2015 11:38:31 -0700 Subject: [Neuroimaging] Site Contributions In-Reply-To: References: Message-ID: Hi everyone, I just added the missing CNAME file, apologies for the oversight, I did not know it was there :) It looks like nipy.org is working as well now too - please let me know if you see any issues. Circle is expected to have some changes in the next week, so I am going to wait for the weekend to debug the building of artifacts. Will let you know when I fix that up! Best, Vanessa On Tue, Oct 27, 2015 at 11:30 AM, vanessa sochat wrote: > Hi Everyone, > > Site is live! > > https://nipy.github.io/ > > Ariel - I'm not sure how to set up the nipy.org. Would you mind taking a > look and fixing that up? > > Circle is having some bugs with the artifact generation, I think I can > probably fix it, but not during the work week. Ben - I added your > contribution to the README but didn't get the other comment in time. The > good news is now anyone and everyone can submit changes as PR. I encourage > everyone to familiarize yourself with tumblr, and start contributing > content, PRs to tweak it. > > Best, > > Vanessa > > On Tue, Oct 27, 2015 at 11:10 AM, vanessa sochat > wrote: > >> Got it! Thanks! :) >> >> On Tue, Oct 27, 2015 at 11:07 AM, Ariel Rokem wrote: >> >>> Hi, >>> On Tue, Oct 27, 2015 at 10:56 AM, vanessa sochat >>> wrote: >>> >>>> Hi Ariel, >>>> >>>> Please add me as an admin to nipy.github.io, so I can set up circle >>>> for CI. Thanks! >>>> >>>> >>> I believe I just did that. Let me know how you get on. >>> >>> >>>> Best, >>>> >>>> Vanessa >>>> >>>> On Tue, Oct 27, 2015 at 10:42 AM, vanessa sochat >>>> wrote: >>>> >>>>> Just as a proof of concept for adding a project - I just added a new >>>>> entry to the data file (copy pasting basically), copied one file, and the >>>>> entire process took me like, 48 seconds :) >>>>> >>>>> On Tue, Oct 27, 2015 at 10:36 AM, Ben Cipollini >>>>> wrote: >>>>> >>>>>> Thanks Vanessa! >>>>>> >>>>>> On Tue, Oct 27, 2015 at 10:35 AM, vanessa sochat < >>>>>> vsochat at stanford.edu> wrote: >>>>>> >>>>>>> I will do some tweaks and get the site working. There will be a >>>>>>> change for the URL so there might be some bugs with my initial release, but >>>>>>> I'll get it fixed asap. Will send an update later. >>>>>>> >>>>>>> On Tue, Oct 27, 2015 at 6:48 AM, Ariel Rokem >>>>>>> wrote: >>>>>>> >>>>>>>> Oh, one more: >>>>>>>> >>>>>>>> On Tue, Oct 27, 2015 at 6:40 AM, Ariel Rokem >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Hi Vanessa, >>>>>>>>> >>>>>>>>> I have a few comments/suggestions: >>>>>>>>> >>>>>>>>> 1. I would rather not have the front page be the project >>>>>>>>> directory. In my opinion, the front page should instead explain briefly >>>>>>>>> what this is, and lead visitors to the various other parts of the website. >>>>>>>>> >>>>>>>>> 2. There are a few issues with formatting in the Code of Conduct >>>>>>>>> page (bullet points appear as continued lines) >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> 3. Please include mindboggle in the project directory (it's been >>>>>>>> recently added!). >>>>>>>> >>>>>>>> >>>>>>>>> Other than these two, I think this is ready to be introduced as a >>>>>>>>> PR against the nipy/nipy.github.com repository (you don't need >>>>>>>>> any admin rights to do that, but I also just added you to "team blog" on >>>>>>>>> the github nipy org, so you can even do the merge yourself, if you want). >>>>>>>>> >>>>>>>>> Cheers, >>>>>>>>> >>>>>>>>> Ariel >>>>>>>>> >>>>>>>>> On Mon, Oct 26, 2015 at 12:56 PM, vanessa sochat < >>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>> >>>>>>>>>> Hi Eleftherios, >>>>>>>>>> >>>>>>>>>> It definitely would be possible! I'm not any sort of admin in the >>>>>>>>>> nipy space, so the farthest I could take it is having the repo for someone >>>>>>>>>> to deploy on nipy.github.io. The code is here: >>>>>>>>>> >>>>>>>>>> https://github.com/vsoch/nipy-jekyll >>>>>>>>>> >>>>>>>>>> and deployment on my github pages: >>>>>>>>>> >>>>>>>>>> http://vsoch.github.io/nipy-jekyll/ >>>>>>>>>> >>>>>>>>>> I mostly stopped working on it because I accomplished all the >>>>>>>>>> things that I set out to do (jekyll site, preview on continuous integration >>>>>>>>>> with circle, standard ways to add new content, and an easy way to multiple >>>>>>>>>> ways to add content a la github >>>>>>>>>> , or for >>>>>>>>>> those who aren't comfortable with pushing and pulling, la social >>>>>>>>>> media ). I think I had suggested >>>>>>>>>> moving forward for people to try out tumblr (and start contributing >>>>>>>>>> content!), and if people were happy, to move it over to the nipy repo. If >>>>>>>>>> the outcome of the work was not a desired solution, I was content to just >>>>>>>>>> let it be. However if there is interest, that is definitely still a >>>>>>>>>> possibility. >>>>>>>>>> >>>>>>>>>> Best, >>>>>>>>>> >>>>>>>>>> Vanessa >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Mon, Oct 26, 2015 at 12:34 PM, Eleftherios Garyfallidis < >>>>>>>>>> garyfallidis at gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> Hi Vanessa and all, >>>>>>>>>>> >>>>>>>>>>> Would it be possible to switch to your much nicer new website? I >>>>>>>>>>> still see the older version being up. >>>>>>>>>>> >>>>>>>>>>> Do you have a plan for this? Or you waiting for some feedback on >>>>>>>>>>> our side? >>>>>>>>>>> >>>>>>>>>>> Best regards, >>>>>>>>>>> Eleftherios >>>>>>>>>>> >>>>>>>>>>> On Wed, Sep 2, 2015 at 12:57 PM, Ben Cipollini < >>>>>>>>>>> bcipolli at ucsd.edu> wrote: >>>>>>>>>>> >>>>>>>>>>>> I think they're good for mobile sites. I think they're >>>>>>>>>>>> generally expanded by default on full screens, and compacted on mobile. So >>>>>>>>>>>> I suggest to keep it, but have a regular menu that's showing on full >>>>>>>>>>>> screens and hidden on mobile. >>>>>>>>>>>> >>>>>>>>>>>> On Wed, Sep 2, 2015 at 9:51 AM, vanessa sochat < >>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> That's a good suggestion, and I'll add as an issue so I can >>>>>>>>>>>>> find it easily when the next round of changes comes around. Generally, >>>>>>>>>>>>> these "hamburger" menu things are useless functionality wise, and only >>>>>>>>>>>>> serve to aesthetically "get rid of the navigation" to have a clean looking >>>>>>>>>>>>> site. In our case, it is probably just annoying to have the extra clicks. >>>>>>>>>>>>> >>>>>>>>>>>>> On Wed, Sep 2, 2015 at 8:50 AM, Ben Cipollini < >>>>>>>>>>>>> bcipolli at ucsd.edu> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> This looks great. It's also cool to see "ask a question" >>>>>>>>>>>>>> integrated into the website, though we'll still have to hash things out for >>>>>>>>>>>>>> that. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Rather than open a github issue (which few may see), I'll >>>>>>>>>>>>>> make a suggestion here: can we have the menu expanded by default when >>>>>>>>>>>>>> accessing via a full-size screen? >>>>>>>>>>>>>> >>>>>>>>>>>>>> It feels odd to me to have to expand the menu in order to >>>>>>>>>>>>>> navigate anywhere, by default. To me, navigation options should be obvious, >>>>>>>>>>>>>> unless pressed for space. >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Sun, Aug 30, 2015 at 1:14 PM, vanessa sochat < >>>>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Hi Everyone, >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> I've finished work on the "contribute" page with my thinking >>>>>>>>>>>>>>> for how to contribute various content: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> http://vsoch.github.io/nipy-jekyll/contribute.html >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> and as an example, put up a quick blog post: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> http://neuroimaging.tumblr.com/ >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> The old "example" blog posts are hidden (private) and can be >>>>>>>>>>>>>>> viewed if you are a contributor. I'd like to add anyone and everyone >>>>>>>>>>>>>>> interested to contribute as "official" contributors via tumblr - if you are >>>>>>>>>>>>>>> interested please send me your email address. I've already invited some of >>>>>>>>>>>>>>> you for which I know the email. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Best, >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Vanessa >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>>>> Stanford University >>>>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>> Stanford University >>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>> >>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>> 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 >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> Neuroimaging mailing list >>>>>>>>>>> Neuroimaging at python.org >>>>>>>>>>> https://mail.python.org/mailman/listinfo/neuroimaging >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>> Stanford University >>>>>>>>>> (603) 321-0676 >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> 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 >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Vanessa Villamia Sochat >>>>>>> Stanford University >>>>>>> (603) 321-0676 >>>>>>> >>>>>>> _______________________________________________ >>>>>>> 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 >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Vanessa Villamia Sochat >>>>> Stanford University >>>>> (603) 321-0676 >>>>> >>>> >>>> >>>> >>>> -- >>>> Vanessa Villamia Sochat >>>> Stanford University >>>> (603) 321-0676 >>>> >>>> _______________________________________________ >>>> 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 >>> >>> >> >> >> -- >> Vanessa Villamia Sochat >> Stanford University >> (603) 321-0676 >> > > > > -- > Vanessa Villamia Sochat > Stanford University > (603) 321-0676 > -- Vanessa Villamia Sochat Stanford University (603) 321-0676 -------------- next part -------------- An HTML attachment was scrubbed... URL: From arokem at gmail.com Tue Oct 27 14:40:01 2015 From: arokem at gmail.com (Ariel Rokem) Date: Tue, 27 Oct 2015 11:40:01 -0700 Subject: [Neuroimaging] Site Contributions In-Reply-To: References: Message-ID: Great work! Will resubmit my blog-post PR through the new mechanism. On Tue, Oct 27, 2015 at 11:38 AM, vanessa sochat wrote: > Hi everyone, > > I just added the missing CNAME file, apologies for the oversight, I did > not know it was there :) It looks like nipy.org is working as well now > too - please let me know if you see any issues. > > Circle is expected to have some changes in the next week, so I am going to > wait for the weekend to debug the building of artifacts. Will let you know > when I fix that up! > > Best, > > Vanessa > > On Tue, Oct 27, 2015 at 11:30 AM, vanessa sochat > wrote: > >> Hi Everyone, >> >> Site is live! >> >> https://nipy.github.io/ >> >> Ariel - I'm not sure how to set up the nipy.org. Would you mind taking a >> look and fixing that up? >> >> Circle is having some bugs with the artifact generation, I think I can >> probably fix it, but not during the work week. Ben - I added your >> contribution to the README but didn't get the other comment in time. The >> good news is now anyone and everyone can submit changes as PR. I encourage >> everyone to familiarize yourself with tumblr, and start contributing >> content, PRs to tweak it. >> >> Best, >> >> Vanessa >> >> On Tue, Oct 27, 2015 at 11:10 AM, vanessa sochat >> wrote: >> >>> Got it! Thanks! :) >>> >>> On Tue, Oct 27, 2015 at 11:07 AM, Ariel Rokem wrote: >>> >>>> Hi, >>>> On Tue, Oct 27, 2015 at 10:56 AM, vanessa sochat >>>> wrote: >>>> >>>>> Hi Ariel, >>>>> >>>>> Please add me as an admin to nipy.github.io, so I can set up circle >>>>> for CI. Thanks! >>>>> >>>>> >>>> I believe I just did that. Let me know how you get on. >>>> >>>> >>>>> Best, >>>>> >>>>> Vanessa >>>>> >>>>> On Tue, Oct 27, 2015 at 10:42 AM, vanessa sochat >>>> > wrote: >>>>> >>>>>> Just as a proof of concept for adding a project - I just added a new >>>>>> entry to the data file (copy pasting basically), copied one file, and the >>>>>> entire process took me like, 48 seconds :) >>>>>> >>>>>> On Tue, Oct 27, 2015 at 10:36 AM, Ben Cipollini >>>>>> wrote: >>>>>> >>>>>>> Thanks Vanessa! >>>>>>> >>>>>>> On Tue, Oct 27, 2015 at 10:35 AM, vanessa sochat < >>>>>>> vsochat at stanford.edu> wrote: >>>>>>> >>>>>>>> I will do some tweaks and get the site working. There will be a >>>>>>>> change for the URL so there might be some bugs with my initial release, but >>>>>>>> I'll get it fixed asap. Will send an update later. >>>>>>>> >>>>>>>> On Tue, Oct 27, 2015 at 6:48 AM, Ariel Rokem >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Oh, one more: >>>>>>>>> >>>>>>>>> On Tue, Oct 27, 2015 at 6:40 AM, Ariel Rokem >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> Hi Vanessa, >>>>>>>>>> >>>>>>>>>> I have a few comments/suggestions: >>>>>>>>>> >>>>>>>>>> 1. I would rather not have the front page be the project >>>>>>>>>> directory. In my opinion, the front page should instead explain briefly >>>>>>>>>> what this is, and lead visitors to the various other parts of the website. >>>>>>>>>> >>>>>>>>>> 2. There are a few issues with formatting in the Code of Conduct >>>>>>>>>> page (bullet points appear as continued lines) >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> 3. Please include mindboggle in the project directory (it's been >>>>>>>>> recently added!). >>>>>>>>> >>>>>>>>> >>>>>>>>>> Other than these two, I think this is ready to be introduced as a >>>>>>>>>> PR against the nipy/nipy.github.com repository (you don't need >>>>>>>>>> any admin rights to do that, but I also just added you to "team blog" on >>>>>>>>>> the github nipy org, so you can even do the merge yourself, if you want). >>>>>>>>>> >>>>>>>>>> Cheers, >>>>>>>>>> >>>>>>>>>> Ariel >>>>>>>>>> >>>>>>>>>> On Mon, Oct 26, 2015 at 12:56 PM, vanessa sochat < >>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>> >>>>>>>>>>> Hi Eleftherios, >>>>>>>>>>> >>>>>>>>>>> It definitely would be possible! I'm not any sort of admin in >>>>>>>>>>> the nipy space, so the farthest I could take it is having the repo for >>>>>>>>>>> someone to deploy on nipy.github.io. The code is here: >>>>>>>>>>> >>>>>>>>>>> https://github.com/vsoch/nipy-jekyll >>>>>>>>>>> >>>>>>>>>>> and deployment on my github pages: >>>>>>>>>>> >>>>>>>>>>> http://vsoch.github.io/nipy-jekyll/ >>>>>>>>>>> >>>>>>>>>>> I mostly stopped working on it because I accomplished all the >>>>>>>>>>> things that I set out to do (jekyll site, preview on continuous integration >>>>>>>>>>> with circle, standard ways to add new content, and an easy way to multiple >>>>>>>>>>> ways to add content a la github >>>>>>>>>>> , or for >>>>>>>>>>> those who aren't comfortable with pushing and pulling, la >>>>>>>>>>> social media ). I think I had >>>>>>>>>>> suggested moving forward for people to try out tumblr (and start >>>>>>>>>>> contributing content!), and if people were happy, to move it over to the >>>>>>>>>>> nipy repo. If the outcome of the work was not a desired solution, I was >>>>>>>>>>> content to just let it be. However if there is interest, that is definitely >>>>>>>>>>> still a possibility. >>>>>>>>>>> >>>>>>>>>>> Best, >>>>>>>>>>> >>>>>>>>>>> Vanessa >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Mon, Oct 26, 2015 at 12:34 PM, Eleftherios Garyfallidis < >>>>>>>>>>> garyfallidis at gmail.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> Hi Vanessa and all, >>>>>>>>>>>> >>>>>>>>>>>> Would it be possible to switch to your much nicer new website? >>>>>>>>>>>> I still see the older version being up. >>>>>>>>>>>> >>>>>>>>>>>> Do you have a plan for this? Or you waiting for some feedback >>>>>>>>>>>> on our side? >>>>>>>>>>>> >>>>>>>>>>>> Best regards, >>>>>>>>>>>> Eleftherios >>>>>>>>>>>> >>>>>>>>>>>> On Wed, Sep 2, 2015 at 12:57 PM, Ben Cipollini < >>>>>>>>>>>> bcipolli at ucsd.edu> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> I think they're good for mobile sites. I think they're >>>>>>>>>>>>> generally expanded by default on full screens, and compacted on mobile. So >>>>>>>>>>>>> I suggest to keep it, but have a regular menu that's showing on full >>>>>>>>>>>>> screens and hidden on mobile. >>>>>>>>>>>>> >>>>>>>>>>>>> On Wed, Sep 2, 2015 at 9:51 AM, vanessa sochat < >>>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> That's a good suggestion, and I'll add as an issue so I can >>>>>>>>>>>>>> find it easily when the next round of changes comes around. Generally, >>>>>>>>>>>>>> these "hamburger" menu things are useless functionality wise, and only >>>>>>>>>>>>>> serve to aesthetically "get rid of the navigation" to have a clean looking >>>>>>>>>>>>>> site. In our case, it is probably just annoying to have the extra clicks. >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Wed, Sep 2, 2015 at 8:50 AM, Ben Cipollini < >>>>>>>>>>>>>> bcipolli at ucsd.edu> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> This looks great. It's also cool to see "ask a question" >>>>>>>>>>>>>>> integrated into the website, though we'll still have to hash things out for >>>>>>>>>>>>>>> that. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Rather than open a github issue (which few may see), I'll >>>>>>>>>>>>>>> make a suggestion here: can we have the menu expanded by default when >>>>>>>>>>>>>>> accessing via a full-size screen? >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> It feels odd to me to have to expand the menu in order to >>>>>>>>>>>>>>> navigate anywhere, by default. To me, navigation options should be obvious, >>>>>>>>>>>>>>> unless pressed for space. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Sun, Aug 30, 2015 at 1:14 PM, vanessa sochat < >>>>>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Hi Everyone, >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> I've finished work on the "contribute" page with my >>>>>>>>>>>>>>>> thinking for how to contribute various content: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> http://vsoch.github.io/nipy-jekyll/contribute.html >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> and as an example, put up a quick blog post: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> http://neuroimaging.tumblr.com/ >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> The old "example" blog posts are hidden (private) and can >>>>>>>>>>>>>>>> be viewed if you are a contributor. I'd like to add anyone and everyone >>>>>>>>>>>>>>>> interested to contribute as "official" contributors via tumblr - if you are >>>>>>>>>>>>>>>> interested please send me your email address. I've already invited some of >>>>>>>>>>>>>>>> you for which I know the email. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Best, >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Vanessa >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>>>>> Stanford University >>>>>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> -- >>>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>>> Stanford University >>>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>>> >>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>> 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 >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> Neuroimaging mailing list >>>>>>>>>>>> Neuroimaging at python.org >>>>>>>>>>>> https://mail.python.org/mailman/listinfo/neuroimaging >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>> Stanford University >>>>>>>>>>> (603) 321-0676 >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> 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 >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Vanessa Villamia Sochat >>>>>>>> Stanford University >>>>>>>> (603) 321-0676 >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> 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 >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Vanessa Villamia Sochat >>>>>> Stanford University >>>>>> (603) 321-0676 >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Vanessa Villamia Sochat >>>>> Stanford University >>>>> (603) 321-0676 >>>>> >>>>> _______________________________________________ >>>>> 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 >>>> >>>> >>> >>> >>> -- >>> Vanessa Villamia Sochat >>> Stanford University >>> (603) 321-0676 >>> >> >> >> >> -- >> Vanessa Villamia Sochat >> Stanford University >> (603) 321-0676 >> > > > > -- > Vanessa Villamia Sochat > Stanford University > (603) 321-0676 > > _______________________________________________ > Neuroimaging mailing list > Neuroimaging at python.org > https://mail.python.org/mailman/listinfo/neuroimaging > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From garyfallidis at gmail.com Tue Oct 27 14:44:50 2015 From: garyfallidis at gmail.com (Eleftherios Garyfallidis) Date: Tue, 27 Oct 2015 14:44:50 -0400 Subject: [Neuroimaging] Site Contributions In-Reply-To: References: Message-ID: Epic awesomeness! Thank you Vanessa! On Tue, Oct 27, 2015 at 2:40 PM, Ariel Rokem wrote: > Great work! Will resubmit my blog-post PR through the new mechanism. > > On Tue, Oct 27, 2015 at 11:38 AM, vanessa sochat > wrote: > >> Hi everyone, >> >> I just added the missing CNAME file, apologies for the oversight, I did >> not know it was there :) It looks like nipy.org is working as well now >> too - please let me know if you see any issues. >> >> Circle is expected to have some changes in the next week, so I am going >> to wait for the weekend to debug the building of artifacts. Will let you >> know when I fix that up! >> >> Best, >> >> Vanessa >> >> On Tue, Oct 27, 2015 at 11:30 AM, vanessa sochat >> wrote: >> >>> Hi Everyone, >>> >>> Site is live! >>> >>> https://nipy.github.io/ >>> >>> Ariel - I'm not sure how to set up the nipy.org. Would you mind taking >>> a look and fixing that up? >>> >>> Circle is having some bugs with the artifact generation, I think I can >>> probably fix it, but not during the work week. Ben - I added your >>> contribution to the README but didn't get the other comment in time. The >>> good news is now anyone and everyone can submit changes as PR. I encourage >>> everyone to familiarize yourself with tumblr, and start contributing >>> content, PRs to tweak it. >>> >>> Best, >>> >>> Vanessa >>> >>> On Tue, Oct 27, 2015 at 11:10 AM, vanessa sochat >>> wrote: >>> >>>> Got it! Thanks! :) >>>> >>>> On Tue, Oct 27, 2015 at 11:07 AM, Ariel Rokem wrote: >>>> >>>>> Hi, >>>>> On Tue, Oct 27, 2015 at 10:56 AM, vanessa sochat >>>> > wrote: >>>>> >>>>>> Hi Ariel, >>>>>> >>>>>> Please add me as an admin to nipy.github.io, so I can set up circle >>>>>> for CI. Thanks! >>>>>> >>>>>> >>>>> I believe I just did that. Let me know how you get on. >>>>> >>>>> >>>>>> Best, >>>>>> >>>>>> Vanessa >>>>>> >>>>>> On Tue, Oct 27, 2015 at 10:42 AM, vanessa sochat < >>>>>> vsochat at stanford.edu> wrote: >>>>>> >>>>>>> Just as a proof of concept for adding a project - I just added a new >>>>>>> entry to the data file (copy pasting basically), copied one file, and the >>>>>>> entire process took me like, 48 seconds :) >>>>>>> >>>>>>> On Tue, Oct 27, 2015 at 10:36 AM, Ben Cipollini >>>>>>> wrote: >>>>>>> >>>>>>>> Thanks Vanessa! >>>>>>>> >>>>>>>> On Tue, Oct 27, 2015 at 10:35 AM, vanessa sochat < >>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>> >>>>>>>>> I will do some tweaks and get the site working. There will be a >>>>>>>>> change for the URL so there might be some bugs with my initial release, but >>>>>>>>> I'll get it fixed asap. Will send an update later. >>>>>>>>> >>>>>>>>> On Tue, Oct 27, 2015 at 6:48 AM, Ariel Rokem >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> Oh, one more: >>>>>>>>>> >>>>>>>>>> On Tue, Oct 27, 2015 at 6:40 AM, Ariel Rokem >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>>> Hi Vanessa, >>>>>>>>>>> >>>>>>>>>>> I have a few comments/suggestions: >>>>>>>>>>> >>>>>>>>>>> 1. I would rather not have the front page be the project >>>>>>>>>>> directory. In my opinion, the front page should instead explain briefly >>>>>>>>>>> what this is, and lead visitors to the various other parts of the website. >>>>>>>>>>> >>>>>>>>>>> 2. There are a few issues with formatting in the Code of Conduct >>>>>>>>>>> page (bullet points appear as continued lines) >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> 3. Please include mindboggle in the project directory (it's been >>>>>>>>>> recently added!). >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>> Other than these two, I think this is ready to be introduced as >>>>>>>>>>> a PR against the nipy/nipy.github.com repository (you don't >>>>>>>>>>> need any admin rights to do that, but I also just added you to "team blog" >>>>>>>>>>> on the github nipy org, so you can even do the merge yourself, if you want). >>>>>>>>>>> >>>>>>>>>>> Cheers, >>>>>>>>>>> >>>>>>>>>>> Ariel >>>>>>>>>>> >>>>>>>>>>> On Mon, Oct 26, 2015 at 12:56 PM, vanessa sochat < >>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>> >>>>>>>>>>>> Hi Eleftherios, >>>>>>>>>>>> >>>>>>>>>>>> It definitely would be possible! I'm not any sort of admin in >>>>>>>>>>>> the nipy space, so the farthest I could take it is having the repo for >>>>>>>>>>>> someone to deploy on nipy.github.io. The code is here: >>>>>>>>>>>> >>>>>>>>>>>> https://github.com/vsoch/nipy-jekyll >>>>>>>>>>>> >>>>>>>>>>>> and deployment on my github pages: >>>>>>>>>>>> >>>>>>>>>>>> http://vsoch.github.io/nipy-jekyll/ >>>>>>>>>>>> >>>>>>>>>>>> I mostly stopped working on it because I accomplished all the >>>>>>>>>>>> things that I set out to do (jekyll site, preview on continuous integration >>>>>>>>>>>> with circle, standard ways to add new content, and an easy way to multiple >>>>>>>>>>>> ways to add content a la github >>>>>>>>>>>> , or for >>>>>>>>>>>> those who aren't comfortable with pushing and pulling, la >>>>>>>>>>>> social media ). I think I had >>>>>>>>>>>> suggested moving forward for people to try out tumblr (and start >>>>>>>>>>>> contributing content!), and if people were happy, to move it over to the >>>>>>>>>>>> nipy repo. If the outcome of the work was not a desired solution, I was >>>>>>>>>>>> content to just let it be. However if there is interest, that is definitely >>>>>>>>>>>> still a possibility. >>>>>>>>>>>> >>>>>>>>>>>> Best, >>>>>>>>>>>> >>>>>>>>>>>> Vanessa >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Mon, Oct 26, 2015 at 12:34 PM, Eleftherios Garyfallidis < >>>>>>>>>>>> garyfallidis at gmail.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Hi Vanessa and all, >>>>>>>>>>>>> >>>>>>>>>>>>> Would it be possible to switch to your much nicer new website? >>>>>>>>>>>>> I still see the older version being up. >>>>>>>>>>>>> >>>>>>>>>>>>> Do you have a plan for this? Or you waiting for some feedback >>>>>>>>>>>>> on our side? >>>>>>>>>>>>> >>>>>>>>>>>>> Best regards, >>>>>>>>>>>>> Eleftherios >>>>>>>>>>>>> >>>>>>>>>>>>> On Wed, Sep 2, 2015 at 12:57 PM, Ben Cipollini < >>>>>>>>>>>>> bcipolli at ucsd.edu> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> I think they're good for mobile sites. I think they're >>>>>>>>>>>>>> generally expanded by default on full screens, and compacted on mobile. So >>>>>>>>>>>>>> I suggest to keep it, but have a regular menu that's showing on full >>>>>>>>>>>>>> screens and hidden on mobile. >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Wed, Sep 2, 2015 at 9:51 AM, vanessa sochat < >>>>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> That's a good suggestion, and I'll add as an issue so I can >>>>>>>>>>>>>>> find it easily when the next round of changes comes around. Generally, >>>>>>>>>>>>>>> these "hamburger" menu things are useless functionality wise, and only >>>>>>>>>>>>>>> serve to aesthetically "get rid of the navigation" to have a clean looking >>>>>>>>>>>>>>> site. In our case, it is probably just annoying to have the extra clicks. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Wed, Sep 2, 2015 at 8:50 AM, Ben Cipollini < >>>>>>>>>>>>>>> bcipolli at ucsd.edu> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> This looks great. It's also cool to see "ask a question" >>>>>>>>>>>>>>>> integrated into the website, though we'll still have to hash things out for >>>>>>>>>>>>>>>> that. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Rather than open a github issue (which few may see), I'll >>>>>>>>>>>>>>>> make a suggestion here: can we have the menu expanded by default when >>>>>>>>>>>>>>>> accessing via a full-size screen? >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> It feels odd to me to have to expand the menu in order to >>>>>>>>>>>>>>>> navigate anywhere, by default. To me, navigation options should be obvious, >>>>>>>>>>>>>>>> unless pressed for space. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Sun, Aug 30, 2015 at 1:14 PM, vanessa sochat < >>>>>>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Hi Everyone, >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> I've finished work on the "contribute" page with my >>>>>>>>>>>>>>>>> thinking for how to contribute various content: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> http://vsoch.github.io/nipy-jekyll/contribute.html >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> and as an example, put up a quick blog post: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> http://neuroimaging.tumblr.com/ >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> The old "example" blog posts are hidden (private) and can >>>>>>>>>>>>>>>>> be viewed if you are a contributor. I'd like to add anyone and everyone >>>>>>>>>>>>>>>>> interested to contribute as "official" contributors via tumblr - if you are >>>>>>>>>>>>>>>>> interested please send me your email address. I've already invited some of >>>>>>>>>>>>>>>>> you for which I know the email. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Best, >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Vanessa >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>>>>>> Stanford University >>>>>>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>>>> Stanford University >>>>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>> Neuroimaging mailing list >>>>>>>>>>>>> Neuroimaging at python.org >>>>>>>>>>>>> https://mail.python.org/mailman/listinfo/neuroimaging >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>> Stanford University >>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> 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 >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Vanessa Villamia Sochat >>>>>>>>> Stanford University >>>>>>>>> (603) 321-0676 >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> 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 >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Vanessa Villamia Sochat >>>>>>> Stanford University >>>>>>> (603) 321-0676 >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Vanessa Villamia Sochat >>>>>> Stanford University >>>>>> (603) 321-0676 >>>>>> >>>>>> _______________________________________________ >>>>>> 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 >>>>> >>>>> >>>> >>>> >>>> -- >>>> Vanessa Villamia Sochat >>>> Stanford University >>>> (603) 321-0676 >>>> >>> >>> >>> >>> -- >>> Vanessa Villamia Sochat >>> Stanford University >>> (603) 321-0676 >>> >> >> >> >> -- >> Vanessa Villamia Sochat >> Stanford University >> (603) 321-0676 >> >> _______________________________________________ >> 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: From bcipolli at ucsd.edu Tue Oct 27 13:56:21 2015 From: bcipolli at ucsd.edu (Ben Cipollini) Date: Tue, 27 Oct 2015 10:56:21 -0700 Subject: [Neuroimaging] Site Contributions In-Reply-To: References: Message-ID: Can you add me to the README.md some info about which files you touched? And where we'd define a custom logo... (if possible) Just so we can catch up to your 48 seconds... or beat it!! On Tue, Oct 27, 2015 at 10:42 AM, vanessa sochat wrote: > Just as a proof of concept for adding a project - I just added a new entry > to the data file (copy pasting basically), copied one file, and the entire > process took me like, 48 seconds :) > > On Tue, Oct 27, 2015 at 10:36 AM, Ben Cipollini wrote: > >> Thanks Vanessa! >> >> On Tue, Oct 27, 2015 at 10:35 AM, vanessa sochat >> wrote: >> >>> I will do some tweaks and get the site working. There will be a change >>> for the URL so there might be some bugs with my initial release, but I'll >>> get it fixed asap. Will send an update later. >>> >>> On Tue, Oct 27, 2015 at 6:48 AM, Ariel Rokem wrote: >>> >>>> Oh, one more: >>>> >>>> On Tue, Oct 27, 2015 at 6:40 AM, Ariel Rokem wrote: >>>> >>>>> Hi Vanessa, >>>>> >>>>> I have a few comments/suggestions: >>>>> >>>>> 1. I would rather not have the front page be the project directory. In >>>>> my opinion, the front page should instead explain briefly what this is, and >>>>> lead visitors to the various other parts of the website. >>>>> >>>>> 2. There are a few issues with formatting in the Code of Conduct page >>>>> (bullet points appear as continued lines) >>>>> >>>> >>>> >>>> 3. Please include mindboggle in the project directory (it's been >>>> recently added!). >>>> >>>> >>>>> Other than these two, I think this is ready to be introduced as a PR >>>>> against the nipy/nipy.github.com repository (you don't need any admin >>>>> rights to do that, but I also just added you to "team blog" on the github >>>>> nipy org, so you can even do the merge yourself, if you want). >>>>> >>>>> Cheers, >>>>> >>>>> Ariel >>>>> >>>>> On Mon, Oct 26, 2015 at 12:56 PM, vanessa sochat >>>> > wrote: >>>>> >>>>>> Hi Eleftherios, >>>>>> >>>>>> It definitely would be possible! I'm not any sort of admin in the >>>>>> nipy space, so the farthest I could take it is having the repo for someone >>>>>> to deploy on nipy.github.io. The code is here: >>>>>> >>>>>> https://github.com/vsoch/nipy-jekyll >>>>>> >>>>>> and deployment on my github pages: >>>>>> >>>>>> http://vsoch.github.io/nipy-jekyll/ >>>>>> >>>>>> I mostly stopped working on it because I accomplished all the things >>>>>> that I set out to do (jekyll site, preview on continuous integration with >>>>>> circle, standard ways to add new content, and an easy way to multiple >>>>>> ways to add content a la github >>>>>> , or for those >>>>>> who aren't comfortable with pushing and pulling, la social media >>>>>> ). I think I had suggested moving >>>>>> forward for people to try out tumblr (and start contributing content!), and >>>>>> if people were happy, to move it over to the nipy repo. If the outcome of >>>>>> the work was not a desired solution, I was content to just let it be. >>>>>> However if there is interest, that is definitely still a possibility. >>>>>> >>>>>> Best, >>>>>> >>>>>> Vanessa >>>>>> >>>>>> >>>>>> >>>>>> On Mon, Oct 26, 2015 at 12:34 PM, Eleftherios Garyfallidis < >>>>>> garyfallidis at gmail.com> wrote: >>>>>> >>>>>>> Hi Vanessa and all, >>>>>>> >>>>>>> Would it be possible to switch to your much nicer new website? I >>>>>>> still see the older version being up. >>>>>>> >>>>>>> Do you have a plan for this? Or you waiting for some feedback on our >>>>>>> side? >>>>>>> >>>>>>> Best regards, >>>>>>> Eleftherios >>>>>>> >>>>>>> On Wed, Sep 2, 2015 at 12:57 PM, Ben Cipollini >>>>>>> wrote: >>>>>>> >>>>>>>> I think they're good for mobile sites. I think they're generally >>>>>>>> expanded by default on full screens, and compacted on mobile. So I suggest >>>>>>>> to keep it, but have a regular menu that's showing on full screens and >>>>>>>> hidden on mobile. >>>>>>>> >>>>>>>> On Wed, Sep 2, 2015 at 9:51 AM, vanessa sochat < >>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>> >>>>>>>>> That's a good suggestion, and I'll add as an issue so I can find >>>>>>>>> it easily when the next round of changes comes around. Generally, these >>>>>>>>> "hamburger" menu things are useless functionality wise, and only serve to >>>>>>>>> aesthetically "get rid of the navigation" to have a clean looking site. In >>>>>>>>> our case, it is probably just annoying to have the extra clicks. >>>>>>>>> >>>>>>>>> On Wed, Sep 2, 2015 at 8:50 AM, Ben Cipollini >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> This looks great. It's also cool to see "ask a question" >>>>>>>>>> integrated into the website, though we'll still have to hash things out for >>>>>>>>>> that. >>>>>>>>>> >>>>>>>>>> Rather than open a github issue (which few may see), I'll make a >>>>>>>>>> suggestion here: can we have the menu expanded by default when accessing >>>>>>>>>> via a full-size screen? >>>>>>>>>> >>>>>>>>>> It feels odd to me to have to expand the menu in order to >>>>>>>>>> navigate anywhere, by default. To me, navigation options should be obvious, >>>>>>>>>> unless pressed for space. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Sun, Aug 30, 2015 at 1:14 PM, vanessa sochat < >>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>> >>>>>>>>>>> Hi Everyone, >>>>>>>>>>> >>>>>>>>>>> I've finished work on the "contribute" page with my thinking for >>>>>>>>>>> how to contribute various content: >>>>>>>>>>> >>>>>>>>>>> http://vsoch.github.io/nipy-jekyll/contribute.html >>>>>>>>>>> >>>>>>>>>>> and as an example, put up a quick blog post: >>>>>>>>>>> >>>>>>>>>>> http://neuroimaging.tumblr.com/ >>>>>>>>>>> >>>>>>>>>>> The old "example" blog posts are hidden (private) and can be >>>>>>>>>>> viewed if you are a contributor. I'd like to add anyone and everyone >>>>>>>>>>> interested to contribute as "official" contributors via tumblr - if you are >>>>>>>>>>> interested please send me your email address. I've already invited some of >>>>>>>>>>> you for which I know the email. >>>>>>>>>>> >>>>>>>>>>> Best, >>>>>>>>>>> >>>>>>>>>>> Vanessa >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>> Stanford University >>>>>>>>>>> (603) 321-0676 >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> 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 >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Vanessa Villamia Sochat >>>>>>>>> Stanford University >>>>>>>>> (603) 321-0676 >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> 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 >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Neuroimaging mailing list >>>>>>> Neuroimaging at python.org >>>>>>> https://mail.python.org/mailman/listinfo/neuroimaging >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Vanessa Villamia Sochat >>>>>> Stanford University >>>>>> (603) 321-0676 >>>>>> >>>>>> _______________________________________________ >>>>>> 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 >>>> >>>> >>> >>> >>> -- >>> Vanessa Villamia Sochat >>> Stanford University >>> (603) 321-0676 >>> >>> _______________________________________________ >>> 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 >> >> > > > -- > Vanessa Villamia Sochat > Stanford University > (603) 321-0676 > > _______________________________________________ > Neuroimaging mailing list > Neuroimaging at python.org > https://mail.python.org/mailman/listinfo/neuroimaging > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From vsochat at stanford.edu Tue Oct 27 14:54:33 2015 From: vsochat at stanford.edu (vanessa sochat) Date: Tue, 27 Oct 2015 11:54:33 -0700 Subject: [Neuroimaging] Site Contributions In-Reply-To: References: Message-ID: +1! :O) On Tue, Oct 27, 2015 at 11:44 AM, Eleftherios Garyfallidis < garyfallidis at gmail.com> wrote: > Epic awesomeness! Thank you Vanessa! > > On Tue, Oct 27, 2015 at 2:40 PM, Ariel Rokem wrote: > >> Great work! Will resubmit my blog-post PR through the new mechanism. >> >> On Tue, Oct 27, 2015 at 11:38 AM, vanessa sochat >> wrote: >> >>> Hi everyone, >>> >>> I just added the missing CNAME file, apologies for the oversight, I did >>> not know it was there :) It looks like nipy.org is working as well now >>> too - please let me know if you see any issues. >>> >>> Circle is expected to have some changes in the next week, so I am going >>> to wait for the weekend to debug the building of artifacts. Will let you >>> know when I fix that up! >>> >>> Best, >>> >>> Vanessa >>> >>> On Tue, Oct 27, 2015 at 11:30 AM, vanessa sochat >>> wrote: >>> >>>> Hi Everyone, >>>> >>>> Site is live! >>>> >>>> https://nipy.github.io/ >>>> >>>> Ariel - I'm not sure how to set up the nipy.org. Would you mind taking >>>> a look and fixing that up? >>>> >>>> Circle is having some bugs with the artifact generation, I think I can >>>> probably fix it, but not during the work week. Ben - I added your >>>> contribution to the README but didn't get the other comment in time. The >>>> good news is now anyone and everyone can submit changes as PR. I encourage >>>> everyone to familiarize yourself with tumblr, and start contributing >>>> content, PRs to tweak it. >>>> >>>> Best, >>>> >>>> Vanessa >>>> >>>> On Tue, Oct 27, 2015 at 11:10 AM, vanessa sochat >>>> wrote: >>>> >>>>> Got it! Thanks! :) >>>>> >>>>> On Tue, Oct 27, 2015 at 11:07 AM, Ariel Rokem >>>>> wrote: >>>>> >>>>>> Hi, >>>>>> On Tue, Oct 27, 2015 at 10:56 AM, vanessa sochat < >>>>>> vsochat at stanford.edu> wrote: >>>>>> >>>>>>> Hi Ariel, >>>>>>> >>>>>>> Please add me as an admin to nipy.github.io, so I can set up circle >>>>>>> for CI. Thanks! >>>>>>> >>>>>>> >>>>>> I believe I just did that. Let me know how you get on. >>>>>> >>>>>> >>>>>>> Best, >>>>>>> >>>>>>> Vanessa >>>>>>> >>>>>>> On Tue, Oct 27, 2015 at 10:42 AM, vanessa sochat < >>>>>>> vsochat at stanford.edu> wrote: >>>>>>> >>>>>>>> Just as a proof of concept for adding a project - I just added a >>>>>>>> new entry to the data file (copy pasting basically), copied one file, and >>>>>>>> the entire process took me like, 48 seconds :) >>>>>>>> >>>>>>>> On Tue, Oct 27, 2015 at 10:36 AM, Ben Cipollini >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Thanks Vanessa! >>>>>>>>> >>>>>>>>> On Tue, Oct 27, 2015 at 10:35 AM, vanessa sochat < >>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>> >>>>>>>>>> I will do some tweaks and get the site working. There will be a >>>>>>>>>> change for the URL so there might be some bugs with my initial release, but >>>>>>>>>> I'll get it fixed asap. Will send an update later. >>>>>>>>>> >>>>>>>>>> On Tue, Oct 27, 2015 at 6:48 AM, Ariel Rokem >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>>> Oh, one more: >>>>>>>>>>> >>>>>>>>>>> On Tue, Oct 27, 2015 at 6:40 AM, Ariel Rokem >>>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>>> Hi Vanessa, >>>>>>>>>>>> >>>>>>>>>>>> I have a few comments/suggestions: >>>>>>>>>>>> >>>>>>>>>>>> 1. I would rather not have the front page be the project >>>>>>>>>>>> directory. In my opinion, the front page should instead explain briefly >>>>>>>>>>>> what this is, and lead visitors to the various other parts of the website. >>>>>>>>>>>> >>>>>>>>>>>> 2. There are a few issues with formatting in the Code of >>>>>>>>>>>> Conduct page (bullet points appear as continued lines) >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> 3. Please include mindboggle in the project directory (it's been >>>>>>>>>>> recently added!). >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>> Other than these two, I think this is ready to be introduced as >>>>>>>>>>>> a PR against the nipy/nipy.github.com repository (you don't >>>>>>>>>>>> need any admin rights to do that, but I also just added you to "team blog" >>>>>>>>>>>> on the github nipy org, so you can even do the merge yourself, if you want). >>>>>>>>>>>> >>>>>>>>>>>> Cheers, >>>>>>>>>>>> >>>>>>>>>>>> Ariel >>>>>>>>>>>> >>>>>>>>>>>> On Mon, Oct 26, 2015 at 12:56 PM, vanessa sochat < >>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Hi Eleftherios, >>>>>>>>>>>>> >>>>>>>>>>>>> It definitely would be possible! I'm not any sort of admin in >>>>>>>>>>>>> the nipy space, so the farthest I could take it is having the repo for >>>>>>>>>>>>> someone to deploy on nipy.github.io. The code is here: >>>>>>>>>>>>> >>>>>>>>>>>>> https://github.com/vsoch/nipy-jekyll >>>>>>>>>>>>> >>>>>>>>>>>>> and deployment on my github pages: >>>>>>>>>>>>> >>>>>>>>>>>>> http://vsoch.github.io/nipy-jekyll/ >>>>>>>>>>>>> >>>>>>>>>>>>> I mostly stopped working on it because I accomplished all the >>>>>>>>>>>>> things that I set out to do (jekyll site, preview on continuous integration >>>>>>>>>>>>> with circle, standard ways to add new content, and an easy way to multiple >>>>>>>>>>>>> ways to add content a la github >>>>>>>>>>>>> , or for >>>>>>>>>>>>> those who aren't comfortable with pushing and pulling, la >>>>>>>>>>>>> social media ). I think I had >>>>>>>>>>>>> suggested moving forward for people to try out tumblr (and start >>>>>>>>>>>>> contributing content!), and if people were happy, to move it over to the >>>>>>>>>>>>> nipy repo. If the outcome of the work was not a desired solution, I was >>>>>>>>>>>>> content to just let it be. However if there is interest, that is definitely >>>>>>>>>>>>> still a possibility. >>>>>>>>>>>>> >>>>>>>>>>>>> Best, >>>>>>>>>>>>> >>>>>>>>>>>>> Vanessa >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> On Mon, Oct 26, 2015 at 12:34 PM, Eleftherios Garyfallidis < >>>>>>>>>>>>> garyfallidis at gmail.com> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Hi Vanessa and all, >>>>>>>>>>>>>> >>>>>>>>>>>>>> Would it be possible to switch to your much nicer new >>>>>>>>>>>>>> website? I still see the older version being up. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Do you have a plan for this? Or you waiting for some feedback >>>>>>>>>>>>>> on our side? >>>>>>>>>>>>>> >>>>>>>>>>>>>> Best regards, >>>>>>>>>>>>>> Eleftherios >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Wed, Sep 2, 2015 at 12:57 PM, Ben Cipollini < >>>>>>>>>>>>>> bcipolli at ucsd.edu> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> I think they're good for mobile sites. I think they're >>>>>>>>>>>>>>> generally expanded by default on full screens, and compacted on mobile. So >>>>>>>>>>>>>>> I suggest to keep it, but have a regular menu that's showing on full >>>>>>>>>>>>>>> screens and hidden on mobile. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Wed, Sep 2, 2015 at 9:51 AM, vanessa sochat < >>>>>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> That's a good suggestion, and I'll add as an issue so I can >>>>>>>>>>>>>>>> find it easily when the next round of changes comes around. Generally, >>>>>>>>>>>>>>>> these "hamburger" menu things are useless functionality wise, and only >>>>>>>>>>>>>>>> serve to aesthetically "get rid of the navigation" to have a clean looking >>>>>>>>>>>>>>>> site. In our case, it is probably just annoying to have the extra clicks. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Wed, Sep 2, 2015 at 8:50 AM, Ben Cipollini < >>>>>>>>>>>>>>>> bcipolli at ucsd.edu> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> This looks great. It's also cool to see "ask a question" >>>>>>>>>>>>>>>>> integrated into the website, though we'll still have to hash things out for >>>>>>>>>>>>>>>>> that. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Rather than open a github issue (which few may see), I'll >>>>>>>>>>>>>>>>> make a suggestion here: can we have the menu expanded by default when >>>>>>>>>>>>>>>>> accessing via a full-size screen? >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> It feels odd to me to have to expand the menu in order to >>>>>>>>>>>>>>>>> navigate anywhere, by default. To me, navigation options should be obvious, >>>>>>>>>>>>>>>>> unless pressed for space. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Sun, Aug 30, 2015 at 1:14 PM, vanessa sochat < >>>>>>>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Hi Everyone, >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> I've finished work on the "contribute" page with my >>>>>>>>>>>>>>>>>> thinking for how to contribute various content: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> http://vsoch.github.io/nipy-jekyll/contribute.html >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> and as an example, put up a quick blog post: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> http://neuroimaging.tumblr.com/ >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> The old "example" blog posts are hidden (private) and can >>>>>>>>>>>>>>>>>> be viewed if you are a contributor. I'd like to add anyone and everyone >>>>>>>>>>>>>>>>>> interested to contribute as "official" contributors via tumblr - if you are >>>>>>>>>>>>>>>>>> interested please send me your email address. I've already invited some of >>>>>>>>>>>>>>>>>> you for which I know the email. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Best, >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Vanessa >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>>>>>>> Stanford University >>>>>>>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>>>>> Stanford University >>>>>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>> Neuroimaging mailing list >>>>>>>>>>>>>> Neuroimaging at python.org >>>>>>>>>>>>>> https://mail.python.org/mailman/listinfo/neuroimaging >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>> Stanford University >>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>> >>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>> 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 >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>> Stanford University >>>>>>>>>> (603) 321-0676 >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> 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 >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Vanessa Villamia Sochat >>>>>>>> Stanford University >>>>>>>> (603) 321-0676 >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Vanessa Villamia Sochat >>>>>>> Stanford University >>>>>>> (603) 321-0676 >>>>>>> >>>>>>> _______________________________________________ >>>>>>> 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 >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Vanessa Villamia Sochat >>>>> Stanford University >>>>> (603) 321-0676 >>>>> >>>> >>>> >>>> >>>> -- >>>> Vanessa Villamia Sochat >>>> Stanford University >>>> (603) 321-0676 >>>> >>> >>> >>> >>> -- >>> Vanessa Villamia Sochat >>> Stanford University >>> (603) 321-0676 >>> >>> _______________________________________________ >>> 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 >> >> > > _______________________________________________ > Neuroimaging mailing list > Neuroimaging at python.org > https://mail.python.org/mailman/listinfo/neuroimaging > > -- Vanessa Villamia Sochat Stanford University (603) 321-0676 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jcohen at polymtl.ca Tue Oct 27 15:04:38 2015 From: jcohen at polymtl.ca (Julien Cohen-Adad) Date: Tue, 27 Oct 2015 15:04:38 -0400 Subject: [Neuroimaging] Site Contributions In-Reply-To: References: Message-ID: Hi everyone, would it be possible to add our neuroimaging project to the nipy website? https://github.com/neuropoly/spinalcordtoolbox it is 100% python and notably uses nibabel and dipy. cheers julien -- Julien Cohen-Adad, PhD Assistant Professor, Polytechnique Montreal Associate Director, Functional Neuroimaging Unit, University of Montreal Phone: 514 340 5121 (office: 2264); Skype: jcohenadad Web: www.neuro.polymtl.ca On Tue, Oct 27, 2015 at 2:44 PM, Eleftherios Garyfallidis < garyfallidis at gmail.com> wrote: > Epic awesomeness! Thank you Vanessa! > > On Tue, Oct 27, 2015 at 2:40 PM, Ariel Rokem wrote: > >> Great work! Will resubmit my blog-post PR through the new mechanism. >> >> On Tue, Oct 27, 2015 at 11:38 AM, vanessa sochat >> wrote: >> >>> Hi everyone, >>> >>> I just added the missing CNAME file, apologies for the oversight, I did >>> not know it was there :) It looks like nipy.org is working as well now >>> too - please let me know if you see any issues. >>> >>> Circle is expected to have some changes in the next week, so I am going >>> to wait for the weekend to debug the building of artifacts. Will let you >>> know when I fix that up! >>> >>> Best, >>> >>> Vanessa >>> >>> On Tue, Oct 27, 2015 at 11:30 AM, vanessa sochat >>> wrote: >>> >>>> Hi Everyone, >>>> >>>> Site is live! >>>> >>>> https://nipy.github.io/ >>>> >>>> Ariel - I'm not sure how to set up the nipy.org. Would you mind taking >>>> a look and fixing that up? >>>> >>>> Circle is having some bugs with the artifact generation, I think I can >>>> probably fix it, but not during the work week. Ben - I added your >>>> contribution to the README but didn't get the other comment in time. The >>>> good news is now anyone and everyone can submit changes as PR. I encourage >>>> everyone to familiarize yourself with tumblr, and start contributing >>>> content, PRs to tweak it. >>>> >>>> Best, >>>> >>>> Vanessa >>>> >>>> On Tue, Oct 27, 2015 at 11:10 AM, vanessa sochat >>>> wrote: >>>> >>>>> Got it! Thanks! :) >>>>> >>>>> On Tue, Oct 27, 2015 at 11:07 AM, Ariel Rokem >>>>> wrote: >>>>> >>>>>> Hi, >>>>>> On Tue, Oct 27, 2015 at 10:56 AM, vanessa sochat < >>>>>> vsochat at stanford.edu> wrote: >>>>>> >>>>>>> Hi Ariel, >>>>>>> >>>>>>> Please add me as an admin to nipy.github.io, so I can set up circle >>>>>>> for CI. Thanks! >>>>>>> >>>>>>> >>>>>> I believe I just did that. Let me know how you get on. >>>>>> >>>>>> >>>>>>> Best, >>>>>>> >>>>>>> Vanessa >>>>>>> >>>>>>> On Tue, Oct 27, 2015 at 10:42 AM, vanessa sochat < >>>>>>> vsochat at stanford.edu> wrote: >>>>>>> >>>>>>>> Just as a proof of concept for adding a project - I just added a >>>>>>>> new entry to the data file (copy pasting basically), copied one file, and >>>>>>>> the entire process took me like, 48 seconds :) >>>>>>>> >>>>>>>> On Tue, Oct 27, 2015 at 10:36 AM, Ben Cipollini >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Thanks Vanessa! >>>>>>>>> >>>>>>>>> On Tue, Oct 27, 2015 at 10:35 AM, vanessa sochat < >>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>> >>>>>>>>>> I will do some tweaks and get the site working. There will be a >>>>>>>>>> change for the URL so there might be some bugs with my initial release, but >>>>>>>>>> I'll get it fixed asap. Will send an update later. >>>>>>>>>> >>>>>>>>>> On Tue, Oct 27, 2015 at 6:48 AM, Ariel Rokem >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>>> Oh, one more: >>>>>>>>>>> >>>>>>>>>>> On Tue, Oct 27, 2015 at 6:40 AM, Ariel Rokem >>>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>>> Hi Vanessa, >>>>>>>>>>>> >>>>>>>>>>>> I have a few comments/suggestions: >>>>>>>>>>>> >>>>>>>>>>>> 1. I would rather not have the front page be the project >>>>>>>>>>>> directory. In my opinion, the front page should instead explain briefly >>>>>>>>>>>> what this is, and lead visitors to the various other parts of the website. >>>>>>>>>>>> >>>>>>>>>>>> 2. There are a few issues with formatting in the Code of >>>>>>>>>>>> Conduct page (bullet points appear as continued lines) >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> 3. Please include mindboggle in the project directory (it's been >>>>>>>>>>> recently added!). >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>> Other than these two, I think this is ready to be introduced as >>>>>>>>>>>> a PR against the nipy/nipy.github.com repository (you don't >>>>>>>>>>>> need any admin rights to do that, but I also just added you to "team blog" >>>>>>>>>>>> on the github nipy org, so you can even do the merge yourself, if you want). >>>>>>>>>>>> >>>>>>>>>>>> Cheers, >>>>>>>>>>>> >>>>>>>>>>>> Ariel >>>>>>>>>>>> >>>>>>>>>>>> On Mon, Oct 26, 2015 at 12:56 PM, vanessa sochat < >>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Hi Eleftherios, >>>>>>>>>>>>> >>>>>>>>>>>>> It definitely would be possible! I'm not any sort of admin in >>>>>>>>>>>>> the nipy space, so the farthest I could take it is having the repo for >>>>>>>>>>>>> someone to deploy on nipy.github.io. The code is here: >>>>>>>>>>>>> >>>>>>>>>>>>> https://github.com/vsoch/nipy-jekyll >>>>>>>>>>>>> >>>>>>>>>>>>> and deployment on my github pages: >>>>>>>>>>>>> >>>>>>>>>>>>> http://vsoch.github.io/nipy-jekyll/ >>>>>>>>>>>>> >>>>>>>>>>>>> I mostly stopped working on it because I accomplished all the >>>>>>>>>>>>> things that I set out to do (jekyll site, preview on continuous integration >>>>>>>>>>>>> with circle, standard ways to add new content, and an easy way to multiple >>>>>>>>>>>>> ways to add content a la github >>>>>>>>>>>>> , or for >>>>>>>>>>>>> those who aren't comfortable with pushing and pulling, la >>>>>>>>>>>>> social media ). I think I had >>>>>>>>>>>>> suggested moving forward for people to try out tumblr (and start >>>>>>>>>>>>> contributing content!), and if people were happy, to move it over to the >>>>>>>>>>>>> nipy repo. If the outcome of the work was not a desired solution, I was >>>>>>>>>>>>> content to just let it be. However if there is interest, that is definitely >>>>>>>>>>>>> still a possibility. >>>>>>>>>>>>> >>>>>>>>>>>>> Best, >>>>>>>>>>>>> >>>>>>>>>>>>> Vanessa >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> On Mon, Oct 26, 2015 at 12:34 PM, Eleftherios Garyfallidis < >>>>>>>>>>>>> garyfallidis at gmail.com> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Hi Vanessa and all, >>>>>>>>>>>>>> >>>>>>>>>>>>>> Would it be possible to switch to your much nicer new >>>>>>>>>>>>>> website? I still see the older version being up. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Do you have a plan for this? Or you waiting for some feedback >>>>>>>>>>>>>> on our side? >>>>>>>>>>>>>> >>>>>>>>>>>>>> Best regards, >>>>>>>>>>>>>> Eleftherios >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Wed, Sep 2, 2015 at 12:57 PM, Ben Cipollini < >>>>>>>>>>>>>> bcipolli at ucsd.edu> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> I think they're good for mobile sites. I think they're >>>>>>>>>>>>>>> generally expanded by default on full screens, and compacted on mobile. So >>>>>>>>>>>>>>> I suggest to keep it, but have a regular menu that's showing on full >>>>>>>>>>>>>>> screens and hidden on mobile. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Wed, Sep 2, 2015 at 9:51 AM, vanessa sochat < >>>>>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> That's a good suggestion, and I'll add as an issue so I can >>>>>>>>>>>>>>>> find it easily when the next round of changes comes around. Generally, >>>>>>>>>>>>>>>> these "hamburger" menu things are useless functionality wise, and only >>>>>>>>>>>>>>>> serve to aesthetically "get rid of the navigation" to have a clean looking >>>>>>>>>>>>>>>> site. In our case, it is probably just annoying to have the extra clicks. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Wed, Sep 2, 2015 at 8:50 AM, Ben Cipollini < >>>>>>>>>>>>>>>> bcipolli at ucsd.edu> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> This looks great. It's also cool to see "ask a question" >>>>>>>>>>>>>>>>> integrated into the website, though we'll still have to hash things out for >>>>>>>>>>>>>>>>> that. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Rather than open a github issue (which few may see), I'll >>>>>>>>>>>>>>>>> make a suggestion here: can we have the menu expanded by default when >>>>>>>>>>>>>>>>> accessing via a full-size screen? >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> It feels odd to me to have to expand the menu in order to >>>>>>>>>>>>>>>>> navigate anywhere, by default. To me, navigation options should be obvious, >>>>>>>>>>>>>>>>> unless pressed for space. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Sun, Aug 30, 2015 at 1:14 PM, vanessa sochat < >>>>>>>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Hi Everyone, >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> I've finished work on the "contribute" page with my >>>>>>>>>>>>>>>>>> thinking for how to contribute various content: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> http://vsoch.github.io/nipy-jekyll/contribute.html >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> and as an example, put up a quick blog post: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> http://neuroimaging.tumblr.com/ >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> The old "example" blog posts are hidden (private) and can >>>>>>>>>>>>>>>>>> be viewed if you are a contributor. I'd like to add anyone and everyone >>>>>>>>>>>>>>>>>> interested to contribute as "official" contributors via tumblr - if you are >>>>>>>>>>>>>>>>>> interested please send me your email address. I've already invited some of >>>>>>>>>>>>>>>>>> you for which I know the email. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Best, >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Vanessa >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>>>>>>> Stanford University >>>>>>>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>>>>> Stanford University >>>>>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>> Neuroimaging mailing list >>>>>>>>>>>>>> Neuroimaging at python.org >>>>>>>>>>>>>> https://mail.python.org/mailman/listinfo/neuroimaging >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>> Stanford University >>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>> >>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>> 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 >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>> Stanford University >>>>>>>>>> (603) 321-0676 >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> 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 >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Vanessa Villamia Sochat >>>>>>>> Stanford University >>>>>>>> (603) 321-0676 >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Vanessa Villamia Sochat >>>>>>> Stanford University >>>>>>> (603) 321-0676 >>>>>>> >>>>>>> _______________________________________________ >>>>>>> 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 >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Vanessa Villamia Sochat >>>>> Stanford University >>>>> (603) 321-0676 >>>>> >>>> >>>> >>>> >>>> -- >>>> Vanessa Villamia Sochat >>>> Stanford University >>>> (603) 321-0676 >>>> >>> >>> >>> >>> -- >>> Vanessa Villamia Sochat >>> Stanford University >>> (603) 321-0676 >>> >>> _______________________________________________ >>> 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 >> >> > > _______________________________________________ > Neuroimaging mailing list > Neuroimaging at python.org > https://mail.python.org/mailman/listinfo/neuroimaging > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bcipolli at ucsd.edu Tue Oct 27 14:44:02 2015 From: bcipolli at ucsd.edu (Ben Cipollini) Date: Tue, 27 Oct 2015 11:44:02 -0700 Subject: [Neuroimaging] Site Contributions In-Reply-To: References: Message-ID: Great! I'll resubmit my "issue" to the nipy repo and start "watching" it :) On Tue, Oct 27, 2015 at 11:40 AM, Ariel Rokem wrote: > Great work! Will resubmit my blog-post PR through the new mechanism. > > On Tue, Oct 27, 2015 at 11:38 AM, vanessa sochat > wrote: > >> Hi everyone, >> >> I just added the missing CNAME file, apologies for the oversight, I did >> not know it was there :) It looks like nipy.org is working as well now >> too - please let me know if you see any issues. >> >> Circle is expected to have some changes in the next week, so I am going >> to wait for the weekend to debug the building of artifacts. Will let you >> know when I fix that up! >> >> Best, >> >> Vanessa >> >> On Tue, Oct 27, 2015 at 11:30 AM, vanessa sochat >> wrote: >> >>> Hi Everyone, >>> >>> Site is live! >>> >>> https://nipy.github.io/ >>> >>> Ariel - I'm not sure how to set up the nipy.org. Would you mind taking >>> a look and fixing that up? >>> >>> Circle is having some bugs with the artifact generation, I think I can >>> probably fix it, but not during the work week. Ben - I added your >>> contribution to the README but didn't get the other comment in time. The >>> good news is now anyone and everyone can submit changes as PR. I encourage >>> everyone to familiarize yourself with tumblr, and start contributing >>> content, PRs to tweak it. >>> >>> Best, >>> >>> Vanessa >>> >>> On Tue, Oct 27, 2015 at 11:10 AM, vanessa sochat >>> wrote: >>> >>>> Got it! Thanks! :) >>>> >>>> On Tue, Oct 27, 2015 at 11:07 AM, Ariel Rokem wrote: >>>> >>>>> Hi, >>>>> On Tue, Oct 27, 2015 at 10:56 AM, vanessa sochat >>>> > wrote: >>>>> >>>>>> Hi Ariel, >>>>>> >>>>>> Please add me as an admin to nipy.github.io, so I can set up circle >>>>>> for CI. Thanks! >>>>>> >>>>>> >>>>> I believe I just did that. Let me know how you get on. >>>>> >>>>> >>>>>> Best, >>>>>> >>>>>> Vanessa >>>>>> >>>>>> On Tue, Oct 27, 2015 at 10:42 AM, vanessa sochat < >>>>>> vsochat at stanford.edu> wrote: >>>>>> >>>>>>> Just as a proof of concept for adding a project - I just added a new >>>>>>> entry to the data file (copy pasting basically), copied one file, and the >>>>>>> entire process took me like, 48 seconds :) >>>>>>> >>>>>>> On Tue, Oct 27, 2015 at 10:36 AM, Ben Cipollini >>>>>>> wrote: >>>>>>> >>>>>>>> Thanks Vanessa! >>>>>>>> >>>>>>>> On Tue, Oct 27, 2015 at 10:35 AM, vanessa sochat < >>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>> >>>>>>>>> I will do some tweaks and get the site working. There will be a >>>>>>>>> change for the URL so there might be some bugs with my initial release, but >>>>>>>>> I'll get it fixed asap. Will send an update later. >>>>>>>>> >>>>>>>>> On Tue, Oct 27, 2015 at 6:48 AM, Ariel Rokem >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> Oh, one more: >>>>>>>>>> >>>>>>>>>> On Tue, Oct 27, 2015 at 6:40 AM, Ariel Rokem >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>>> Hi Vanessa, >>>>>>>>>>> >>>>>>>>>>> I have a few comments/suggestions: >>>>>>>>>>> >>>>>>>>>>> 1. I would rather not have the front page be the project >>>>>>>>>>> directory. In my opinion, the front page should instead explain briefly >>>>>>>>>>> what this is, and lead visitors to the various other parts of the website. >>>>>>>>>>> >>>>>>>>>>> 2. There are a few issues with formatting in the Code of Conduct >>>>>>>>>>> page (bullet points appear as continued lines) >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> 3. Please include mindboggle in the project directory (it's been >>>>>>>>>> recently added!). >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>> Other than these two, I think this is ready to be introduced as >>>>>>>>>>> a PR against the nipy/nipy.github.com repository (you don't >>>>>>>>>>> need any admin rights to do that, but I also just added you to "team blog" >>>>>>>>>>> on the github nipy org, so you can even do the merge yourself, if you want). >>>>>>>>>>> >>>>>>>>>>> Cheers, >>>>>>>>>>> >>>>>>>>>>> Ariel >>>>>>>>>>> >>>>>>>>>>> On Mon, Oct 26, 2015 at 12:56 PM, vanessa sochat < >>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>> >>>>>>>>>>>> Hi Eleftherios, >>>>>>>>>>>> >>>>>>>>>>>> It definitely would be possible! I'm not any sort of admin in >>>>>>>>>>>> the nipy space, so the farthest I could take it is having the repo for >>>>>>>>>>>> someone to deploy on nipy.github.io. The code is here: >>>>>>>>>>>> >>>>>>>>>>>> https://github.com/vsoch/nipy-jekyll >>>>>>>>>>>> >>>>>>>>>>>> and deployment on my github pages: >>>>>>>>>>>> >>>>>>>>>>>> http://vsoch.github.io/nipy-jekyll/ >>>>>>>>>>>> >>>>>>>>>>>> I mostly stopped working on it because I accomplished all the >>>>>>>>>>>> things that I set out to do (jekyll site, preview on continuous integration >>>>>>>>>>>> with circle, standard ways to add new content, and an easy way to multiple >>>>>>>>>>>> ways to add content a la github >>>>>>>>>>>> , or for >>>>>>>>>>>> those who aren't comfortable with pushing and pulling, la >>>>>>>>>>>> social media ). I think I had >>>>>>>>>>>> suggested moving forward for people to try out tumblr (and start >>>>>>>>>>>> contributing content!), and if people were happy, to move it over to the >>>>>>>>>>>> nipy repo. If the outcome of the work was not a desired solution, I was >>>>>>>>>>>> content to just let it be. However if there is interest, that is definitely >>>>>>>>>>>> still a possibility. >>>>>>>>>>>> >>>>>>>>>>>> Best, >>>>>>>>>>>> >>>>>>>>>>>> Vanessa >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Mon, Oct 26, 2015 at 12:34 PM, Eleftherios Garyfallidis < >>>>>>>>>>>> garyfallidis at gmail.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Hi Vanessa and all, >>>>>>>>>>>>> >>>>>>>>>>>>> Would it be possible to switch to your much nicer new website? >>>>>>>>>>>>> I still see the older version being up. >>>>>>>>>>>>> >>>>>>>>>>>>> Do you have a plan for this? Or you waiting for some feedback >>>>>>>>>>>>> on our side? >>>>>>>>>>>>> >>>>>>>>>>>>> Best regards, >>>>>>>>>>>>> Eleftherios >>>>>>>>>>>>> >>>>>>>>>>>>> On Wed, Sep 2, 2015 at 12:57 PM, Ben Cipollini < >>>>>>>>>>>>> bcipolli at ucsd.edu> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> I think they're good for mobile sites. I think they're >>>>>>>>>>>>>> generally expanded by default on full screens, and compacted on mobile. So >>>>>>>>>>>>>> I suggest to keep it, but have a regular menu that's showing on full >>>>>>>>>>>>>> screens and hidden on mobile. >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Wed, Sep 2, 2015 at 9:51 AM, vanessa sochat < >>>>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> That's a good suggestion, and I'll add as an issue so I can >>>>>>>>>>>>>>> find it easily when the next round of changes comes around. Generally, >>>>>>>>>>>>>>> these "hamburger" menu things are useless functionality wise, and only >>>>>>>>>>>>>>> serve to aesthetically "get rid of the navigation" to have a clean looking >>>>>>>>>>>>>>> site. In our case, it is probably just annoying to have the extra clicks. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Wed, Sep 2, 2015 at 8:50 AM, Ben Cipollini < >>>>>>>>>>>>>>> bcipolli at ucsd.edu> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> This looks great. It's also cool to see "ask a question" >>>>>>>>>>>>>>>> integrated into the website, though we'll still have to hash things out for >>>>>>>>>>>>>>>> that. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Rather than open a github issue (which few may see), I'll >>>>>>>>>>>>>>>> make a suggestion here: can we have the menu expanded by default when >>>>>>>>>>>>>>>> accessing via a full-size screen? >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> It feels odd to me to have to expand the menu in order to >>>>>>>>>>>>>>>> navigate anywhere, by default. To me, navigation options should be obvious, >>>>>>>>>>>>>>>> unless pressed for space. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Sun, Aug 30, 2015 at 1:14 PM, vanessa sochat < >>>>>>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Hi Everyone, >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> I've finished work on the "contribute" page with my >>>>>>>>>>>>>>>>> thinking for how to contribute various content: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> http://vsoch.github.io/nipy-jekyll/contribute.html >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> and as an example, put up a quick blog post: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> http://neuroimaging.tumblr.com/ >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> The old "example" blog posts are hidden (private) and can >>>>>>>>>>>>>>>>> be viewed if you are a contributor. I'd like to add anyone and everyone >>>>>>>>>>>>>>>>> interested to contribute as "official" contributors via tumblr - if you are >>>>>>>>>>>>>>>>> interested please send me your email address. I've already invited some of >>>>>>>>>>>>>>>>> you for which I know the email. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Best, >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Vanessa >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>>>>>> Stanford University >>>>>>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>>>> Stanford University >>>>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>> Neuroimaging mailing list >>>>>>>>>>>>> Neuroimaging at python.org >>>>>>>>>>>>> https://mail.python.org/mailman/listinfo/neuroimaging >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>> Stanford University >>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> 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 >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Vanessa Villamia Sochat >>>>>>>>> Stanford University >>>>>>>>> (603) 321-0676 >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> 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 >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Vanessa Villamia Sochat >>>>>>> Stanford University >>>>>>> (603) 321-0676 >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Vanessa Villamia Sochat >>>>>> Stanford University >>>>>> (603) 321-0676 >>>>>> >>>>>> _______________________________________________ >>>>>> 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 >>>>> >>>>> >>>> >>>> >>>> -- >>>> Vanessa Villamia Sochat >>>> Stanford University >>>> (603) 321-0676 >>>> >>> >>> >>> >>> -- >>> Vanessa Villamia Sochat >>> Stanford University >>> (603) 321-0676 >>> >> >> >> >> -- >> Vanessa Villamia Sochat >> Stanford University >> (603) 321-0676 >> >> _______________________________________________ >> 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: From vsochat at stanford.edu Tue Oct 27 15:19:34 2015 From: vsochat at stanford.edu (vanessa sochat) Date: Tue, 27 Oct 2015 12:19:34 -0700 Subject: [Neuroimaging] Site Contributions In-Reply-To: References: Message-ID: Hey Ariel, Do we have a nipy discus? I would like to add comments to posts so we can talk about things like these: http://neuroimaging.tumblr.com/post/132031797431/write-stdout-to-file-for-fsl-cluster Best, Vanessa On Tue, Oct 27, 2015 at 11:44 AM, Ben Cipollini wrote: > Great! I'll resubmit my "issue" to the nipy repo and start "watching" it :) > > On Tue, Oct 27, 2015 at 11:40 AM, Ariel Rokem wrote: > >> Great work! Will resubmit my blog-post PR through the new mechanism. >> >> On Tue, Oct 27, 2015 at 11:38 AM, vanessa sochat >> wrote: >> >>> Hi everyone, >>> >>> I just added the missing CNAME file, apologies for the oversight, I did >>> not know it was there :) It looks like nipy.org is working as well now >>> too - please let me know if you see any issues. >>> >>> Circle is expected to have some changes in the next week, so I am going >>> to wait for the weekend to debug the building of artifacts. Will let you >>> know when I fix that up! >>> >>> Best, >>> >>> Vanessa >>> >>> On Tue, Oct 27, 2015 at 11:30 AM, vanessa sochat >>> wrote: >>> >>>> Hi Everyone, >>>> >>>> Site is live! >>>> >>>> https://nipy.github.io/ >>>> >>>> Ariel - I'm not sure how to set up the nipy.org. Would you mind taking >>>> a look and fixing that up? >>>> >>>> Circle is having some bugs with the artifact generation, I think I can >>>> probably fix it, but not during the work week. Ben - I added your >>>> contribution to the README but didn't get the other comment in time. The >>>> good news is now anyone and everyone can submit changes as PR. I encourage >>>> everyone to familiarize yourself with tumblr, and start contributing >>>> content, PRs to tweak it. >>>> >>>> Best, >>>> >>>> Vanessa >>>> >>>> On Tue, Oct 27, 2015 at 11:10 AM, vanessa sochat >>>> wrote: >>>> >>>>> Got it! Thanks! :) >>>>> >>>>> On Tue, Oct 27, 2015 at 11:07 AM, Ariel Rokem >>>>> wrote: >>>>> >>>>>> Hi, >>>>>> On Tue, Oct 27, 2015 at 10:56 AM, vanessa sochat < >>>>>> vsochat at stanford.edu> wrote: >>>>>> >>>>>>> Hi Ariel, >>>>>>> >>>>>>> Please add me as an admin to nipy.github.io, so I can set up circle >>>>>>> for CI. Thanks! >>>>>>> >>>>>>> >>>>>> I believe I just did that. Let me know how you get on. >>>>>> >>>>>> >>>>>>> Best, >>>>>>> >>>>>>> Vanessa >>>>>>> >>>>>>> On Tue, Oct 27, 2015 at 10:42 AM, vanessa sochat < >>>>>>> vsochat at stanford.edu> wrote: >>>>>>> >>>>>>>> Just as a proof of concept for adding a project - I just added a >>>>>>>> new entry to the data file (copy pasting basically), copied one file, and >>>>>>>> the entire process took me like, 48 seconds :) >>>>>>>> >>>>>>>> On Tue, Oct 27, 2015 at 10:36 AM, Ben Cipollini >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Thanks Vanessa! >>>>>>>>> >>>>>>>>> On Tue, Oct 27, 2015 at 10:35 AM, vanessa sochat < >>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>> >>>>>>>>>> I will do some tweaks and get the site working. There will be a >>>>>>>>>> change for the URL so there might be some bugs with my initial release, but >>>>>>>>>> I'll get it fixed asap. Will send an update later. >>>>>>>>>> >>>>>>>>>> On Tue, Oct 27, 2015 at 6:48 AM, Ariel Rokem >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>>> Oh, one more: >>>>>>>>>>> >>>>>>>>>>> On Tue, Oct 27, 2015 at 6:40 AM, Ariel Rokem >>>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>>> Hi Vanessa, >>>>>>>>>>>> >>>>>>>>>>>> I have a few comments/suggestions: >>>>>>>>>>>> >>>>>>>>>>>> 1. I would rather not have the front page be the project >>>>>>>>>>>> directory. In my opinion, the front page should instead explain briefly >>>>>>>>>>>> what this is, and lead visitors to the various other parts of the website. >>>>>>>>>>>> >>>>>>>>>>>> 2. There are a few issues with formatting in the Code of >>>>>>>>>>>> Conduct page (bullet points appear as continued lines) >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> 3. Please include mindboggle in the project directory (it's been >>>>>>>>>>> recently added!). >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>> Other than these two, I think this is ready to be introduced as >>>>>>>>>>>> a PR against the nipy/nipy.github.com repository (you don't >>>>>>>>>>>> need any admin rights to do that, but I also just added you to "team blog" >>>>>>>>>>>> on the github nipy org, so you can even do the merge yourself, if you want). >>>>>>>>>>>> >>>>>>>>>>>> Cheers, >>>>>>>>>>>> >>>>>>>>>>>> Ariel >>>>>>>>>>>> >>>>>>>>>>>> On Mon, Oct 26, 2015 at 12:56 PM, vanessa sochat < >>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Hi Eleftherios, >>>>>>>>>>>>> >>>>>>>>>>>>> It definitely would be possible! I'm not any sort of admin in >>>>>>>>>>>>> the nipy space, so the farthest I could take it is having the repo for >>>>>>>>>>>>> someone to deploy on nipy.github.io. The code is here: >>>>>>>>>>>>> >>>>>>>>>>>>> https://github.com/vsoch/nipy-jekyll >>>>>>>>>>>>> >>>>>>>>>>>>> and deployment on my github pages: >>>>>>>>>>>>> >>>>>>>>>>>>> http://vsoch.github.io/nipy-jekyll/ >>>>>>>>>>>>> >>>>>>>>>>>>> I mostly stopped working on it because I accomplished all the >>>>>>>>>>>>> things that I set out to do (jekyll site, preview on continuous integration >>>>>>>>>>>>> with circle, standard ways to add new content, and an easy way to multiple >>>>>>>>>>>>> ways to add content a la github >>>>>>>>>>>>> , or for >>>>>>>>>>>>> those who aren't comfortable with pushing and pulling, la >>>>>>>>>>>>> social media ). I think I had >>>>>>>>>>>>> suggested moving forward for people to try out tumblr (and start >>>>>>>>>>>>> contributing content!), and if people were happy, to move it over to the >>>>>>>>>>>>> nipy repo. If the outcome of the work was not a desired solution, I was >>>>>>>>>>>>> content to just let it be. However if there is interest, that is definitely >>>>>>>>>>>>> still a possibility. >>>>>>>>>>>>> >>>>>>>>>>>>> Best, >>>>>>>>>>>>> >>>>>>>>>>>>> Vanessa >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> On Mon, Oct 26, 2015 at 12:34 PM, Eleftherios Garyfallidis < >>>>>>>>>>>>> garyfallidis at gmail.com> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Hi Vanessa and all, >>>>>>>>>>>>>> >>>>>>>>>>>>>> Would it be possible to switch to your much nicer new >>>>>>>>>>>>>> website? I still see the older version being up. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Do you have a plan for this? Or you waiting for some feedback >>>>>>>>>>>>>> on our side? >>>>>>>>>>>>>> >>>>>>>>>>>>>> Best regards, >>>>>>>>>>>>>> Eleftherios >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Wed, Sep 2, 2015 at 12:57 PM, Ben Cipollini < >>>>>>>>>>>>>> bcipolli at ucsd.edu> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> I think they're good for mobile sites. I think they're >>>>>>>>>>>>>>> generally expanded by default on full screens, and compacted on mobile. So >>>>>>>>>>>>>>> I suggest to keep it, but have a regular menu that's showing on full >>>>>>>>>>>>>>> screens and hidden on mobile. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Wed, Sep 2, 2015 at 9:51 AM, vanessa sochat < >>>>>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> That's a good suggestion, and I'll add as an issue so I can >>>>>>>>>>>>>>>> find it easily when the next round of changes comes around. Generally, >>>>>>>>>>>>>>>> these "hamburger" menu things are useless functionality wise, and only >>>>>>>>>>>>>>>> serve to aesthetically "get rid of the navigation" to have a clean looking >>>>>>>>>>>>>>>> site. In our case, it is probably just annoying to have the extra clicks. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Wed, Sep 2, 2015 at 8:50 AM, Ben Cipollini < >>>>>>>>>>>>>>>> bcipolli at ucsd.edu> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> This looks great. It's also cool to see "ask a question" >>>>>>>>>>>>>>>>> integrated into the website, though we'll still have to hash things out for >>>>>>>>>>>>>>>>> that. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Rather than open a github issue (which few may see), I'll >>>>>>>>>>>>>>>>> make a suggestion here: can we have the menu expanded by default when >>>>>>>>>>>>>>>>> accessing via a full-size screen? >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> It feels odd to me to have to expand the menu in order to >>>>>>>>>>>>>>>>> navigate anywhere, by default. To me, navigation options should be obvious, >>>>>>>>>>>>>>>>> unless pressed for space. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Sun, Aug 30, 2015 at 1:14 PM, vanessa sochat < >>>>>>>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Hi Everyone, >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> I've finished work on the "contribute" page with my >>>>>>>>>>>>>>>>>> thinking for how to contribute various content: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> http://vsoch.github.io/nipy-jekyll/contribute.html >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> and as an example, put up a quick blog post: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> http://neuroimaging.tumblr.com/ >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> The old "example" blog posts are hidden (private) and can >>>>>>>>>>>>>>>>>> be viewed if you are a contributor. I'd like to add anyone and everyone >>>>>>>>>>>>>>>>>> interested to contribute as "official" contributors via tumblr - if you are >>>>>>>>>>>>>>>>>> interested please send me your email address. I've already invited some of >>>>>>>>>>>>>>>>>> you for which I know the email. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Best, >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Vanessa >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>>>>>>> Stanford University >>>>>>>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>>>>> Stanford University >>>>>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>> Neuroimaging mailing list >>>>>>>>>>>>>> Neuroimaging at python.org >>>>>>>>>>>>>> https://mail.python.org/mailman/listinfo/neuroimaging >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>> Stanford University >>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>> >>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>> 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 >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>> Stanford University >>>>>>>>>> (603) 321-0676 >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> 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 >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Vanessa Villamia Sochat >>>>>>>> Stanford University >>>>>>>> (603) 321-0676 >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Vanessa Villamia Sochat >>>>>>> Stanford University >>>>>>> (603) 321-0676 >>>>>>> >>>>>>> _______________________________________________ >>>>>>> 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 >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Vanessa Villamia Sochat >>>>> Stanford University >>>>> (603) 321-0676 >>>>> >>>> >>>> >>>> >>>> -- >>>> Vanessa Villamia Sochat >>>> Stanford University >>>> (603) 321-0676 >>>> >>> >>> >>> >>> -- >>> Vanessa Villamia Sochat >>> Stanford University >>> (603) 321-0676 >>> >>> _______________________________________________ >>> 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 >> >> > > _______________________________________________ > Neuroimaging mailing list > Neuroimaging at python.org > https://mail.python.org/mailman/listinfo/neuroimaging > > -- Vanessa Villamia Sochat Stanford University (603) 321-0676 -------------- next part -------------- An HTML attachment was scrubbed... URL: From bcipolli at ucsd.edu Tue Oct 27 15:31:01 2015 From: bcipolli at ucsd.edu (Ben Cipollini) Date: Tue, 27 Oct 2015 12:31:01 -0700 Subject: [Neuroimaging] Site Contributions In-Reply-To: References: Message-ID: Oh no, another place for discussion? :-/ Can we redirect them to the mailing list or neurostars? On Tue, Oct 27, 2015 at 12:19 PM, vanessa sochat wrote: > Hey Ariel, > > Do we have a nipy discus? I would like to add comments to posts so we can > talk about things like these: > > > http://neuroimaging.tumblr.com/post/132031797431/write-stdout-to-file-for-fsl-cluster > > Best, > > Vanessa > > On Tue, Oct 27, 2015 at 11:44 AM, Ben Cipollini wrote: > >> Great! I'll resubmit my "issue" to the nipy repo and start "watching" it >> :) >> >> On Tue, Oct 27, 2015 at 11:40 AM, Ariel Rokem wrote: >> >>> Great work! Will resubmit my blog-post PR through the new mechanism. >>> >>> On Tue, Oct 27, 2015 at 11:38 AM, vanessa sochat >>> wrote: >>> >>>> Hi everyone, >>>> >>>> I just added the missing CNAME file, apologies for the oversight, I did >>>> not know it was there :) It looks like nipy.org is working as well now >>>> too - please let me know if you see any issues. >>>> >>>> Circle is expected to have some changes in the next week, so I am going >>>> to wait for the weekend to debug the building of artifacts. Will let you >>>> know when I fix that up! >>>> >>>> Best, >>>> >>>> Vanessa >>>> >>>> On Tue, Oct 27, 2015 at 11:30 AM, vanessa sochat >>>> wrote: >>>> >>>>> Hi Everyone, >>>>> >>>>> Site is live! >>>>> >>>>> https://nipy.github.io/ >>>>> >>>>> Ariel - I'm not sure how to set up the nipy.org. Would you mind >>>>> taking a look and fixing that up? >>>>> >>>>> Circle is having some bugs with the artifact generation, I think I can >>>>> probably fix it, but not during the work week. Ben - I added your >>>>> contribution to the README but didn't get the other comment in time. The >>>>> good news is now anyone and everyone can submit changes as PR. I encourage >>>>> everyone to familiarize yourself with tumblr, and start contributing >>>>> content, PRs to tweak it. >>>>> >>>>> Best, >>>>> >>>>> Vanessa >>>>> >>>>> On Tue, Oct 27, 2015 at 11:10 AM, vanessa sochat >>>> > wrote: >>>>> >>>>>> Got it! Thanks! :) >>>>>> >>>>>> On Tue, Oct 27, 2015 at 11:07 AM, Ariel Rokem >>>>>> wrote: >>>>>> >>>>>>> Hi, >>>>>>> On Tue, Oct 27, 2015 at 10:56 AM, vanessa sochat < >>>>>>> vsochat at stanford.edu> wrote: >>>>>>> >>>>>>>> Hi Ariel, >>>>>>>> >>>>>>>> Please add me as an admin to nipy.github.io, so I can set up >>>>>>>> circle for CI. Thanks! >>>>>>>> >>>>>>>> >>>>>>> I believe I just did that. Let me know how you get on. >>>>>>> >>>>>>> >>>>>>>> Best, >>>>>>>> >>>>>>>> Vanessa >>>>>>>> >>>>>>>> On Tue, Oct 27, 2015 at 10:42 AM, vanessa sochat < >>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>> >>>>>>>>> Just as a proof of concept for adding a project - I just added a >>>>>>>>> new entry to the data file (copy pasting basically), copied one file, and >>>>>>>>> the entire process took me like, 48 seconds :) >>>>>>>>> >>>>>>>>> On Tue, Oct 27, 2015 at 10:36 AM, Ben Cipollini >>>>>>>> > wrote: >>>>>>>>> >>>>>>>>>> Thanks Vanessa! >>>>>>>>>> >>>>>>>>>> On Tue, Oct 27, 2015 at 10:35 AM, vanessa sochat < >>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>> >>>>>>>>>>> I will do some tweaks and get the site working. There will be a >>>>>>>>>>> change for the URL so there might be some bugs with my initial release, but >>>>>>>>>>> I'll get it fixed asap. Will send an update later. >>>>>>>>>>> >>>>>>>>>>> On Tue, Oct 27, 2015 at 6:48 AM, Ariel Rokem >>>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>>> Oh, one more: >>>>>>>>>>>> >>>>>>>>>>>> On Tue, Oct 27, 2015 at 6:40 AM, Ariel Rokem >>>>>>>>>>>> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Hi Vanessa, >>>>>>>>>>>>> >>>>>>>>>>>>> I have a few comments/suggestions: >>>>>>>>>>>>> >>>>>>>>>>>>> 1. I would rather not have the front page be the project >>>>>>>>>>>>> directory. In my opinion, the front page should instead explain briefly >>>>>>>>>>>>> what this is, and lead visitors to the various other parts of the website. >>>>>>>>>>>>> >>>>>>>>>>>>> 2. There are a few issues with formatting in the Code of >>>>>>>>>>>>> Conduct page (bullet points appear as continued lines) >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> 3. Please include mindboggle in the project directory (it's >>>>>>>>>>>> been recently added!). >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>>> Other than these two, I think this is ready to be introduced >>>>>>>>>>>>> as a PR against the nipy/nipy.github.com repository (you >>>>>>>>>>>>> don't need any admin rights to do that, but I also just added you to "team >>>>>>>>>>>>> blog" on the github nipy org, so you can even do the merge yourself, if you >>>>>>>>>>>>> want). >>>>>>>>>>>>> >>>>>>>>>>>>> Cheers, >>>>>>>>>>>>> >>>>>>>>>>>>> Ariel >>>>>>>>>>>>> >>>>>>>>>>>>> On Mon, Oct 26, 2015 at 12:56 PM, vanessa sochat < >>>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Hi Eleftherios, >>>>>>>>>>>>>> >>>>>>>>>>>>>> It definitely would be possible! I'm not any sort of admin in >>>>>>>>>>>>>> the nipy space, so the farthest I could take it is having the repo for >>>>>>>>>>>>>> someone to deploy on nipy.github.io. The code is here: >>>>>>>>>>>>>> >>>>>>>>>>>>>> https://github.com/vsoch/nipy-jekyll >>>>>>>>>>>>>> >>>>>>>>>>>>>> and deployment on my github pages: >>>>>>>>>>>>>> >>>>>>>>>>>>>> http://vsoch.github.io/nipy-jekyll/ >>>>>>>>>>>>>> >>>>>>>>>>>>>> I mostly stopped working on it because I accomplished all the >>>>>>>>>>>>>> things that I set out to do (jekyll site, preview on continuous integration >>>>>>>>>>>>>> with circle, standard ways to add new content, and an easy way to multiple >>>>>>>>>>>>>> ways to add content a la github >>>>>>>>>>>>>> , or for >>>>>>>>>>>>>> those who aren't comfortable with pushing and pulling, la >>>>>>>>>>>>>> social media ). I think I >>>>>>>>>>>>>> had suggested moving forward for people to try out tumblr (and start >>>>>>>>>>>>>> contributing content!), and if people were happy, to move it over to the >>>>>>>>>>>>>> nipy repo. If the outcome of the work was not a desired solution, I was >>>>>>>>>>>>>> content to just let it be. However if there is interest, that is definitely >>>>>>>>>>>>>> still a possibility. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Best, >>>>>>>>>>>>>> >>>>>>>>>>>>>> Vanessa >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Mon, Oct 26, 2015 at 12:34 PM, Eleftherios Garyfallidis < >>>>>>>>>>>>>> garyfallidis at gmail.com> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Hi Vanessa and all, >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Would it be possible to switch to your much nicer new >>>>>>>>>>>>>>> website? I still see the older version being up. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Do you have a plan for this? Or you waiting for some >>>>>>>>>>>>>>> feedback on our side? >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Best regards, >>>>>>>>>>>>>>> Eleftherios >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Wed, Sep 2, 2015 at 12:57 PM, Ben Cipollini < >>>>>>>>>>>>>>> bcipolli at ucsd.edu> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> I think they're good for mobile sites. I think they're >>>>>>>>>>>>>>>> generally expanded by default on full screens, and compacted on mobile. So >>>>>>>>>>>>>>>> I suggest to keep it, but have a regular menu that's showing on full >>>>>>>>>>>>>>>> screens and hidden on mobile. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Wed, Sep 2, 2015 at 9:51 AM, vanessa sochat < >>>>>>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> That's a good suggestion, and I'll add as an issue so I >>>>>>>>>>>>>>>>> can find it easily when the next round of changes comes around. Generally, >>>>>>>>>>>>>>>>> these "hamburger" menu things are useless functionality wise, and only >>>>>>>>>>>>>>>>> serve to aesthetically "get rid of the navigation" to have a clean looking >>>>>>>>>>>>>>>>> site. In our case, it is probably just annoying to have the extra clicks. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Wed, Sep 2, 2015 at 8:50 AM, Ben Cipollini < >>>>>>>>>>>>>>>>> bcipolli at ucsd.edu> wrote: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> This looks great. It's also cool to see "ask a question" >>>>>>>>>>>>>>>>>> integrated into the website, though we'll still have to hash things out for >>>>>>>>>>>>>>>>>> that. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Rather than open a github issue (which few may see), I'll >>>>>>>>>>>>>>>>>> make a suggestion here: can we have the menu expanded by default when >>>>>>>>>>>>>>>>>> accessing via a full-size screen? >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> It feels odd to me to have to expand the menu in order to >>>>>>>>>>>>>>>>>> navigate anywhere, by default. To me, navigation options should be obvious, >>>>>>>>>>>>>>>>>> unless pressed for space. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> On Sun, Aug 30, 2015 at 1:14 PM, vanessa sochat < >>>>>>>>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Hi Everyone, >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> I've finished work on the "contribute" page with my >>>>>>>>>>>>>>>>>>> thinking for how to contribute various content: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> http://vsoch.github.io/nipy-jekyll/contribute.html >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> and as an example, put up a quick blog post: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> http://neuroimaging.tumblr.com/ >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> The old "example" blog posts are hidden (private) and >>>>>>>>>>>>>>>>>>> can be viewed if you are a contributor. I'd like to add anyone and everyone >>>>>>>>>>>>>>>>>>> interested to contribute as "official" contributors via tumblr - if you are >>>>>>>>>>>>>>>>>>> interested please send me your email address. I've already invited some of >>>>>>>>>>>>>>>>>>> you for which I know the email. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Best, >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Vanessa >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>>>>>>>> Stanford University >>>>>>>>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>>>>>> Stanford University >>>>>>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>> Neuroimaging mailing list >>>>>>>>>>>>>>> Neuroimaging at python.org >>>>>>>>>>>>>>> https://mail.python.org/mailman/listinfo/neuroimaging >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> -- >>>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>>> Stanford University >>>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>>> >>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>> 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 >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>> Stanford University >>>>>>>>>>> (603) 321-0676 >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> 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 >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Vanessa Villamia Sochat >>>>>>>>> Stanford University >>>>>>>>> (603) 321-0676 >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Vanessa Villamia Sochat >>>>>>>> Stanford University >>>>>>>> (603) 321-0676 >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> 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 >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Vanessa Villamia Sochat >>>>>> Stanford University >>>>>> (603) 321-0676 >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Vanessa Villamia Sochat >>>>> Stanford University >>>>> (603) 321-0676 >>>>> >>>> >>>> >>>> >>>> -- >>>> Vanessa Villamia Sochat >>>> Stanford University >>>> (603) 321-0676 >>>> >>>> _______________________________________________ >>>> 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 >>> >>> >> >> _______________________________________________ >> Neuroimaging mailing list >> Neuroimaging at python.org >> https://mail.python.org/mailman/listinfo/neuroimaging >> >> > > > -- > Vanessa Villamia Sochat > Stanford University > (603) 321-0676 > > _______________________________________________ > Neuroimaging mailing list > Neuroimaging at python.org > https://mail.python.org/mailman/listinfo/neuroimaging > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From krzysztof.gorgolewski at gmail.com Tue Oct 27 15:35:23 2015 From: krzysztof.gorgolewski at gmail.com (Chris Filo Gorgolewski) Date: Tue, 27 Oct 2015 12:35:23 -0700 Subject: [Neuroimaging] Site Contributions In-Reply-To: References: Message-ID: I agree - let's try to direct people to neurostars.org and make improve it if needs be. On Tue, Oct 27, 2015 at 12:31 PM, Ben Cipollini wrote: > Oh no, another place for discussion? :-/ > > Can we redirect them to the mailing list or neurostars? > > On Tue, Oct 27, 2015 at 12:19 PM, vanessa sochat > wrote: > >> Hey Ariel, >> >> Do we have a nipy discus? I would like to add comments to posts so we can >> talk about things like these: >> >> >> http://neuroimaging.tumblr.com/post/132031797431/write-stdout-to-file-for-fsl-cluster >> >> Best, >> >> Vanessa >> >> On Tue, Oct 27, 2015 at 11:44 AM, Ben Cipollini >> wrote: >> >>> Great! I'll resubmit my "issue" to the nipy repo and start "watching" it >>> :) >>> >>> On Tue, Oct 27, 2015 at 11:40 AM, Ariel Rokem wrote: >>> >>>> Great work! Will resubmit my blog-post PR through the new mechanism. >>>> >>>> On Tue, Oct 27, 2015 at 11:38 AM, vanessa sochat >>>> wrote: >>>> >>>>> Hi everyone, >>>>> >>>>> I just added the missing CNAME file, apologies for the oversight, I >>>>> did not know it was there :) It looks like nipy.org is working as >>>>> well now too - please let me know if you see any issues. >>>>> >>>>> Circle is expected to have some changes in the next week, so I am >>>>> going to wait for the weekend to debug the building of artifacts. Will let >>>>> you know when I fix that up! >>>>> >>>>> Best, >>>>> >>>>> Vanessa >>>>> >>>>> On Tue, Oct 27, 2015 at 11:30 AM, vanessa sochat >>>> > wrote: >>>>> >>>>>> Hi Everyone, >>>>>> >>>>>> Site is live! >>>>>> >>>>>> https://nipy.github.io/ >>>>>> >>>>>> Ariel - I'm not sure how to set up the nipy.org. Would you mind >>>>>> taking a look and fixing that up? >>>>>> >>>>>> Circle is having some bugs with the artifact generation, I think I >>>>>> can probably fix it, but not during the work week. Ben - I added your >>>>>> contribution to the README but didn't get the other comment in time. The >>>>>> good news is now anyone and everyone can submit changes as PR. I encourage >>>>>> everyone to familiarize yourself with tumblr, and start contributing >>>>>> content, PRs to tweak it. >>>>>> >>>>>> Best, >>>>>> >>>>>> Vanessa >>>>>> >>>>>> On Tue, Oct 27, 2015 at 11:10 AM, vanessa sochat < >>>>>> vsochat at stanford.edu> wrote: >>>>>> >>>>>>> Got it! Thanks! :) >>>>>>> >>>>>>> On Tue, Oct 27, 2015 at 11:07 AM, Ariel Rokem >>>>>>> wrote: >>>>>>> >>>>>>>> Hi, >>>>>>>> On Tue, Oct 27, 2015 at 10:56 AM, vanessa sochat < >>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>> >>>>>>>>> Hi Ariel, >>>>>>>>> >>>>>>>>> Please add me as an admin to nipy.github.io, so I can set up >>>>>>>>> circle for CI. Thanks! >>>>>>>>> >>>>>>>>> >>>>>>>> I believe I just did that. Let me know how you get on. >>>>>>>> >>>>>>>> >>>>>>>>> Best, >>>>>>>>> >>>>>>>>> Vanessa >>>>>>>>> >>>>>>>>> On Tue, Oct 27, 2015 at 10:42 AM, vanessa sochat < >>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>> >>>>>>>>>> Just as a proof of concept for adding a project - I just added a >>>>>>>>>> new entry to the data file (copy pasting basically), copied one file, and >>>>>>>>>> the entire process took me like, 48 seconds :) >>>>>>>>>> >>>>>>>>>> On Tue, Oct 27, 2015 at 10:36 AM, Ben Cipollini < >>>>>>>>>> bcipolli at ucsd.edu> wrote: >>>>>>>>>> >>>>>>>>>>> Thanks Vanessa! >>>>>>>>>>> >>>>>>>>>>> On Tue, Oct 27, 2015 at 10:35 AM, vanessa sochat < >>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>> >>>>>>>>>>>> I will do some tweaks and get the site working. There will be a >>>>>>>>>>>> change for the URL so there might be some bugs with my initial release, but >>>>>>>>>>>> I'll get it fixed asap. Will send an update later. >>>>>>>>>>>> >>>>>>>>>>>> On Tue, Oct 27, 2015 at 6:48 AM, Ariel Rokem >>>>>>>>>>>> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Oh, one more: >>>>>>>>>>>>> >>>>>>>>>>>>> On Tue, Oct 27, 2015 at 6:40 AM, Ariel Rokem >>>>>>>>>>>> > wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Hi Vanessa, >>>>>>>>>>>>>> >>>>>>>>>>>>>> I have a few comments/suggestions: >>>>>>>>>>>>>> >>>>>>>>>>>>>> 1. I would rather not have the front page be the project >>>>>>>>>>>>>> directory. In my opinion, the front page should instead explain briefly >>>>>>>>>>>>>> what this is, and lead visitors to the various other parts of the website. >>>>>>>>>>>>>> >>>>>>>>>>>>>> 2. There are a few issues with formatting in the Code of >>>>>>>>>>>>>> Conduct page (bullet points appear as continued lines) >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> 3. Please include mindboggle in the project directory (it's >>>>>>>>>>>>> been recently added!). >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>>> Other than these two, I think this is ready to be introduced >>>>>>>>>>>>>> as a PR against the nipy/nipy.github.com repository (you >>>>>>>>>>>>>> don't need any admin rights to do that, but I also just added you to "team >>>>>>>>>>>>>> blog" on the github nipy org, so you can even do the merge yourself, if you >>>>>>>>>>>>>> want). >>>>>>>>>>>>>> >>>>>>>>>>>>>> Cheers, >>>>>>>>>>>>>> >>>>>>>>>>>>>> Ariel >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Mon, Oct 26, 2015 at 12:56 PM, vanessa sochat < >>>>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Hi Eleftherios, >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> It definitely would be possible! I'm not any sort of admin >>>>>>>>>>>>>>> in the nipy space, so the farthest I could take it is having the repo for >>>>>>>>>>>>>>> someone to deploy on nipy.github.io. The code is here: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> https://github.com/vsoch/nipy-jekyll >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> and deployment on my github pages: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> http://vsoch.github.io/nipy-jekyll/ >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> I mostly stopped working on it because I accomplished all >>>>>>>>>>>>>>> the things that I set out to do (jekyll site, preview on continuous >>>>>>>>>>>>>>> integration with circle, standard ways to add new content, and an easy way >>>>>>>>>>>>>>> to multiple ways to add content a la github >>>>>>>>>>>>>>> , or >>>>>>>>>>>>>>> for those who aren't comfortable with pushing and pulling, la >>>>>>>>>>>>>>> social media ). I think I >>>>>>>>>>>>>>> had suggested moving forward for people to try out tumblr (and start >>>>>>>>>>>>>>> contributing content!), and if people were happy, to move it over to the >>>>>>>>>>>>>>> nipy repo. If the outcome of the work was not a desired solution, I was >>>>>>>>>>>>>>> content to just let it be. However if there is interest, that is definitely >>>>>>>>>>>>>>> still a possibility. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Best, >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Vanessa >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Mon, Oct 26, 2015 at 12:34 PM, Eleftherios Garyfallidis < >>>>>>>>>>>>>>> garyfallidis at gmail.com> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Hi Vanessa and all, >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Would it be possible to switch to your much nicer new >>>>>>>>>>>>>>>> website? I still see the older version being up. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Do you have a plan for this? Or you waiting for some >>>>>>>>>>>>>>>> feedback on our side? >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Best regards, >>>>>>>>>>>>>>>> Eleftherios >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Wed, Sep 2, 2015 at 12:57 PM, Ben Cipollini < >>>>>>>>>>>>>>>> bcipolli at ucsd.edu> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> I think they're good for mobile sites. I think they're >>>>>>>>>>>>>>>>> generally expanded by default on full screens, and compacted on mobile. So >>>>>>>>>>>>>>>>> I suggest to keep it, but have a regular menu that's showing on full >>>>>>>>>>>>>>>>> screens and hidden on mobile. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Wed, Sep 2, 2015 at 9:51 AM, vanessa sochat < >>>>>>>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> That's a good suggestion, and I'll add as an issue so I >>>>>>>>>>>>>>>>>> can find it easily when the next round of changes comes around. Generally, >>>>>>>>>>>>>>>>>> these "hamburger" menu things are useless functionality wise, and only >>>>>>>>>>>>>>>>>> serve to aesthetically "get rid of the navigation" to have a clean looking >>>>>>>>>>>>>>>>>> site. In our case, it is probably just annoying to have the extra clicks. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> On Wed, Sep 2, 2015 at 8:50 AM, Ben Cipollini < >>>>>>>>>>>>>>>>>> bcipolli at ucsd.edu> wrote: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> This looks great. It's also cool to see "ask a question" >>>>>>>>>>>>>>>>>>> integrated into the website, though we'll still have to hash things out for >>>>>>>>>>>>>>>>>>> that. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Rather than open a github issue (which few may see), >>>>>>>>>>>>>>>>>>> I'll make a suggestion here: can we have the menu expanded by default when >>>>>>>>>>>>>>>>>>> accessing via a full-size screen? >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> It feels odd to me to have to expand the menu in order >>>>>>>>>>>>>>>>>>> to navigate anywhere, by default. To me, navigation options should be >>>>>>>>>>>>>>>>>>> obvious, unless pressed for space. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> On Sun, Aug 30, 2015 at 1:14 PM, vanessa sochat < >>>>>>>>>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Hi Everyone, >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> I've finished work on the "contribute" page with my >>>>>>>>>>>>>>>>>>>> thinking for how to contribute various content: >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> http://vsoch.github.io/nipy-jekyll/contribute.html >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> and as an example, put up a quick blog post: >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> http://neuroimaging.tumblr.com/ >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> The old "example" blog posts are hidden (private) and >>>>>>>>>>>>>>>>>>>> can be viewed if you are a contributor. I'd like to add anyone and everyone >>>>>>>>>>>>>>>>>>>> interested to contribute as "official" contributors via tumblr - if you are >>>>>>>>>>>>>>>>>>>> interested please send me your email address. I've already invited some of >>>>>>>>>>>>>>>>>>>> you for which I know the email. >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Best, >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Vanessa >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>>>>>>>>> Stanford University >>>>>>>>>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>>>>>>> Stanford University >>>>>>>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>> Neuroimaging mailing list >>>>>>>>>>>>>>>> Neuroimaging at python.org >>>>>>>>>>>>>>>> https://mail.python.org/mailman/listinfo/neuroimaging >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>>>> Stanford University >>>>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>> 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 >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>> Stanford University >>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> 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 >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>> Stanford University >>>>>>>>>> (603) 321-0676 >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Vanessa Villamia Sochat >>>>>>>>> Stanford University >>>>>>>>> (603) 321-0676 >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> 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 >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Vanessa Villamia Sochat >>>>>>> Stanford University >>>>>>> (603) 321-0676 >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Vanessa Villamia Sochat >>>>>> Stanford University >>>>>> (603) 321-0676 >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Vanessa Villamia Sochat >>>>> Stanford University >>>>> (603) 321-0676 >>>>> >>>>> _______________________________________________ >>>>> 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 >>>> >>>> >>> >>> _______________________________________________ >>> Neuroimaging mailing list >>> Neuroimaging at python.org >>> https://mail.python.org/mailman/listinfo/neuroimaging >>> >>> >> >> >> -- >> Vanessa Villamia Sochat >> Stanford University >> (603) 321-0676 >> >> _______________________________________________ >> 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: From vsochat at stanford.edu Tue Oct 27 15:38:59 2015 From: vsochat at stanford.edu (vanessa sochat) Date: Tue, 27 Oct 2015 12:38:59 -0700 Subject: [Neuroimaging] Site Contributions In-Reply-To: References: Message-ID: Sure thing. There might be a trick to integrate the two, I'll look into it. I just added comments: http://neuroimaging.tumblr.com/post/132031797431/write-stdout-to-file-for-fsl-cluster and for now I will redirect people to neurostars. Here is how to post via email: https://www.tumblr.com/docs/en/posting#emailpostheader The email for us is: [image: Inline image 1] This is so great! Anyone can contribute absolutely anything, and they don't need to know what a PR is :) On Tue, Oct 27, 2015 at 12:31 PM, Ben Cipollini wrote: > Oh no, another place for discussion? :-/ > > Can we redirect them to the mailing list or neurostars? > > On Tue, Oct 27, 2015 at 12:19 PM, vanessa sochat > wrote: > >> Hey Ariel, >> >> Do we have a nipy discus? I would like to add comments to posts so we can >> talk about things like these: >> >> >> http://neuroimaging.tumblr.com/post/132031797431/write-stdout-to-file-for-fsl-cluster >> >> Best, >> >> Vanessa >> >> On Tue, Oct 27, 2015 at 11:44 AM, Ben Cipollini >> wrote: >> >>> Great! I'll resubmit my "issue" to the nipy repo and start "watching" it >>> :) >>> >>> On Tue, Oct 27, 2015 at 11:40 AM, Ariel Rokem wrote: >>> >>>> Great work! Will resubmit my blog-post PR through the new mechanism. >>>> >>>> On Tue, Oct 27, 2015 at 11:38 AM, vanessa sochat >>>> wrote: >>>> >>>>> Hi everyone, >>>>> >>>>> I just added the missing CNAME file, apologies for the oversight, I >>>>> did not know it was there :) It looks like nipy.org is working as >>>>> well now too - please let me know if you see any issues. >>>>> >>>>> Circle is expected to have some changes in the next week, so I am >>>>> going to wait for the weekend to debug the building of artifacts. Will let >>>>> you know when I fix that up! >>>>> >>>>> Best, >>>>> >>>>> Vanessa >>>>> >>>>> On Tue, Oct 27, 2015 at 11:30 AM, vanessa sochat >>>> > wrote: >>>>> >>>>>> Hi Everyone, >>>>>> >>>>>> Site is live! >>>>>> >>>>>> https://nipy.github.io/ >>>>>> >>>>>> Ariel - I'm not sure how to set up the nipy.org. Would you mind >>>>>> taking a look and fixing that up? >>>>>> >>>>>> Circle is having some bugs with the artifact generation, I think I >>>>>> can probably fix it, but not during the work week. Ben - I added your >>>>>> contribution to the README but didn't get the other comment in time. The >>>>>> good news is now anyone and everyone can submit changes as PR. I encourage >>>>>> everyone to familiarize yourself with tumblr, and start contributing >>>>>> content, PRs to tweak it. >>>>>> >>>>>> Best, >>>>>> >>>>>> Vanessa >>>>>> >>>>>> On Tue, Oct 27, 2015 at 11:10 AM, vanessa sochat < >>>>>> vsochat at stanford.edu> wrote: >>>>>> >>>>>>> Got it! Thanks! :) >>>>>>> >>>>>>> On Tue, Oct 27, 2015 at 11:07 AM, Ariel Rokem >>>>>>> wrote: >>>>>>> >>>>>>>> Hi, >>>>>>>> On Tue, Oct 27, 2015 at 10:56 AM, vanessa sochat < >>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>> >>>>>>>>> Hi Ariel, >>>>>>>>> >>>>>>>>> Please add me as an admin to nipy.github.io, so I can set up >>>>>>>>> circle for CI. Thanks! >>>>>>>>> >>>>>>>>> >>>>>>>> I believe I just did that. Let me know how you get on. >>>>>>>> >>>>>>>> >>>>>>>>> Best, >>>>>>>>> >>>>>>>>> Vanessa >>>>>>>>> >>>>>>>>> On Tue, Oct 27, 2015 at 10:42 AM, vanessa sochat < >>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>> >>>>>>>>>> Just as a proof of concept for adding a project - I just added a >>>>>>>>>> new entry to the data file (copy pasting basically), copied one file, and >>>>>>>>>> the entire process took me like, 48 seconds :) >>>>>>>>>> >>>>>>>>>> On Tue, Oct 27, 2015 at 10:36 AM, Ben Cipollini < >>>>>>>>>> bcipolli at ucsd.edu> wrote: >>>>>>>>>> >>>>>>>>>>> Thanks Vanessa! >>>>>>>>>>> >>>>>>>>>>> On Tue, Oct 27, 2015 at 10:35 AM, vanessa sochat < >>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>> >>>>>>>>>>>> I will do some tweaks and get the site working. There will be a >>>>>>>>>>>> change for the URL so there might be some bugs with my initial release, but >>>>>>>>>>>> I'll get it fixed asap. Will send an update later. >>>>>>>>>>>> >>>>>>>>>>>> On Tue, Oct 27, 2015 at 6:48 AM, Ariel Rokem >>>>>>>>>>>> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Oh, one more: >>>>>>>>>>>>> >>>>>>>>>>>>> On Tue, Oct 27, 2015 at 6:40 AM, Ariel Rokem >>>>>>>>>>>> > wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Hi Vanessa, >>>>>>>>>>>>>> >>>>>>>>>>>>>> I have a few comments/suggestions: >>>>>>>>>>>>>> >>>>>>>>>>>>>> 1. I would rather not have the front page be the project >>>>>>>>>>>>>> directory. In my opinion, the front page should instead explain briefly >>>>>>>>>>>>>> what this is, and lead visitors to the various other parts of the website. >>>>>>>>>>>>>> >>>>>>>>>>>>>> 2. There are a few issues with formatting in the Code of >>>>>>>>>>>>>> Conduct page (bullet points appear as continued lines) >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> 3. Please include mindboggle in the project directory (it's >>>>>>>>>>>>> been recently added!). >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>>> Other than these two, I think this is ready to be introduced >>>>>>>>>>>>>> as a PR against the nipy/nipy.github.com repository (you >>>>>>>>>>>>>> don't need any admin rights to do that, but I also just added you to "team >>>>>>>>>>>>>> blog" on the github nipy org, so you can even do the merge yourself, if you >>>>>>>>>>>>>> want). >>>>>>>>>>>>>> >>>>>>>>>>>>>> Cheers, >>>>>>>>>>>>>> >>>>>>>>>>>>>> Ariel >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Mon, Oct 26, 2015 at 12:56 PM, vanessa sochat < >>>>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Hi Eleftherios, >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> It definitely would be possible! I'm not any sort of admin >>>>>>>>>>>>>>> in the nipy space, so the farthest I could take it is having the repo for >>>>>>>>>>>>>>> someone to deploy on nipy.github.io. The code is here: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> https://github.com/vsoch/nipy-jekyll >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> and deployment on my github pages: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> http://vsoch.github.io/nipy-jekyll/ >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> I mostly stopped working on it because I accomplished all >>>>>>>>>>>>>>> the things that I set out to do (jekyll site, preview on continuous >>>>>>>>>>>>>>> integration with circle, standard ways to add new content, and an easy way >>>>>>>>>>>>>>> to multiple ways to add content a la github >>>>>>>>>>>>>>> , or >>>>>>>>>>>>>>> for those who aren't comfortable with pushing and pulling, la >>>>>>>>>>>>>>> social media ). I think I >>>>>>>>>>>>>>> had suggested moving forward for people to try out tumblr (and start >>>>>>>>>>>>>>> contributing content!), and if people were happy, to move it over to the >>>>>>>>>>>>>>> nipy repo. If the outcome of the work was not a desired solution, I was >>>>>>>>>>>>>>> content to just let it be. However if there is interest, that is definitely >>>>>>>>>>>>>>> still a possibility. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Best, >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Vanessa >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Mon, Oct 26, 2015 at 12:34 PM, Eleftherios Garyfallidis < >>>>>>>>>>>>>>> garyfallidis at gmail.com> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Hi Vanessa and all, >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Would it be possible to switch to your much nicer new >>>>>>>>>>>>>>>> website? I still see the older version being up. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Do you have a plan for this? Or you waiting for some >>>>>>>>>>>>>>>> feedback on our side? >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Best regards, >>>>>>>>>>>>>>>> Eleftherios >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Wed, Sep 2, 2015 at 12:57 PM, Ben Cipollini < >>>>>>>>>>>>>>>> bcipolli at ucsd.edu> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> I think they're good for mobile sites. I think they're >>>>>>>>>>>>>>>>> generally expanded by default on full screens, and compacted on mobile. So >>>>>>>>>>>>>>>>> I suggest to keep it, but have a regular menu that's showing on full >>>>>>>>>>>>>>>>> screens and hidden on mobile. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Wed, Sep 2, 2015 at 9:51 AM, vanessa sochat < >>>>>>>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> That's a good suggestion, and I'll add as an issue so I >>>>>>>>>>>>>>>>>> can find it easily when the next round of changes comes around. Generally, >>>>>>>>>>>>>>>>>> these "hamburger" menu things are useless functionality wise, and only >>>>>>>>>>>>>>>>>> serve to aesthetically "get rid of the navigation" to have a clean looking >>>>>>>>>>>>>>>>>> site. In our case, it is probably just annoying to have the extra clicks. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> On Wed, Sep 2, 2015 at 8:50 AM, Ben Cipollini < >>>>>>>>>>>>>>>>>> bcipolli at ucsd.edu> wrote: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> This looks great. It's also cool to see "ask a question" >>>>>>>>>>>>>>>>>>> integrated into the website, though we'll still have to hash things out for >>>>>>>>>>>>>>>>>>> that. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Rather than open a github issue (which few may see), >>>>>>>>>>>>>>>>>>> I'll make a suggestion here: can we have the menu expanded by default when >>>>>>>>>>>>>>>>>>> accessing via a full-size screen? >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> It feels odd to me to have to expand the menu in order >>>>>>>>>>>>>>>>>>> to navigate anywhere, by default. To me, navigation options should be >>>>>>>>>>>>>>>>>>> obvious, unless pressed for space. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> On Sun, Aug 30, 2015 at 1:14 PM, vanessa sochat < >>>>>>>>>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Hi Everyone, >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> I've finished work on the "contribute" page with my >>>>>>>>>>>>>>>>>>>> thinking for how to contribute various content: >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> http://vsoch.github.io/nipy-jekyll/contribute.html >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> and as an example, put up a quick blog post: >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> http://neuroimaging.tumblr.com/ >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> The old "example" blog posts are hidden (private) and >>>>>>>>>>>>>>>>>>>> can be viewed if you are a contributor. I'd like to add anyone and everyone >>>>>>>>>>>>>>>>>>>> interested to contribute as "official" contributors via tumblr - if you are >>>>>>>>>>>>>>>>>>>> interested please send me your email address. I've already invited some of >>>>>>>>>>>>>>>>>>>> you for which I know the email. >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Best, >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Vanessa >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>>>>>>>>> Stanford University >>>>>>>>>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>>>>>>> Stanford University >>>>>>>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>> Neuroimaging mailing list >>>>>>>>>>>>>>>> Neuroimaging at python.org >>>>>>>>>>>>>>>> https://mail.python.org/mailman/listinfo/neuroimaging >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>>>> Stanford University >>>>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>> 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 >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>> Stanford University >>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> 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 >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>> Stanford University >>>>>>>>>> (603) 321-0676 >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Vanessa Villamia Sochat >>>>>>>>> Stanford University >>>>>>>>> (603) 321-0676 >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> 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 >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Vanessa Villamia Sochat >>>>>>> Stanford University >>>>>>> (603) 321-0676 >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Vanessa Villamia Sochat >>>>>> Stanford University >>>>>> (603) 321-0676 >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Vanessa Villamia Sochat >>>>> Stanford University >>>>> (603) 321-0676 >>>>> >>>>> _______________________________________________ >>>>> 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 >>>> >>>> >>> >>> _______________________________________________ >>> Neuroimaging mailing list >>> Neuroimaging at python.org >>> https://mail.python.org/mailman/listinfo/neuroimaging >>> >>> >> >> >> -- >> Vanessa Villamia Sochat >> Stanford University >> (603) 321-0676 >> >> _______________________________________________ >> 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 > > -- Vanessa Villamia Sochat Stanford University (603) 321-0676 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 5337 bytes Desc: not available URL: From vsochat at stanford.edu Tue Oct 27 15:29:20 2015 From: vsochat at stanford.edu (vanessa sochat) Date: Tue, 27 Oct 2015 12:29:20 -0700 Subject: [Neuroimaging] Site Contributions In-Reply-To: References: Message-ID: nevermind found it :) https://github.com/arokem/nipy.github.com/blob/master/_config.yml#L33 -------------- next part -------------- An HTML attachment was scrubbed... URL: From vsochat at stanford.edu Tue Oct 27 15:46:26 2015 From: vsochat at stanford.edu (vanessa sochat) Date: Tue, 27 Oct 2015 12:46:26 -0700 Subject: [Neuroimaging] Site Contributions In-Reply-To: References: Message-ID: Do we have a nipy twitter? it would be good to push the blog posts right into the twitter-verse. On Tue, Oct 27, 2015 at 12:38 PM, vanessa sochat wrote: > Sure thing. There might be a trick to integrate the two, I'll look into > it. I just added comments: > > > http://neuroimaging.tumblr.com/post/132031797431/write-stdout-to-file-for-fsl-cluster > > and for now I will redirect people to neurostars. > > Here is how to post via email: > > https://www.tumblr.com/docs/en/posting#emailpostheader > > The email for us is: > > [image: Inline image 1] > > This is so great! Anyone can contribute absolutely anything, and they > don't need to know what a PR is :) > > On Tue, Oct 27, 2015 at 12:31 PM, Ben Cipollini wrote: > >> Oh no, another place for discussion? :-/ >> >> Can we redirect them to the mailing list or neurostars? >> >> On Tue, Oct 27, 2015 at 12:19 PM, vanessa sochat >> wrote: >> >>> Hey Ariel, >>> >>> Do we have a nipy discus? I would like to add comments to posts so we >>> can talk about things like these: >>> >>> >>> http://neuroimaging.tumblr.com/post/132031797431/write-stdout-to-file-for-fsl-cluster >>> >>> Best, >>> >>> Vanessa >>> >>> On Tue, Oct 27, 2015 at 11:44 AM, Ben Cipollini >>> wrote: >>> >>>> Great! I'll resubmit my "issue" to the nipy repo and start "watching" >>>> it :) >>>> >>>> On Tue, Oct 27, 2015 at 11:40 AM, Ariel Rokem wrote: >>>> >>>>> Great work! Will resubmit my blog-post PR through the new mechanism. >>>>> >>>>> On Tue, Oct 27, 2015 at 11:38 AM, vanessa sochat >>>> > wrote: >>>>> >>>>>> Hi everyone, >>>>>> >>>>>> I just added the missing CNAME file, apologies for the oversight, I >>>>>> did not know it was there :) It looks like nipy.org is working as >>>>>> well now too - please let me know if you see any issues. >>>>>> >>>>>> Circle is expected to have some changes in the next week, so I am >>>>>> going to wait for the weekend to debug the building of artifacts. Will let >>>>>> you know when I fix that up! >>>>>> >>>>>> Best, >>>>>> >>>>>> Vanessa >>>>>> >>>>>> On Tue, Oct 27, 2015 at 11:30 AM, vanessa sochat < >>>>>> vsochat at stanford.edu> wrote: >>>>>> >>>>>>> Hi Everyone, >>>>>>> >>>>>>> Site is live! >>>>>>> >>>>>>> https://nipy.github.io/ >>>>>>> >>>>>>> Ariel - I'm not sure how to set up the nipy.org. Would you mind >>>>>>> taking a look and fixing that up? >>>>>>> >>>>>>> Circle is having some bugs with the artifact generation, I think I >>>>>>> can probably fix it, but not during the work week. Ben - I added your >>>>>>> contribution to the README but didn't get the other comment in time. The >>>>>>> good news is now anyone and everyone can submit changes as PR. I encourage >>>>>>> everyone to familiarize yourself with tumblr, and start contributing >>>>>>> content, PRs to tweak it. >>>>>>> >>>>>>> Best, >>>>>>> >>>>>>> Vanessa >>>>>>> >>>>>>> On Tue, Oct 27, 2015 at 11:10 AM, vanessa sochat < >>>>>>> vsochat at stanford.edu> wrote: >>>>>>> >>>>>>>> Got it! Thanks! :) >>>>>>>> >>>>>>>> On Tue, Oct 27, 2015 at 11:07 AM, Ariel Rokem >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Hi, >>>>>>>>> On Tue, Oct 27, 2015 at 10:56 AM, vanessa sochat < >>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>> >>>>>>>>>> Hi Ariel, >>>>>>>>>> >>>>>>>>>> Please add me as an admin to nipy.github.io, so I can set up >>>>>>>>>> circle for CI. Thanks! >>>>>>>>>> >>>>>>>>>> >>>>>>>>> I believe I just did that. Let me know how you get on. >>>>>>>>> >>>>>>>>> >>>>>>>>>> Best, >>>>>>>>>> >>>>>>>>>> Vanessa >>>>>>>>>> >>>>>>>>>> On Tue, Oct 27, 2015 at 10:42 AM, vanessa sochat < >>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>> >>>>>>>>>>> Just as a proof of concept for adding a project - I just added a >>>>>>>>>>> new entry to the data file (copy pasting basically), copied one file, and >>>>>>>>>>> the entire process took me like, 48 seconds :) >>>>>>>>>>> >>>>>>>>>>> On Tue, Oct 27, 2015 at 10:36 AM, Ben Cipollini < >>>>>>>>>>> bcipolli at ucsd.edu> wrote: >>>>>>>>>>> >>>>>>>>>>>> Thanks Vanessa! >>>>>>>>>>>> >>>>>>>>>>>> On Tue, Oct 27, 2015 at 10:35 AM, vanessa sochat < >>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> I will do some tweaks and get the site working. There will be >>>>>>>>>>>>> a change for the URL so there might be some bugs with my initial release, >>>>>>>>>>>>> but I'll get it fixed asap. Will send an update later. >>>>>>>>>>>>> >>>>>>>>>>>>> On Tue, Oct 27, 2015 at 6:48 AM, Ariel Rokem >>>>>>>>>>>> > wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Oh, one more: >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Tue, Oct 27, 2015 at 6:40 AM, Ariel Rokem < >>>>>>>>>>>>>> arokem at gmail.com> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Hi Vanessa, >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> I have a few comments/suggestions: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> 1. I would rather not have the front page be the project >>>>>>>>>>>>>>> directory. In my opinion, the front page should instead explain briefly >>>>>>>>>>>>>>> what this is, and lead visitors to the various other parts of the website. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> 2. There are a few issues with formatting in the Code of >>>>>>>>>>>>>>> Conduct page (bullet points appear as continued lines) >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> 3. Please include mindboggle in the project directory (it's >>>>>>>>>>>>>> been recently added!). >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Other than these two, I think this is ready to be introduced >>>>>>>>>>>>>>> as a PR against the nipy/nipy.github.com repository (you >>>>>>>>>>>>>>> don't need any admin rights to do that, but I also just added you to "team >>>>>>>>>>>>>>> blog" on the github nipy org, so you can even do the merge yourself, if you >>>>>>>>>>>>>>> want). >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Cheers, >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Ariel >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Mon, Oct 26, 2015 at 12:56 PM, vanessa sochat < >>>>>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Hi Eleftherios, >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> It definitely would be possible! I'm not any sort of admin >>>>>>>>>>>>>>>> in the nipy space, so the farthest I could take it is having the repo for >>>>>>>>>>>>>>>> someone to deploy on nipy.github.io. The code is here: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> https://github.com/vsoch/nipy-jekyll >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> and deployment on my github pages: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> http://vsoch.github.io/nipy-jekyll/ >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> I mostly stopped working on it because I accomplished all >>>>>>>>>>>>>>>> the things that I set out to do (jekyll site, preview on continuous >>>>>>>>>>>>>>>> integration with circle, standard ways to add new content, and an easy way >>>>>>>>>>>>>>>> to multiple ways to add content a la github >>>>>>>>>>>>>>>> , or >>>>>>>>>>>>>>>> for those who aren't comfortable with pushing and pulling, la >>>>>>>>>>>>>>>> social media ). I think I >>>>>>>>>>>>>>>> had suggested moving forward for people to try out tumblr (and start >>>>>>>>>>>>>>>> contributing content!), and if people were happy, to move it over to the >>>>>>>>>>>>>>>> nipy repo. If the outcome of the work was not a desired solution, I was >>>>>>>>>>>>>>>> content to just let it be. However if there is interest, that is definitely >>>>>>>>>>>>>>>> still a possibility. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Best, >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Vanessa >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Mon, Oct 26, 2015 at 12:34 PM, Eleftherios Garyfallidis >>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Hi Vanessa and all, >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Would it be possible to switch to your much nicer new >>>>>>>>>>>>>>>>> website? I still see the older version being up. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Do you have a plan for this? Or you waiting for some >>>>>>>>>>>>>>>>> feedback on our side? >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Best regards, >>>>>>>>>>>>>>>>> Eleftherios >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Wed, Sep 2, 2015 at 12:57 PM, Ben Cipollini < >>>>>>>>>>>>>>>>> bcipolli at ucsd.edu> wrote: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> I think they're good for mobile sites. I think they're >>>>>>>>>>>>>>>>>> generally expanded by default on full screens, and compacted on mobile. So >>>>>>>>>>>>>>>>>> I suggest to keep it, but have a regular menu that's showing on full >>>>>>>>>>>>>>>>>> screens and hidden on mobile. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> On Wed, Sep 2, 2015 at 9:51 AM, vanessa sochat < >>>>>>>>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> That's a good suggestion, and I'll add as an issue so I >>>>>>>>>>>>>>>>>>> can find it easily when the next round of changes comes around. Generally, >>>>>>>>>>>>>>>>>>> these "hamburger" menu things are useless functionality wise, and only >>>>>>>>>>>>>>>>>>> serve to aesthetically "get rid of the navigation" to have a clean looking >>>>>>>>>>>>>>>>>>> site. In our case, it is probably just annoying to have the extra clicks. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> On Wed, Sep 2, 2015 at 8:50 AM, Ben Cipollini < >>>>>>>>>>>>>>>>>>> bcipolli at ucsd.edu> wrote: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> This looks great. It's also cool to see "ask a >>>>>>>>>>>>>>>>>>>> question" integrated into the website, though we'll still have to hash >>>>>>>>>>>>>>>>>>>> things out for that. >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Rather than open a github issue (which few may see), >>>>>>>>>>>>>>>>>>>> I'll make a suggestion here: can we have the menu expanded by default when >>>>>>>>>>>>>>>>>>>> accessing via a full-size screen? >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> It feels odd to me to have to expand the menu in order >>>>>>>>>>>>>>>>>>>> to navigate anywhere, by default. To me, navigation options should be >>>>>>>>>>>>>>>>>>>> obvious, unless pressed for space. >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> On Sun, Aug 30, 2015 at 1:14 PM, vanessa sochat < >>>>>>>>>>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> Hi Everyone, >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> I've finished work on the "contribute" page with my >>>>>>>>>>>>>>>>>>>>> thinking for how to contribute various content: >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> http://vsoch.github.io/nipy-jekyll/contribute.html >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> and as an example, put up a quick blog post: >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> http://neuroimaging.tumblr.com/ >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> The old "example" blog posts are hidden (private) and >>>>>>>>>>>>>>>>>>>>> can be viewed if you are a contributor. I'd like to add anyone and everyone >>>>>>>>>>>>>>>>>>>>> interested to contribute as "official" contributors via tumblr - if you are >>>>>>>>>>>>>>>>>>>>> interested please send me your email address. I've already invited some of >>>>>>>>>>>>>>>>>>>>> you for which I know the email. >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> Best, >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> Vanessa >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>>>>>>>>>> Stanford University >>>>>>>>>>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>>>>>>>> Stanford University >>>>>>>>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>> Neuroimaging mailing list >>>>>>>>>>>>>>>>> Neuroimaging at python.org >>>>>>>>>>>>>>>>> https://mail.python.org/mailman/listinfo/neuroimaging >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>>>>> Stanford University >>>>>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>> Stanford University >>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>> >>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>> 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 >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>> Stanford University >>>>>>>>>>> (603) 321-0676 >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>> Stanford University >>>>>>>>>> (603) 321-0676 >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> 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 >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Vanessa Villamia Sochat >>>>>>>> Stanford University >>>>>>>> (603) 321-0676 >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Vanessa Villamia Sochat >>>>>>> Stanford University >>>>>>> (603) 321-0676 >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Vanessa Villamia Sochat >>>>>> Stanford University >>>>>> (603) 321-0676 >>>>>> >>>>>> _______________________________________________ >>>>>> 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 >>>>> >>>>> >>>> >>>> _______________________________________________ >>>> Neuroimaging mailing list >>>> Neuroimaging at python.org >>>> https://mail.python.org/mailman/listinfo/neuroimaging >>>> >>>> >>> >>> >>> -- >>> Vanessa Villamia Sochat >>> Stanford University >>> (603) 321-0676 >>> >>> _______________________________________________ >>> 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 >> >> > > > -- > Vanessa Villamia Sochat > Stanford University > (603) 321-0676 > -- Vanessa Villamia Sochat Stanford University (603) 321-0676 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 5337 bytes Desc: not available URL: From krzysztof.gorgolewski at gmail.com Tue Oct 27 15:47:30 2015 From: krzysztof.gorgolewski at gmail.com (Chris Filo Gorgolewski) Date: Tue, 27 Oct 2015 12:47:30 -0700 Subject: [Neuroimaging] Site Contributions In-Reply-To: References: Message-ID: neurostars is based on biostars and provide a variety of ways to integrate sources. Satra and Roman will know more. Best, Chris On Tue, Oct 27, 2015 at 12:38 PM, vanessa sochat wrote: > Sure thing. There might be a trick to integrate the two, I'll look into > it. I just added comments: > > > http://neuroimaging.tumblr.com/post/132031797431/write-stdout-to-file-for-fsl-cluster > > and for now I will redirect people to neurostars. > > Here is how to post via email: > > https://www.tumblr.com/docs/en/posting#emailpostheader > > The email for us is: > > [image: Inline image 1] > > This is so great! Anyone can contribute absolutely anything, and they > don't need to know what a PR is :) > > On Tue, Oct 27, 2015 at 12:31 PM, Ben Cipollini wrote: > >> Oh no, another place for discussion? :-/ >> >> Can we redirect them to the mailing list or neurostars? >> >> On Tue, Oct 27, 2015 at 12:19 PM, vanessa sochat >> wrote: >> >>> Hey Ariel, >>> >>> Do we have a nipy discus? I would like to add comments to posts so we >>> can talk about things like these: >>> >>> >>> http://neuroimaging.tumblr.com/post/132031797431/write-stdout-to-file-for-fsl-cluster >>> >>> Best, >>> >>> Vanessa >>> >>> On Tue, Oct 27, 2015 at 11:44 AM, Ben Cipollini >>> wrote: >>> >>>> Great! I'll resubmit my "issue" to the nipy repo and start "watching" >>>> it :) >>>> >>>> On Tue, Oct 27, 2015 at 11:40 AM, Ariel Rokem wrote: >>>> >>>>> Great work! Will resubmit my blog-post PR through the new mechanism. >>>>> >>>>> On Tue, Oct 27, 2015 at 11:38 AM, vanessa sochat >>>> > wrote: >>>>> >>>>>> Hi everyone, >>>>>> >>>>>> I just added the missing CNAME file, apologies for the oversight, I >>>>>> did not know it was there :) It looks like nipy.org is working as >>>>>> well now too - please let me know if you see any issues. >>>>>> >>>>>> Circle is expected to have some changes in the next week, so I am >>>>>> going to wait for the weekend to debug the building of artifacts. Will let >>>>>> you know when I fix that up! >>>>>> >>>>>> Best, >>>>>> >>>>>> Vanessa >>>>>> >>>>>> On Tue, Oct 27, 2015 at 11:30 AM, vanessa sochat < >>>>>> vsochat at stanford.edu> wrote: >>>>>> >>>>>>> Hi Everyone, >>>>>>> >>>>>>> Site is live! >>>>>>> >>>>>>> https://nipy.github.io/ >>>>>>> >>>>>>> Ariel - I'm not sure how to set up the nipy.org. Would you mind >>>>>>> taking a look and fixing that up? >>>>>>> >>>>>>> Circle is having some bugs with the artifact generation, I think I >>>>>>> can probably fix it, but not during the work week. Ben - I added your >>>>>>> contribution to the README but didn't get the other comment in time. The >>>>>>> good news is now anyone and everyone can submit changes as PR. I encourage >>>>>>> everyone to familiarize yourself with tumblr, and start contributing >>>>>>> content, PRs to tweak it. >>>>>>> >>>>>>> Best, >>>>>>> >>>>>>> Vanessa >>>>>>> >>>>>>> On Tue, Oct 27, 2015 at 11:10 AM, vanessa sochat < >>>>>>> vsochat at stanford.edu> wrote: >>>>>>> >>>>>>>> Got it! Thanks! :) >>>>>>>> >>>>>>>> On Tue, Oct 27, 2015 at 11:07 AM, Ariel Rokem >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Hi, >>>>>>>>> On Tue, Oct 27, 2015 at 10:56 AM, vanessa sochat < >>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>> >>>>>>>>>> Hi Ariel, >>>>>>>>>> >>>>>>>>>> Please add me as an admin to nipy.github.io, so I can set up >>>>>>>>>> circle for CI. Thanks! >>>>>>>>>> >>>>>>>>>> >>>>>>>>> I believe I just did that. Let me know how you get on. >>>>>>>>> >>>>>>>>> >>>>>>>>>> Best, >>>>>>>>>> >>>>>>>>>> Vanessa >>>>>>>>>> >>>>>>>>>> On Tue, Oct 27, 2015 at 10:42 AM, vanessa sochat < >>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>> >>>>>>>>>>> Just as a proof of concept for adding a project - I just added a >>>>>>>>>>> new entry to the data file (copy pasting basically), copied one file, and >>>>>>>>>>> the entire process took me like, 48 seconds :) >>>>>>>>>>> >>>>>>>>>>> On Tue, Oct 27, 2015 at 10:36 AM, Ben Cipollini < >>>>>>>>>>> bcipolli at ucsd.edu> wrote: >>>>>>>>>>> >>>>>>>>>>>> Thanks Vanessa! >>>>>>>>>>>> >>>>>>>>>>>> On Tue, Oct 27, 2015 at 10:35 AM, vanessa sochat < >>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> I will do some tweaks and get the site working. There will be >>>>>>>>>>>>> a change for the URL so there might be some bugs with my initial release, >>>>>>>>>>>>> but I'll get it fixed asap. Will send an update later. >>>>>>>>>>>>> >>>>>>>>>>>>> On Tue, Oct 27, 2015 at 6:48 AM, Ariel Rokem >>>>>>>>>>>> > wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Oh, one more: >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Tue, Oct 27, 2015 at 6:40 AM, Ariel Rokem < >>>>>>>>>>>>>> arokem at gmail.com> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Hi Vanessa, >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> I have a few comments/suggestions: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> 1. I would rather not have the front page be the project >>>>>>>>>>>>>>> directory. In my opinion, the front page should instead explain briefly >>>>>>>>>>>>>>> what this is, and lead visitors to the various other parts of the website. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> 2. There are a few issues with formatting in the Code of >>>>>>>>>>>>>>> Conduct page (bullet points appear as continued lines) >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> 3. Please include mindboggle in the project directory (it's >>>>>>>>>>>>>> been recently added!). >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Other than these two, I think this is ready to be introduced >>>>>>>>>>>>>>> as a PR against the nipy/nipy.github.com repository (you >>>>>>>>>>>>>>> don't need any admin rights to do that, but I also just added you to "team >>>>>>>>>>>>>>> blog" on the github nipy org, so you can even do the merge yourself, if you >>>>>>>>>>>>>>> want). >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Cheers, >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Ariel >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Mon, Oct 26, 2015 at 12:56 PM, vanessa sochat < >>>>>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Hi Eleftherios, >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> It definitely would be possible! I'm not any sort of admin >>>>>>>>>>>>>>>> in the nipy space, so the farthest I could take it is having the repo for >>>>>>>>>>>>>>>> someone to deploy on nipy.github.io. The code is here: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> https://github.com/vsoch/nipy-jekyll >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> and deployment on my github pages: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> http://vsoch.github.io/nipy-jekyll/ >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> I mostly stopped working on it because I accomplished all >>>>>>>>>>>>>>>> the things that I set out to do (jekyll site, preview on continuous >>>>>>>>>>>>>>>> integration with circle, standard ways to add new content, and an easy way >>>>>>>>>>>>>>>> to multiple ways to add content a la github >>>>>>>>>>>>>>>> , or >>>>>>>>>>>>>>>> for those who aren't comfortable with pushing and pulling, la >>>>>>>>>>>>>>>> social media ). I think I >>>>>>>>>>>>>>>> had suggested moving forward for people to try out tumblr (and start >>>>>>>>>>>>>>>> contributing content!), and if people were happy, to move it over to the >>>>>>>>>>>>>>>> nipy repo. If the outcome of the work was not a desired solution, I was >>>>>>>>>>>>>>>> content to just let it be. However if there is interest, that is definitely >>>>>>>>>>>>>>>> still a possibility. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Best, >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Vanessa >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Mon, Oct 26, 2015 at 12:34 PM, Eleftherios Garyfallidis >>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Hi Vanessa and all, >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Would it be possible to switch to your much nicer new >>>>>>>>>>>>>>>>> website? I still see the older version being up. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Do you have a plan for this? Or you waiting for some >>>>>>>>>>>>>>>>> feedback on our side? >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Best regards, >>>>>>>>>>>>>>>>> Eleftherios >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Wed, Sep 2, 2015 at 12:57 PM, Ben Cipollini < >>>>>>>>>>>>>>>>> bcipolli at ucsd.edu> wrote: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> I think they're good for mobile sites. I think they're >>>>>>>>>>>>>>>>>> generally expanded by default on full screens, and compacted on mobile. So >>>>>>>>>>>>>>>>>> I suggest to keep it, but have a regular menu that's showing on full >>>>>>>>>>>>>>>>>> screens and hidden on mobile. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> On Wed, Sep 2, 2015 at 9:51 AM, vanessa sochat < >>>>>>>>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> That's a good suggestion, and I'll add as an issue so I >>>>>>>>>>>>>>>>>>> can find it easily when the next round of changes comes around. Generally, >>>>>>>>>>>>>>>>>>> these "hamburger" menu things are useless functionality wise, and only >>>>>>>>>>>>>>>>>>> serve to aesthetically "get rid of the navigation" to have a clean looking >>>>>>>>>>>>>>>>>>> site. In our case, it is probably just annoying to have the extra clicks. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> On Wed, Sep 2, 2015 at 8:50 AM, Ben Cipollini < >>>>>>>>>>>>>>>>>>> bcipolli at ucsd.edu> wrote: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> This looks great. It's also cool to see "ask a >>>>>>>>>>>>>>>>>>>> question" integrated into the website, though we'll still have to hash >>>>>>>>>>>>>>>>>>>> things out for that. >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Rather than open a github issue (which few may see), >>>>>>>>>>>>>>>>>>>> I'll make a suggestion here: can we have the menu expanded by default when >>>>>>>>>>>>>>>>>>>> accessing via a full-size screen? >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> It feels odd to me to have to expand the menu in order >>>>>>>>>>>>>>>>>>>> to navigate anywhere, by default. To me, navigation options should be >>>>>>>>>>>>>>>>>>>> obvious, unless pressed for space. >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> On Sun, Aug 30, 2015 at 1:14 PM, vanessa sochat < >>>>>>>>>>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> Hi Everyone, >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> I've finished work on the "contribute" page with my >>>>>>>>>>>>>>>>>>>>> thinking for how to contribute various content: >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> http://vsoch.github.io/nipy-jekyll/contribute.html >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> and as an example, put up a quick blog post: >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> http://neuroimaging.tumblr.com/ >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> The old "example" blog posts are hidden (private) and >>>>>>>>>>>>>>>>>>>>> can be viewed if you are a contributor. I'd like to add anyone and everyone >>>>>>>>>>>>>>>>>>>>> interested to contribute as "official" contributors via tumblr - if you are >>>>>>>>>>>>>>>>>>>>> interested please send me your email address. I've already invited some of >>>>>>>>>>>>>>>>>>>>> you for which I know the email. >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> Best, >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> Vanessa >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>>>>>>>>>> Stanford University >>>>>>>>>>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>>>>>>>> Stanford University >>>>>>>>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>> Neuroimaging mailing list >>>>>>>>>>>>>>>>> Neuroimaging at python.org >>>>>>>>>>>>>>>>> https://mail.python.org/mailman/listinfo/neuroimaging >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>>>>> Stanford University >>>>>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>> Stanford University >>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>> >>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>> 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 >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>> Stanford University >>>>>>>>>>> (603) 321-0676 >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>> Stanford University >>>>>>>>>> (603) 321-0676 >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> 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 >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Vanessa Villamia Sochat >>>>>>>> Stanford University >>>>>>>> (603) 321-0676 >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Vanessa Villamia Sochat >>>>>>> Stanford University >>>>>>> (603) 321-0676 >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Vanessa Villamia Sochat >>>>>> Stanford University >>>>>> (603) 321-0676 >>>>>> >>>>>> _______________________________________________ >>>>>> 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 >>>>> >>>>> >>>> >>>> _______________________________________________ >>>> Neuroimaging mailing list >>>> Neuroimaging at python.org >>>> https://mail.python.org/mailman/listinfo/neuroimaging >>>> >>>> >>> >>> >>> -- >>> Vanessa Villamia Sochat >>> Stanford University >>> (603) 321-0676 >>> >>> _______________________________________________ >>> 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 >> >> > > > -- > Vanessa Villamia Sochat > Stanford University > (603) 321-0676 > > _______________________________________________ > Neuroimaging mailing list > Neuroimaging at python.org > https://mail.python.org/mailman/listinfo/neuroimaging > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 5337 bytes Desc: not available URL: From vsochat at stanford.edu Tue Oct 27 15:50:08 2015 From: vsochat at stanford.edu (vanessa sochat) Date: Tue, 27 Oct 2015 12:50:08 -0700 Subject: [Neuroimaging] Site Contributions In-Reply-To: References: Message-ID: How about nipyorg for a twitter? Some hairy dude in a swimming pool has "nipy" On Tue, Oct 27, 2015 at 12:47 PM, Chris Filo Gorgolewski < krzysztof.gorgolewski at gmail.com> wrote: > neurostars is based on biostars and provide a variety of ways to integrate > sources. Satra and Roman will know more. > > Best, > Chris > > On Tue, Oct 27, 2015 at 12:38 PM, vanessa sochat > wrote: > >> Sure thing. There might be a trick to integrate the two, I'll look into >> it. I just added comments: >> >> >> http://neuroimaging.tumblr.com/post/132031797431/write-stdout-to-file-for-fsl-cluster >> >> and for now I will redirect people to neurostars. >> >> Here is how to post via email: >> >> https://www.tumblr.com/docs/en/posting#emailpostheader >> >> The email for us is: >> >> [image: Inline image 1] >> >> This is so great! Anyone can contribute absolutely anything, and they >> don't need to know what a PR is :) >> >> On Tue, Oct 27, 2015 at 12:31 PM, Ben Cipollini >> wrote: >> >>> Oh no, another place for discussion? :-/ >>> >>> Can we redirect them to the mailing list or neurostars? >>> >>> On Tue, Oct 27, 2015 at 12:19 PM, vanessa sochat >>> wrote: >>> >>>> Hey Ariel, >>>> >>>> Do we have a nipy discus? I would like to add comments to posts so we >>>> can talk about things like these: >>>> >>>> >>>> http://neuroimaging.tumblr.com/post/132031797431/write-stdout-to-file-for-fsl-cluster >>>> >>>> Best, >>>> >>>> Vanessa >>>> >>>> On Tue, Oct 27, 2015 at 11:44 AM, Ben Cipollini >>>> wrote: >>>> >>>>> Great! I'll resubmit my "issue" to the nipy repo and start "watching" >>>>> it :) >>>>> >>>>> On Tue, Oct 27, 2015 at 11:40 AM, Ariel Rokem >>>>> wrote: >>>>> >>>>>> Great work! Will resubmit my blog-post PR through the new mechanism. >>>>>> >>>>>> On Tue, Oct 27, 2015 at 11:38 AM, vanessa sochat < >>>>>> vsochat at stanford.edu> wrote: >>>>>> >>>>>>> Hi everyone, >>>>>>> >>>>>>> I just added the missing CNAME file, apologies for the oversight, I >>>>>>> did not know it was there :) It looks like nipy.org is working as >>>>>>> well now too - please let me know if you see any issues. >>>>>>> >>>>>>> Circle is expected to have some changes in the next week, so I am >>>>>>> going to wait for the weekend to debug the building of artifacts. Will let >>>>>>> you know when I fix that up! >>>>>>> >>>>>>> Best, >>>>>>> >>>>>>> Vanessa >>>>>>> >>>>>>> On Tue, Oct 27, 2015 at 11:30 AM, vanessa sochat < >>>>>>> vsochat at stanford.edu> wrote: >>>>>>> >>>>>>>> Hi Everyone, >>>>>>>> >>>>>>>> Site is live! >>>>>>>> >>>>>>>> https://nipy.github.io/ >>>>>>>> >>>>>>>> Ariel - I'm not sure how to set up the nipy.org. Would you mind >>>>>>>> taking a look and fixing that up? >>>>>>>> >>>>>>>> Circle is having some bugs with the artifact generation, I think I >>>>>>>> can probably fix it, but not during the work week. Ben - I added your >>>>>>>> contribution to the README but didn't get the other comment in time. The >>>>>>>> good news is now anyone and everyone can submit changes as PR. I encourage >>>>>>>> everyone to familiarize yourself with tumblr, and start contributing >>>>>>>> content, PRs to tweak it. >>>>>>>> >>>>>>>> Best, >>>>>>>> >>>>>>>> Vanessa >>>>>>>> >>>>>>>> On Tue, Oct 27, 2015 at 11:10 AM, vanessa sochat < >>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>> >>>>>>>>> Got it! Thanks! :) >>>>>>>>> >>>>>>>>> On Tue, Oct 27, 2015 at 11:07 AM, Ariel Rokem >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> Hi, >>>>>>>>>> On Tue, Oct 27, 2015 at 10:56 AM, vanessa sochat < >>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>> >>>>>>>>>>> Hi Ariel, >>>>>>>>>>> >>>>>>>>>>> Please add me as an admin to nipy.github.io, so I can set up >>>>>>>>>>> circle for CI. Thanks! >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> I believe I just did that. Let me know how you get on. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>> Best, >>>>>>>>>>> >>>>>>>>>>> Vanessa >>>>>>>>>>> >>>>>>>>>>> On Tue, Oct 27, 2015 at 10:42 AM, vanessa sochat < >>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>> >>>>>>>>>>>> Just as a proof of concept for adding a project - I just added >>>>>>>>>>>> a new entry to the data file (copy pasting basically), copied one file, and >>>>>>>>>>>> the entire process took me like, 48 seconds :) >>>>>>>>>>>> >>>>>>>>>>>> On Tue, Oct 27, 2015 at 10:36 AM, Ben Cipollini < >>>>>>>>>>>> bcipolli at ucsd.edu> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Thanks Vanessa! >>>>>>>>>>>>> >>>>>>>>>>>>> On Tue, Oct 27, 2015 at 10:35 AM, vanessa sochat < >>>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> I will do some tweaks and get the site working. There will be >>>>>>>>>>>>>> a change for the URL so there might be some bugs with my initial release, >>>>>>>>>>>>>> but I'll get it fixed asap. Will send an update later. >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Tue, Oct 27, 2015 at 6:48 AM, Ariel Rokem < >>>>>>>>>>>>>> arokem at gmail.com> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Oh, one more: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Tue, Oct 27, 2015 at 6:40 AM, Ariel Rokem < >>>>>>>>>>>>>>> arokem at gmail.com> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Hi Vanessa, >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> I have a few comments/suggestions: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> 1. I would rather not have the front page be the project >>>>>>>>>>>>>>>> directory. In my opinion, the front page should instead explain briefly >>>>>>>>>>>>>>>> what this is, and lead visitors to the various other parts of the website. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> 2. There are a few issues with formatting in the Code of >>>>>>>>>>>>>>>> Conduct page (bullet points appear as continued lines) >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> 3. Please include mindboggle in the project directory (it's >>>>>>>>>>>>>>> been recently added!). >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Other than these two, I think this is ready to be >>>>>>>>>>>>>>>> introduced as a PR against the nipy/nipy.github.com >>>>>>>>>>>>>>>> repository (you don't need any admin rights to do that, but I also just >>>>>>>>>>>>>>>> added you to "team blog" on the github nipy org, so you can even do the >>>>>>>>>>>>>>>> merge yourself, if you want). >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Cheers, >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Ariel >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Mon, Oct 26, 2015 at 12:56 PM, vanessa sochat < >>>>>>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Hi Eleftherios, >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> It definitely would be possible! I'm not any sort of admin >>>>>>>>>>>>>>>>> in the nipy space, so the farthest I could take it is having the repo for >>>>>>>>>>>>>>>>> someone to deploy on nipy.github.io. The code is here: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> https://github.com/vsoch/nipy-jekyll >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> and deployment on my github pages: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> http://vsoch.github.io/nipy-jekyll/ >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> I mostly stopped working on it because I accomplished all >>>>>>>>>>>>>>>>> the things that I set out to do (jekyll site, preview on continuous >>>>>>>>>>>>>>>>> integration with circle, standard ways to add new content, and an easy way >>>>>>>>>>>>>>>>> to multiple ways to add content a la github >>>>>>>>>>>>>>>>> , or >>>>>>>>>>>>>>>>> for those who aren't comfortable with pushing and pulling, la >>>>>>>>>>>>>>>>> social media ). I think I >>>>>>>>>>>>>>>>> had suggested moving forward for people to try out tumblr (and start >>>>>>>>>>>>>>>>> contributing content!), and if people were happy, to move it over to the >>>>>>>>>>>>>>>>> nipy repo. If the outcome of the work was not a desired solution, I was >>>>>>>>>>>>>>>>> content to just let it be. However if there is interest, that is definitely >>>>>>>>>>>>>>>>> still a possibility. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Best, >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Vanessa >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Mon, Oct 26, 2015 at 12:34 PM, Eleftherios Garyfallidis >>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Hi Vanessa and all, >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Would it be possible to switch to your much nicer new >>>>>>>>>>>>>>>>>> website? I still see the older version being up. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Do you have a plan for this? Or you waiting for some >>>>>>>>>>>>>>>>>> feedback on our side? >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Best regards, >>>>>>>>>>>>>>>>>> Eleftherios >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> On Wed, Sep 2, 2015 at 12:57 PM, Ben Cipollini < >>>>>>>>>>>>>>>>>> bcipolli at ucsd.edu> wrote: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> I think they're good for mobile sites. I think they're >>>>>>>>>>>>>>>>>>> generally expanded by default on full screens, and compacted on mobile. So >>>>>>>>>>>>>>>>>>> I suggest to keep it, but have a regular menu that's showing on full >>>>>>>>>>>>>>>>>>> screens and hidden on mobile. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> On Wed, Sep 2, 2015 at 9:51 AM, vanessa sochat < >>>>>>>>>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> That's a good suggestion, and I'll add as an issue so I >>>>>>>>>>>>>>>>>>>> can find it easily when the next round of changes comes around. Generally, >>>>>>>>>>>>>>>>>>>> these "hamburger" menu things are useless functionality wise, and only >>>>>>>>>>>>>>>>>>>> serve to aesthetically "get rid of the navigation" to have a clean looking >>>>>>>>>>>>>>>>>>>> site. In our case, it is probably just annoying to have the extra clicks. >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> On Wed, Sep 2, 2015 at 8:50 AM, Ben Cipollini < >>>>>>>>>>>>>>>>>>>> bcipolli at ucsd.edu> wrote: >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> This looks great. It's also cool to see "ask a >>>>>>>>>>>>>>>>>>>>> question" integrated into the website, though we'll still have to hash >>>>>>>>>>>>>>>>>>>>> things out for that. >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> Rather than open a github issue (which few may see), >>>>>>>>>>>>>>>>>>>>> I'll make a suggestion here: can we have the menu expanded by default when >>>>>>>>>>>>>>>>>>>>> accessing via a full-size screen? >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> It feels odd to me to have to expand the menu in order >>>>>>>>>>>>>>>>>>>>> to navigate anywhere, by default. To me, navigation options should be >>>>>>>>>>>>>>>>>>>>> obvious, unless pressed for space. >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> On Sun, Aug 30, 2015 at 1:14 PM, vanessa sochat < >>>>>>>>>>>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> Hi Everyone, >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> I've finished work on the "contribute" page with my >>>>>>>>>>>>>>>>>>>>>> thinking for how to contribute various content: >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> http://vsoch.github.io/nipy-jekyll/contribute.html >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> and as an example, put up a quick blog post: >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> http://neuroimaging.tumblr.com/ >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> The old "example" blog posts are hidden (private) and >>>>>>>>>>>>>>>>>>>>>> can be viewed if you are a contributor. I'd like to add anyone and everyone >>>>>>>>>>>>>>>>>>>>>> interested to contribute as "official" contributors via tumblr - if you are >>>>>>>>>>>>>>>>>>>>>> interested please send me your email address. I've already invited some of >>>>>>>>>>>>>>>>>>>>>> you for which I know the email. >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> Best, >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> Vanessa >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>>>>>>>>>>> Stanford University >>>>>>>>>>>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>>>>>>>>> Stanford University >>>>>>>>>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>> Neuroimaging mailing list >>>>>>>>>>>>>>>>>> Neuroimaging at python.org >>>>>>>>>>>>>>>>>> https://mail.python.org/mailman/listinfo/neuroimaging >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>>>>>> Stanford University >>>>>>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> -- >>>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>>> Stanford University >>>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>>> >>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>> 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 >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>> Stanford University >>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>> Stanford University >>>>>>>>>>> (603) 321-0676 >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> 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 >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Vanessa Villamia Sochat >>>>>>>>> Stanford University >>>>>>>>> (603) 321-0676 >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Vanessa Villamia Sochat >>>>>>>> Stanford University >>>>>>>> (603) 321-0676 >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Vanessa Villamia Sochat >>>>>>> Stanford University >>>>>>> (603) 321-0676 >>>>>>> >>>>>>> _______________________________________________ >>>>>>> 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 >>>>>> >>>>>> >>>>> >>>>> _______________________________________________ >>>>> Neuroimaging mailing list >>>>> Neuroimaging at python.org >>>>> https://mail.python.org/mailman/listinfo/neuroimaging >>>>> >>>>> >>>> >>>> >>>> -- >>>> Vanessa Villamia Sochat >>>> Stanford University >>>> (603) 321-0676 >>>> >>>> _______________________________________________ >>>> 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 >>> >>> >> >> >> -- >> Vanessa Villamia Sochat >> Stanford University >> (603) 321-0676 >> >> _______________________________________________ >> 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 > > -- Vanessa Villamia Sochat Stanford University (603) 321-0676 -------------- next part -------------- An HTML attachment was scrubbed... URL: From vsochat at stanford.edu Tue Oct 27 16:09:29 2015 From: vsochat at stanford.edu (vanessa sochat) Date: Tue, 27 Oct 2015 13:09:29 -0700 Subject: [Neuroimaging] Site Contributions In-Reply-To: References: Message-ID: Ok, the first one was a little messy because I enabled twitter integration after the first post (and so I needed to reblog), but now the two are connected, so you can keep track of posts via twitter: https://twitter.com/nipyorg Best, Vanessa On Tue, Oct 27, 2015 at 12:50 PM, vanessa sochat wrote: > How about nipyorg for a twitter? Some hairy dude in a swimming pool has > "nipy" > > On Tue, Oct 27, 2015 at 12:47 PM, Chris Filo Gorgolewski < > krzysztof.gorgolewski at gmail.com> wrote: > >> neurostars is based on biostars and provide a variety of ways to >> integrate sources. Satra and Roman will know more. >> >> Best, >> Chris >> >> On Tue, Oct 27, 2015 at 12:38 PM, vanessa sochat >> wrote: >> >>> Sure thing. There might be a trick to integrate the two, I'll look into >>> it. I just added comments: >>> >>> >>> http://neuroimaging.tumblr.com/post/132031797431/write-stdout-to-file-for-fsl-cluster >>> >>> and for now I will redirect people to neurostars. >>> >>> Here is how to post via email: >>> >>> https://www.tumblr.com/docs/en/posting#emailpostheader >>> >>> The email for us is: >>> >>> [image: Inline image 1] >>> >>> This is so great! Anyone can contribute absolutely anything, and they >>> don't need to know what a PR is :) >>> >>> On Tue, Oct 27, 2015 at 12:31 PM, Ben Cipollini >>> wrote: >>> >>>> Oh no, another place for discussion? :-/ >>>> >>>> Can we redirect them to the mailing list or neurostars? >>>> >>>> On Tue, Oct 27, 2015 at 12:19 PM, vanessa sochat >>>> wrote: >>>> >>>>> Hey Ariel, >>>>> >>>>> Do we have a nipy discus? I would like to add comments to posts so we >>>>> can talk about things like these: >>>>> >>>>> >>>>> http://neuroimaging.tumblr.com/post/132031797431/write-stdout-to-file-for-fsl-cluster >>>>> >>>>> Best, >>>>> >>>>> Vanessa >>>>> >>>>> On Tue, Oct 27, 2015 at 11:44 AM, Ben Cipollini >>>>> wrote: >>>>> >>>>>> Great! I'll resubmit my "issue" to the nipy repo and start "watching" >>>>>> it :) >>>>>> >>>>>> On Tue, Oct 27, 2015 at 11:40 AM, Ariel Rokem >>>>>> wrote: >>>>>> >>>>>>> Great work! Will resubmit my blog-post PR through the new mechanism. >>>>>>> >>>>>>> On Tue, Oct 27, 2015 at 11:38 AM, vanessa sochat < >>>>>>> vsochat at stanford.edu> wrote: >>>>>>> >>>>>>>> Hi everyone, >>>>>>>> >>>>>>>> I just added the missing CNAME file, apologies for the oversight, I >>>>>>>> did not know it was there :) It looks like nipy.org is working as >>>>>>>> well now too - please let me know if you see any issues. >>>>>>>> >>>>>>>> Circle is expected to have some changes in the next week, so I am >>>>>>>> going to wait for the weekend to debug the building of artifacts. Will let >>>>>>>> you know when I fix that up! >>>>>>>> >>>>>>>> Best, >>>>>>>> >>>>>>>> Vanessa >>>>>>>> >>>>>>>> On Tue, Oct 27, 2015 at 11:30 AM, vanessa sochat < >>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>> >>>>>>>>> Hi Everyone, >>>>>>>>> >>>>>>>>> Site is live! >>>>>>>>> >>>>>>>>> https://nipy.github.io/ >>>>>>>>> >>>>>>>>> Ariel - I'm not sure how to set up the nipy.org. Would you mind >>>>>>>>> taking a look and fixing that up? >>>>>>>>> >>>>>>>>> Circle is having some bugs with the artifact generation, I think I >>>>>>>>> can probably fix it, but not during the work week. Ben - I added your >>>>>>>>> contribution to the README but didn't get the other comment in time. The >>>>>>>>> good news is now anyone and everyone can submit changes as PR. I encourage >>>>>>>>> everyone to familiarize yourself with tumblr, and start contributing >>>>>>>>> content, PRs to tweak it. >>>>>>>>> >>>>>>>>> Best, >>>>>>>>> >>>>>>>>> Vanessa >>>>>>>>> >>>>>>>>> On Tue, Oct 27, 2015 at 11:10 AM, vanessa sochat < >>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>> >>>>>>>>>> Got it! Thanks! :) >>>>>>>>>> >>>>>>>>>> On Tue, Oct 27, 2015 at 11:07 AM, Ariel Rokem >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>>> Hi, >>>>>>>>>>> On Tue, Oct 27, 2015 at 10:56 AM, vanessa sochat < >>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>> >>>>>>>>>>>> Hi Ariel, >>>>>>>>>>>> >>>>>>>>>>>> Please add me as an admin to nipy.github.io, so I can set up >>>>>>>>>>>> circle for CI. Thanks! >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> I believe I just did that. Let me know how you get on. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>> Best, >>>>>>>>>>>> >>>>>>>>>>>> Vanessa >>>>>>>>>>>> >>>>>>>>>>>> On Tue, Oct 27, 2015 at 10:42 AM, vanessa sochat < >>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Just as a proof of concept for adding a project - I just added >>>>>>>>>>>>> a new entry to the data file (copy pasting basically), copied one file, and >>>>>>>>>>>>> the entire process took me like, 48 seconds :) >>>>>>>>>>>>> >>>>>>>>>>>>> On Tue, Oct 27, 2015 at 10:36 AM, Ben Cipollini < >>>>>>>>>>>>> bcipolli at ucsd.edu> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Thanks Vanessa! >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Tue, Oct 27, 2015 at 10:35 AM, vanessa sochat < >>>>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> I will do some tweaks and get the site working. There will >>>>>>>>>>>>>>> be a change for the URL so there might be some bugs with my initial >>>>>>>>>>>>>>> release, but I'll get it fixed asap. Will send an update later. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Tue, Oct 27, 2015 at 6:48 AM, Ariel Rokem < >>>>>>>>>>>>>>> arokem at gmail.com> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Oh, one more: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Tue, Oct 27, 2015 at 6:40 AM, Ariel Rokem < >>>>>>>>>>>>>>>> arokem at gmail.com> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Hi Vanessa, >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> I have a few comments/suggestions: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> 1. I would rather not have the front page be the project >>>>>>>>>>>>>>>>> directory. In my opinion, the front page should instead explain briefly >>>>>>>>>>>>>>>>> what this is, and lead visitors to the various other parts of the website. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> 2. There are a few issues with formatting in the Code of >>>>>>>>>>>>>>>>> Conduct page (bullet points appear as continued lines) >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> 3. Please include mindboggle in the project directory (it's >>>>>>>>>>>>>>>> been recently added!). >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Other than these two, I think this is ready to be >>>>>>>>>>>>>>>>> introduced as a PR against the nipy/nipy.github.com >>>>>>>>>>>>>>>>> repository (you don't need any admin rights to do that, but I also just >>>>>>>>>>>>>>>>> added you to "team blog" on the github nipy org, so you can even do the >>>>>>>>>>>>>>>>> merge yourself, if you want). >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Cheers, >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Ariel >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Mon, Oct 26, 2015 at 12:56 PM, vanessa sochat < >>>>>>>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Hi Eleftherios, >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> It definitely would be possible! I'm not any sort of >>>>>>>>>>>>>>>>>> admin in the nipy space, so the farthest I could take it is having the repo >>>>>>>>>>>>>>>>>> for someone to deploy on nipy.github.io. The code is >>>>>>>>>>>>>>>>>> here: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> https://github.com/vsoch/nipy-jekyll >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> and deployment on my github pages: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> http://vsoch.github.io/nipy-jekyll/ >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> I mostly stopped working on it because I accomplished all >>>>>>>>>>>>>>>>>> the things that I set out to do (jekyll site, preview on continuous >>>>>>>>>>>>>>>>>> integration with circle, standard ways to add new content, and an easy way >>>>>>>>>>>>>>>>>> to multiple ways to add content a la github >>>>>>>>>>>>>>>>>> , or >>>>>>>>>>>>>>>>>> for those who aren't comfortable with pushing and pulling, la >>>>>>>>>>>>>>>>>> social media ). I think >>>>>>>>>>>>>>>>>> I had suggested moving forward for people to try out tumblr (and start >>>>>>>>>>>>>>>>>> contributing content!), and if people were happy, to move it over to the >>>>>>>>>>>>>>>>>> nipy repo. If the outcome of the work was not a desired solution, I was >>>>>>>>>>>>>>>>>> content to just let it be. However if there is interest, that is definitely >>>>>>>>>>>>>>>>>> still a possibility. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Best, >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Vanessa >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> On Mon, Oct 26, 2015 at 12:34 PM, Eleftherios >>>>>>>>>>>>>>>>>> Garyfallidis wrote: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Hi Vanessa and all, >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Would it be possible to switch to your much nicer new >>>>>>>>>>>>>>>>>>> website? I still see the older version being up. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Do you have a plan for this? Or you waiting for some >>>>>>>>>>>>>>>>>>> feedback on our side? >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Best regards, >>>>>>>>>>>>>>>>>>> Eleftherios >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> On Wed, Sep 2, 2015 at 12:57 PM, Ben Cipollini < >>>>>>>>>>>>>>>>>>> bcipolli at ucsd.edu> wrote: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> I think they're good for mobile sites. I think they're >>>>>>>>>>>>>>>>>>>> generally expanded by default on full screens, and compacted on mobile. So >>>>>>>>>>>>>>>>>>>> I suggest to keep it, but have a regular menu that's showing on full >>>>>>>>>>>>>>>>>>>> screens and hidden on mobile. >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> On Wed, Sep 2, 2015 at 9:51 AM, vanessa sochat < >>>>>>>>>>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> That's a good suggestion, and I'll add as an issue so >>>>>>>>>>>>>>>>>>>>> I can find it easily when the next round of changes comes around. >>>>>>>>>>>>>>>>>>>>> Generally, these "hamburger" menu things are useless functionality wise, >>>>>>>>>>>>>>>>>>>>> and only serve to aesthetically "get rid of the navigation" to have a clean >>>>>>>>>>>>>>>>>>>>> looking site. In our case, it is probably just annoying to have the extra >>>>>>>>>>>>>>>>>>>>> clicks. >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> On Wed, Sep 2, 2015 at 8:50 AM, Ben Cipollini < >>>>>>>>>>>>>>>>>>>>> bcipolli at ucsd.edu> wrote: >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> This looks great. It's also cool to see "ask a >>>>>>>>>>>>>>>>>>>>>> question" integrated into the website, though we'll still have to hash >>>>>>>>>>>>>>>>>>>>>> things out for that. >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> Rather than open a github issue (which few may see), >>>>>>>>>>>>>>>>>>>>>> I'll make a suggestion here: can we have the menu expanded by default when >>>>>>>>>>>>>>>>>>>>>> accessing via a full-size screen? >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> It feels odd to me to have to expand the menu in >>>>>>>>>>>>>>>>>>>>>> order to navigate anywhere, by default. To me, navigation options should be >>>>>>>>>>>>>>>>>>>>>> obvious, unless pressed for space. >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> On Sun, Aug 30, 2015 at 1:14 PM, vanessa sochat < >>>>>>>>>>>>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> Hi Everyone, >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> I've finished work on the "contribute" page with my >>>>>>>>>>>>>>>>>>>>>>> thinking for how to contribute various content: >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> http://vsoch.github.io/nipy-jekyll/contribute.html >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> and as an example, put up a quick blog post: >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> http://neuroimaging.tumblr.com/ >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> The old "example" blog posts are hidden (private) >>>>>>>>>>>>>>>>>>>>>>> and can be viewed if you are a contributor. I'd like to add anyone and >>>>>>>>>>>>>>>>>>>>>>> everyone interested to contribute as "official" contributors via tumblr - >>>>>>>>>>>>>>>>>>>>>>> if you are interested please send me your email address. I've already >>>>>>>>>>>>>>>>>>>>>>> invited some of you for which I know the email. >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> Best, >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> Vanessa >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>>>>>>>>>>>> Stanford University >>>>>>>>>>>>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>>>>>>>>>> Stanford University >>>>>>>>>>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>>> Neuroimaging mailing list >>>>>>>>>>>>>>>>>>> Neuroimaging at python.org >>>>>>>>>>>>>>>>>>> https://mail.python.org/mailman/listinfo/neuroimaging >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>>>>>>> Stanford University >>>>>>>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>>>> Stanford University >>>>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>> Stanford University >>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>> Stanford University >>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> 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 >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>> Stanford University >>>>>>>>>> (603) 321-0676 >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Vanessa Villamia Sochat >>>>>>>>> Stanford University >>>>>>>>> (603) 321-0676 >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Vanessa Villamia Sochat >>>>>>>> Stanford University >>>>>>>> (603) 321-0676 >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> 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 >>>>>>> >>>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Neuroimaging mailing list >>>>>> Neuroimaging at python.org >>>>>> https://mail.python.org/mailman/listinfo/neuroimaging >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Vanessa Villamia Sochat >>>>> Stanford University >>>>> (603) 321-0676 >>>>> >>>>> _______________________________________________ >>>>> 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 >>>> >>>> >>> >>> >>> -- >>> Vanessa Villamia Sochat >>> Stanford University >>> (603) 321-0676 >>> >>> _______________________________________________ >>> 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 >> >> > > > -- > Vanessa Villamia Sochat > Stanford University > (603) 321-0676 > -- Vanessa Villamia Sochat Stanford University (603) 321-0676 -------------- next part -------------- An HTML attachment was scrubbed... URL: From arokem at gmail.com Tue Oct 27 16:20:42 2015 From: arokem at gmail.com (Ariel Rokem) Date: Tue, 27 Oct 2015 13:20:42 -0700 Subject: [Neuroimaging] Site Contributions In-Reply-To: References: Message-ID: Hey Julien, On Tue, Oct 27, 2015 at 12:04 PM, Julien Cohen-Adad wrote: > Hi everyone, > > would it be possible to add our neuroimaging project to the nipy website? > https://github.com/neuropoly/spinalcordtoolbox > > I am +1 for adding the toolbox to the project directory. How about putting in a PR on the website Github repo for this? http://nipy.org/contribute.html#add-a-package > it is 100% python and notably uses nibabel and dipy. > > cheers > julien > > > -- > Julien Cohen-Adad, PhD > Assistant Professor, Polytechnique Montreal > Associate Director, Functional Neuroimaging Unit, University of Montreal > Phone: 514 340 5121 (office: 2264); Skype: jcohenadad > Web: www.neuro.polymtl.ca > > On Tue, Oct 27, 2015 at 2:44 PM, Eleftherios Garyfallidis < > garyfallidis at gmail.com> wrote: > >> Epic awesomeness! Thank you Vanessa! >> >> On Tue, Oct 27, 2015 at 2:40 PM, Ariel Rokem wrote: >> >>> Great work! Will resubmit my blog-post PR through the new mechanism. >>> >>> On Tue, Oct 27, 2015 at 11:38 AM, vanessa sochat >>> wrote: >>> >>>> Hi everyone, >>>> >>>> I just added the missing CNAME file, apologies for the oversight, I did >>>> not know it was there :) It looks like nipy.org is working as well now >>>> too - please let me know if you see any issues. >>>> >>>> Circle is expected to have some changes in the next week, so I am going >>>> to wait for the weekend to debug the building of artifacts. Will let you >>>> know when I fix that up! >>>> >>>> Best, >>>> >>>> Vanessa >>>> >>>> On Tue, Oct 27, 2015 at 11:30 AM, vanessa sochat >>>> wrote: >>>> >>>>> Hi Everyone, >>>>> >>>>> Site is live! >>>>> >>>>> https://nipy.github.io/ >>>>> >>>>> Ariel - I'm not sure how to set up the nipy.org. Would you mind >>>>> taking a look and fixing that up? >>>>> >>>>> Circle is having some bugs with the artifact generation, I think I can >>>>> probably fix it, but not during the work week. Ben - I added your >>>>> contribution to the README but didn't get the other comment in time. The >>>>> good news is now anyone and everyone can submit changes as PR. I encourage >>>>> everyone to familiarize yourself with tumblr, and start contributing >>>>> content, PRs to tweak it. >>>>> >>>>> Best, >>>>> >>>>> Vanessa >>>>> >>>>> On Tue, Oct 27, 2015 at 11:10 AM, vanessa sochat >>>> > wrote: >>>>> >>>>>> Got it! Thanks! :) >>>>>> >>>>>> On Tue, Oct 27, 2015 at 11:07 AM, Ariel Rokem >>>>>> wrote: >>>>>> >>>>>>> Hi, >>>>>>> On Tue, Oct 27, 2015 at 10:56 AM, vanessa sochat < >>>>>>> vsochat at stanford.edu> wrote: >>>>>>> >>>>>>>> Hi Ariel, >>>>>>>> >>>>>>>> Please add me as an admin to nipy.github.io, so I can set up >>>>>>>> circle for CI. Thanks! >>>>>>>> >>>>>>>> >>>>>>> I believe I just did that. Let me know how you get on. >>>>>>> >>>>>>> >>>>>>>> Best, >>>>>>>> >>>>>>>> Vanessa >>>>>>>> >>>>>>>> On Tue, Oct 27, 2015 at 10:42 AM, vanessa sochat < >>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>> >>>>>>>>> Just as a proof of concept for adding a project - I just added a >>>>>>>>> new entry to the data file (copy pasting basically), copied one file, and >>>>>>>>> the entire process took me like, 48 seconds :) >>>>>>>>> >>>>>>>>> On Tue, Oct 27, 2015 at 10:36 AM, Ben Cipollini >>>>>>>> > wrote: >>>>>>>>> >>>>>>>>>> Thanks Vanessa! >>>>>>>>>> >>>>>>>>>> On Tue, Oct 27, 2015 at 10:35 AM, vanessa sochat < >>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>> >>>>>>>>>>> I will do some tweaks and get the site working. There will be a >>>>>>>>>>> change for the URL so there might be some bugs with my initial release, but >>>>>>>>>>> I'll get it fixed asap. Will send an update later. >>>>>>>>>>> >>>>>>>>>>> On Tue, Oct 27, 2015 at 6:48 AM, Ariel Rokem >>>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>>> Oh, one more: >>>>>>>>>>>> >>>>>>>>>>>> On Tue, Oct 27, 2015 at 6:40 AM, Ariel Rokem >>>>>>>>>>>> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Hi Vanessa, >>>>>>>>>>>>> >>>>>>>>>>>>> I have a few comments/suggestions: >>>>>>>>>>>>> >>>>>>>>>>>>> 1. I would rather not have the front page be the project >>>>>>>>>>>>> directory. In my opinion, the front page should instead explain briefly >>>>>>>>>>>>> what this is, and lead visitors to the various other parts of the website. >>>>>>>>>>>>> >>>>>>>>>>>>> 2. There are a few issues with formatting in the Code of >>>>>>>>>>>>> Conduct page (bullet points appear as continued lines) >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> 3. Please include mindboggle in the project directory (it's >>>>>>>>>>>> been recently added!). >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>>> Other than these two, I think this is ready to be introduced >>>>>>>>>>>>> as a PR against the nipy/nipy.github.com repository (you >>>>>>>>>>>>> don't need any admin rights to do that, but I also just added you to "team >>>>>>>>>>>>> blog" on the github nipy org, so you can even do the merge yourself, if you >>>>>>>>>>>>> want). >>>>>>>>>>>>> >>>>>>>>>>>>> Cheers, >>>>>>>>>>>>> >>>>>>>>>>>>> Ariel >>>>>>>>>>>>> >>>>>>>>>>>>> On Mon, Oct 26, 2015 at 12:56 PM, vanessa sochat < >>>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Hi Eleftherios, >>>>>>>>>>>>>> >>>>>>>>>>>>>> It definitely would be possible! I'm not any sort of admin in >>>>>>>>>>>>>> the nipy space, so the farthest I could take it is having the repo for >>>>>>>>>>>>>> someone to deploy on nipy.github.io. The code is here: >>>>>>>>>>>>>> >>>>>>>>>>>>>> https://github.com/vsoch/nipy-jekyll >>>>>>>>>>>>>> >>>>>>>>>>>>>> and deployment on my github pages: >>>>>>>>>>>>>> >>>>>>>>>>>>>> http://vsoch.github.io/nipy-jekyll/ >>>>>>>>>>>>>> >>>>>>>>>>>>>> I mostly stopped working on it because I accomplished all the >>>>>>>>>>>>>> things that I set out to do (jekyll site, preview on continuous integration >>>>>>>>>>>>>> with circle, standard ways to add new content, and an easy way to multiple >>>>>>>>>>>>>> ways to add content a la github >>>>>>>>>>>>>> , or for >>>>>>>>>>>>>> those who aren't comfortable with pushing and pulling, la >>>>>>>>>>>>>> social media ). I think I >>>>>>>>>>>>>> had suggested moving forward for people to try out tumblr (and start >>>>>>>>>>>>>> contributing content!), and if people were happy, to move it over to the >>>>>>>>>>>>>> nipy repo. If the outcome of the work was not a desired solution, I was >>>>>>>>>>>>>> content to just let it be. However if there is interest, that is definitely >>>>>>>>>>>>>> still a possibility. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Best, >>>>>>>>>>>>>> >>>>>>>>>>>>>> Vanessa >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Mon, Oct 26, 2015 at 12:34 PM, Eleftherios Garyfallidis < >>>>>>>>>>>>>> garyfallidis at gmail.com> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Hi Vanessa and all, >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Would it be possible to switch to your much nicer new >>>>>>>>>>>>>>> website? I still see the older version being up. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Do you have a plan for this? Or you waiting for some >>>>>>>>>>>>>>> feedback on our side? >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Best regards, >>>>>>>>>>>>>>> Eleftherios >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Wed, Sep 2, 2015 at 12:57 PM, Ben Cipollini < >>>>>>>>>>>>>>> bcipolli at ucsd.edu> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> I think they're good for mobile sites. I think they're >>>>>>>>>>>>>>>> generally expanded by default on full screens, and compacted on mobile. So >>>>>>>>>>>>>>>> I suggest to keep it, but have a regular menu that's showing on full >>>>>>>>>>>>>>>> screens and hidden on mobile. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Wed, Sep 2, 2015 at 9:51 AM, vanessa sochat < >>>>>>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> That's a good suggestion, and I'll add as an issue so I >>>>>>>>>>>>>>>>> can find it easily when the next round of changes comes around. Generally, >>>>>>>>>>>>>>>>> these "hamburger" menu things are useless functionality wise, and only >>>>>>>>>>>>>>>>> serve to aesthetically "get rid of the navigation" to have a clean looking >>>>>>>>>>>>>>>>> site. In our case, it is probably just annoying to have the extra clicks. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Wed, Sep 2, 2015 at 8:50 AM, Ben Cipollini < >>>>>>>>>>>>>>>>> bcipolli at ucsd.edu> wrote: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> This looks great. It's also cool to see "ask a question" >>>>>>>>>>>>>>>>>> integrated into the website, though we'll still have to hash things out for >>>>>>>>>>>>>>>>>> that. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Rather than open a github issue (which few may see), I'll >>>>>>>>>>>>>>>>>> make a suggestion here: can we have the menu expanded by default when >>>>>>>>>>>>>>>>>> accessing via a full-size screen? >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> It feels odd to me to have to expand the menu in order to >>>>>>>>>>>>>>>>>> navigate anywhere, by default. To me, navigation options should be obvious, >>>>>>>>>>>>>>>>>> unless pressed for space. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> On Sun, Aug 30, 2015 at 1:14 PM, vanessa sochat < >>>>>>>>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Hi Everyone, >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> I've finished work on the "contribute" page with my >>>>>>>>>>>>>>>>>>> thinking for how to contribute various content: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> http://vsoch.github.io/nipy-jekyll/contribute.html >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> and as an example, put up a quick blog post: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> http://neuroimaging.tumblr.com/ >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> The old "example" blog posts are hidden (private) and >>>>>>>>>>>>>>>>>>> can be viewed if you are a contributor. I'd like to add anyone and everyone >>>>>>>>>>>>>>>>>>> interested to contribute as "official" contributors via tumblr - if you are >>>>>>>>>>>>>>>>>>> interested please send me your email address. I've already invited some of >>>>>>>>>>>>>>>>>>> you for which I know the email. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Best, >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Vanessa >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>>>>>>>> Stanford University >>>>>>>>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>>>>>> Stanford University >>>>>>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>> Neuroimaging mailing list >>>>>>>>>>>>>>> Neuroimaging at python.org >>>>>>>>>>>>>>> https://mail.python.org/mailman/listinfo/neuroimaging >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> -- >>>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>>> Stanford University >>>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>>> >>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>> 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 >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>> Stanford University >>>>>>>>>>> (603) 321-0676 >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> 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 >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Vanessa Villamia Sochat >>>>>>>>> Stanford University >>>>>>>>> (603) 321-0676 >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Vanessa Villamia Sochat >>>>>>>> Stanford University >>>>>>>> (603) 321-0676 >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> 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 >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Vanessa Villamia Sochat >>>>>> Stanford University >>>>>> (603) 321-0676 >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Vanessa Villamia Sochat >>>>> Stanford University >>>>> (603) 321-0676 >>>>> >>>> >>>> >>>> >>>> -- >>>> Vanessa Villamia Sochat >>>> Stanford University >>>> (603) 321-0676 >>>> >>>> _______________________________________________ >>>> 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 >>> >>> >> >> _______________________________________________ >> 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: From jcohen at polymtl.ca Tue Oct 27 17:17:13 2015 From: jcohen at polymtl.ca (Julien Cohen-Adad) Date: Tue, 27 Oct 2015 17:17:13 -0400 Subject: [Neuroimaging] Site Contributions In-Reply-To: References: Message-ID: will do. thanks! On Tue, Oct 27, 2015 at 4:20 PM, Ariel Rokem wrote: > Hey Julien, > > On Tue, Oct 27, 2015 at 12:04 PM, Julien Cohen-Adad > wrote: > >> Hi everyone, >> >> would it be possible to add our neuroimaging project to the nipy website? >> https://github.com/neuropoly/spinalcordtoolbox >> >> > I am +1 for adding the toolbox to the project directory. > > How about putting in a PR on the website Github repo for this? > > http://nipy.org/contribute.html#add-a-package > > > >> it is 100% python and notably uses nibabel and dipy. >> >> cheers >> julien >> >> >> -- >> Julien Cohen-Adad, PhD >> Assistant Professor, Polytechnique Montreal >> Associate Director, Functional Neuroimaging Unit, University of Montreal >> Phone: 514 340 5121 (office: 2264); Skype: jcohenadad >> Web: www.neuro.polymtl.ca >> >> On Tue, Oct 27, 2015 at 2:44 PM, Eleftherios Garyfallidis < >> garyfallidis at gmail.com> wrote: >> >>> Epic awesomeness! Thank you Vanessa! >>> >>> On Tue, Oct 27, 2015 at 2:40 PM, Ariel Rokem wrote: >>> >>>> Great work! Will resubmit my blog-post PR through the new mechanism. >>>> >>>> On Tue, Oct 27, 2015 at 11:38 AM, vanessa sochat >>>> wrote: >>>> >>>>> Hi everyone, >>>>> >>>>> I just added the missing CNAME file, apologies for the oversight, I >>>>> did not know it was there :) It looks like nipy.org is working as >>>>> well now too - please let me know if you see any issues. >>>>> >>>>> Circle is expected to have some changes in the next week, so I am >>>>> going to wait for the weekend to debug the building of artifacts. Will let >>>>> you know when I fix that up! >>>>> >>>>> Best, >>>>> >>>>> Vanessa >>>>> >>>>> On Tue, Oct 27, 2015 at 11:30 AM, vanessa sochat >>>> > wrote: >>>>> >>>>>> Hi Everyone, >>>>>> >>>>>> Site is live! >>>>>> >>>>>> https://nipy.github.io/ >>>>>> >>>>>> Ariel - I'm not sure how to set up the nipy.org. Would you mind >>>>>> taking a look and fixing that up? >>>>>> >>>>>> Circle is having some bugs with the artifact generation, I think I >>>>>> can probably fix it, but not during the work week. Ben - I added your >>>>>> contribution to the README but didn't get the other comment in time. The >>>>>> good news is now anyone and everyone can submit changes as PR. I encourage >>>>>> everyone to familiarize yourself with tumblr, and start contributing >>>>>> content, PRs to tweak it. >>>>>> >>>>>> Best, >>>>>> >>>>>> Vanessa >>>>>> >>>>>> On Tue, Oct 27, 2015 at 11:10 AM, vanessa sochat < >>>>>> vsochat at stanford.edu> wrote: >>>>>> >>>>>>> Got it! Thanks! :) >>>>>>> >>>>>>> On Tue, Oct 27, 2015 at 11:07 AM, Ariel Rokem >>>>>>> wrote: >>>>>>> >>>>>>>> Hi, >>>>>>>> On Tue, Oct 27, 2015 at 10:56 AM, vanessa sochat < >>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>> >>>>>>>>> Hi Ariel, >>>>>>>>> >>>>>>>>> Please add me as an admin to nipy.github.io, so I can set up >>>>>>>>> circle for CI. Thanks! >>>>>>>>> >>>>>>>>> >>>>>>>> I believe I just did that. Let me know how you get on. >>>>>>>> >>>>>>>> >>>>>>>>> Best, >>>>>>>>> >>>>>>>>> Vanessa >>>>>>>>> >>>>>>>>> On Tue, Oct 27, 2015 at 10:42 AM, vanessa sochat < >>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>> >>>>>>>>>> Just as a proof of concept for adding a project - I just added a >>>>>>>>>> new entry to the data file (copy pasting basically), copied one file, and >>>>>>>>>> the entire process took me like, 48 seconds :) >>>>>>>>>> >>>>>>>>>> On Tue, Oct 27, 2015 at 10:36 AM, Ben Cipollini < >>>>>>>>>> bcipolli at ucsd.edu> wrote: >>>>>>>>>> >>>>>>>>>>> Thanks Vanessa! >>>>>>>>>>> >>>>>>>>>>> On Tue, Oct 27, 2015 at 10:35 AM, vanessa sochat < >>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>> >>>>>>>>>>>> I will do some tweaks and get the site working. There will be a >>>>>>>>>>>> change for the URL so there might be some bugs with my initial release, but >>>>>>>>>>>> I'll get it fixed asap. Will send an update later. >>>>>>>>>>>> >>>>>>>>>>>> On Tue, Oct 27, 2015 at 6:48 AM, Ariel Rokem >>>>>>>>>>>> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Oh, one more: >>>>>>>>>>>>> >>>>>>>>>>>>> On Tue, Oct 27, 2015 at 6:40 AM, Ariel Rokem >>>>>>>>>>>> > wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Hi Vanessa, >>>>>>>>>>>>>> >>>>>>>>>>>>>> I have a few comments/suggestions: >>>>>>>>>>>>>> >>>>>>>>>>>>>> 1. I would rather not have the front page be the project >>>>>>>>>>>>>> directory. In my opinion, the front page should instead explain briefly >>>>>>>>>>>>>> what this is, and lead visitors to the various other parts of the website. >>>>>>>>>>>>>> >>>>>>>>>>>>>> 2. There are a few issues with formatting in the Code of >>>>>>>>>>>>>> Conduct page (bullet points appear as continued lines) >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> 3. Please include mindboggle in the project directory (it's >>>>>>>>>>>>> been recently added!). >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>>> Other than these two, I think this is ready to be introduced >>>>>>>>>>>>>> as a PR against the nipy/nipy.github.com repository (you >>>>>>>>>>>>>> don't need any admin rights to do that, but I also just added you to "team >>>>>>>>>>>>>> blog" on the github nipy org, so you can even do the merge yourself, if you >>>>>>>>>>>>>> want). >>>>>>>>>>>>>> >>>>>>>>>>>>>> Cheers, >>>>>>>>>>>>>> >>>>>>>>>>>>>> Ariel >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Mon, Oct 26, 2015 at 12:56 PM, vanessa sochat < >>>>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Hi Eleftherios, >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> It definitely would be possible! I'm not any sort of admin >>>>>>>>>>>>>>> in the nipy space, so the farthest I could take it is having the repo for >>>>>>>>>>>>>>> someone to deploy on nipy.github.io. The code is here: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> https://github.com/vsoch/nipy-jekyll >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> and deployment on my github pages: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> http://vsoch.github.io/nipy-jekyll/ >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> I mostly stopped working on it because I accomplished all >>>>>>>>>>>>>>> the things that I set out to do (jekyll site, preview on continuous >>>>>>>>>>>>>>> integration with circle, standard ways to add new content, and an easy way >>>>>>>>>>>>>>> to multiple ways to add content a la github >>>>>>>>>>>>>>> , or >>>>>>>>>>>>>>> for those who aren't comfortable with pushing and pulling, la >>>>>>>>>>>>>>> social media ). I think I >>>>>>>>>>>>>>> had suggested moving forward for people to try out tumblr (and start >>>>>>>>>>>>>>> contributing content!), and if people were happy, to move it over to the >>>>>>>>>>>>>>> nipy repo. If the outcome of the work was not a desired solution, I was >>>>>>>>>>>>>>> content to just let it be. However if there is interest, that is definitely >>>>>>>>>>>>>>> still a possibility. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Best, >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Vanessa >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Mon, Oct 26, 2015 at 12:34 PM, Eleftherios Garyfallidis < >>>>>>>>>>>>>>> garyfallidis at gmail.com> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Hi Vanessa and all, >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Would it be possible to switch to your much nicer new >>>>>>>>>>>>>>>> website? I still see the older version being up. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Do you have a plan for this? Or you waiting for some >>>>>>>>>>>>>>>> feedback on our side? >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Best regards, >>>>>>>>>>>>>>>> Eleftherios >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Wed, Sep 2, 2015 at 12:57 PM, Ben Cipollini < >>>>>>>>>>>>>>>> bcipolli at ucsd.edu> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> I think they're good for mobile sites. I think they're >>>>>>>>>>>>>>>>> generally expanded by default on full screens, and compacted on mobile. So >>>>>>>>>>>>>>>>> I suggest to keep it, but have a regular menu that's showing on full >>>>>>>>>>>>>>>>> screens and hidden on mobile. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Wed, Sep 2, 2015 at 9:51 AM, vanessa sochat < >>>>>>>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> That's a good suggestion, and I'll add as an issue so I >>>>>>>>>>>>>>>>>> can find it easily when the next round of changes comes around. Generally, >>>>>>>>>>>>>>>>>> these "hamburger" menu things are useless functionality wise, and only >>>>>>>>>>>>>>>>>> serve to aesthetically "get rid of the navigation" to have a clean looking >>>>>>>>>>>>>>>>>> site. In our case, it is probably just annoying to have the extra clicks. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> On Wed, Sep 2, 2015 at 8:50 AM, Ben Cipollini < >>>>>>>>>>>>>>>>>> bcipolli at ucsd.edu> wrote: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> This looks great. It's also cool to see "ask a question" >>>>>>>>>>>>>>>>>>> integrated into the website, though we'll still have to hash things out for >>>>>>>>>>>>>>>>>>> that. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Rather than open a github issue (which few may see), >>>>>>>>>>>>>>>>>>> I'll make a suggestion here: can we have the menu expanded by default when >>>>>>>>>>>>>>>>>>> accessing via a full-size screen? >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> It feels odd to me to have to expand the menu in order >>>>>>>>>>>>>>>>>>> to navigate anywhere, by default. To me, navigation options should be >>>>>>>>>>>>>>>>>>> obvious, unless pressed for space. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> On Sun, Aug 30, 2015 at 1:14 PM, vanessa sochat < >>>>>>>>>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Hi Everyone, >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> I've finished work on the "contribute" page with my >>>>>>>>>>>>>>>>>>>> thinking for how to contribute various content: >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> http://vsoch.github.io/nipy-jekyll/contribute.html >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> and as an example, put up a quick blog post: >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> http://neuroimaging.tumblr.com/ >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> The old "example" blog posts are hidden (private) and >>>>>>>>>>>>>>>>>>>> can be viewed if you are a contributor. I'd like to add anyone and everyone >>>>>>>>>>>>>>>>>>>> interested to contribute as "official" contributors via tumblr - if you are >>>>>>>>>>>>>>>>>>>> interested please send me your email address. I've already invited some of >>>>>>>>>>>>>>>>>>>> you for which I know the email. >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Best, >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Vanessa >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>>>>>>>>> Stanford University >>>>>>>>>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>>>>>>> Stanford University >>>>>>>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>> Neuroimaging mailing list >>>>>>>>>>>>>>>> Neuroimaging at python.org >>>>>>>>>>>>>>>> https://mail.python.org/mailman/listinfo/neuroimaging >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>>>> Stanford University >>>>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>> 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 >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>> Stanford University >>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> 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 >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>> Stanford University >>>>>>>>>> (603) 321-0676 >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Vanessa Villamia Sochat >>>>>>>>> Stanford University >>>>>>>>> (603) 321-0676 >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> 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 >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Vanessa Villamia Sochat >>>>>>> Stanford University >>>>>>> (603) 321-0676 >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Vanessa Villamia Sochat >>>>>> Stanford University >>>>>> (603) 321-0676 >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Vanessa Villamia Sochat >>>>> Stanford University >>>>> (603) 321-0676 >>>>> >>>>> _______________________________________________ >>>>> 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 >>>> >>>> >>> >>> _______________________________________________ >>> 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 >> >> > > _______________________________________________ > Neuroimaging mailing list > Neuroimaging at python.org > https://mail.python.org/mailman/listinfo/neuroimaging > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandre.gramfort at telecom-paristech.fr Tue Oct 27 17:24:30 2015 From: alexandre.gramfort at telecom-paristech.fr (Alexandre Gramfort) Date: Tue, 27 Oct 2015 22:24:30 +0100 Subject: [Neuroimaging] [ANN] MNE-Python 0.10 Release Message-ID: Hi, We are pleased to announce the new 0.10 release of MNE-python. A few highlights: Forward modeling: - Add support for BEM model creation with mne.make_bem_model - Add support for BEM solution computation mne.make_bem_solution - New "mne flash_bem" command to compute BEM surfaces from Flash MRI images - Add source space morphing Stats / Processing: - Add support for generalized M-way repeated measures ANOVA for fully balanced designs - Add new object mne.decoding.TimeDecoding for decoding sensors' evoked response across time - Add new method mne.preprocessing.Xdawn for denoising and decoding of ERP/ERF - Add new object mne.decoding.LinearModel for decoding M/EEG data and interpreting coefficients of linear models with patterns attribute - Adapt corrmap function (Viola et al. 2009) to semi-automatically detect similar independent components across data sets Visualisation: - Add interactive plotting of topomap from time-frequency representation by selection ROI in time-frequency plane - New ICA plotters for raw and epoch components - New epochs browser to interactively view and manipulate epochs - Add support for plotting patterns/filters mne.decoding.csp.CSP and mne.decoding.base.LinearModel - Add interactive plotting of single trials by right clicking on channel name in epochs browser - Add support for drawing topomaps by selecting a time-interval in mne.Evoked.plot Code quality: - Speed up TF-MxNE inverse solver with block coordinate descent - Speed up zero-phase overlap-add (default) filtering by a factor of up to 2 using linearity - Add support for saving large epochs into multiple files - Add support for jointly resampling a raw object and event matrix to avoid issues with resampling status channels - Add preload argument to mne.read_epochs to enable on-demand reads from disk - Big rewrite of simulation module. Allows to simulate raw with artefacts (ECG, EOG) and evoked data, exploiting the forward solution. Dataset / reproducible results - Add fetcher mne.datasets.brainstorm for datasets used by Brainstorm in their tutorials Documentation: - New web site with new documentation structure to facilitate documentation improvements. For a full list of improvements and API changes, see: http://martinos.org/mne/stable/whats_new.html#version-0-10 To install the latest release the following command should do the job: pip install --upgrade --user mne As usual we welcome your bug reports, feature requests, critics and contributions. Some links: - https://github.com/mne-tools/mne-python (code + readme on how to install) - http://martinos.org/mne (full MNE documentation) Follow us on Twitter: https://twitter.com/mne_python Regards, The MNE-Python developers People who contributed to this release with their number of commits: The committer list for this release is the following (preceded by number of commits): 273 Eric Larson 270 Jaakko Leppakangas 194 Alexandre Gramfort 128 Denis A. Engemann 114 Jona Sassenhagen 107 Mark Wronkiewicz 97 Teon Brooks 81 Lorenzo De Santis 55 Yousra Bekhti 54 Jean-Remi King 48 Romain Trachel 45 Mainak Jas 40 Alexandre Barachant 32 Marijn van Vliet 26 Jair Montoya 22 Chris Holdgraf 16 Christopher J. Bailey 7 Christian Brodbeck 5 Natalie Klein 5 Fede Raimondo 5 Alan Leggitt 5 Roan LaPlante 5 Ross Maddox 4 Dan G. Wakeman 3 Daniel McCloy 3 Daniel Strohmeier 1 Jussi Nurminen From arokem at gmail.com Wed Oct 28 19:53:58 2015 From: arokem at gmail.com (Ariel Rokem) Date: Wed, 28 Oct 2015 16:53:58 -0700 Subject: [Neuroimaging] [dipy]Numpy on py2.6-32 bot Message-ID: Does anyone know what version of numpy is running on this buildbot? http://nipy.bic.berkeley.edu/builders/dipy-py2.6-32 We are planning to drop support for numpy<1.7 with the upcoming release (unless someone tells me that's crazy) and I suspect that these failures could be because this bot hasn't gotten the memo. Thanks! -------------- next part -------------- An HTML attachment was scrubbed... URL: From njs at pobox.com Wed Oct 28 19:56:53 2015 From: njs at pobox.com (Nathaniel Smith) Date: Wed, 28 Oct 2015 16:56:53 -0700 Subject: [Neuroimaging] [dipy]Numpy on py2.6-32 bot In-Reply-To: References: Message-ID: Useful general tip: if you put a 'pip freeze' command in your build script, then it dumps the versions of all installed packages to stdout and you can look at them in your build logs later. -n On Wed, Oct 28, 2015 at 4:53 PM, Ariel Rokem wrote: > Does anyone know what version of numpy is running on this buildbot? > > http://nipy.bic.berkeley.edu/builders/dipy-py2.6-32 > > We are planning to drop support for numpy<1.7 with the upcoming release > (unless someone tells me that's crazy) and I suspect that these failures > could be because this bot hasn't gotten the memo. > > Thanks! > > _______________________________________________ > Neuroimaging mailing list > Neuroimaging at python.org > https://mail.python.org/mailman/listinfo/neuroimaging > -- Nathaniel J. Smith -- http://vorpus.org From spilgrim at umail.iu.edu Wed Oct 28 20:47:55 2015 From: spilgrim at umail.iu.edu (Samuel Pilgrim) Date: Wed, 28 Oct 2015 20:47:55 -0400 Subject: [Neuroimaging] Reconstruction of the diffusion signal with the Tensor model after de-noising In-Reply-To: References: Message-ID: Ariel, Sorry it took me a while to get back to you. I just wanted to let you know that your advice was quite helpful. I believe I've more or less gotten tensor fitting to work after applying the denoising procedure. There are still a number of other difficulties with the script that I'm working on, so I'm looking forward to your visit to Franco's lab. Thanks again, Sam On Fri, Oct 16, 2015 at 9:28 AM, Samuel Pilgrim wrote: > Ariel, > Thanks a lot. I'll try that out today/tomorrow and get back to you. > > Best, > Sam > > On Fri, Oct 16, 2015 at 2:46 AM, Ariel Rokem wrote: > >> Hi Sam, >> >> You might be able to draw inspiration from the new DKI example, in which >> denoising is first applied: >> >> https://github.com/nipy/dipy/blob/master/doc/examples/reconst_dki.py#L124 >> >> And then a model is fit (in this case the DKI model, but the TensorModel >> would look very similar): >> >> https://github.com/nipy/dipy/blob/master/doc/examples/reconst_dki.py#L124 >> https://github.com/nipy/dipy/blob/master/doc/examples/reconst_dki.py#L145 >> >> Does that work for you? >> >> Cheers, >> >> Ariel >> >> >> >> On Wed, Oct 14, 2015 at 2:21 PM, Samuel Pilgrim >> wrote: >> >>> Neuroimaging mailing list, >>> >>> I'm an undergraduate experimenting with dipy and am currently working >>> on a project that would combine a few of the examples given in the >>> documentation. In particular, I'd like to be able to take one of the >>> sample data-sets, apply the de-noising procedure described in the >>> documentation under "Denoise images using Non-Local Means" and then use >>> the tensor model to reconstruct the diffusion signal using the de-noised >>> data. I have scripts that do each of these things separately, but when I >>> try to do reconstruction with de-noised data, I get an alignment error on >>> the line that reads " tenfit = tenmodel.fit(maskdata) ". I believe >>> the issue is caused by a command in the de-noising part of the script that >>> goes " data = data[..., 1] ". After this line, the dimension of the >>> object data has been reduced by one, (i.e. the command print(data.shape) >>> returns a tuple of 3 integers instead of 4. I think this is what's causing >>> the alignment issue later, but I also can't get it to run without this >>> line. Any assistance would be greatly appreciated. >>> >>> Best, >>> Sam >>> >>> _______________________________________________ >>> 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: From vsochat at stanford.edu Sat Oct 31 15:44:04 2015 From: vsochat at stanford.edu (vanessa sochat) Date: Sat, 31 Oct 2015 12:44:04 -0700 Subject: [Neuroimaging] Site Contributions In-Reply-To: References: Message-ID: Hi Roman, Thanks for the details about neurostars - the general framework to provide a forum is really great and I can definitely see integrating the API into some of our resources in the future. For the particular case of nipy, given the challenges of hosting it on a static place, and that we have very few contributions, it's probably not the best use of time (for now) to try to automatically integrate into neurostars. I'll be happy to forward people along manually for the time being. I am going to keep your note handy, however, because I definitely would see value in adding functionality to the API to post programatically! Thanks again, Best, Vanessa On Sat, Oct 31, 2015 at 2:33 AM, Roman Valls Guimer? wrote: > Hi Vanessa, Chris, Satra, > > I quickly parsed your thread so I might be missing the important > questions, chime in if so... Better email integration has been an wished > feature for a quite a while now, hopefully in the 4th iteration of the > biostars engine we'll get there: > > https://github.com/ialbert/biostar-central/tree/4.0 > > (@satra, Istvan is changing the database backend to MongoDB, perhaps a > good opportunity to also experiment/switch to more semantic-friendly > databases?) > > Also, Vanessa, I'm not sure what is the state of neurostars API since I've > not been mantaining the site as it deserves, but you can use it, i.e: > > http://neurostars.org/api/traffic/ > > More info over here: > > https://neurostars.org/info/api/ > > Anyhow, unfortunately this year's GSoC student wasn't as prolific as Paolo > Coffetti, but I hope we can push the site forward together in the > future.... landing California on the 4th Nov, are you up for a combined > hackathon on neurostars and/or CWL? > > Cheers! > Roman > > On Tue, Oct 27, 2015 at 9:09 PM, vanessa sochat > wrote: > >> Ok, the first one was a little messy because I enabled twitter >> integration after the first post (and so I needed to reblog), but now the >> two are connected, so you can keep track of posts via twitter: >> >> https://twitter.com/nipyorg >> >> Best, >> >> Vanessa >> >> On Tue, Oct 27, 2015 at 12:50 PM, vanessa sochat >> wrote: >> >>> How about nipyorg for a twitter? Some hairy dude in a swimming pool has >>> "nipy" >>> >>> On Tue, Oct 27, 2015 at 12:47 PM, Chris Filo Gorgolewski < >>> krzysztof.gorgolewski at gmail.com> wrote: >>> >>>> neurostars is based on biostars and provide a variety of ways to >>>> integrate sources. Satra and Roman will know more. >>>> >>>> Best, >>>> Chris >>>> >>>> On Tue, Oct 27, 2015 at 12:38 PM, vanessa sochat >>>> wrote: >>>> >>>>> Sure thing. There might be a trick to integrate the two, I'll look >>>>> into it. I just added comments: >>>>> >>>>> >>>>> http://neuroimaging.tumblr.com/post/132031797431/write-stdout-to-file-for-fsl-cluster >>>>> >>>>> and for now I will redirect people to neurostars. >>>>> >>>>> Here is how to post via email: >>>>> >>>>> https://www.tumblr.com/docs/en/posting#emailpostheader >>>>> >>>>> The email for us is: >>>>> >>>>> [image: Inline image 1] >>>>> >>>>> This is so great! Anyone can contribute absolutely anything, and they >>>>> don't need to know what a PR is :) >>>>> >>>>> On Tue, Oct 27, 2015 at 12:31 PM, Ben Cipollini >>>>> wrote: >>>>> >>>>>> Oh no, another place for discussion? :-/ >>>>>> >>>>>> Can we redirect them to the mailing list or neurostars? >>>>>> >>>>>> On Tue, Oct 27, 2015 at 12:19 PM, vanessa sochat < >>>>>> vsochat at stanford.edu> wrote: >>>>>> >>>>>>> Hey Ariel, >>>>>>> >>>>>>> Do we have a nipy discus? I would like to add comments to posts so >>>>>>> we can talk about things like these: >>>>>>> >>>>>>> >>>>>>> http://neuroimaging.tumblr.com/post/132031797431/write-stdout-to-file-for-fsl-cluster >>>>>>> >>>>>>> Best, >>>>>>> >>>>>>> Vanessa >>>>>>> >>>>>>> On Tue, Oct 27, 2015 at 11:44 AM, Ben Cipollini >>>>>>> wrote: >>>>>>> >>>>>>>> Great! I'll resubmit my "issue" to the nipy repo and start >>>>>>>> "watching" it :) >>>>>>>> >>>>>>>> On Tue, Oct 27, 2015 at 11:40 AM, Ariel Rokem >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Great work! Will resubmit my blog-post PR through the new >>>>>>>>> mechanism. >>>>>>>>> >>>>>>>>> On Tue, Oct 27, 2015 at 11:38 AM, vanessa sochat < >>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>> >>>>>>>>>> Hi everyone, >>>>>>>>>> >>>>>>>>>> I just added the missing CNAME file, apologies for the oversight, >>>>>>>>>> I did not know it was there :) It looks like nipy.org is working >>>>>>>>>> as well now too - please let me know if you see any issues. >>>>>>>>>> >>>>>>>>>> Circle is expected to have some changes in the next week, so I am >>>>>>>>>> going to wait for the weekend to debug the building of artifacts. Will let >>>>>>>>>> you know when I fix that up! >>>>>>>>>> >>>>>>>>>> Best, >>>>>>>>>> >>>>>>>>>> Vanessa >>>>>>>>>> >>>>>>>>>> On Tue, Oct 27, 2015 at 11:30 AM, vanessa sochat < >>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>> >>>>>>>>>>> Hi Everyone, >>>>>>>>>>> >>>>>>>>>>> Site is live! >>>>>>>>>>> >>>>>>>>>>> https://nipy.github.io/ >>>>>>>>>>> >>>>>>>>>>> Ariel - I'm not sure how to set up the nipy.org. Would you mind >>>>>>>>>>> taking a look and fixing that up? >>>>>>>>>>> >>>>>>>>>>> Circle is having some bugs with the artifact generation, I think >>>>>>>>>>> I can probably fix it, but not during the work week. Ben - I added your >>>>>>>>>>> contribution to the README but didn't get the other comment in time. The >>>>>>>>>>> good news is now anyone and everyone can submit changes as PR. I encourage >>>>>>>>>>> everyone to familiarize yourself with tumblr, and start contributing >>>>>>>>>>> content, PRs to tweak it. >>>>>>>>>>> >>>>>>>>>>> Best, >>>>>>>>>>> >>>>>>>>>>> Vanessa >>>>>>>>>>> >>>>>>>>>>> On Tue, Oct 27, 2015 at 11:10 AM, vanessa sochat < >>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>> >>>>>>>>>>>> Got it! Thanks! :) >>>>>>>>>>>> >>>>>>>>>>>> On Tue, Oct 27, 2015 at 11:07 AM, Ariel Rokem >>>>>>>>>>> > wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Hi, >>>>>>>>>>>>> On Tue, Oct 27, 2015 at 10:56 AM, vanessa sochat < >>>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Hi Ariel, >>>>>>>>>>>>>> >>>>>>>>>>>>>> Please add me as an admin to nipy.github.io, so I can set up >>>>>>>>>>>>>> circle for CI. Thanks! >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> I believe I just did that. Let me know how you get on. >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>>> Best, >>>>>>>>>>>>>> >>>>>>>>>>>>>> Vanessa >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Tue, Oct 27, 2015 at 10:42 AM, vanessa sochat < >>>>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Just as a proof of concept for adding a project - I just >>>>>>>>>>>>>>> added a new entry to the data file (copy pasting basically), copied one >>>>>>>>>>>>>>> file, and the entire process took me like, 48 seconds :) >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Tue, Oct 27, 2015 at 10:36 AM, Ben Cipollini < >>>>>>>>>>>>>>> bcipolli at ucsd.edu> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Thanks Vanessa! >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Tue, Oct 27, 2015 at 10:35 AM, vanessa sochat < >>>>>>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> I will do some tweaks and get the site working. There will >>>>>>>>>>>>>>>>> be a change for the URL so there might be some bugs with my initial >>>>>>>>>>>>>>>>> release, but I'll get it fixed asap. Will send an update later. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Tue, Oct 27, 2015 at 6:48 AM, Ariel Rokem < >>>>>>>>>>>>>>>>> arokem at gmail.com> wrote: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Oh, one more: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> On Tue, Oct 27, 2015 at 6:40 AM, Ariel Rokem < >>>>>>>>>>>>>>>>>> arokem at gmail.com> wrote: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Hi Vanessa, >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> I have a few comments/suggestions: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> 1. I would rather not have the front page be the project >>>>>>>>>>>>>>>>>>> directory. In my opinion, the front page should instead explain briefly >>>>>>>>>>>>>>>>>>> what this is, and lead visitors to the various other parts of the website. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> 2. There are a few issues with formatting in the Code of >>>>>>>>>>>>>>>>>>> Conduct page (bullet points appear as continued lines) >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> 3. Please include mindboggle in the project directory >>>>>>>>>>>>>>>>>> (it's been recently added!). >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Other than these two, I think this is ready to be >>>>>>>>>>>>>>>>>>> introduced as a PR against the nipy/nipy.github.com >>>>>>>>>>>>>>>>>>> repository (you don't need any admin rights to do that, but I also just >>>>>>>>>>>>>>>>>>> added you to "team blog" on the github nipy org, so you can even do the >>>>>>>>>>>>>>>>>>> merge yourself, if you want). >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Cheers, >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Ariel >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> On Mon, Oct 26, 2015 at 12:56 PM, vanessa sochat < >>>>>>>>>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Hi Eleftherios, >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> It definitely would be possible! I'm not any sort of >>>>>>>>>>>>>>>>>>>> admin in the nipy space, so the farthest I could take it is having the repo >>>>>>>>>>>>>>>>>>>> for someone to deploy on nipy.github.io. The code is >>>>>>>>>>>>>>>>>>>> here: >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> https://github.com/vsoch/nipy-jekyll >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> and deployment on my github pages: >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> http://vsoch.github.io/nipy-jekyll/ >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> I mostly stopped working on it because I accomplished >>>>>>>>>>>>>>>>>>>> all the things that I set out to do (jekyll site, preview on continuous >>>>>>>>>>>>>>>>>>>> integration with circle, standard ways to add new content, and an easy way >>>>>>>>>>>>>>>>>>>> to multiple ways to add content a la github >>>>>>>>>>>>>>>>>>>> , >>>>>>>>>>>>>>>>>>>> or for those who aren't comfortable with pushing and pulling, la >>>>>>>>>>>>>>>>>>>> social media ). I >>>>>>>>>>>>>>>>>>>> think I had suggested moving forward for people to try out tumblr (and >>>>>>>>>>>>>>>>>>>> start contributing content!), and if people were happy, to move it over to >>>>>>>>>>>>>>>>>>>> the nipy repo. If the outcome of the work was not a desired solution, I was >>>>>>>>>>>>>>>>>>>> content to just let it be. However if there is interest, that is definitely >>>>>>>>>>>>>>>>>>>> still a possibility. >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Best, >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Vanessa >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> On Mon, Oct 26, 2015 at 12:34 PM, Eleftherios >>>>>>>>>>>>>>>>>>>> Garyfallidis wrote: >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> Hi Vanessa and all, >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> Would it be possible to switch to your much nicer new >>>>>>>>>>>>>>>>>>>>> website? I still see the older version being up. >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> Do you have a plan for this? Or you waiting for some >>>>>>>>>>>>>>>>>>>>> feedback on our side? >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> Best regards, >>>>>>>>>>>>>>>>>>>>> Eleftherios >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> On Wed, Sep 2, 2015 at 12:57 PM, Ben Cipollini < >>>>>>>>>>>>>>>>>>>>> bcipolli at ucsd.edu> wrote: >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> I think they're good for mobile sites. I think >>>>>>>>>>>>>>>>>>>>>> they're generally expanded by default on full screens, and compacted on >>>>>>>>>>>>>>>>>>>>>> mobile. So I suggest to keep it, but have a regular menu that's showing on >>>>>>>>>>>>>>>>>>>>>> full screens and hidden on mobile. >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> On Wed, Sep 2, 2015 at 9:51 AM, vanessa sochat < >>>>>>>>>>>>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> That's a good suggestion, and I'll add as an issue >>>>>>>>>>>>>>>>>>>>>>> so I can find it easily when the next round of changes comes around. >>>>>>>>>>>>>>>>>>>>>>> Generally, these "hamburger" menu things are useless functionality wise, >>>>>>>>>>>>>>>>>>>>>>> and only serve to aesthetically "get rid of the navigation" to have a clean >>>>>>>>>>>>>>>>>>>>>>> looking site. In our case, it is probably just annoying to have the extra >>>>>>>>>>>>>>>>>>>>>>> clicks. >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> On Wed, Sep 2, 2015 at 8:50 AM, Ben Cipollini < >>>>>>>>>>>>>>>>>>>>>>> bcipolli at ucsd.edu> wrote: >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> This looks great. It's also cool to see "ask a >>>>>>>>>>>>>>>>>>>>>>>> question" integrated into the website, though we'll still have to hash >>>>>>>>>>>>>>>>>>>>>>>> things out for that. >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> Rather than open a github issue (which few may >>>>>>>>>>>>>>>>>>>>>>>> see), I'll make a suggestion here: can we have the menu expanded by default >>>>>>>>>>>>>>>>>>>>>>>> when accessing via a full-size screen? >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> It feels odd to me to have to expand the menu in >>>>>>>>>>>>>>>>>>>>>>>> order to navigate anywhere, by default. To me, navigation options should be >>>>>>>>>>>>>>>>>>>>>>>> obvious, unless pressed for space. >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> On Sun, Aug 30, 2015 at 1:14 PM, vanessa sochat < >>>>>>>>>>>>>>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> Hi Everyone, >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> I've finished work on the "contribute" page with >>>>>>>>>>>>>>>>>>>>>>>>> my thinking for how to contribute various content: >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> http://vsoch.github.io/nipy-jekyll/contribute.html >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> and as an example, put up a quick blog post: >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> http://neuroimaging.tumblr.com/ >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> The old "example" blog posts are hidden (private) >>>>>>>>>>>>>>>>>>>>>>>>> and can be viewed if you are a contributor. I'd like to add anyone and >>>>>>>>>>>>>>>>>>>>>>>>> everyone interested to contribute as "official" contributors via tumblr - >>>>>>>>>>>>>>>>>>>>>>>>> if you are interested please send me your email address. I've already >>>>>>>>>>>>>>>>>>>>>>>>> invited some of you for which I know the email. >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> Best, >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> Vanessa >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>>>>>>>>>>>>>> Stanford University >>>>>>>>>>>>>>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>>>>>>>>>>>> Stanford University >>>>>>>>>>>>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>>>>> Neuroimaging mailing list >>>>>>>>>>>>>>>>>>>>> Neuroimaging at python.org >>>>>>>>>>>>>>>>>>>>> https://mail.python.org/mailman/listinfo/neuroimaging >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>>>>>>>>> Stanford University >>>>>>>>>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>>>>>> Stanford University >>>>>>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>>>> Stanford University >>>>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> -- >>>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>>> Stanford University >>>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>>> >>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>> 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 >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>> Stanford University >>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>> Stanford University >>>>>>>>>>> (603) 321-0676 >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>> Stanford University >>>>>>>>>> (603) 321-0676 >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> 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 >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Neuroimaging mailing list >>>>>>>> Neuroimaging at python.org >>>>>>>> https://mail.python.org/mailman/listinfo/neuroimaging >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Vanessa Villamia Sochat >>>>>>> Stanford University >>>>>>> (603) 321-0676 >>>>>>> >>>>>>> _______________________________________________ >>>>>>> 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 >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Vanessa Villamia Sochat >>>>> Stanford University >>>>> (603) 321-0676 >>>>> >>>>> _______________________________________________ >>>>> 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 >>>> >>>> >>> >>> >>> -- >>> Vanessa Villamia Sochat >>> Stanford University >>> (603) 321-0676 >>> >> >> >> >> -- >> Vanessa Villamia Sochat >> Stanford University >> (603) 321-0676 >> > > > > -- > > -- Vanessa Villamia Sochat Stanford University (603) 321-0676 -------------- next part -------------- An HTML attachment was scrubbed... URL: From roman at incf.org Sat Oct 31 05:33:16 2015 From: roman at incf.org (=?UTF-8?Q?Roman_Valls_Guimer=C3=A0?=) Date: Sat, 31 Oct 2015 10:33:16 +0100 Subject: [Neuroimaging] Site Contributions In-Reply-To: References: Message-ID: Hi Vanessa, Chris, Satra, I quickly parsed your thread so I might be missing the important questions, chime in if so... Better email integration has been an wished feature for a quite a while now, hopefully in the 4th iteration of the biostars engine we'll get there: https://github.com/ialbert/biostar-central/tree/4.0 (@satra, Istvan is changing the database backend to MongoDB, perhaps a good opportunity to also experiment/switch to more semantic-friendly databases?) Also, Vanessa, I'm not sure what is the state of neurostars API since I've not been mantaining the site as it deserves, but you can use it, i.e: http://neurostars.org/api/traffic/ More info over here: https://neurostars.org/info/api/ Anyhow, unfortunately this year's GSoC student wasn't as prolific as Paolo Coffetti, but I hope we can push the site forward together in the future.... landing California on the 4th Nov, are you up for a combined hackathon on neurostars and/or CWL? Cheers! Roman On Tue, Oct 27, 2015 at 9:09 PM, vanessa sochat wrote: > Ok, the first one was a little messy because I enabled twitter integration > after the first post (and so I needed to reblog), but now the two are > connected, so you can keep track of posts via twitter: > > https://twitter.com/nipyorg > > Best, > > Vanessa > > On Tue, Oct 27, 2015 at 12:50 PM, vanessa sochat > wrote: > >> How about nipyorg for a twitter? Some hairy dude in a swimming pool has >> "nipy" >> >> On Tue, Oct 27, 2015 at 12:47 PM, Chris Filo Gorgolewski < >> krzysztof.gorgolewski at gmail.com> wrote: >> >>> neurostars is based on biostars and provide a variety of ways to >>> integrate sources. Satra and Roman will know more. >>> >>> Best, >>> Chris >>> >>> On Tue, Oct 27, 2015 at 12:38 PM, vanessa sochat >>> wrote: >>> >>>> Sure thing. There might be a trick to integrate the two, I'll look into >>>> it. I just added comments: >>>> >>>> >>>> http://neuroimaging.tumblr.com/post/132031797431/write-stdout-to-file-for-fsl-cluster >>>> >>>> and for now I will redirect people to neurostars. >>>> >>>> Here is how to post via email: >>>> >>>> https://www.tumblr.com/docs/en/posting#emailpostheader >>>> >>>> The email for us is: >>>> >>>> [image: Inline image 1] >>>> >>>> This is so great! Anyone can contribute absolutely anything, and they >>>> don't need to know what a PR is :) >>>> >>>> On Tue, Oct 27, 2015 at 12:31 PM, Ben Cipollini >>>> wrote: >>>> >>>>> Oh no, another place for discussion? :-/ >>>>> >>>>> Can we redirect them to the mailing list or neurostars? >>>>> >>>>> On Tue, Oct 27, 2015 at 12:19 PM, vanessa sochat >>>> > wrote: >>>>> >>>>>> Hey Ariel, >>>>>> >>>>>> Do we have a nipy discus? I would like to add comments to posts so we >>>>>> can talk about things like these: >>>>>> >>>>>> >>>>>> http://neuroimaging.tumblr.com/post/132031797431/write-stdout-to-file-for-fsl-cluster >>>>>> >>>>>> Best, >>>>>> >>>>>> Vanessa >>>>>> >>>>>> On Tue, Oct 27, 2015 at 11:44 AM, Ben Cipollini >>>>>> wrote: >>>>>> >>>>>>> Great! I'll resubmit my "issue" to the nipy repo and start >>>>>>> "watching" it :) >>>>>>> >>>>>>> On Tue, Oct 27, 2015 at 11:40 AM, Ariel Rokem >>>>>>> wrote: >>>>>>> >>>>>>>> Great work! Will resubmit my blog-post PR through the new >>>>>>>> mechanism. >>>>>>>> >>>>>>>> On Tue, Oct 27, 2015 at 11:38 AM, vanessa sochat < >>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>> >>>>>>>>> Hi everyone, >>>>>>>>> >>>>>>>>> I just added the missing CNAME file, apologies for the oversight, >>>>>>>>> I did not know it was there :) It looks like nipy.org is working >>>>>>>>> as well now too - please let me know if you see any issues. >>>>>>>>> >>>>>>>>> Circle is expected to have some changes in the next week, so I am >>>>>>>>> going to wait for the weekend to debug the building of artifacts. Will let >>>>>>>>> you know when I fix that up! >>>>>>>>> >>>>>>>>> Best, >>>>>>>>> >>>>>>>>> Vanessa >>>>>>>>> >>>>>>>>> On Tue, Oct 27, 2015 at 11:30 AM, vanessa sochat < >>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>> >>>>>>>>>> Hi Everyone, >>>>>>>>>> >>>>>>>>>> Site is live! >>>>>>>>>> >>>>>>>>>> https://nipy.github.io/ >>>>>>>>>> >>>>>>>>>> Ariel - I'm not sure how to set up the nipy.org. Would you mind >>>>>>>>>> taking a look and fixing that up? >>>>>>>>>> >>>>>>>>>> Circle is having some bugs with the artifact generation, I think >>>>>>>>>> I can probably fix it, but not during the work week. Ben - I added your >>>>>>>>>> contribution to the README but didn't get the other comment in time. The >>>>>>>>>> good news is now anyone and everyone can submit changes as PR. I encourage >>>>>>>>>> everyone to familiarize yourself with tumblr, and start contributing >>>>>>>>>> content, PRs to tweak it. >>>>>>>>>> >>>>>>>>>> Best, >>>>>>>>>> >>>>>>>>>> Vanessa >>>>>>>>>> >>>>>>>>>> On Tue, Oct 27, 2015 at 11:10 AM, vanessa sochat < >>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>> >>>>>>>>>>> Got it! Thanks! :) >>>>>>>>>>> >>>>>>>>>>> On Tue, Oct 27, 2015 at 11:07 AM, Ariel Rokem >>>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>>> Hi, >>>>>>>>>>>> On Tue, Oct 27, 2015 at 10:56 AM, vanessa sochat < >>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Hi Ariel, >>>>>>>>>>>>> >>>>>>>>>>>>> Please add me as an admin to nipy.github.io, so I can set up >>>>>>>>>>>>> circle for CI. Thanks! >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> I believe I just did that. Let me know how you get on. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>>> Best, >>>>>>>>>>>>> >>>>>>>>>>>>> Vanessa >>>>>>>>>>>>> >>>>>>>>>>>>> On Tue, Oct 27, 2015 at 10:42 AM, vanessa sochat < >>>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Just as a proof of concept for adding a project - I just >>>>>>>>>>>>>> added a new entry to the data file (copy pasting basically), copied one >>>>>>>>>>>>>> file, and the entire process took me like, 48 seconds :) >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Tue, Oct 27, 2015 at 10:36 AM, Ben Cipollini < >>>>>>>>>>>>>> bcipolli at ucsd.edu> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Thanks Vanessa! >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Tue, Oct 27, 2015 at 10:35 AM, vanessa sochat < >>>>>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> I will do some tweaks and get the site working. There will >>>>>>>>>>>>>>>> be a change for the URL so there might be some bugs with my initial >>>>>>>>>>>>>>>> release, but I'll get it fixed asap. Will send an update later. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Tue, Oct 27, 2015 at 6:48 AM, Ariel Rokem < >>>>>>>>>>>>>>>> arokem at gmail.com> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Oh, one more: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Tue, Oct 27, 2015 at 6:40 AM, Ariel Rokem < >>>>>>>>>>>>>>>>> arokem at gmail.com> wrote: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Hi Vanessa, >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> I have a few comments/suggestions: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> 1. I would rather not have the front page be the project >>>>>>>>>>>>>>>>>> directory. In my opinion, the front page should instead explain briefly >>>>>>>>>>>>>>>>>> what this is, and lead visitors to the various other parts of the website. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> 2. There are a few issues with formatting in the Code of >>>>>>>>>>>>>>>>>> Conduct page (bullet points appear as continued lines) >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> 3. Please include mindboggle in the project directory >>>>>>>>>>>>>>>>> (it's been recently added!). >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Other than these two, I think this is ready to be >>>>>>>>>>>>>>>>>> introduced as a PR against the nipy/nipy.github.com >>>>>>>>>>>>>>>>>> repository (you don't need any admin rights to do that, but I also just >>>>>>>>>>>>>>>>>> added you to "team blog" on the github nipy org, so you can even do the >>>>>>>>>>>>>>>>>> merge yourself, if you want). >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Cheers, >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Ariel >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> On Mon, Oct 26, 2015 at 12:56 PM, vanessa sochat < >>>>>>>>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Hi Eleftherios, >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> It definitely would be possible! I'm not any sort of >>>>>>>>>>>>>>>>>>> admin in the nipy space, so the farthest I could take it is having the repo >>>>>>>>>>>>>>>>>>> for someone to deploy on nipy.github.io. The code is >>>>>>>>>>>>>>>>>>> here: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> https://github.com/vsoch/nipy-jekyll >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> and deployment on my github pages: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> http://vsoch.github.io/nipy-jekyll/ >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> I mostly stopped working on it because I accomplished >>>>>>>>>>>>>>>>>>> all the things that I set out to do (jekyll site, preview on continuous >>>>>>>>>>>>>>>>>>> integration with circle, standard ways to add new content, and an easy way >>>>>>>>>>>>>>>>>>> to multiple ways to add content a la github >>>>>>>>>>>>>>>>>>> , >>>>>>>>>>>>>>>>>>> or for those who aren't comfortable with pushing and pulling, la >>>>>>>>>>>>>>>>>>> social media ). I think >>>>>>>>>>>>>>>>>>> I had suggested moving forward for people to try out tumblr (and start >>>>>>>>>>>>>>>>>>> contributing content!), and if people were happy, to move it over to the >>>>>>>>>>>>>>>>>>> nipy repo. If the outcome of the work was not a desired solution, I was >>>>>>>>>>>>>>>>>>> content to just let it be. However if there is interest, that is definitely >>>>>>>>>>>>>>>>>>> still a possibility. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Best, >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Vanessa >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> On Mon, Oct 26, 2015 at 12:34 PM, Eleftherios >>>>>>>>>>>>>>>>>>> Garyfallidis wrote: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Hi Vanessa and all, >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Would it be possible to switch to your much nicer new >>>>>>>>>>>>>>>>>>>> website? I still see the older version being up. >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Do you have a plan for this? Or you waiting for some >>>>>>>>>>>>>>>>>>>> feedback on our side? >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Best regards, >>>>>>>>>>>>>>>>>>>> Eleftherios >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> On Wed, Sep 2, 2015 at 12:57 PM, Ben Cipollini < >>>>>>>>>>>>>>>>>>>> bcipolli at ucsd.edu> wrote: >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> I think they're good for mobile sites. I think they're >>>>>>>>>>>>>>>>>>>>> generally expanded by default on full screens, and compacted on mobile. So >>>>>>>>>>>>>>>>>>>>> I suggest to keep it, but have a regular menu that's showing on full >>>>>>>>>>>>>>>>>>>>> screens and hidden on mobile. >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> On Wed, Sep 2, 2015 at 9:51 AM, vanessa sochat < >>>>>>>>>>>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> That's a good suggestion, and I'll add as an issue so >>>>>>>>>>>>>>>>>>>>>> I can find it easily when the next round of changes comes around. >>>>>>>>>>>>>>>>>>>>>> Generally, these "hamburger" menu things are useless functionality wise, >>>>>>>>>>>>>>>>>>>>>> and only serve to aesthetically "get rid of the navigation" to have a clean >>>>>>>>>>>>>>>>>>>>>> looking site. In our case, it is probably just annoying to have the extra >>>>>>>>>>>>>>>>>>>>>> clicks. >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> On Wed, Sep 2, 2015 at 8:50 AM, Ben Cipollini < >>>>>>>>>>>>>>>>>>>>>> bcipolli at ucsd.edu> wrote: >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> This looks great. It's also cool to see "ask a >>>>>>>>>>>>>>>>>>>>>>> question" integrated into the website, though we'll still have to hash >>>>>>>>>>>>>>>>>>>>>>> things out for that. >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> Rather than open a github issue (which few may see), >>>>>>>>>>>>>>>>>>>>>>> I'll make a suggestion here: can we have the menu expanded by default when >>>>>>>>>>>>>>>>>>>>>>> accessing via a full-size screen? >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> It feels odd to me to have to expand the menu in >>>>>>>>>>>>>>>>>>>>>>> order to navigate anywhere, by default. To me, navigation options should be >>>>>>>>>>>>>>>>>>>>>>> obvious, unless pressed for space. >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> On Sun, Aug 30, 2015 at 1:14 PM, vanessa sochat < >>>>>>>>>>>>>>>>>>>>>>> vsochat at stanford.edu> wrote: >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> Hi Everyone, >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> I've finished work on the "contribute" page with my >>>>>>>>>>>>>>>>>>>>>>>> thinking for how to contribute various content: >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> http://vsoch.github.io/nipy-jekyll/contribute.html >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> and as an example, put up a quick blog post: >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> http://neuroimaging.tumblr.com/ >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> The old "example" blog posts are hidden (private) >>>>>>>>>>>>>>>>>>>>>>>> and can be viewed if you are a contributor. I'd like to add anyone and >>>>>>>>>>>>>>>>>>>>>>>> everyone interested to contribute as "official" contributors via tumblr - >>>>>>>>>>>>>>>>>>>>>>>> if you are interested please send me your email address. I've already >>>>>>>>>>>>>>>>>>>>>>>> invited some of you for which I know the email. >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> Best, >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> Vanessa >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>>>>>>>>>>>>> Stanford University >>>>>>>>>>>>>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>>>>>>>>>>> Stanford University >>>>>>>>>>>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>>>> Neuroimaging mailing list >>>>>>>>>>>>>>>>>>>> Neuroimaging at python.org >>>>>>>>>>>>>>>>>>>> https://mail.python.org/mailman/listinfo/neuroimaging >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>>>>>>>> Stanford University >>>>>>>>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>>>>> Stanford University >>>>>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> -- >>>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>>> Stanford University >>>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>>>> Stanford University >>>>>>>>>>>>> (603) 321-0676 >>>>>>>>>>>>> >>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>> 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 >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>>> Stanford University >>>>>>>>>>> (603) 321-0676 >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Vanessa Villamia Sochat >>>>>>>>>> Stanford University >>>>>>>>>> (603) 321-0676 >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Vanessa Villamia Sochat >>>>>>>>> Stanford University >>>>>>>>> (603) 321-0676 >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> 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 >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Neuroimaging mailing list >>>>>>> Neuroimaging at python.org >>>>>>> https://mail.python.org/mailman/listinfo/neuroimaging >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Vanessa Villamia Sochat >>>>>> Stanford University >>>>>> (603) 321-0676 >>>>>> >>>>>> _______________________________________________ >>>>>> 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 >>>>> >>>>> >>>> >>>> >>>> -- >>>> Vanessa Villamia Sochat >>>> Stanford University >>>> (603) 321-0676 >>>> >>>> _______________________________________________ >>>> 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 >>> >>> >> >> >> -- >> Vanessa Villamia Sochat >> Stanford University >> (603) 321-0676 >> > > > > -- > Vanessa Villamia Sochat > Stanford University > (603) 321-0676 > -- -------------- next part -------------- An HTML attachment was scrubbed... URL: From vsochat at stanford.edu Sat Oct 31 17:53:51 2015 From: vsochat at stanford.edu (vanessa sochat) Date: Sat, 31 Oct 2015 14:53:51 -0700 Subject: [Neuroimaging] Circle Debugging Message-ID: Hi Everyone, I've fixed circle so that it builds the site, and renders the artifacts, I did this with changes to the circle.yml: https://github.com/nipy/nipy.github.com/blob/master/circle.yml and added a new script to generate the correct urls: https://github.com/nipy/nipy.github.com/blob/master/circle_urls.sh so the build works again: https://circleci.com/gh/nipy/nipy.github.com Unfortunately, circle seems to be doing some kind of redirect business with the static urls, so the pages render (but not the style). https://circle-artifacts.com/gh/nipy/nipy.github.com/50/artifacts/0/home/ubuntu/nipy.github.com/_site/index.html If someone else wants to take a look at this new bug that would be great, I've been working on this since 4am and want to use the remainder of the day to work on other things. Thanks! Best, Vanessa -- Vanessa Villamia Sochat Stanford University (603) 321-0676 -------------- next part -------------- An HTML attachment was scrubbed... URL: