Individual projects should and are able to organize however they choose, I believe this is codified by TSC Rules. The debate between the ‘firehose of information’ list, I.E. the Open Stack list model, that requires skillful filtering and increases the chance of missing something due to overload, and the each project has its own list, I.E. the OpenDaylight model where claims include that it’s difficult to stay looped in and that it is tedious to subscribe to all the lists, has been debated ad infinitum.
I’m not interested in repeating it. I’m for finding ways to increase communication in SO and so far many have been shy to use the list as it broadcasts to the whole ONAP community. If that is a blocker for needed communication, I am for trying something different, including a separate list. I have no doubt that the community can subscribe to said list and still stay looped into SO plans and communication. https://lists.onap.org/g/main/topics or groups.io makes staying up on topics rather easy. I am not proposing that all projects follow suit or that the TSC mandate separate lists, but projects are welcome to create lists according to their own organizing decisions. Thanks, Marcus Williams IRC, Twitter, etc. @ mgkwill Intel Corp. From: [email protected] [mailto:[email protected]] On Behalf Of Victor Morales Sent: Monday, August 6, 2018 5:59 AM To: [email protected]; [email protected]; Michael O'Brien <[email protected]> Subject: Re: [onap-discuss] [SO] separate mailing list Marcus, What about using hashtags? I’m agree with Tal and Michael about creating a separate mailing list per project could reduce the communication among projects. Shouldn’t be better to provide some mailing list etiquette information as OpenStack does? https://wiki.openstack.org/wiki/MailingListEtiquette Regards, Victor Morales From: <[email protected]<mailto:[email protected]>> on behalf of Tal Liron <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Saturday, August 4, 2018 at 10:06 AM To: onap-discuss <[email protected]<mailto:[email protected]>>, Michael O'Brien <[email protected]<mailto:[email protected]>> Subject: Re: [onap-discuss] [SO] separate mailing list I agree strongly with Michael that it's a bad idea. If every project had its own mailing list it would make visibility and participation that much harder. But perhaps we can create a WeChat group for the project to help dev coordination. And I do think we should do something else, though -- have clearly separate "support" and "development" mailing lists for ONAP in general. There is "onap-users" that is never used and "onap-discuss" which is just too general and becomes the catchall for everything. On Fri, Aug 3, 2018 at 8:10 PM Michael O'Brien <[email protected]<mailto:[email protected]>> wrote: -1 on a separate mailing list per project I find that splitting up the already distinct project more is not a good development. Onap-discuss should be the goto place for anything onap related including sdnc, security and so related items. /michael From: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> On Behalf Of Marcus G K Williams Sent: Friday, August 3, 2018 3:03 PM To: Seshu m <[email protected]<mailto:[email protected]>> Cc: [email protected]<mailto:[email protected]>; Jessica Wagantall <[email protected]<mailto:[email protected]>> Subject: [onap-discuss] [SO] separate mailing list Seshu, +2 to your mention of setting up a separate list for SO. As an FYI, I setup a list for SDNC when I was a committer there last year (https://lists.onap.org/g/onap-sdnc/topics ). The process just entailed opening a ticket with the LF. I’d imagine the process is the same, even though we migrated to groups.io<http://groups.io>. Thanks, Marcus Williams IRC, Twitter, etc. @ mgkwill Intel Corp. This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#11688): https://lists.onap.org/g/onap-discuss/message/11688 Mute This Topic: https://lists.onap.org/mt/24157225/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
