On Thu, Mar 10, 2016 at 5:00 AM, Mattmann, Chris A (3980) < [email protected]> wrote: > > - Even considering 40 threads I doubt there have only be <= 40 *decisions* > on the project to date. IOW they are being made somewhere but it's unclear > where. Email is easy to follow on a phone on the go whatever. >
The Hadoop project has a tradition of design docs being posted to JIRA as PDF, and discussion happening there. For example: https://issues.apache.org/jira/browse/HDFS-7285 That approach seems OK, but inferior to something that can be commented on inline (such as a text document in a code review tool). In Kudu, we've been trending toward decisions being made through discussions on design docs happening in change requests like this one: http://gerrit.cloudera.org/2443/ which seems like a reasonable way to review a design doc. Once it's committed, the design doc lives in the main ASF code repository, like these: http://github.com/apache/incubator-kudu/tree/master/docs/design-docs (we're also working on moving more design docs over from individual directories, and legacy design docs that lived on Google Docs, into the central location [1, 2]). I suppose another way to review designs would be to paste each doc into an email on the list, and people could comment inline on it. Once reviewed, I'd want us to commit it anyway, though. There are pros and cons to this approach, relative to what we're doing now: One pro is that it could be more transparent to people not intimately involved with the project, especially to people browsing the dev list. On the downside, it would be easier for the author to miss some comments while revising the doc, be a bit messier, and people may still leave comments on Gerrit when the author goes to do the final commit of the completed design doc. That said, I personally wouldn't have a problem with trying it out. * Create a [email protected] and send all automated > traffic there. *-issues is one option; we could make another name for > it. > > That will help to separate the signal from the noise in terms of > dev/architectural/etc. discussions from code reviews and automated > commit messages. > As of a couple weeks ago, we no longer sending JIRA traffic to dev@. It now goes to issues@: http://mail-archives.apache.org/mod_mbox/incubator-kudu-issues/ We might want to consider creating a reviews@ list to get the Gerrit traffic off of the main dev list, if people want to use the archives to browse non-tool oriented developer discussion on the dev list instead of using email filters to separate out the different kinds of traffic. (I personally use email fliters for that.) Mike [1] http://gerrit.cloudera.org/2499/ [2] http://gerrit.cloudera.org/2495/
