Just some feedback from my side as we were having similar discussions on the PLC4X project.
The thing is, if technical discussions are held on GitHub, in PRs or in Jira, getting an overview of what's happening requires to register to all of these and to continuously monitor all of these systems. Also did we try out the code reviews of GitHub and had these forwarded to the dev list. This resulted in mornings with 100 new emails because every single comment to every single line of a PR resulted in a separate Email (not quite what we wanted). So now we're discussing technical things where people should be involved on the dev-list and implementation specific stuff we think is not worth wasting the other project members time in PRs and Jira issues. Chris Am 03.12.18, 12:59 schrieb "Xiangdong Huang" <[email protected]>: Hi, Thanks for the information. I think the two suggestions are good: 1. Move discussions about big PR or design details to the dev list: > If a PR is a big change, or if discussion veers into into design details rather than just code, we expect our committers to say "let's move this to the dev list". 2. a weekly or monthly report for reporting how many PR or issues are resolved is useful. I think we can try like this for a while to see whether it is useful :D Best, ----------------------------------- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Bertrand Delacretaz <[email protected]> 于2018年12月3日周一 下午5:45写道： > Hi Kevin, > > On Sat, Dec 1, 2018 at 6:32 PM Kevin A. McGrail <[email protected]> > wrote: > > Bertrand, wasn't this issue discussed recently?... > > There was this "Discussions in pull requests vs. dev list" thread on > comdev, which might help. > > > https://lists.apache.org/thread.html/a90d871d7e8637b7ed566bcc5f06a9920b480097647d1b70424fce1e@%3Cdev.community.apache.org%3E > > -Bertrand >
