On Fri, 7 Jun 2019 at 15:52, Christofer Dutz <christofer.d...@c-ware.de> wrote:
> Hi all, > > I would like to propose to introduce a new mailing-list for intra-project > communication. > I think we should be cautious about creating new foundation-wide lists. unless there's an existing group or activity that the list serves, I expect that it's hard to get critical mass to make the list useful the recent creation of diversity@ made sense, for example, because a specific group of people (rather miraculously) emerged who would use the list. I think it would have not worked to create the diversity@ list first and then invite people to join it. if that makes sense? horse before the cart, etc, etc for intra-project communication, is there a reason why copying multiple project-specific lists is not a viable option? > As it is my primary goal to help communication in the IoT field at Apache > I would like your votes on this. > I absolutely do not want to contribute stop energy to your efforts here. having said that, I lack the context behind this proposal. has there been a discussion somewhere else about this? i.e., are multiple IoT related projects requesting one? > b) create a tech@a.o<mailto:tech@a.o> list that's expected to be used with > [subject][line][tags] only > I can't weigh in on (a) or (c) without more information. but (b) seems to be unrelated to this proposal. is there a feeling that enough people would subscribe to a gene...@apache.org type list to make it useful? honestly, my initial concern is community management. who is going to moderate that list? (specifically, and at a minimum, making sure people abide by our Code of Conduct). project communities, and their associated lists, small as they are, can be exhausting to manage. how much more challenging would that be for a foundation-wide list. and who would do it? > The vote will stay open for the normal 72 hours. > I think it was premature to start a vote. voting is the failure mode of discussion :) if you are sure that what you want to do is okay, you can just inform the list and wait for lazy consensus (i.e., no objections). if a discussion is started, then consensus building should be used before any options are tabled for voting
