[cl-debian] pkg-common-lisp.alioth.debian.org is born!
Hi all! Cc:ing all the people invoveld in Common Lisp work on Debian, sorry if you receive this mail in double. Please respect the Reply-To: and Mail-Followup-To: headers, thanks! Finally, my proposal to going to common maintenance [1] comes to life: pkg-common-lisp has been created on Alioth [2]. Let's have fun! What's done: 1) inserted the project into the Alioth tree: * Development Status: 6 - Mature * Environment: Console (Text Based) * Intended Audience: Developers * License: OSI Approved * Operating System: POSIX * Programming Language: Lisp * Topic: Packaging 2) added old members of the CL-Debian project. If someone wants to be added, she/he can file a request on the Alioth project page [2] or drop me a mail. 4) created the -commits mailing list: this will be close to everyone but mails coming from alioth.debian.org, since I guess this should be the envelop for automatic commit mails for every VCS (this setup should be tested, however). 5) created the -devel mailing list, whose purpose is duplex: being in the Maintainer: debian/control field for every package which is co-maintained and being the official list for the team (thus super-seedingl-debian@common-lisp.net). While in the beginning I thought to migrate the cl-debian@ archives as well, I don't think it's a good idea anymore, so I'll do it only if someone asks for it. FYI, this mail has been posted primarily on the -devel mailing list, please reply there (R-T and M-F-T accordingly set). 6) moved the CL-Debian Alioth homepage [3] to the new project [4], adapting it for the new mailing list and goals, thus removing its "darcs-centrism". There's space for improvements ;-) I voluntarily omitted information about the old "central" darcs repository in the new homepage, because as for the mailing list, the sooner we move, the better is. For this reason, the old homepage [3] now automatically redirects to the new homepage [4]. The next steps are the following: some of them will be managed soon after this mail. 7) migrate everyone subscribed to cl-debian@ to the new -devel mailing list, to promote the latter. In 2 weeks at last the old cl-debian@ will be closed. Is this kind enough to the cl-debian@ subscribers? I'm all for it, because there's no point in having two mailing list: the sooner the new one is used, the better is. 8) since the VCS poll [5] ended with no real decisions, pkg-common-lisp's supported VCSs ATM are, in alphabetical order: bzr, darcs, git and hg. Directories for these VCSs already exists on Alioth: you can migrate your packages, but please follow the instructions on the Debian Wiki [6] and the ones described below. If people state which package can be co-maintained, everyone in the project can migrate that package. This means that the debian/ folder needs to be adjusted: a- debian/changelog: add a note about the new maintainer b- debian/control Maintainer: Debian Common Lisp Team <pkg-common-lisp-devel@lists.alioth.debian.org> Uploaders: [who usually take care of the package and the sponsor(s)] c- debian/copyright it should reflect the Uploaders: debian/control field, at least for the Debian-related work. Please send a mail to this list as soon as a package migration is completed. About the debian/ folder, which reflects the Debian work done on the package: I'm in favor of clearly add copyright and license information in the debian/copyright file (as I do for all my packages, e.g. [7]). I'd like that the team agrees on a single license for the Debian work (my preference is always for GPL...), but it it's considered too much a pain we'll continue with the status quo. 9) do we need some other Alioth features, like the tracker, news, task manager or forum? I prefer to keep as simple as possible: - the -devel mailing list for discussion - the Debian BTS [8] for all bugs/wishlists Maybe we should enable the tracker if we want project's problems to be monitored by other than the Debian BTS [8]. However, about this issue, I'm in favor of a Debian cl-debian (meta)package, which would combines this project with a "basic" Common Lisp installation on Debian. This is a very new idea, thus it needs a bit more reflexion. I'm eager of anyone comments :-) Thx, bye, Gismo / Luca Footnotes: [1] http://common-lisp.net/pipermail/cl-debian/2007-October/002859.html [2] http://cl-debian.alioth.debian.org [3] http://alioth.debian.org/projects/pkg-common-lisp/ [4] http://pkg-common-lisp.alioth.debian.org [5] http://www.livejournal.com/poll/?id=1097084 [6] http://wiki.debian.org/Alioth [7] http://packages.debian.org/changelogs/pool/main/s/stumpwm/stumpwm_20070908-1... [8] http://bugs.debian.org
Hi Great work Luca, I'll start migrating asap. On Fri, 11 Jan 2008 18:59:26 +0100, "Luca Capello" <luca@pca.it> said:
9) do we need some other Alioth features, like the tracker, news, task manager or forum? I prefer to keep as simple as possible:
I got a complaint from a ubuntu user a while ago that he could not find a place to report a clc bug, so maybe having some hints on how to open bugs from non-debian systems would be nice to have.
Maybe we should enable the tracker if we want project's problems to be monitored by other than the Debian BTS [8]. However, about this issue, I'm in favor of a Debian cl-debian (meta)package, which would combines this project with a "basic" Common Lisp installation on Debian. This is a very new idea, thus it needs a bit more reflexion.
The 'standard' CL would depend on the architecture?
I'm eager of anyone comments :-)
How and where do we upload the darcs/git/bzr repositories? Ciao, Peter
Hi Peter, I'm sorry for the lag, free time is a mirage, lately... On Sat, 12 Jan 2008 00:00:38 +0100, Peter Van Eynde wrote:
I'll start migrating asap.
This is also my intention, at least for the packages I maintain. Then, I'll start pinging who already expressed a positive feeling to team maintenance and helping her/him to migrate.
On Fri, 11 Jan 2008 18:59:26 +0100, "Luca Capello" <luca@pca.it> said:
9) do we need some other Alioth features, like the tracker, news, task manager or forum? I prefer to keep as simple as possible:
I got a complaint from a ubuntu user a while ago that he could not find a place to report a clc bug, so maybe having some hints on how to open bugs from non-debian systems would be nice to have.
Mmm, this could be a point in favor of the Alioth tracker, but I'm still skeptical. Anyway, for sure the team website is missing pieces: the idea is to provide links or, directly, all the necessary information to contribute and report bugs or suggestions.
Maybe we should enable the tracker if we want project's problems to be monitored by other than the Debian BTS [8]. However, about this issue, I'm in favor of a Debian cl-debian (meta)package, which would combines this project with a "basic" Common Lisp installation on Debian. This is a very new idea, thus it needs a bit more reflexion.
The 'standard' CL would depend on the architecture?
This could be an option, but my first idea was to poll the list users to know if there's a "major" CL implementation most people use and install it by default if no others are already installed. In this way, newbies have a common background when reporting bugs. This would also help developers, e.g. providing a cl-debian-policy package from the same source one. Anyway, let's discuss this after the team is completely operative ;-)
I'm eager of anyone comments :-)
How and where do we upload the darcs/git/bzr repositories?
Basically, I don't think the website should repeat information already available in the official Debian wiki: in alphabetical order bzr [1], darcs [2], git [3] and hg [4]. As I stated before, this needs to be integrate into our website, patches welcome. BTW, we should put the website into a VCS, too (no preference for me). What I'm still working on is how to have automatic commit mails for the different VCSs, since the Debian wiki has all the necessary information for git only [3]. I've a script for darcs (written by Marco Baringer for the BESE suite [5]), but I haven't completely tuned it to Alioth. Bzr and hg are still a bit unknown to me, so if people more involved with them would like to step in... Thx, bye, Gismo / Luca Footnotes: [1] http://wiki.debian.org/Alioth/Bzr [2] http://wiki.debian.org/Alioth/Darcs [3] http://wiki.debian.org/Alioth/Git [4] http://wiki.debian.org/Alioth/Hg [5] http://common-lisp.net/project/bese/
Hi all! On Fri, 11 Jan 2008 18:59:26 +0100, Luca Capello wrote:
Cc:ing all the people invoveld in Common Lisp work on Debian, sorry if you receive this mail in double. Please respect the Reply-To: and Mail-Followup-To: headers, thanks!
Still valid :-)
4) created the -commits mailing list: this will be close to everyone but mails coming from alioth.debian.org, since I guess this should be the envelop for automatic commit mails for every VCS (this setup should be tested, however).
Browsing (again) the PTS documentation [1], I noticed that we could avoid the -commits mailing list and use the sourcepackage_cvs@ PTS alias instead. In this way, people subscribed to the PTS with keyword 'cvs' will automatically get every commit. This approach has one big advantage: subscription is per package and not per project, i.e. you can decide to have commit mail for SBCL and not for CLISP. Will both be useful? If not, which one is the best? I'm not even sure the -commits mailing list should be archived: if not, I think the PTS is the way to go.
7) migrate everyone subscribed to cl-debian@ to the new -devel mailing list, to promote the latter. In 2 weeks at last the old cl-debian@ will be closed. Is this kind enough to the cl-debian@ subscribers? I'm all for it, because there's no point in having two mailing list: the sooner the new one is used, the better is.
Since no one replies against this, I just did it. You should have received a welcome message: in case you don't, either manually subscribe to the -devel mailing list or send me a mail. People will be unsubscribed from the old cl-debian@ mailing list in three days and the old cl-debian@ mailing list will be deactivated in two weeks from now.
8) since the VCS poll [5] ended with no real decisions, pkg-common-lisp's supported VCSs ATM are, in alphabetical order: bzr, darcs, git and hg. Directories for these VCSs already exists on Alioth: you can migrate your packages, but please follow the instructions on the Debian Wiki [6] and the ones described below.
I'll write soon another mail specific to git and darcs.
If people state which package can be co-maintained, everyone in the project can migrate that package. This means that the debian/ folder needs to be adjusted:
a- debian/changelog:
add a note about the new maintainer
b- debian/control
Maintainer: Debian Common Lisp Team <pkg-common-lisp-devel@lists.alioth.debian.org> Uploaders: [who usually take care of the package and the sponsor(s)]
c- debian/copyright
it should reflect the Uploaders: debian/control field, at least for the Debian-related work.
d- add the -commits mailing list to the automatic notification every time a patch is committed. The necessary steps are specific for each VCS, so I'll come back to this soon :-) e- as soon as the new version is uploaded, please remove cl-debian@ from the PTS [2]. I'll try to keep track of this and remove any package that has already migrated, but I can miss some of them... Thx, bye, Gismo / Luca Footnotes: [1] http://www.debian.org/doc/manuals/developers-reference/ch-resources.en.html#... [2] http://www.debian.org/doc/manuals/developers-reference/ch-resources.en.html#...
Hi all! On Wed, 23 Jan 2008 01:58:02 +0100, Luca Capello wrote:
On Fri, 11 Jan 2008 18:59:26 +0100, Luca Capello wrote:
7) migrate everyone subscribed to cl-debian@ to the new -devel mailing list, to promote the latter. In 2 weeks at last the old cl-debian@ will be closed. Is this kind enough to the cl-debian@ subscribers? I'm all for it, because there's no point in having two mailing list: the sooner the new one is used, the better is.
Since no one replies against this, I just did it. You should have received a welcome message: in case you don't, either manually subscribe to the -devel mailing list or send me a mail. People will be unsubscribed from the old cl-debian@ mailing list in three days and the old cl-debian@ mailing list will be deactivated in two weeks from now.
After this mail I'll mass unsubscribe all the people from cl-debian@ and the list will be then moderated for every post, until final deactivation (a mail will be sent when this will happen). Thx, bye, Gismo / Luca
participants (2)
-
Luca Capello -
Peter Van Eynde