Hi, On Sun, Jan 24, 2010 at 01:51:42AM +0800, Thomas Goirand wrote: > Sebastian Harl wrote: > > 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 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. I don't think that using two different "service providers" makes a lot of sense. Imho, we should either use alioth for Git and mailing lists or do both on our own (I could host that 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. Yep, I'll do that, if Dan agrees with it. > > 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 Well, somebody must have heard you … 1.2.17 has just been released a few hours ago ;-) > > 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. Well, Dan replied to my other E-mail in private telling me that he's currently waiting for his sponsor to review and upload 1.2.17RC2. Dan, I'd happily sponsor the package as well (but, imho, it makes sense to upgrade to 1.2.17 before uploading -- I hope, this should not be a lot of work). > 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. Feel free to provide patches *scnr* ;-) Cheers, Sebastian -- Sebastian "tokkee" Harl +++ GnuPG-ID: 0x8501C7FC +++ http://tokkee.org/ Those who would give up Essential Liberty to purchase a little Temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin
signature.asc
Description: Digital signature
