Skip to content

MailingLists

Jump to bottom
Jeff Squyres edited this page Sep 2, 2014 · 8 revisions

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
  • Bug tracking activity: Mail is sent to this list by the bug tracking system for every activity that happens on a ticket
  • Public SVN commits: Mail is sent to this list for every public SVN commit, but the diff of the change is not included if it is over 40k
  • Public SVN commits (full): Mail is sent to this list for every public SVN commit; the diff of the change is always included in the mail, regardless of size
  • 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:

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
  • Private SVN commits: Private SVN commits, including the OMPI SVN /tmp branches and the OMPI documents tree (for academic / not-yet-published papers), but the diff of the change is not included if it is over 40k
  • Private SVN commits (full): Private SVN commits, including the OMPI SVN /tmp branches and the OMPI documents tree (for academic / not-yet-published papers); the diff of the change is always included in the mail, regardless of size
Clone this wiki locally