[Neuroimaging] Site Discussion

Wed Aug 26 21:38:19 CEST 2015

Whoops:

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

> Hi Eleftherios,
>
> On Wed, Aug 26, 2015 at 11:52 AM, Eleftherios Garyfallidis <
> garyfallidis at gmail.com> wrote:
>
>> Hi Vanessa,
>>
>> I think we need to setup a hangout to discuss about this. Before we move
>> forward with more coding.
>> Figuring out the content will make designing the website much easier.
>>
>> By the way thank you for all the hard work. It's really inspiring.
>>
>> One important issue is what the portal will be about. And that is not
>> currently clear.
>>
>> If the purpose is only to provide links to the other websites then we can
>> just use the technology that
>> we already have using sphinx and/or bootstrap/css or pelican.
>>
>> If the purpose is to make something that is really dynamic and people can
>> add comments on the fly
>> I think we really need something like django.
>>
>> But anyway. Can all the interested parties meet and discuss these
>> following important issues:
>>
>> a) What the portal is about? We need to reach consensus. This is
>> currently vague.
>>
>
> See above: "...to create a community portal on that page, where a large
> number of projects in this space could be represented through a (semi-)
> rational organization. Something with a front page that tells the beginner
> that there are many paths through this particular garden, and guides them
> along to what they need"
>
>
>> b) Which projects are currently under the neuroimaging in python
>> umbrella? Projects that do not share the
>> same vision should not be promoted. I think. But maybe others think
>> differently. I would like to hear the
>> opinions on that.
>>
>>
> I think this vision should be inclusive. See more below for clarification.
>
>
>> c) How the website and e-mail lists/forums will benefit and promote the
>> work and the vision of this organization.
>>
>> d) Make some decisions on the technologies that we can use to support a,
>> b, c.
>>
>> Maybe points b and c are not clear. So here are some clarifications.
>>
>> (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.
>>
>
> Yes - I think that a "neuroimaging in python"  website should definitely
> include projects that are under that particular github organization. See
> also response to (a) above and "many paths".
>
>>
>>
Meant to say: "... website should definitely include projects that are
*not* under that particular github organization" (e.g. nilearn, etc.). I
carefully wrote a statement of principles, so that we can look at a project
and get a rough estimate whether it fits in or not (not based on whether it
is under some specific github org): http://nipy.org/code-of-conduct/

For example, if a project is not released under a permissive open-source
license ("open" and "collaborative"), it probably doesn't belong there.

> (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.
>>
>> My feeling is that we really need such a meeting and that the discussion
>> in the e-mail list was not that helpful.
>>
>
> -1 to a meeting on this. Those take too much time, don't typically lead to
> decision making by consensus, and don't leave any trace, so don't
> facilitate consistent follow up. I strongly feel that a public email forum
> like this is exactly the right place to discuss these things. How would you
> feel if you discovered that the website was changed in some way that you
> don't like in a meeting that you hadn't attended? Actually, we already know
> how you feel about that... ;D
>
> Cheers,
>
> Ariel
>
> I know you specifically were happy to hangout as I suggested in a previous
>> e-mail.
>>
>> I hope you can suggest a time and then resolve this and move on to a
>> better future.
>>
>> Best regards,
>> Eleftherios
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> 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
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/neuroimaging/attachments/20150826/bfac267b/attachment.html>