Hi Matt, I’ve just rationalised the first-comes on the Catalyst related distributions that I flagged:
> For Catalyst-Controller-WrapCGI, you have first-come on the lead module and > one other module, and RKITOVER has first-come on one module. RKITOVER has > done all releases, so makes sense for him to get first-come? > > For Catalyst-DispatchType-Regex, you have first-come on the lead module, but > MGRIMES has first-come on the other three, and has done all releases. Also > transfer first-come to him? > > For Catalyst-Engine-Apache, AGRUNDMA has first-come on the lead module, and > you have first-come on the others. AGRUNDMA did most releases, then in 2010 > BOBTFISH did 3 releases and FLORA did one. No releases in the last 10 years, > but again, make sense to give AGRUNDMA first-come on all? > > For Catalyst-Model-CDBI-Plain, JESTER has first-come on the lead module and > you have first-come on Catalyst::Helper::Model::CDBI::Plain. JESTER did 2 > releases in 2005, and MRAMBERG did a single release also in 2005. Again, > maybe irrelevant, but give JESTER first-come? On all of these, I gave the indicated person first-come. > For Catalyst-Plugin-Authentication-Store-DBIC, MRAMBERG has first-come on the > lead module, DKAMHOLZ has a first-come from some releases he did in 2006, and > you have two first-comes from doing the two most recent releases, which were > in 2008. MRAMBERG did some releases before you, so with the default rule he’d > get first-come on all — sound ok? I ended up giving you first-come on this distribution, as it was split three ways, and you did the most recent releases anyway, even though they were in 2008, so it may all be academic. Cheers, Neil
