Sebastian Harl wrote: > Hi Daniel and Thomas, > > On Sat, Jan 02, 2010 at 10:15:55PM +0800, Thomas Goirand wrote: >> Daniel Walrond wrote: >> Would you consider that we co-maintain this package in Debian? > > I've also talked to Daniel about that in private some time last year > but, then, somehow lost track of the package for some reason. > > Anyway, Daniel did not mind having some co-maintainers back then and I'm > also still willing to join a team. > > What do you guys think about team-maintaining mlmmj? Do you prefer > alioth or some private archive/mailing list (I don't care about that)?
I strongly believe as well that we need to build a team here. MLMMJ is increasingly a good project, people from SUSE and Gentoo have moved to it for a reason. Now Daniel doesn't seem to have enough time to work on this package (otherwise it would have been already uploaded with the updates). Us 3 like MLMMJ and are willing to work together on this. Sticking with a single maintainer doesn't make sense seeing the importance of the package and the lack of time Daniel seems to have. I don't care about using Alioth or not, what's important is that: - we have a public space for our talks - we use Git for maintaining as a team Alioth is ok for the Git, as for the package maintaining discussions, a new list on the mlmmj.org could do as well. As I am not a DD yet (I'm at the end of the applying questions), I can't do much on Alioth, but maybe you, Sebastian, could create a project on gforge, and add both us 3 to it, so we all have access rights on the Git. > Do you have any further changes? Daniel, in some of the recent bug > reports you mentioned that you were about to finish 1.2.16 packages > yourself -- did you base them on my changes? I do believe that we'd rather package 1.2.17~RC2. I'm sure that a final release will be out very soon, and that 1.2.17~RC2 is already in good shape. Sure, we need more testings, and the sooner we can test that 1.2.17~RC2, the better we are for having 1.2.17 in Squeeze. > I do not plan to upload an NMU but would rather like to get some > feedback from you guys first to get the new upstream release into the > archive and not disrupt any of your work. I do agree that an NMU is not what has to be done here yet, as this is not the Debian policy/habits to do such take over, and this is quite not polite. However, if Daniel has no time managing the package and keep saying he will do it "soon", we'll get stuck. At some point we have to set a deadline for a take over by a team management system. The fact that you, Sebastian, is already a DD is a very good thing. One more thing. I have myself contributed a PHP web moderation tool for MLMMJ that is in the contrib folder of 1.2.17, it would be nice to have this packaged as well somewhere in /usr/share (with a restrictive password protected thing by default to avoid issues). Such tool is quite important when running high traffic moderated list. Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
