MailingLists

There are several public and private mailing lists used by the Open MPI development team.

Public lists

The public lists are open to all, but every list requires a subscription in order to be able to post (some only allow restricted posting, such as the announcement list). See http://www.open-mpi.org/community/lists/ompi.php for more detail on the public lists:

• Announcements: For announcements of new releases of Open MPI
• User discussions: For user-level questions / discussions about Open MPI
• Development discussions: For developer discussions about Open MPI
• Commits: Mail is sent to this list for every push to Github in the following repositories:
  • ompi
  • ompi-release
  • ompi-tests
  • ompi-www
  • ompi-docs
• Open MPI web site mirrors: Low volume mailing list for owners of Open MPI web site mirrors
• Nightly tarball creation results: Mail is sent to this list every night for each Open MPI nightly snapshot tarball that is created
• MTT Open MPI testing results: Mail is sent to this list Mon-Thu evenings and Tue-Fri containing the 12 and 24 hour daily Open MPI regression testing results; mail is sent on Monday morning for the weekend Open MPI regression testing results

Sub-projects:

• MTT announcements: For announcements of new releases of the MPI Testing Tool (MTT)

• MTT users: For user-level questions / discussions about MTT

• MTT devel: For developer discussions about MTT

• MTT commits: Mail is sent to this list for every push to Github.

• Hwloc announcements: For announcements of new releases of the Hardware Locality (hwloc)

• Hwloc users: For user-level questions / discussions about Hwloc

• Hwloc devel: For developer discussions about Hwloc

• Hwloc commits: Mail is sent to this list for every push to Github.

• PMIx announcements: For announcements of new releases of the PMIx library

• PMIx users: For user-level questions / discussions about PMIx

• PMIx devel: For developer discussions about PMIx

• PMIx commits: Mail is sent to this list for every push to Github.

Private lists

Why are there private lists in an open source project? There are a few reasons:

1. The administrative group's duties include, among other things, resolving conflicts. These conversations are not intended to be public.
2. Since the core development group contains several academics who rely on the "publish or perish" philosophy of competitive research, some discussions must be kept private until conference/journal papers can be written and published.
3. Non-public information needs to be distributed among the core group that would not be good to be "Google-able", such as teleconference phone numbers/codes, trade show planning, etc.

Here are the private lists (admission to these lists is restricted):

• Administrative: The administrative steering group for Open MPI (see Admistrative-rules)
• Development core: Development group core