...
- Status Quo - keep all the existing mailing list.
- Let all managed projects continue to have their own mailing lists (one list per project - only the xyz-dev list). A self managed project can request to have it's mailing list continued - subject to TSC approval.
- Each of the projects will be mapped to one of the categories (Kernel, App, Service, Protocol, etc.) as per the project's category in https://wiki-archive.opendaylight.org/view/Project_list.
- Each of the projects is mapped to be either kernel-dev (all kernel Projects) or app-dev (all Support, App, and Protocol Projects w/ some exceptions).
| Vote | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
Option 1 -: Status Quo Option 2 -: Managed Projects + some self managed projects Option 3 -: Map to the project category as per https://wiki.opendaylight.org/view/Project_list. Option 4: - Map to either kernel-dev (all kernel Projects) or app-dev (all Support, App, and Protocol Projects w/ some exceptions). |
Common to all options:
- Common mailing lists like discuss, tsc, release, dev, etc. remain untouched (no changes).
- Documentation, Marketing, Security, Discuss, Release, TSC, Dev and Integration lists would remain.
- Mailing lists which will be retired will be mapped to some common mailing list. So people will be able to continue to post messages to the list, but the message will be instead mapped to the common mapped mailing list.
...
- There are probably 100+ project mailings lists including xyz-dev, xyz-users, etc. for some projects.
- The huge number of mailing lists mean that there is no traffic other than spam on some of these mailing lists and yet it confuses newcomers which mailing lists to ask questions on.
- Administration (message approval, spam/phishing email rejection) becomes hard for so many mailing lists.
Options:
...
- mailing
...
- lists
...
- .