[Ncep.list.nems.announce] Identifying code managers of apps

Sarah Lu - NOAA Affiliate sarah.lu at noaa.gov
Fri Dec 9 14:31:51 UTC 2016

Samuel --

Could you please clarify how NGAC  (or NEMS-aerosols; NEMS-chem) will be

Also, the gocart source code has been moved to nceplibs/chem/trunk.      I
can't create a branch until nceplibs so I also like to know where these
branches should be managed.  Thanks. -- Sarah

On Fri, Dec 9, 2016 at 9:18 AM, Samuel Trahan - NOAA Affiliate <
samuel.trahan at noaa.gov> wrote:

> Hello all,
> The WAM app is not being retired yet.  After discussion with a WAM
> developer, we've determined that the WAM development may need a separate
> app to support WAM development that is independent of the GSM trunk.  We're
> going to meet with the WAM developers in about two weeks to discuss whether
> a WAM app or a NEMSGSM branch would be a better approach.  Until then, we
> will retain the WAM app as a placeholder for future development.  Note that
> having a separate app does not mean that the work will never be merged
> back.  It just makes it simpler for WAM to have different branches or tags
> for NEMS testing.
> Sincerely,
> Sam Trahan
> On Thu, Dec 8, 2016 at 5:12 PM, Samuel Trahan - NOAA Affiliate <
> samuel.trahan at noaa.gov> wrote:
>> Hello all,
>> We've made progress on identifying code managers and old apps.  Below is
>> a list of actions I have taken, or will soon take, with approximate dates.
>> Also, the "apps/obsolete" directory is now "apps/unsupported" to clarify
>> its purpose.
>> Full information is in this living document which requires a NOAA Google
>> account to access:
>> https://docs.google.com/a/noaa.gov/spreadsheets/d/17OFFtmPyh
>> SgBAAiTOqCPjBEPSXSWxcglMc5zc3sohXY/edit?usp=sharing
>> Actions I have taken or will soon take:
>> HYCOM-Ice is renamed to HYCOM-GSM-CICE
>> Coupled-FIM move to apps/unsupported/ directory
>> WAM move to apps/unsupported/ directory.  WAM work will happen in NEMSGSM
>> after NEMSLegacy is retired and NEMSLegacy until then.
>> NEMSLegacy retired.  It will remain in the nems/apps level for a few
>> months longer so that any externals pointing to it without a revision
>> number will not have to be updated.  If you use a revision number when
>> pointing to NEMSLegacy, then you will not be impacted by its move.
>> Sincerely,
>> Sam Trahan
>> On Thu, Dec 8, 2016 at 10:06 AM, Samuel Trahan - NOAA Affiliate <
>> samuel.trahan at noaa.gov> wrote:
>>> Hi all,
>>> As per a discussion of PIs, all NEMS apps (nems/apps directory) must
>>> have code managers.  You may get emails from Mark Iredell, myself, or one
>>> of your bosses asking who a code manager is for a specific app.  Once this
>>> information is gathered for all apps and all compontents, it will be posted
>>> in a sensible location.
>>> Apps that have no code manager and have not been updated in several
>>> months will be moved to a new nems/apps/obsolete directory.  People will
>>> still be able to view and use them from the new location, but it will be
>>> clear to anyone using it that the app is no longer maintained.
>>> That new "obsolete" directory, presently empty, is here:
>>> https://svnemc.ncep.noaa.gov/projects/nems/apps/obsolete
>>> Sincerely,
>>> Sam Trahan
> _______________________________________________
> Ncep.list.nems.announce mailing list
> Ncep.list.nems.announce at lstsrv.ncep.noaa.gov
> https://www.lstsrv.ncep.noaa.gov/mailman/listinfo/ncep.list.nems.announce
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://www.lstsrv.ncep.noaa.gov/pipermail/ncep.list.nems.announce/attachments/20161209/1089d526/attachment.html 

More information about the Ncep.list.nems.announce mailing list