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

General List
The  openstack@lists.openstack.org  general mailing list is the most active list. You should join this list when you start to know OpenStack. Request for help and community announcements are allowed on this list. Its rate can be up to 100 messages per day.

You should follow the MailingListEtiquette guidelines for posting to this list.


 * Subscribe at http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

The list is archived in several places:


 * http://openstack.markmail.org/
 * http://www.mail-archive.com/openstack@lists.launchpad.net/
 * http://lists.openstack.org/pipermail/openstack/

Note: this general list was previously set up at lists.launchpad.net.

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/

Future Development
This high-traffic list for the developers of OpenStack to discuss development issues and roadmap. It is focused on the next release of OpenStack: you should post on this list if you are a contributor to OpenStack or are very familiar with OpenStack development and want to discuss very precise topics, contribution ideas and similar. Do not ask support requests on this list.


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

Note that this is a single development list for all OpenStack projects. You can use Mailman Topics (on the [Subscribe] page) to help with sorting and filtering messages. Please read the [recent] [threads] to see why suggestions to split the list by projects might be met with strong resistance. You can use Topics to filter the list and have nearly the same effect if you only want to see messages for specific projects.


 * Short guide to using topics: http://lists.openstack.org/pipermail/openstack-dev/2013-November/019233.html
 * Recent summary of why: http://lists.openstack.org/pipermail/openstack-dev/2013-December/021281.html
 * Summary of Stackforge list discussions: http://lists.openstack.org/pipermail/openstack-dev/2013-November/019295.html

Operators
This is a specific list for existing OpenStack cloud operators. It is a forum to exchange best practices around operating an OpenStack installation at scale. You can ask for support on this list.


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

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 git://git.openstack.org/openstack-infra/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.