[Pkg-zope-developers] about the pkg-zope repositories

[martin f krafft]

So yes, I had told a bunch of people that debconf5 would be the
pinnacle of pkg-zope development and we'd be ready to roll out the
best Zope distribution ever right afterwards. Lemme break this up:

  1. Debian will provide the best Zope distribution of all
  2. Debconf5 was productive wrt pkg-zope
  3. We are ready to roll

(1) holds, (2) is only marginally true, (3) is not. Or not quite.

Fact is that we are currently working on two separate tracks. Fabio
is leading the zope-common transition as part of the Google Summer
of Code project he was awarded. And as some of you may know, I am
concentrating on wedding APT packaging and the bazaar revision
control system (which is based on GNU arch).

  http://blog.madduck.net/debian/2005.08.10-arch-packaging.html
  http://blog.madduck.net/debian/2005.08.11-arch-packaging-over.html

Fact is that the system works beautifully and I am loving it, but
it's awfully complex. I have documented most of it on our wiki

  http://debian.madduck.net/pkg-zope/wiki/Arch

but I still am not at the point where I can

  (a) claim that I am fully in control of the system or understand
      all its angles.

  (b) expect you guys to invest a lot of work into learning it.

Again, as some of you may know, I am travelling to Ireland tomorrow

  http://blog.madduck.net/debian/2004.08.14-arch-complexity-and-phd.html

for a potentially significant change of life. I am kinda putting off
all kinds of promises until after my talk tomorrow, so stay tuned.

However, the future will likely see a tool that will make managing
packages in teams in a repository much easier. I think it's best if
we wait for this tool because

  - it will save everyone time
  - it will give me more time to test and understand; I'd hate to
    teach you things that turn out to be wrong later so that you
    have to unlearn
  - the tools (baz/bzr) get better every day, so waiting does not
    hurt.

In the mean time, I think we might all want to work on migrating
existing packages to the new policy

  http://debian.madduck.net/pkg-zope/wiki/Packages/Policy

and uploading them to experimental using regular means. Until the
repositories are in place, we'll just have to communicate a lot by
email.

Does this sound like a fair deal? Comments welcome?

-- 
 .''`.     martin f. krafft <madduck at debian.org>
: :'  :    proud Debian developer and author: http://debiansystem.info
`. `'`
  `-  Debian - when you have better things to do than fixing a system
 
Invalid/expired PGP (sub)keys? Use subkeys.pgp.net as keyserver!
 
"everyone smiles as you drift past the flower
 that grows so incredibly high."
                                                        -- the beatles
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature (GPG/PGP)
Url : http://lists.alioth.debian.org/pipermail/pkg-zope-developers/attachments/20050815/e5f3b0f1/attachment.pgp