...
- Review software vocabulary for Software Grid (jmhunt & atticus)
- printed writeup of proposed vocabulary was circulated by Jon at the meeting. That text is posted off the main CSS wiki page at .
- we reminded ourselves of the IS&T new web site look-and-feel, into which this download page would fit.
See http://cspace.mit.edu - Questions that came up:
- Should we devote web page space to the "Support" column on the web page (the group says Yes)
- How do we indicate that a product is on the way out? How do we convey the current lifecycle discussion about why we're at the version we're at and you should know about it. (Maybe Hermes.)
- What about the "More details..." link -- put all the useful detailed info there. Include the product lifecycle info, accessibility compliance, download size, etc.
- How do we decided to provide, say, Brio, instead of some competitor tool -- who is "we" and "when did they know it?" Sidebar conversation about the internal team-driven politics of major software acquisition.
- Call for cost-cutting/cost-saving measures (tjm & all)
- Proposal for a 30-minute agenda item -- how to link when a product is decided upon to the process of creating training and documentation and product front doors and so on. Each is different, but what is the visible triggering event for the create-support-for-this process. Where in the organization are these facts articulated? Agreed on as a topic for a future meeting.
...