[Neuroimaging] Site Discussion

Thu Aug 27 00:40:35 CEST 2015

On Wed, Aug 26, 2015 at 3:29 PM, Ariel Rokem <arokem at gmail.com> wrote:

>
>
> On Wed, Aug 26, 2015 at 3:25 PM, Eleftherios Garyfallidis <
> garyfallidis at gmail.com> wrote:
>
>> So another push for Jekyll?
>>
>>
> Yep. And if that turns out to be unsuccessful - sphinx.
>
> Big Bada-boum!
>

Sorry - unless you have any other suggestions on how to go about this
(apart from a hangout to discuss this)?

>
>
>>
>> On Wed, Aug 26, 2015 at 6:05 PM, Ariel Rokem <arokem at gmail.com> wrote:
>>
>>> Hey Eleftherios,
>>>
>>> On Wed, Aug 26, 2015 at 1:08 PM, Eleftherios Garyfallidis <
>>> garyfallidis at gmail.com> wrote:
>>>
>>>> Hi Vanessa,
>>>>
>>>> On Wed, Aug 26, 2015 at 3:20 PM, vanessa sochat <vsochat at stanford.edu>
>>>> wrote:
>>>>
>>>>> 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.
>>>>>
>>>>>
>>>> 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?
>>>>
>>>
>>> I think that question has been answered here:
>>> https://mail.python.org/pipermail/neuroimaging/2015-August/000380.html
>>>
>>>
>>>> Best,
>>>> Eleftherios
>>>>
>>>>
>>>>
>>>>> On Wed, Aug 26, 2015 at 12:09 PM, vanessa sochat <vsochat at stanford.edu
>>>>> > wrote:
>>>>>
>>>>>> Hi Eleftherios,
>>>>>>
>>>>>> 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:
>>>>>>
>>>>>> a) What the portal is about? We need to reach consensus. This is
>>>>>>> currently vague.
>>>>>>>
>>>>>>> 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.
>>>>>>
>>>>>>
>>>>>>> c) How the website and e-mail lists/forums will benefit and promote
>>>>>>> the work and the vision of this organization.
>>>>>>>
>>>>>>> For the work - the website blog will afford all the things that
>>>>>> blogs afford: sharing ideas, examples, links, social media integration, etc.
>>>>>>
>>>>>>
>>>>>>> d) Make some decisions on the technologies that we can use to
>>>>>>> support a, b, c.
>>>>>>>
>>>>>>> Again, this is more about hosting and responsibility.
>>>>>>
>>>>>>
>>>>>>> (b) is critical because for example I saw that you added in the
>>>>>>> website projects which are not currently under our
>>>>>>> github organization https://github.com/nipy. I think we need
>>>>>>> consensus to take such a decisions.
>>>>>>>
>>>>>>> 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 *after* getting
>>>>>> the site functioning.
>>>>>>
>>>>>>
>>>>>>> (c) is also much related to Matthew's e-mail for supporting or not
>>>>>>> Neurostars for answering questions about the NIPY
>>>>>>> projects. This information and whatever we decide must be
>>>>>>> highlighted clearly in the portal.
>>>>>>>
>>>>>>> Lorem,.. ipsum...
>>>>>>
>>>>>> :)
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Aug 26, 2015 at 1:54 PM, vanessa sochat <
>>>>>>> vsochat at stanford.edu> wrote:
>>>>>>>
>>>>>>>> exactly :)
>>>>>>>>
>>>>>>>> https://www.youtube.com/watch?v=Uwzg7SYZKF0
>>>>>>>>
>>>>>>>> On Wed, Aug 26, 2015 at 10:46 AM, Ariel Rokem <arokem at gmail.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Sorry - didn't see that one for some reason.
>>>>>>>>>
>>>>>>>>> On Wed, Aug 26, 2015 at 9:23 AM, Vanessa Villamia Sochat <
>>>>>>>>> vsochat at stanford.edu> wrote:
>>>>>>>>>
>>>>>>>>>> Hi everyone!
>>>>>>>>>>
>>>>>>>>>> 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!
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> +1
>>>>>>>>>
>>>>>>>>> Bada-boum!
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> I will send out an update likely during weekend time when I've
>>>>>>>>>> tested some things.
>>>>>>>>>>
>>>>>>>>>> Best,
>>>>>>>>>>
>>>>>>>>>> Vanessa
>>>>>>>>>>
>>>>>>>>>> > On Aug 26, 2015, at 8:32 AM, Matthew Brett <
>>>>>>>>>> matthew.brett at gmail.com> wrote:
>>>>>>>>>> >
>>>>>>>>>> > Hi,
>>>>>>>>>> >
>>>>>>>>>> >> On Wed, Aug 26, 2015 at 4:10 PM, vanessa sochat <
>>>>>>>>>> vsochat at stanford.edu> wrote:
>>>>>>>>>> >> Hi Group,
>>>>>>>>>> >>
>>>>>>>>>> >> Ben and I are having some discussion on the higher level goals
>>>>>>>>>> of the site,
>>>>>>>>>> >> and want to bring everyone in. In summary, we want something
>>>>>>>>>> that is easy to
>>>>>>>>>> >> contribute content to, and has continuous integration for
>>>>>>>>>> previewing
>>>>>>>>>> >> updates. I am wondering, what was wrong with the initial look
>>>>>>>>>> of the site?
>>>>>>>>>> >> Was it that sphinx is hard to update?
>>>>>>>>>> >
>>>>>>>>>> > Actually, I think that sphinx is a very good option, and most
>>>>>>>>>> other
>>>>>>>>>> > scientific Python sites use sphinx for their main pages.
>>>>>>>>>> >
>>>>>>>>>> > The particular template that we were using was a little dated
>>>>>>>>>> and
>>>>>>>>>> > ugly, but I bet that could be improved.
>>>>>>>>>> >
>>>>>>>>>> > Most if not all developers are perfectly capable of building the
>>>>>>>>>> > sphinx documentation locally to preview it, but we can also do
>>>>>>>>>> what
>>>>>>>>>> > other projects are doing, and build / publish the docs in some
>>>>>>>>>> > temporary place for each commit, using an entry in the travis-ci
>>>>>>>>>> > matrix of jobs.
>>>>>>>>>> >
>>>>>>>>>> > I think Ariel was particularly attracted to Jekyll / github
>>>>>>>>>> pages,
>>>>>>>>>> > because it is very easy to get a rendered version to look at
>>>>>>>>>> with a
>>>>>>>>>> > git push, and although that is generally desirable, I think
>>>>>>>>>> building /
>>>>>>>>>> > reviewing locally is at least as important.
>>>>>>>>>> >
>>>>>>>>>> > So - if it were entirely up to me - I would prefer we go back to
>>>>>>>>>> > sphinx, on the basis that it is a very familiar workflow to most
>>>>>>>>>> > Python developers.
>>>>>>>>>> >
>>>>>>>>>> > Thanks very much for doing all this work by the way - it's very
>>>>>>>>>> > helpful, and I'm sorry that we are going round and round.
>>>>>>>>>> >
>>>>>>>>>> > See you,
>>>>>>>>>> >
>>>>>>>>>> > 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
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> 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
>>>>
>>>>
>>>
>>> _______________________________________________
>>> Neuroimaging mailing list
>>> Neuroimaging at python.org
>>> https://mail.python.org/mailman/listinfo/neuroimaging
>>>
>>>
>>
>> _______________________________________________
>> Neuroimaging mailing list
>> Neuroimaging at python.org
>> https://mail.python.org/mailman/listinfo/neuroimaging
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/neuroimaging/attachments/20150826/b2788616/attachment.html>