[Ncep.list.nems.announce] NEMS repo or disk access issues?
Samuel Trahan - NOAA Affiliate
samuel.trahan at noaa.gov
Fri May 5 19:37:07 UTC 2017
Yes, just their branch. However, all apps are in the nems project, so they
have the same access permissions. If they can write to their app branch,
then they can write to everything in the projects/nems directory. They
could even delete the entire apps directory. (Please don't.)
On Fri, May 5, 2017 at 3:17 PM, Jun Wang - NOAA Affiliate <jun.wang at noaa.gov
> For item 2), I assume you are asking people to test if they are able to
> commit to their app BRANCH, not trunk, right? I know NEMS allows developers
> to commit to their app's trunk, but I would like to ask developers to avoid
> testing their access to NEMSfv3gfs trunk as we are preparing fv3 v0 release
> which will go public on May 15. Thanks.
> On Fri, May 5, 2017 at 3:00 PM, Samuel Trahan - NOAA Affiliate <
> samuel.trahan at noaa.gov> wrote:
>> NEMS developers,
>> We are occasionally receiving emails from users that cannot access
>> repositories or disk areas they need for NEMS development. Rather than
>> flooding NCO and RDHPCS with tickets, we would like to gather all
>> information and send it in one bulk request.
>> Do NOT respond to this email. Instead, email Samuel.Trahan at noaa.gov and
>> Mark.Iredell at noaa.gov with the subject line "NEMS access"
>> Please test your access to all apps.
>> 1. Are you able to check out ("svn checkout") your app, including all
>> 2. Are you able to commit changes ("svn commit") to your app?
>> 3. Are you able to commit changes ("svn commit") to the components of
>> your app?
>> 4. Is your application development team able to write to your
>> application's compset input areas?
>> Sam Trahan
>> Ncep.list.nems.announce mailing list
>> Ncep.list.nems.announce at lstsrv.ncep.noaa.gov
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ncep.list.nems.announce