The state of the package, and where we go from here

[Wouter van Heyst]

On Sat, Nov 25, 2006 at 06:07:52PM +0000, James Westby wrote:
> > > I think dato had some ideas on this, and I am reluctant to do too much
> > > with the package in his absence, but we can at least do something useful
> > > with this code that we have.
> > 
> > Did dato leave some sort of vision in what direction to go, or can we
> > contact him?
> 
> He didn't really leave a vision, there are a few hints in the ITP 
> 
> http://lists.debian.org/debian-devel/2006/08/msg00274.html
> 
> and he did mention that he had different ideas to me. As for contacting
> him I'm not sure about that.

I see, I'll react below.

> > > As for infrastructure/colloboration type things I would like to know
> > > what you think.
> > > 
> > > We have 3 lists discuss, maint and commits, I think the purposes are
> > > pretty clear. I'll see about setting up the commits list at some point.
> > 
> > I'm only on -discuss atm, do we need the others yet?
> 
> The package has just been uploaded with -maint as the maintainer. You
> can subscribe there if you want to try and help deal with the flood of
> bug reports I'm sure we will receive.

Will do.

> -commits is dead at the moment. In fact you'll know better than me how
> to get it going. I haven't ever used hooks from bzr yet.

Depends on what you want, the standard way of operating is to locally
have a post_commit hook using the email plugin. For an example, see
https://lists.ubuntu.com/archives/bazaar-commits/2006-November/date.html

> > With the decentral nature of bzr anyone can go ahead and make changes as
> > they like, but certainly for pushing to bzr.debian.org I'd suggest
> > people communicate first, untill there is a team that has a good idea of
> > what everyone is up to and enough confidence to just go ahead.
> 
> It sounds like a very good idea to me. We've already had John working on
> changelog.py on his own branch, and I'll make sure to look over the
> changes and merge something soon.
> 
> Everyone should also feel free create a subdir in the bzr repository and
> push any branches there should they feel the need.

A people/ subdir sounds like a good idea, a central place for the public
mirrors of what people are working on. 

> On another note, I think there are two things we can do with the
> package,
> 
>   1) Provide a uniform and clean API for manipulating Debian related
>      data. I think this will come with time. I personally haven't looked
>      over the rest of the code yet to see how it does it's stuff. I also
>      think I'll benifit from learning from the people involved that can
>      actually code python.

After reading the ITP I have a better picture of where python-debian
could be going. Is anyone aware of other code dealing with Debian
related data that might be a candidate for merging?

Wouter van Heyst
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 307 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-python-debian-discuss/attachments/20061126/ce947cfc/attachment.pgp