Mailing list management is not uniform across all Linux Foundation projects. Some Projects handle it with many small mailing lists and others Projects opt for fewer lists and rely on tagging of email that can be filtered by their email client. The decision the ONAP Project made was to use email tagging rather than numerous small lists. Lists were to be created only for the main discuss list, the TSC and for any sub-committees. This was done to lower the pure administrative, and physical cost in true budget terms, but also due to the overhead for the Community created by a proliferation of mailing lists and the possibility for communication lapses when messages and replies are cross posted to lists someone is not a member of.
Gentle Community member, Miss Manners is very pleased to hear that it works for you over there.
OK, maybe it isn't fun, but doing so is likely to make you more popular with your fellow Community members as it gives them a way to focus on the emails that are of importance to them... even it it means that it is your project team's emails they want to ignore.
Groups.io uses #hashtags for topic (or ONAP project team thread) management. You tag a message by including a #hashtag within or at the end of the subject line of the message. Only the onap-discuss list is set up with a set list of hashtags. A complete list of tags can befound here: https://lists.onap.org/g/onap-discuss/hashtags
Please use support.linuxfoundation.org and ask for one.
If an individual ONAP project Community decides that a truly dedicated list is absolutely necessary, you must first get buy in from Moderators of the onap-discuss, onap-tsc and any of the subcommittee lists. There is a high likelihood that your new list will generate extra work for them due to cross posting and they simply may not be OK with that. This is an all-or-nothing requirement.
Once you can provide proof of sign-off, the following rules apply:
If all of those provisions are acceptable, please open a ticket via support.linuxfoundation.org including all supporting documentation, including the approvals of the other list Moderators, the list name, email addresses of the Moderators and the email of the initial membership list.
Of course you can. HOWEVER, It will not be part of the groups.io ONAP Project hierarchy and the LF isn't responsible for any of it.
Bless your little heart. I bet the rules about the "LF not being responsible for any of it" are going to suck for you a lot more than the original set of rules would have sucked?
Please re-read the I REALLY want a dedicated mailing list for my ONAP project section and then open a ticket support.linuxfoundation.org which includes all of the requested info and an explanation of your current list and what additional help you are requesting.