AG3 Cycle-1 Plan Outline

Launch Beta Programme

C1- : Announce Beta Programme

DONE 28 Jan 2008 announcement of beta test programme - see 28 Jan 2008 news item

C1- : Recruit Beta testers

• Ensure they understand the role
• Encourage feedback with fast responses
• Incentive

DONE 28 Jan 2008: email defining role sent to all beta testers. plus description of feedback areas contained on the beta tester website.

Purpose

• Polish our product especially VODesktop
• Find and eliminate obscure and hard to locate bugs

C1- : Science Doumentation

• Number One Priority
• Full support for writers

Science documentation updated to support the 28 Jan 2008 beta programme launch.

C1- : Marketing

• Materials
• Events
• “Press releases”

C1- : Announcements

• NAM
• Post NAM?
• Follow-up?

Alliances

C1- : Data Centre integration

• Consortium members at least
• Links and references from home page
• More if possible (on-going effort)

C1- : Strategic

• Aladin (crucial new version doesn't leave us out)
• Others? DS9 (again)?

C1- : Outreach

• Seminars
• Conferences
• Road-shows
• Workshops

Prepare infrastructure

On-line:

C1- : Web sites

C1- : Help Desk

• SLAs
• For our users
• What we expected the Data Centres to aim for

C1- : Downloads

• Binaries / sources / etc

C1- : Packaging

Deployments

C1- : Central Services

• Registry, VOSpace, Community
• AG managed

C1- : Core Services

• Consortium member holdings
• Deploy ourselves if necessary

C1- : Applications

• Critical
• Useful

C1- : Deployment Bundles

• By site type
• Identify
• “Package”

Dependencies

C1- : Identify

• Firewall issues
• Caching / Ports / etc
• Software versions
• Define supported platforms (including versions!)
• Publish details

C1- : Eliminate (preferably)

C1- : Work around (as a minimum)

Operations for real

C1- : Help Desk

• Deliver support
• Work to rota
• Review and augment
  • Statistics (but not too many)
  • Symptom/Solution Info incl. FAQ

Operations for real

C1- : Central / Core Services

• Administer
• Review * Capacity * Performance * Reliability
• Document best practise

C1- : Technical Documentation

• Admin (vital)
• Programmer (later)

Complete engineering

Key developments outstanding

C1- : VOSpace

C1- : Complete move to Registry V1.0

C1- : AR changes to support above

C1- : Bug Fixing!

Robustness and Performance

C1- : Testing

• Design
• Implement
• Automate

C1- : Profiling / tuning

C1- : Purpose:

• Product confidence
• Capacity Planning

Developments

C1- : Planned improvements

C1- : Track standards (IVOA and Industry)

C1- : Tools support

• Improve
• Expand
• Integrate

-- KeithNoddle - 14 Dec 2007