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

[Wouter van Heyst]

On Thu, Nov 23, 2006 at 09:00:41PM +0000, James Westby wrote:
> Hi all,
> 
> So, it's a day late, but here's some thoughts on pkg-python-debian.
> 
> The 0.1.0 version is sitting in NEW on it's way to experimental. I have
> branched this off on alioth so that we have it if we need it, and until
> bzr supports tags.

<snip api stability ponderings>

I haven't made use of the code a python developer yet, just browsing
through it and end-user use of bzr-builddeb. Something like the bzrlib
api promises may be too heavy-weight, someone who has a vested in the
api not changing under their feet should speak up.

> 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?

> 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?

> We have a shared bzr repository for the package ar bzr.debian.org. If
> you are not sure how to deal with all of that then let me know. The idea
> is for the package to be built by bzr-builddeb, also let me know if you
> don't know what that is.

*some idea of what that is ;)*

> As for collaboration I am happy for you to change whatever you want
> really. I would really appreciate people updating debian/copyright (and
> the files themselves) if you make a significant contribution to someone
> elses work (including the packaging).
> 
> My changelog.py is only used by bzr-builddeb as far as I know. So I
> would at least like a notice if you change the API so that I can update
> it. I would also like if big changes were discussed on the mailing list
> first, and a consensus could be reached on where to go. It's probably
> not that important with a small code base, but I think it's good to get
> in to good habits. 

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.

> I would really like your opinion on the comments above (if you can
> decipher them, it's a bit of a stream of consciousness) and any other
> thoughts that you might have.

< james_w> LarstiQ: just fire up your mail client and let yourself go.

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/20061125/05a84fdf/attachment.pgp