+1 Right now, the onap-discuss mailing list has 5 topics [1]: admin development infrastructure installation users
People mailing the onap-discuss would need to create subject lines that can be filtered, as we do OpenStack, OPNFV, and many other Open Source communities [2]. ONAP examples: [onap-discuss][admin] [onap-discuss][development] [onap-discuss][installation] [onap-discuss][infrastructure] [onap-discuss][users] Also, the topic feature of mailman needs to be configured for individual projects, ie: demo dcae mso Examples of project-specific subject lines: [onap-discuss][demo] [onap-discuss][dcae] [onap-discuss][mso] Users can then subscribe to specific filters as we all choosing to receive emails that do not match a filter. [1] https://lists.onap.org/mailman/options/onap-discuss [2] https://wiki.openstack.org/wiki/MailingListEtiquette Andy Grimberg - do you where I create a ticket to have projects added to the onap-discuss top categories? ----- Aimee Ukasick Open Source Engagement OPNFV, OpenStack, ONAP IRC: aimeeu On 04/20/2017 08:46 AM, Andrew Grimberg wrote: > On 04/20/2017 03:16 AM, Josef Reisinger wrote: >> Folks, >> >> good to see this huge activity on the list .. but honestly, it starts to >> become overwhelming. What do you think about splitting the discussion >> list in per-domain lists, i.e. >> o onap-install for all topics regarding installation in openstack >> (vanilla/rackspace) >> o onap-admin for admin related task, if users in the portal are missing >> etc... >> o onap-develop for the ones interesting to develop onap core functions >> o onap-users for the ones finally creating services using onap. >> >> I know there will be overlap here and there - what's the view of the >> community? > > One of the things we've seen with our various communities is that the > more mailing lists that they have the harder and more confusing it is > for someone new to know where to send their questions and thus they end > up cross-spamming to far more lists than they really need which ends up > seeing the other lists getting a lot of chatter that they really don't need. > > Instead of splitting the list, I would suggest that using the topic > feature of mailman until we have a truly relevant need to split out a > particular topic to its own list. > > To help this along I've added a few topics to the list. > > I'll see about adding information to the ONAP wiki, but in the mean time > here [0] is some documentation from the OpenDaylight wiki on topics. > > Topics just now added to the list are: > > [admin] > [devel] > [infrastructure] or [infra] > [install] > [user] or [users] > > At a very minimum if folks start using topics, even if they aren't > specifically defined then it becomes easier for people to write mail > filters to handle bringing mail that is more relevant to them into a > more visible or manageable location. > > -Andy- > > [0] https://wiki.opendaylight.org/view/Communication > > > > _______________________________________________ > onap-discuss mailing list > onap-discuss at lists.onap.org > https://lists.onap.org/mailman/listinfo/onap-discuss > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: <http://lists.onap.org/pipermail/onap-discuss/attachments/20170420/f45d13ec/attachment.sig>
