Well, if you are reading our mailing list, provide information what
should be packaged or how we could enhancing packaging thit would be
really cool. Moreover becoming a member of the Alioth team and commit
packaging code. Serving as proxy in case of things we would like to
ask upstream at Sanger and so on.
> The Sanger Institute is composed of several independent faculties I fallSure - you probably can not deal with all Sanger faculties.
> under one of these.
> But it would be very interesting for someone to have more of a central roleThere used to be official Debian developers at Sanger but they did not
> in packaging Sangers mature code for Debian.
played an important role here inside the Debian Med team
(unforutunately).
> > I guess you are talking about
> >
> > https://github.com/sanger-pathogens/snp_sites
> >Just do some
git tag 0.1
git push --tags
would be perfectly sufficient (If I'm not totally wrong - I do not use
github). can you publish your work you mentioned at some place to let
us have a look?
It might be worth digging in git-buildpackage where you can leave the
.git structure. See Debian Med policy for this.
> My initial procedure was, as I said above, to strip away all git relatedI agree that making it the most simple is a good way to start. So in
> stuff and build the package as simply as possible.
> I also had a look at gitbuilder procedures, but didn't follow this line as
> I was advised to keep it simple.
principle there is nothing wrong with your approach.
> I am going through these documents and even if not for this package, IThat's very cool if we can meet in Stonehaven!!!
> would be quite keen to go through the mentoring of the month method later
> in February.
> Possibly after the Stonehaven meet up which I am attending.