+1 for supporting different working styles. On Thu, Oct 6, 2016 at 10:58 AM, Kenneth Knowles <[email protected]> wrote:
> +1 to [email protected] if it is turnkey for infra to set > up, aka points 1 and 2. > > Even though I would not personally read it via email, getting the > information in yet another format and infrastructure (and stewardship) is > valuable for search, archival, and supporting diverse work styles. The > benefit might not be huge, but I think it will be enough to justify the > (hopefully negligible) cost. > > Kenn > > On Thu, Oct 6, 2016 at 4:54 AM Jean-Baptiste Onofré <[email protected]> > wrote: > > Hi team, > > following the discussion we had about technical discussion that should > happen on the mailing list, I would like to propose the following: > > 1. We create a new mailing list: [email protected]. > 2. We configure github integration to send all pull request comments on > review mailing list. It would allow to track and simplify the way to > read the comments and to keep up to date. > 3. A technical discussion should be send on dev mailing list with the > [DISCUSS] keyword in the subject. > 4. Once a discussion is open, the author should periodically send an > update on the discussion (once a week) containing a summary of the last > exchanges happened on the Jira or github (quick and direct summary). > 5. Once we consider the discussion close (no update in the last two > weeks), the author send a [CLOSE] e-mail on the thread. > > WDYT ? > > Regards > JB > -- > Jean-Baptiste Onofré > [email protected] > http://blog.nanthrax.net > Talend - http://www.talend.com >
