<div dir="ltr">Hi Vanessa, <div class="gmail_extra"><br><div class="gmail_quote">On Thu, Aug 27, 2015 at 10:04 AM, vanessa sochat <span dir="ltr"><<a href="mailto:vsochat@stanford.edu" target="_blank">vsochat@stanford.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">1. Blog posts would be posted via tumblr. There is a PR mechanism - posts are submitted on our <a href="http://neuroimaging.tumblr.com/submit" target="_blank">submit page</a>, and there is some mechanism for reviewing submissions, or giving specific users free access to post what they like.<div><br></div><div><img src="cid:ii_idugcs4v0_14f7016b2c585e35" width="353" height="343" style="margin-right:0px"><br><br></div><div><br></div><div> We can also block if needed. <div><br></div></div></div></blockquote><div><br></div><div>OK - seems good. </div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><div></div><div><b>Pages vs. Posts</b><br></div><div>Jekyll will render almost anything (.md, .html, etc) not in a standard directory as a page, and so posts and pages are not much different in regard to format. The distinction is that to get pagination to work (i.e., the "blogroll") a custom configuration is needed for a <a href="http://jekyllrb.com/docs/posts/" target="_blank">special posts folder</a>, and the files are expected to be named with a date format. This is where we ran into trouble in satisfying the need for CI, ghpages, and local development to work. If you remember this original post:<div><br></div><div><a href="https://mail.python.org/pipermail/neuroimaging/2015-August/000307.html" target="_blank">https://mail.python.org/pipermail/neuroimaging/2015-August/000307.html</a><br></div><div><br></div></div></div></div></blockquote><div><br></div><div><div>THANK YOU for explaining that again, slowly :-) </div></div><div><br></div><div>Makes sense. I am 100% on board with moving blogging activities to an external platform - tumblr seems fine. </div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><div><div></div><div>much discussion came after that, and both Ben and I <a href="https://circleci.com/gh/vsoch/nipy-jekyll/tree/ben" target="_blank">spent days</a> trying to get something (even hacky) to work. To answer your question, the first move to an external platform was because the function just wouldn't work with Jekyll. However, after thinking about it, in making a choice that submitting a PR to a github repo is required to contribute, we are making a very strong statement about who we want to contribute. I'm not sure that we want to do that. If you want to take jekyll posts for a spin and see if you can get it working, I think it would be useful if we wanted some kind of "developer-only" posts. My general sense is that one of the goals of the site is to make it easier for contribution from the larger community, and so <i>only</i> having developer-friendly posts seems unwise. </div></div></div></div></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><div><div></div><div><b>Post content discussion is needed</b></div><div>It would be good to have discussion about what kind of posts we would want shared on nipy - for example I build little fun tools and think (and write) about methods all the time and post on my blog. I would guess other researchers might write things up from conferences, or even little tutorials. Some of that content could be really great to add to the nipy site for others to find.</div></div></div></div></blockquote><div><br></div><div>I think that I would probably write here every once in a while. The example of embedding nbviewer is compelling to me. I might post a notebook with some small observation about neuroimaging in python, as I run into these. I haven't been particularly consistent as a blogger in the past, though, so that's a tentative promise. </div><div><br></div><div>A post that I would definitely write up almost immediately: GSoC is coming to an end, and I would like to write a summary blog-post from the point of view of mentoring one of the dipy projects. Saying something about the joys and trials of the experience, and talk about things we need to think about next time we do this. </div><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><div><div></div><div>2. Yes, there is commenting - two flavors. People can <a href="http://neuroimaging.tumblr.com/ask" target="_blank">ask general questions</a>, I just enabled that to show you. We can also enable <a href="http://classroom.synonym.com/can-comment-tumblr-15664.html" target="_blank">comments for posts via disqus</a>.</div></div></div></div></blockquote><div><br></div><div>That's good If I didn't know better I'd suggest we direct people from neurostars to the "ask me anything" box ;-D </div><div><br></div><div>=> maybe we should disable that one.</div><div><br></div><div>I think that we really just want the option for people to comment on the specific contents of a particular post. </div><div><br></div><div>Thanks again for all your efforts in thinking/doing on this! </div><div><br></div><div>Ariel </div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><div><div></div></div></div></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Aug 27, 2015 at 9:06 AM, Ariel Rokem <span dir="ltr"><<a href="mailto:arokem@gmail.com" target="_blank">arokem@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">Hi Vanessa, <div class="gmail_extra"><br><div class="gmail_quote"><span>On Wed, Aug 26, 2015 at 4:13 PM, vanessa sochat <span dir="ltr"><<a href="mailto:vsochat@stanford.edu" target="_blank">vsochat@stanford.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div>This should be fairly easy to maintain. The main "package" pages are jekyll, meaning anyone can push a PR to the repo, preview on circle, and then deploy to github pages with approved changes. Developers know how to use github.</div><div><br></div>The hidden blog is hosted at tumblr, which means that:</div></blockquote><div><br></div></span><div>Slick! I noticed the little tumblr features appearing ("folllow neuroimaging"), and thought that was some magic you put in without even noticing that I was redirected to the tumblr URL. I don't mind it.</div><div><br></div><div>Two questions regarding that: </div><div><br></div><div>1. Blog posts would just be posted to this, right? No PR/review mechanism here? Is the main motivation to reduce the barrier to entry, or is this still about the CI jekyll baseurl business? Otherwise, we could still have the blog be part of the main site. As I understand it (and I might easily be wrong) Jekyll doesn't really make a distinction between "regular" pages and "blog posts" when generating the site from markdown files.</div><div><br></div><div>2. Commenting? Could that easily be enabled on tumblr? </div><div><div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div></div><div>- anyone can contribute content. We can let it get pushed or put it in a queue for approval.</div><div>- posts can be done on mobile, or from email. In html, markdown, or standard text editor.</div><div>- we can choose to "hide" the <a href="http://neuroimaging.tumblr.com" target="_blank">neuroimaging.tumblr.com</a> url if we want, but it's really not so bad.</div><div>- looks spiffy on mobile too :)</div><div>- posts can be associated with authors, but don't need to be.</div><div>- people can ask questions on posts, share posts, like them, etc.</div><div>- integrated notifications, social media, apps, all the standard stuff you get with a platform like this. Tumblr has an API :)</div><div><br></div><div>We kill lots of birds with a snakey thought stone. The site has CI, hosted for free on ghpages, and is an easy workflow for developers to update or add their packages. The site is also better integrated into the non-developer community, because anyone can contribute content easily without github, and we still have control over that content.</div><div><br></div><div>If there is a huge redesign of the site, then the template would need to be updated on tumblr, but that really comes down to copy pasting the base code into the template editor. This was the idea that I had this morning.</div><div><br></div></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Aug 26, 2015 at 3:44 PM, vanessa sochat <span dir="ltr"><<a href="mailto:vsochat@stanford.edu" target="_blank">vsochat@stanford.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><b>Continuous integration:</b><div><a href="https://circle-artifacts.com/gh/vsoch/nipy-jekyll/68/artifacts/0/home/ubuntu/nipy-jekyll/_site/index.html" target="_blank">https://circle-artifacts.com/gh/vsoch/nipy-jekyll/68/artifacts/0/home/ubuntu/nipy-jekyll/_site/index.html</a><br></div><div><br></div><div><b>Gihub pages:</b></div><div><a href="http://vsoch.github.io/nipy-jekyll/" target="_blank">http://vsoch.github.io/nipy-jekyll/</a><br></div><div><b><br></b></div><div>All things seem to be in working order :)</div><div><br></div><div><br></div></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Aug 26, 2015 at 3:25 PM, Eleftherios Garyfallidis <span dir="ltr"><<a href="mailto:garyfallidis@gmail.com" target="_blank">garyfallidis@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div>So another push for Jekyll? </div><div><br></div></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Aug 26, 2015 at 6:05 PM, Ariel Rokem <span dir="ltr"><<a href="mailto:arokem@gmail.com" target="_blank">arokem@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">Hey Eleftherios, <div class="gmail_extra"><br><div class="gmail_quote"><span>On Wed, Aug 26, 2015 at 1:08 PM, Eleftherios Garyfallidis <span dir="ltr"><<a href="mailto:garyfallidis@gmail.com" target="_blank">garyfallidis@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div>Hi Vanessa,</div><div><br></div><div class="gmail_extra"><div class="gmail_quote"><span>On Wed, Aug 26, 2015 at 3:20 PM, vanessa sochat <span dir="ltr"><<a href="mailto:vsochat@stanford.edu" target="_blank">vsochat@stanford.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">Eleftherios, it's good that you express concern because that means that you care about nipy, and we can work together to ensure that the vision is properly reflected in this site. It's typically not a straight path to converge on the right solution, and I think that it's ok we are needing to try different things. If it isn't too troubling to you, please let me implement what I have in mind, and then we can move forward with discussion on the points of content.</div><div><div><div class="gmail_extra"><br></div></div></div></blockquote><div> </div></span><div>Sure, be happy to prepare whatever you think will help the discussion. Can I ask you to summarize quickly here the next steps of development that you have in mind?</div></div></div></div></blockquote><div><br></div></span><div>I think that question has been answered here: <a href="https://mail.python.org/pipermail/neuroimaging/2015-August/000380.html" target="_blank">https://mail.python.org/pipermail/neuroimaging/2015-August/000380.html</a></div><div><div><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div></div><div>Best,</div><div>Eleftherios</div><div><div><div><br></div><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div><div><div class="gmail_extra"><div class="gmail_quote">On Wed, Aug 26, 2015 at 12:09 PM, vanessa sochat <span dir="ltr"><<a href="mailto:vsochat@stanford.edu" target="_blank">vsochat@stanford.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">Hi Eleftherios,<div><br></div><div>A framework like Django is too heavy for a simple portal and blog, and we want to stay away from making something substantial that requires regular maintenance and care, and an actual server. We can achieve all the functionality of comments / social media, etc by integrating a blogging platform into a site that works on Github pages. Question b (sites included) and c (organization vision) needs discussion from everyone, and for the rest, here are my thoughts: </div><div class="gmail_extra"><br><div class="gmail_quote"><span><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div>a) What the portal is about? We need to reach consensus. This is currently vague.<br></div><div><br></div></div></blockquote></span><div>A simple portal that gives nipy a brand, links to its products, and integrates some platform for us to easily write about it. If something more substantial than that is desired, then we first need to resolve where it will be hosted and who takes responsibility for its life.</div><span><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div></div><div>c) How the website and e-mail lists/forums will benefit and promote the work and the vision of this organization.</div><div><br></div></div></blockquote></span><div>For the work - the website blog will afford all the things that blogs afford: sharing ideas, examples, links, social media integration, etc.</div><span><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div></div><div>d) Make some decisions on the technologies that we can use to support a, b, c.</div><div><br></div></div></blockquote></span><div>Again, this is more about hosting and responsibility.</div><span><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div>(b) is critical because for example I saw that you added in the website projects which are not currently under our </div><div>github organization <a href="https://github.com/nipy" target="_blank">https://github.com/nipy</a>. I think we need consensus to take such a decisions.</div><div><br></div></div></blockquote></span><div>You should consider all current content on the site as Lorem Ipsum etc. I simply reproduced what is on the current site and did not make any "decisions." As I said earlier, content and template come <i>after</i> getting the site functioning.</div><span><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div></div><div>(c) is also much related to Matthew's e-mail for supporting or not Neurostars for answering questions about the NIPY </div><div>projects. This information and whatever we decide must be highlighted clearly in the portal.</div><div><br></div></div></blockquote></span><div>Lorem,.. ipsum... </div><div><br></div><div>:)</div><div><div><div><br></div><div><br></div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><br></div><div><br></div></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Aug 26, 2015 at 1:54 PM, vanessa sochat <span dir="ltr"><<a href="mailto:vsochat@stanford.edu" target="_blank">vsochat@stanford.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">exactly :)<div><br></div><div><a href="https://www.youtube.com/watch?v=Uwzg7SYZKF0" target="_blank">https://www.youtube.com/watch?v=Uwzg7SYZKF0</a><br></div></div><div class="gmail_extra"><div><div><br><div class="gmail_quote">On Wed, Aug 26, 2015 at 10:46 AM, Ariel Rokem <span dir="ltr"><<a href="mailto:arokem@gmail.com" target="_blank">arokem@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">Sorry - didn't see that one for some reason.<br><div class="gmail_extra"><br><div class="gmail_quote"><span>On Wed, Aug 26, 2015 at 9:23 AM, Vanessa Villamia Sochat <span dir="ltr"><<a href="mailto:vsochat@stanford.edu" target="_blank">vsochat@stanford.edu</a>></span> wrote:<br></span><span><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Hi everyone!<br>
<br>
I thought more about this on my walk - here is a reasonable game plan! I will do the work to put together a solution that integrates Ariel's original vision with ghpages, the parts of Jekyll that do work, and a more non developer friendly integrated blog. I think this could meet all of our goals and be a solution that better integrates social aspects of our community - github just doesn't specialize in blogging but many services do. If that does not work, then we can go to Sphinx. Boum!<br></blockquote><div><br></div></span><div>+1 </div><div><br></div><div>Bada-boum! </div><div><div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
I will send out an update likely during weekend time when I've tested some things.<br>
<br>
Best,<br>
<br>
Vanessa<br>
<div><div><br>
> On Aug 26, 2015, at 8:32 AM, Matthew Brett <<a href="mailto:matthew.brett@gmail.com" target="_blank">matthew.brett@gmail.com</a>> wrote:<br>
><br>
> Hi,<br>
><br>
>> On Wed, Aug 26, 2015 at 4:10 PM, vanessa sochat <<a href="mailto:vsochat@stanford.edu" target="_blank">vsochat@stanford.edu</a>> wrote:<br>
>> Hi Group,<br>
>><br>
>> Ben and I are having some discussion on the higher level goals of the site,<br>
>> and want to bring everyone in. In summary, we want something that is easy to<br>
>> contribute content to, and has continuous integration for previewing<br>
>> updates. I am wondering, what was wrong with the initial look of the site?<br>
>> Was it that sphinx is hard to update?<br>
><br>
> Actually, I think that sphinx is a very good option, and most other<br>
> scientific Python sites use sphinx for their main pages.<br>
><br>
> The particular template that we were using was a little dated and<br>
> ugly, but I bet that could be improved.<br>
><br>
> Most if not all developers are perfectly capable of building the<br>
> sphinx documentation locally to preview it, but we can also do what<br>
> other projects are doing, and build / publish the docs in some<br>
> temporary place for each commit, using an entry in the travis-ci<br>
> matrix of jobs.<br>
><br>
> I think Ariel was particularly attracted to Jekyll / github pages,<br>
> because it is very easy to get a rendered version to look at with a<br>
> git push, and although that is generally desirable, I think building /<br>
> reviewing locally is at least as important.<br>
><br>
> So - if it were entirely up to me - I would prefer we go back to<br>
> sphinx, on the basis that it is a very familiar workflow to most<br>
> Python developers.<br>
><br>
> Thanks very much for doing all this work by the way - it's very<br>
> helpful, and I'm sorry that we are going round and round.<br>
><br>
> See you,<br>
><br>
> Matthew<br>
> _______________________________________________<br>
> Neuroimaging mailing list<br>
> <a href="mailto:Neuroimaging@python.org" target="_blank">Neuroimaging@python.org</a><br>
> <a href="https://mail.python.org/mailman/listinfo/neuroimaging" rel="noreferrer" target="_blank">https://mail.python.org/mailman/listinfo/neuroimaging</a><br>
<br>
_______________________________________________<br>
Neuroimaging mailing list<br>
<a href="mailto:Neuroimaging@python.org" target="_blank">Neuroimaging@python.org</a><br>
<a href="https://mail.python.org/mailman/listinfo/neuroimaging" rel="noreferrer" target="_blank">https://mail.python.org/mailman/listinfo/neuroimaging</a><br>
</div></div></blockquote></div></div></div><br></div></div>
<br>_______________________________________________<br>
Neuroimaging mailing list<br>
<a href="mailto:Neuroimaging@python.org" target="_blank">Neuroimaging@python.org</a><br>
<a href="https://mail.python.org/mailman/listinfo/neuroimaging" rel="noreferrer" target="_blank">https://mail.python.org/mailman/listinfo/neuroimaging</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div></div></div><span>-- <br><div>Vanessa Villamia Sochat<br>Stanford University<br><div><div><div><a href="tel:%28603%29%20321-0676" value="+16033210676" target="_blank">(603) 321-0676</a></div></div></div></div>
</span></div>
<br>_______________________________________________<br>
Neuroimaging mailing list<br>
<a href="mailto:Neuroimaging@python.org" target="_blank">Neuroimaging@python.org</a><br>
<a href="https://mail.python.org/mailman/listinfo/neuroimaging" rel="noreferrer" target="_blank">https://mail.python.org/mailman/listinfo/neuroimaging</a><br>
<br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
Neuroimaging mailing list<br>
<a href="mailto:Neuroimaging@python.org" target="_blank">Neuroimaging@python.org</a><br>
<a href="https://mail.python.org/mailman/listinfo/neuroimaging" rel="noreferrer" target="_blank">https://mail.python.org/mailman/listinfo/neuroimaging</a><br>
<br></blockquote></div></div></div><div><div><br><br clear="all"><div><br></div>-- <br><div>Vanessa Villamia Sochat<br>Stanford University<br><div><div><div><a href="tel:%28603%29%20321-0676" value="+16033210676" target="_blank">(603) 321-0676</a></div></div></div></div>
</div></div></div></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div>Vanessa Villamia Sochat<br>Stanford University<br><div><div><div><a href="tel:%28603%29%20321-0676" value="+16033210676" target="_blank">(603) 321-0676</a></div></div></div></div>
</div>
</div></div><br>_______________________________________________<br>
Neuroimaging mailing list<br>
<a href="mailto:Neuroimaging@python.org" target="_blank">Neuroimaging@python.org</a><br>
<a href="https://mail.python.org/mailman/listinfo/neuroimaging" rel="noreferrer" target="_blank">https://mail.python.org/mailman/listinfo/neuroimaging</a><br>
<br></blockquote></div></div></div><br></div></div>
<br>_______________________________________________<br>
Neuroimaging mailing list<br>
<a href="mailto:Neuroimaging@python.org" target="_blank">Neuroimaging@python.org</a><br>
<a href="https://mail.python.org/mailman/listinfo/neuroimaging" rel="noreferrer" target="_blank">https://mail.python.org/mailman/listinfo/neuroimaging</a><br>
<br></blockquote></div></div></div><br></div></div>
<br>_______________________________________________<br>
Neuroimaging mailing list<br>
<a href="mailto:Neuroimaging@python.org" target="_blank">Neuroimaging@python.org</a><br>
<a href="https://mail.python.org/mailman/listinfo/neuroimaging" rel="noreferrer" target="_blank">https://mail.python.org/mailman/listinfo/neuroimaging</a><br>
<br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
Neuroimaging mailing list<br>
<a href="mailto:Neuroimaging@python.org" target="_blank">Neuroimaging@python.org</a><br>
<a href="https://mail.python.org/mailman/listinfo/neuroimaging" rel="noreferrer" target="_blank">https://mail.python.org/mailman/listinfo/neuroimaging</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div>Vanessa Villamia Sochat<br>Stanford University<br><div><div><div><a href="tel:%28603%29%20321-0676" value="+16033210676" target="_blank">(603) 321-0676</a></div></div></div></div>
</div>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div>Vanessa Villamia Sochat<br>Stanford University<br><div><div><div><a href="tel:%28603%29%20321-0676" value="+16033210676" target="_blank">(603) 321-0676</a></div></div></div></div>
</div>
</div></div><br>_______________________________________________<br>
Neuroimaging mailing list<br>
<a href="mailto:Neuroimaging@python.org" target="_blank">Neuroimaging@python.org</a><br>
<a href="https://mail.python.org/mailman/listinfo/neuroimaging" rel="noreferrer" target="_blank">https://mail.python.org/mailman/listinfo/neuroimaging</a><br>
<br></blockquote></div></div></div><br></div></div>
<br>_______________________________________________<br>
Neuroimaging mailing list<br>
<a href="mailto:Neuroimaging@python.org" target="_blank">Neuroimaging@python.org</a><br>
<a href="https://mail.python.org/mailman/listinfo/neuroimaging" rel="noreferrer" target="_blank">https://mail.python.org/mailman/listinfo/neuroimaging</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div>Vanessa Villamia Sochat<br>Stanford University<br><div><div><div><a href="tel:%28603%29%20321-0676" value="+16033210676" target="_blank">(603) 321-0676</a></div></div></div></div>
</div>
</div></div><br>_______________________________________________<br>
Neuroimaging mailing list<br>
<a href="mailto:Neuroimaging@python.org" target="_blank">Neuroimaging@python.org</a><br>
<a href="https://mail.python.org/mailman/listinfo/neuroimaging" rel="noreferrer" target="_blank">https://mail.python.org/mailman/listinfo/neuroimaging</a><br>
<br></blockquote></div><br></div></div>