[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#728797: ITP: python-mne -- Python modules for MEG and EEG data analysis



On Wed, 06 Nov 2013, Andreas Tille wrote:
> > > In any case it has several advantages to at least maintain a clone in
> > > one of our repositories at git.debian.org because we have some tools
> > > browsing the repositories and doing some general analysis over the
> > > VCS status.  It would be good if we could do this also for mne-python
> > > but the NeuroDebian people might have the last word in case they agree
> > > that they take over the package.  In any case it would be really
> > > interesting to describe the workflow they are using in some kind of
> > > policy document.  

Hi guys -- nice to see a live discussion ;)

Indeed we do not have yet as clear policy/workflow as Debian Med does...

in majority of the cases I am trying to "integrate" packaging within the
(clone of) upstream repository, so to bring lives of both
"developments" into a single history.  Thus it is not an 'overlay'
repository as Debian Med usually does, but rather a 'debian' branch
which contains the packaging and merges from upstream's master or
release branches (if those are divergent from master, it becomes a bit
more dance).  I guess this should be the major difference from how
Debian Med does it, right Andreas?

> > > In case this sounds convincing we could take over
> > > this into Debian Med policy[1].

> > having python-mne in both would be great. Yaroslav has helped me
> > up to now to meet neurodebian's requirements. I'd appreciate any
> > help (pull request) to meet Debian Med policy.

> "Having in both" is the wrong expression.  Debian Med is pure Debian and
> thus we bring the package into official Debian and it is available for
> all users in medicine and neuroscience.  You might like to understand
> the idea of Debian Pure Blends[1].

I guess Alexandre meant "in both Debian and NeuroDebian", because we
would immediately provide backport builds for all supported Debian and
Ubuntu releases.

> The actual Debian Med policy describes some conventions and workflows we
> have agreed upon inside the packaging team.  I somehow have the feeling
> that it might create less work for you if you follow the advise of
> Yaroslav and he might sponsor the package. 

I am yet to do thorough review, so if you have a moment indeed it would
be helpful... e.g. overlooked adding debian/upstream file ;)  and
actually this upcoming release AFAIK is rushed to get mne-python
publication out (so it could be added to debian/upstream for
references), right Alexandre? ;-)

-- 
Yaroslav O. Halchenko, Ph.D.
http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org
Senior Research Associate,     Psychological and Brain Sciences Dept.
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834                       Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik        


Reply to: