On 2018-11-22 08:59 +0100, Thomas Goirand wrote:
> On 11/22/18 6:02 AM, Wookey wrote:

No advice on best way to start a python packaging template?

> > And it looks like it should be called src:drf-filters
> > binary:python3-djangoresetframework-filters to fit in with naming
> > conventions of related packages/python team (even though upstream is
> > 'django-rest-framework-filters'). Right?
> The binary package name is right, though there's no convention for the
> source package naming. "drf-filters" doesn't feel very descriptive to me
> though.

I agree, but I took it from 
drf-extensions -> python3-djangorestframework-extensions
drf-generators -> python3-djangorestframework-generators
drf-haystack -> python3-djangorestframework-haystack

on the other hand there is:
djangorestframework-gis -> python3-djangorestframework-gis

I don't care which is used. I guess djangorestframework-filters is
clearer, and closer to upstream so people can find it. I'll go with
that unless someone says the drf-* names are a better plan.

> > Also related: I've updated drf-extensions to 0.4 (from the current
> > 0.3.1), as that is needed for lava, and fixes
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865851
> > 
> > What I'm not quite sure about is if there is any reason _not_ to
> > update this package. It has no reverse dependencies so I presume this
> > is a good idea and I should just get on with it? would a 10-day NMU be
> > appropriate?
> If you join the team, I see no reason why you couldn't do the upgrade
> yourself indeed, especially if you do a 10-day NMU on it.

So I need to join the team to do anything in the salsa repos? I don't
claim any real python extertise (I can just about read it - I try to
avoid writing it as I'm a bash, perl and C person). I would prefer to
sort this out to a decent standard and then hand it over the python
team for maintenance, but I can join up as a minor conributor if that
works better.

It occurs to me that you probably prefer me to do this as a branch in
the drf-extensions salsa repo, rather than a simple NMU? I prefer the
latter as I know how to do that (sbuild+dupload), but if I have the
permissions I can have a go at this newfangled git-pq + salsa stuff. I
presume that'll be less work for you guys and I suppose I'll learn
something :-)

Principal hats:  Linaro, Debian, Wookware, ARM

Attachment: signature.asc
Description: PGP signature

Reply via email to