Following FOSDEM, today I presented NeuroFedora on eLife Innovation Leaders.
The topic for the discussion was "road mapping for an open project",
and I presented NeuroFedora the roadmap for our sig as well. The main
points to highlight from the discussion was how the sig formed, the
real problem that we intend to solve, how would we solve that, and our
plans for the future.
There were some interesting questions in the discussion as well, but
the most interesting was, how do we actually test the tools before
packaging them. Apart from the basic unit tests (that upstream
provides), do we do any other tests to ensure it's correctness?
Since, we have a lack of neuroscientists in the sig, who actually use
the packaged tools, I believe that we should test the tools packaged
by us, as a QA to actually verify that they work in Fedora.
As an example, if we package a DICOM image viewer, then we should make
sure that we are able to view images in it, other than the actual math
behind it that is verified by the unit tests. This may turn out to be
quite difficult for some complicated tools, but it would help us
gradually shift from packaging to testing as well.
Other than that, below are the notes made by Emmy during the talk for
everyone's reference. The slides for the talk are present here .
How we roadmap Neurofedora and implemented our ideology!
Vision: make it easier for people to use neuroscience software
At the beginning:
> Why do people need NeuroFedora?
> Neuroscience is very multi-disciplinary
> Only a few are trained software developers; most neuroscientists struggle with
Neurofedora is a volunteer-driven group
> They ensure quality of software – that the research produced (at least parts that
are handled by the software) is reproducible
> Good documentation is key!
> Challenging to recruit workforce, time is precious for existing users and
> Challenges to conduct proper review
How they built a roadmap: setting up project milestones
> Build core community - people that share similar visions
> Ensure the problem actually exist
> Provide the tools!
> Marketing and reaching out to the community - if people don’t know about you, then
people cannot try and it and use it?
> Future prospects: what else can we do for the community? We value the quality of our
work, and we’d like to work with the community to safeguard that
Current core team: 10 members, 4 neuroscientists
() ascii ribbon campaign - against html e-mail
- against proprietary attachments