On Tue, Mar 8, 2016 at 9:23 AM, Sam Ruby <ru...@intertwingly.net> wrote: > On Tue, Mar 8, 2016 at 7:54 AM, Sam Ruby <ru...@intertwingly.net> wrote: >> >> A template is just one part of the process. Deciding which podlings >> need to be reminded, and where to send those reminders is also >> important. In particular, what are the exceptions. This very mailing >> list is an exception, where the name does not match the PMC for ASF >> infrastructure implementation reasons. > > To facilitate discussion, I tossed together a quick and dirty cross > reference of active podlings vs mailing lists: > > https://whimsy.apache.org/incubator/maillist > > In particular, look for the gaps. I'm confident that this can be > easily corrected, but this is the types of problems than need looking > into. And an example of the types of problems that trip up automated > jobs, either causing them to fail outright; or worse to silently fail.
First level analysis: 1) old podlings which had mailing lists created using a different (more difficult to graduate) infrastructure implementation: blur, wave 2) new podlings that don't yet have a mailing list: gearpump, mnemonic 3) podlings whose mailing lists are hosted by their sponsoring project: log4cxx2 4) podlings whose mailing lists are named differently: odftoolkit Thoughts? - Sam Ruby
