Dear All,
Thanks for your inputs. I still have to go through the whole thread but
I will start with some comments about GitHub and documentation.
A copy of all SPM releases is now available on GitHub:
https://github.com/spm/
It does not contain the full history yet; that's something I would like
to do, preferably including as well the history from the version control
system (SCCS) that was used before Subversion but last time I looked at
it, I still had conversion issues (otherwise it seems we could go back
to March 1994).
That said, I agree, this is just a mirror of our code repository and
development does not take place on GitHub; this is something we would
have to discuss internally first. We welcome, and receive, bug reports,
feature requests and code/documentation contributions. I agree that
GitHub's pull request, issue and code review mechanisms would make this
easier and more transparent.
As a side note, the maintenance of the previous versions of SPM (SPM99,
SPM2, SPM5, SPM8) is taking place on GitHub, with many contributions
from Dimitri Papadopoulos Orfanos over the years (previously on
SourceForge).
Concerning the documentation, there is a wiki on Wikibooks since 2005:
https://en.wikibooks.org/wiki/SPM
where anyone can make changes. A great recent example is the section on
slice timing that started like this:
https://en.wikibooks.org/w/index.php?title=SPM/Slice_Timing&oldid=2680405
and was completely overwritten and massively expanded by Stephen
Larroque at the end of last year to look like this:
https://en.wikibooks.org/wiki/SPM/Slice_Timing
If everyone from this list follows Stephen's example and write an entry
on their favourite topic, we would have an amazing exhaustive documentation.
Peter also explored using GitBook (https://www.gitbook.com/):
https://github.com/spm/spm-docs
starting with documentation about DCM. It's still work in progress but
it might be an interesting direction to create a pretty,
community-driven documentation.
Best regards,
Guillaume.
On 12/04/18 02:24, Stephanie Kern wrote:
> As a newbie to SPM, I love learning about what SPM can offer and having
> the code accessible would be a huge help. I agree that it would be
> helpful to see it maintained on Github. While I can see the transfer to
> Github as being difficult, with people responding with enthusiasm to
> this idea, I don't think it would be impossible.
>
>
>
> On Wed, Apr 11, 2018 at 7:11 PM, David Newberry <[log in to unmask]
> <mailto:[log in to unmask]>> wrote:
>
> SPM would prosper from being open to community involvement in
> development. It would be great to see it maintained on github. In
> terms of both code, and -- just as importantly -- documentation,
> allowing the community to contribute would be a great asset.
>
> -David Newberry
>
>
--
Guillaume Flandin, PhD
Wellcome Trust Centre for Neuroimaging
University College London
12 Queen Square
London WC1N 3BG
|