[mpas-developers] /home/subversion/mpas/model revision 146

Xylar S. Asay-Davis xylar at lanl.gov
Thu Mar 18 14:49:45 MDT 2010


The sentence:
"Development code will not be distributed outside the development group in
any form with the consent and knowledge of the developers committee and
the oversight committee"
should almost certainly read:
"Development code will not be distributed outside the development group in
any form *without* the consent and knowledge of the developers committee
and the oversight committee."

> <p><b>ringler at lanl.gov</b> 2010-03-18 12:17:04 -0600 (Thu, 18 Mar
> 2010)</p><p><br>
> Document summarizing how the MPAS project will be managed<br>
> between NCAR and LANL.<br>
> </p><hr noshade><pre><font color="gray">Added:
> trunk/documents/oversight.txt
> ===================================================================
> --- trunk/documents/oversight.txt	                        (rev 0)
> +++ trunk/documents/oversight.txt	2010-03-18 18:17:04 UTC (rev 146)
> @@ -0,0 +1,31 @@
> +Project Management for the Model for Prediction Across Scales (MPAS)
> +
> +February 2, 2010
> +
> +
> +The MPAS project is jointly managed by the primary development set
> partners. The primary development partners currently are the Mesoscale and
> Microscale Meteorological Division (MMM) at the National Center for
> Atmospheric Research and the Climate, Ocean and Sea Ice Modeling (COSIM)
> at Los Alamos National Laboratory.
> +
> +Each development partner has someone designated as MPAS project leader.
> These individuals collectively form the oversight committee for MPAS.  The
> co-chairs of the oversight committee are the leads of the primary
> development partners.  The oversight committee addresses, as needed,
> issues related to project management, project direction, software releases
> and the addition of new partners. The oversight committee will strive to
> manage by consensus, and the co-chairs will together make decisions where
> consensus is not possible.
> +
> +Code development will be based on Subver
>  sion (SVN) within a repository located at svn-mpas-model.cgd.ucar.edu
> (the development repository).   The repository is controlled by a
> developersÕ committee.  This committee is composed of active developers,
> that is, developers who have read-write access to the development
> repository.  Chair(s) of the developersÕ committee are appointed by the
> oversight committee.  Developer access will be granted by the development
> committee, in consultation with the oversight committee, on a
> case-by-case basis. Development code will not be distributed outside the
> development group in any form with the consent and knowledge of the
> developers committee and the oversight committee.
> +
> +Code releases to the general community will be distributed through a
> repository maintained at SourceForge (http://mpas.sourceforge.net/ ), and
> the SourceForge site will serve as the conduit through which MPAS
> interacts with the outside world. The primary development partners will
> maintain a wide variety of cont
>  ent at the SourceForge site that might include a web site, documents,
> source code for download, data files, wikis, bug tracking tools, etc. The
> Open Source licensing agreements will be determined at a later date.
> +
> +This document will be updated as needed by the oversight committee.
> +
> +Oversight Committee as of February 1, 2010:
> +MMM NCAR (co-chair): Bill Skamarock, skamaroc at ucar.edu, 303-497-8161
> +COSIM LANL (co-chair): Todd Ringler, ringler at lanl.gov, 505-667-7744
> +
> +This document is maintained at
> +svn-mpas-model.cgd.ucar.edu/trunk/documents/oversight.txt
> +
> +
> +
> +
> +
> +
> +
> +
> +
> +
> </font>
> </pre>
> _______________________________________________
> mpas-developers mailing list
> mpas-developers at mailman.ucar.edu
> http://mailman.ucar.edu/mailman/listinfo/mpas-developers
>


***********************
Xylar S. Asay-Davis
E-mail: xylar at lanl.gov
Phone: (505) 606-0025
Fax: (505) 665-2659
CNLS, MS B258
Los Alamos National Laboratory
Los Alamos, NM 87545
***********************



More information about the mpas-developers mailing list