Now that netloc has rolled into hwloc, I think it is safe to kill the
netloc lists.

mtt-devel-core and mtt-annouce should be kept. They probably need to be
cleaned. But the hope is that we release MTT at some point in the near-ish
future.

On Mon, Jul 18, 2016 at 10:20 AM, Jeff Squyres (jsquyres) <
jsquy...@cisco.com> wrote:

> We're progressing in the migration plans.  Next up is the mailing lists.
> The first step is to determine which lists to migrate, and which to delete
> (because they're now no longer necessary, anyway).
>
> These are the lists we plan to keep/migrate, and the lists we plan to
> delete/not migrate -- if you know of any list we mis-classified, please let
> us know ASAP.  We plan to start this migration as early as Tuesday
> afternoon.
>
> Lists that we want to keep:
> • Admin
> • Announce
> • Devel
> • Devel-core
> • Hwloc-announce
> • Hwloc-commits -- gitdub sends to this list; KEEP
> • Hwloc-devel
> • Hwloc-users
> • Mirrors
> • Mtt-commits
> • Mtt-devel
> • Mtt-results -- daily MTT results sent to this list; KEEP
> • Mtt-users
> • Ompi-commits -- gitdub sends to this list; KEEP
> • Users
>
> Lists that we know that we do not want to migrate:
> • Bugs -- Trac used to send to this list; it’s now moot and can be killed.
> • Docs -- kill?
> • mtt-announce -- kill?
> • mtt-devel-core -- kill?
> • Netloc-announce -- kill?
> • Netloc-bugs -- kill?
> • Netloc-commits -- kill?
> • Netloc-devel -- kill?
> • Netloc-users -- kill?
> • ompi-user-docs-bugs -- kill?
> • ompi-user-docs-svn -- kill?
> • otpo-bugs -- kill?
> • otpo-svn -- kill?
> • otpo-users -- kill?
> • Any glassbottom list
> • Any orcm list
> • Any pmix list
>
> --
> Jeff Squyres
> jsquy...@cisco.com
> For corporate legal information go to:
> http://www.cisco.com/web/about/doing_business/legal/cri/
>
> _______________________________________________
> devel mailing list
> de...@open-mpi.org
> Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post:
> http://www.open-mpi.org/community/lists/devel/2016/07/19231.php

Reply via email to