Mailing Lists

'Help needed': If you want to help administer our mailman installation please contact communitymngr@openstack.org

How Do I Subscribe To A Mailing List?
Welcome! If you have never subscribed to a mailing list before, here are some suggestions.
 * click the link for the mailing list to which you wish to subscribe
 * you will be taken to a page for that mailing list, there will be instructions about how to subscribe
 * read the instructions, you will probably be asked for an email address you wish to use to subscribe to the mailing list, enter your email address
 * you will receive an email to the email address you entered asking you to confirm your subscription, follow the instructions in the email to confirm your subscription
 * Question: "What do I do if my subscription confirmation has expired?"
 * Answer: Subscribe again
 * Read the Mailing List Etiquette wikipage: https://wiki.openstack.org/wiki/MailingListEtiquette

Announcements
Announcements about the OpenStack project like product release information and security advisories. This is a low-traffic, read-only list.


 * Subscribe: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-announce
 * Archives: http://lists.openstack.org/pipermail/openstack-announce/

Users, Operators and Future Development
https://docs.openstack.org/project-team-guide/open-community.html#mailing-lists

Foundation
Hosts the community discussion around the OpenStack Foundation & Board.


 * Subscribe: http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation
 * Archives: http://lists.openstack.org/pipermail/foundation/

Interop Working Group

 * http://lists.openstack.org/cgi-bin/mailman/listinfo/interop-wg
 * Archives: http://lists.openstack.org/pipermail/interop-wg/

The following defcore-committee mailing list was shut down on Friday December 9, 2016, it was replaced by new mail list interop-wg, but you can review the history mail in archives.


 * http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee
 * Archives: http://lists.openstack.org/pipermail/defcore-committee/

Community
Discussions about the OpenStack International User Groups Community.The OpenStack International User Groups Community team is the main contact point for anybody running a local OpenStack User Group. Add your group to OpenStackUsersGroup.


 * Subscribe: http://lists.openstack.org/cgi-bin/mailman/listinfo/community
 * Archives: http://lists.openstack.org/pipermail/community/

Internationalisation and Translation
Internationalisation and translation discussions. If you are interested in translating OpenStack, adding a new language to the translation system, asking questions about how to modify your code to work with i18n, you should join this low-traffic list.


 * Subscribe: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
 * Archives: http://lists.openstack.org/pipermail/openstack-i18n/

Other lists
Lots of other lists are available. See the complete list.

How to request your own list
It is possible to request a mailing list in a languages different than English. Basically to create a new mailing list you need to propose a change to the puppet configuration. Here is how to do it:


 * 1) clone the system-config repository

$ git clone https://opendev.org/opendev/system-config/


 * 1) follow the [development workflow] and [create a branch] after making sure you have the latest upstream changes:

$ git remote update $ git checkout master $ git pull origin master

then

$ git checkout -b VIETNAMESE #for example


 * 1) edit the file modules/openstack_project/manifests/lists.pp adding something along the lines:

maillist { 'openstack-LANGUAGE_ISO_2_LETTER_EXTENSION': ensure     => present, admin      => 'YOUR EMAIL ADDRESS', password   => $listpassword, description => 'DESCRIPTION OF THE LIST IN VIETNAMESE', webserver  => $listdomain, mailserver => $listdomain, }


 * 1) make sure that you use spaces, not tabs; and make sure that the => are aligned in the editor


 * 1) commit the changes

$ git commit -a $ git review

Send a message to the Community mailing list with the review URL and somebody will review your request. If you're not already familiar with git review and prefer not to learn it, ask on the Community mailing list to create one list for you. Let me know what you prefer.