Unidata Users Committee Actions/Resolutions - 13-14 March 1997
ACTION 1:
Reacting to a discussion about keeping the community informed, it was agreed that
Unidata would continue sending email announcements to the community about upcoming
UserComm meetings, including topics for discussion, prior to each UserComm meeting.
ACTION 2:
Fulker was asked to send a community announcement referencing the URL link to
Unidata's five-year proposal, after it has been finalized and sent to the NSF.
ACTION 3:
Unidata should seek access to the FSL-NOAAport archived data using LDM technologies.
ACTION 4:
Unidata should follow the progress of the EOSDIS and any parallel development
taking place for client-server development using netCDF. EOSDIS DAAC
in-a-box should also be tracked.
ACTION 5:
Sandra Nilsson should contact WSI to check on an amendment to the contract to
use NIDS after four hours, rather than the 48 hours currently required.
ACTION 6:
Unidata should clarify the status of the Space Science & Engineering Center (SSEC)
plans for OS/2, including specific dates of sunset plans for OS/2, if they exist.
RESOLUTION to Unidata Policy Committee
The Users Committee requests that the Policy Committee reconsider its recommendation
that the UPC develop a plan for the sunset of OS/2 by summer 1998, in favor of
a comprehensive transition plan that will allow the UPC and the Unidata user community
to achieve the goal of platform independence by 2003. The development of this
plan should solicit input and discussion from all segments of the user community
and should address their diverse needs.
ACTION 7:
Fulker was asked to forward the OS/2 Resolution to the Policy Committee as soon
as possible for their response.
ACTION 8:
To provide cross fertilization, the Unidata UserComm would like to have a representative
as liaison at the Policy group meetings for GREATT, and would like a GREATT Policy
group representative to be a liaison at the Unidata UserComm meetings.
ACTION 9:
The UPC will create an email list for Linux users and track the community
interest using Linux and Solaris x86.
ACTION 10:
Unidata should add a link to a page of resources to be used for the workshop.
ACTION 11:
Mike Schmidt will check the GIS software packaging and licensing issue.
ACTION 12:
Unidata will survey sites to find out which ones are losing the 4km data. In addition
to this issue, Unidata will query the sites about adding the statistics to their
IDD site information to make tracking easier at the UPC.
Linda Miller lmiller@unidata.ucar.edu
Questions or comments can be sent to lmiller@unidata.ucar.edu
Go to the Unidata Homepage.