On Sun, Jan 18, 2015 at 7:34 AM, Benedikt Ritter <brit...@apache.org> wrote: > Hi all, > > over at the Apache Commons Project, we have a long discussion about our > mailing lists. Are they to noisy? Should they be splitted up into sublists? > Should individual components go TLP? > IMHO Ben McCann summed up the core problem pretty well [1]. Mailing lists > are simply a outdated tool from the 90s. They can not compete with tools > like github/gitlab that integrate the code with the possibility to do code > reviews, disucssions and bugtracking. >
So there are reasons that we choose to mandate mailing lists, and one of them is traceability. People know where to look for decisions; ten years down the road we know where to look for decisions and know that we are retaining the information. Github is a great tool for review workflows, but it isn't mutually exclusive with mailing lists. Infra built integration[1] that lets you have both worlds. Every discussion comment from github copied to a mailing list, and every mailing list comment in that thread copied back to Github. Many projects (more than 40) are using this to great effect - it's become a core part of their contribution and review workflow, many have tied it into Jenkins or Travis so they get CI feedback in the process. --David [1] https://blogs.apache.org/infra/entry/improved_integration_between_apache_and
