March 2001


Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Michael Snyder <[log in to unmask]>
Reply To:
Departmental Technology Coordinators <[log in to unmask]>
Thu, 1 Mar 2001 09:55:30 -0500
text/plain (7 kB) , mrsnyder.vcf (7 kB)
Bravo for your good work on the standards committee! You're really cooking! I
like the side by side dog and pony show idea. Where and when would this happen
to best effect? Can we get going on evaluating the polling software right
away? I'll connect with Doug Varney. keep up the good work.
Michael Snyder

Geoffrey Duke wrote:

> [I took Lyman's notes, and merged them with my own notes and the agenda.
> Please respond with any comments, corrections, additions, questions...
> --Geoff]
> Notes from the IT Standards Group meeting:
> IT Network Standards Workgroup Meeting
>     Friday, February 23, 2001
>     10:00 am to 11:30 am
>     Waterman 238 Conference room
> Present: Doug Varney, Alan Howard, Nichole Chittenden, Geoff Duke, Andy
> Gingras, Lyman Ross, Dean Williams
> Lyman graciously volunteered to take notes.
> Goals:
> o Discuss progress on current items
> o Establish framework for the April's Annual Bulletin
> o Prioritize the list of pending items
> o Feedback about standards group functioning
> We began by discussing the committee's annual April Bulletin.
> 1. Exercise
>    We each responded on paper to the question "What three things should
>    the stds group's annual bulletin include?" Results used later.
> 2. Progress updates on current standards efforts
>  - Antivirus products
>    owner(s): Greg MacKinnon and Lynne Meeks
>    <>
>    Although Greg and Lynne were unable to attend, the information on the
>    web site is current. This process will not be concluded in time for
>    the results to be included in the Bulletin
>    Question posed: How many people are participating in the open
>    evaluations? Do we have any way of knowing?
>  - Web-based survey tools
>    owner(s): Doug Varney
>    <>
>    Doug reported on Web-based survey tools.  He anticipates that such
>    software would be of use to a small group of researchers making use of
>    survey instruments and a larger group of people, departments and
>    offices needing a tool for data gathering.  One example is the
>    Learning Coop, which surveys students who have received tutoring.
>    There are three products worth investigating: Perseus, Survey Said
>    and Qustion Mark. How many do we want to evaluate? 2? 3?
>    The next step will be to establish a timeline for choosing a product
>    and then to enlist a group of testers.  We will be unable to do this
>    before the April bulletin but should announce that we're working on it
>    and aim to make a recommendation by the start of the fall semester.
>  - Drive imaging products
>    owner(s): Geoffrey Duke
>    <>
>    Geoff reported on the imaging software.  For the near term the
>    currently licensed version of Ghost will meet most peoples needs.
>    We won't upgrade as the cost is prohibitive including a per machine
>    charge.
>  - Wireless Planning Task Force
>    owner(s): Alan Howard
>    Alan Howard reported on the committee he's chairing on wireless
>    networking.  That group is interested in locating the interested
>    groups on campus, airing their concerns and finding out what has
>    actually been deployed on campus.
>    He reported that there is a pilot project in the Bailey/Howe
>    Library's McCrorey Gallery.  Hardware is in place, however, the
>    project won't be advertised until documentation and policies have been
>    drafted.
>    Nichole reported that the business school may add wireless to its
>    required student computer configuration.
>    Alan hopes that the standards committee will recommend a standard card.
>    This may be as simple as accepting the three that are currently being
>    used with Dell and Apple: Airnet, Airport and Orinoco.  Andy added
>    that these are the only cards the Depot has sold.  We also need to
>    think about what OS's we'll support.  Geoff noted that Phil Plourde has
>    already done a lot of work on this.
>    Alan would also like to see us adopt a 128 bit encryption standard for
>    wireless devices.
>    Geoff suggested creating a home for information related to the
>    Wireless planning process within the standards group's projects
>    website, and offered the standards listserv as a vehicle for online
>    discussion. Alan said that these were both good ideas.
> 2. Standards Group Annual Bulletin
>  - Results of Exercise
>    'What three things should the Stds Group Annual Bulletin include?"
>    1. Sunset old Oses
>       Personal productivity software standards/ OS standards
>       What do the standards do for me? (support, $ incentives, etc.) *
>       Recommended/supported desktop and laptop systems
>       WWW data gathering process/tool
>    2. Email client software
>       Wireless standards
>       How will the standards impact me? *
>       Recommended/supported software suites
>       WWWW site building tools
>    3. Web browser support
>       Support standards
>       How were the standards developed? *
>       Suggestions for future hardware and software support *
>       Access to UVM institutional data
>  - Discussion
>    The group then discussed what should be in the upcoming bulletin.
>    Ideas included phasing out legacy OSes, future hardware/software trends
>    and informing people about the standards process.
>    what is the relationship btw standards and support? The web team is
>    (as of when?) recommending Dreamweaver. Are they providing support
>    for this tool? If it's a standard, should people expect to get
>    training via Training & Development, support from CIT?
>    Discussed how broadly the bulletin needs to be disseminated.
>    Include with system purchases our software standards.
>  - What items should be included in this bulletin?
>  - What does the bulletin need to say?
>  - Finalize outline, list of items to be included in bulletin
>    Andy suggested establishing a baseline of our standards. Name the
>    general recommendations: Dell Optiplex, Latitude ; Apple iMac, G3,
>    G4, Powerbook; HP Network printers;
>    Proposed phase-out of legacy OSes (DOS, Win3.x, Mac OS 7, Win 95)
>    Proposed phase-out of legacy office suites (Office  4, Office 95)
>    Recommended Office suites. Include information about purchasing under
>    the MS Select Agreement.
>    Andy suggested that we should remind people of the hardware standards
>    currently in place as well as the various licensing programs for
>    software.  He noted that people are purchasing MS Office at the
>    bookstore and paying twice what they would through the campus select
>    program.
>    Nicole added mention of the MS Campus Agreement's renewal--opportunity
>    for other departments to join.
>    Current topics, to be concluded by end of summer:
>    - antivirus tool
>    - web survey/data gathering tool
>    On the Horizon;
>    What's coming out over the next year?
>    What directions are things moving in?
>    The group then discussed other priorities.
>    Geoff proposed that we concentrate on web browsers and email programs.
>    The system configuration for students' Back-to-School bundles need to
>    be determined by June. Browser, Email clients are primary.
>    Other ideas: hand-held devices. Palm? HandSpring Visor? PocketPC?
>    It was agreed that Geoff should draft the April bulletin and ask for
>    comments by email.
> 3. Other business?
>    Many thanks to Greg MacKinnon for his work on the IT Standards
>    web site and documentation.
>  - Is there anyone interested in helping with this task?
>  - Any comments or suggestions on the way the standards group
>    is functioning?
>         = Should we be meeting more often?
>         = Is there anything we should do differently?
>    Geoff suggested that the Standards group may want to provide
>    side-by-side demonstrations of some products. Have a dog-and-pony
>    show where people who don't have time to install and explore every
>    product have an opportunity to see the choices and have the chance
>    to ask questions (maybe even get interested enough to test something
>    on their own).
> We ended on time.