On 10/28/2016 04:24 PM, Mats Wichmann wrote: > On 10/28/2016 04:56 PM, Gregg Reynolds wrote: >> On Oct 28, 2016 5:35 PM, "Mats Wichmann" <mats at osg.samsung.com >> <mailto:mats at osg.samsung.com>> wrote: >>> >>> On 10/28/2016 04:33 PM, Gregg Reynolds wrote: >>>> On Oct 28, 2016 5:25 PM, "Nivedita Singhvi" <niveditasinghvi at gmail.com >>>> <mailto:niveditasinghvi at gmail.com> <mailto:niveditasinghvi at gmail.com >>>> <mailto:niveditasinghvi at gmail.com>>> wrote: >>>>> >>>>> Hello, >>>>> >>>>> While the wiki page lists the names of the architects, maintainers >>>>> and other contacts, it does not provide an email (except for a few) >>>>> or other contact info: >>>>> >>>>> https://wiki.iotivity.org/projects_and_functionsrmation. >>>>> >>>>> While it's possible to hunt down some folks on the mailing list or via >>>>> the git tree (not always reachable, or accessible to all), it would be >>>>> nice to have the preferred email contact available off that wiki page, >>>>> or elsewhere, following the model that the Linux Kernel Maintainers >>>>> file takes. >>>>> >>>>> https://www.kernel.org/doc/linux/MAINTAINERS >>>>> >>>>> >>>>> Would the iotivity community please consider this? >>>>> >>>> >>>> +1 >>> >>> I know not everyone is always here all the time, but is there a problem >>> with mailing to this list? >>> >> not sure I understand the question. personally I prefer that everything be >> discussed on this list, but as a matter of fact that is not what happens >> with gerrit. tons of stuff gets discussed only by the people included as >> gerrit reviewers, and the results end up presented to the rest of us as >> facts on the ground. >> >> somewhere on the web there is a great article explaining why email is the >> best way to deal with patches (esp. wrt to linux) but naturally I cannot >> find it. > > I know well the materials to which you refer, about email discussions. Greg > KH has commented, and presented, at length on the topic. Some people think we > who agree with that are dinosaurs :) > >> I think this is a (relatively) major problem with a gerrit-based project. >> >> one obvious way to begin to address this is to send daily digests. > > I think we could take 20 people and get >20 discrete opinions. It's no good > if important discussion gets buried in the reviewing tool so most people > don't see it or are able to find it. It's not any better if so much is in > email that only the people whose job it is to live 12 hours a day parsing > those emails as maintainers can keep track of if all the parts of something > have been handled. Mostly it has to do with work styles, I believe. Since > I'm mainly a kibitzer here, I should stop now. > > > Personally, I think a Maintainers file inside the project is a reasonable > proposal (I wasn't trying to shoot that down, just hint that I don't see this > list used that much for detailed technical discussion and we could try that).
Thanks, Mats! I share the sentiments wrt Gerrit (it has been hard to join this project and come up to speed, and I've yet to get to the point where I can even submit a patch). I would very much like to second the request to use this mailing list much more for technical discussions, including bug stuff (not internal bug infrastructure). thanks, Nivedita
