JB, Are there any examples of similar process for another Apache project? Providing regular updates of discussion happening another open list seems burdensome, especially for new contributors who come to project with large proposals.
If a feature is large enough, may be a there needs to be a design doc that others could comment on and reach a good consensus before lot of work goes in, rather than trying to summarize review comments. What about the replies to weekly summary of a review? Should those go to review or just stay on dev list? On Thu, Oct 6, 2016 at 4:53 AM, Jean-Baptiste Onofré <j...@nanthrax.net> 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: rev...@beam.incubator.apache.org. > 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é > jbono...@apache.org > http://blog.nanthrax.net > Talend - http://www.talend.com >
