Hello all, First, I would like for us to decide on a central package repository. I don't really care where it is as long as it's public and easy to upgrade the apt files of the repo (ie should be a Debian system). I think someone mentioned alioth having ftp access... but I cannot seem to locate it. Next, I think we should organize a place where we can log changes to packages and report which packages are being worked on and by whom. The mailing list is probably a good place to announce if you are done a particular package, or if you require assistance from another developer. However, we also need to have a log of what packages are worked on by who... I propose we do this via the alioth CVS repository. I have setup an 'admin' repository (maybe a misleading name) for this purpose. Once you have an alioth user account let me or Arnd know and we can up your access level to 'developer'. At this point you will be able to check out the admin package. cvs -d :ext:YOU@cvs.alioth.debian.org:/cvsroot/debian-x86-64 co admin (replace YOU with your alioth user name) You can also view files in CVS here: http://cvs.alioth.debian.org/cgi-bin/cvsweb.cgi/admin/?cvsroot=debian-x86-64 I would ask that the developers currently porting packages please update this list (I can do it for you by proxy). I was going to move on to another package, and I am not sure if any of them are already taken care of. Arnd, seems to have all (of most of) the core libraries ported. I was looking at the dependencies of sbuild.. and was considering moving to perl, bind9 (for libdns), or exim. Since we don't need these to be 64bit... maybe it's time to start using sbuild. Any thoughts? Regards, B. -- WebSig: http://www.jukie.net/~bart/sig/
Attachment:
pgpjvE9NlDtcE.pgp
Description: PGP signature