AGENDA
1. Minimum Spec Review for WISE 3.0
Let's review and confirm the currently expected minimum spec. Also need to discuss the recommended browsers on Mac and PC. Are we dropping IE for the Mac?
Results: We'll focus on supporting Firefox 2.0 and Safari 2.0-3.0 for Mac, and IE 7.0, Firefox 2.0, Safari 3.0 for the PC.
2. Overview of TELS Portal & PAS Portal Status
Hiroki will give overview of TELS Portal & PAS Portal status. Accomplishments, next week's goals. Discuss important dates and everybody's role.
- 0.9 Beta for Portal is planned for next Wednesday.
- We'll ask the Concord folks to help starting testing next Wednesday.
- August 7th Research Group we'll show them the Beta and get them involved in testing using the [testing scripts. |http://www.telscenter.org/confluence/display/TCS/Test+Scripts+07.25.07]
- Matt & Tony will talk about finding an existing Help System template based on Wiki technology.
2.1 Trouble Ticket System
We need a Trouble Ticket System (some way for users to contact us about bugs, questions, opinions about WISE). This might not be needed for the Fall, but will be needed for January 2008. We'd like to have the first version ready for the Fall so people can test it.
Discuss how the current WISE 2.0 Trouble Ticket system works and how WISE 3.0 Trouble Ticket should work.
- Overall plan is to SIMPLIFY the W2 trouble ticket system for W3. No database back end. More user friendly.
- VERSION 1 : Tony will set up a GoogleGroup account to which we can auto-email 1) General WISE Trouble Tickets OR 2) Project-Specific Trouble Tickets. We'll work out who has access to the Group/Subgroups later.
3. Overview of Authoring Tool
Doug will give an update on testing of the authoring tool this week. Tony will give an latest status of Author Tool plus attack plan.
- Major underlying technology in SAIL core are coming from Turadg and company. Implementing "OTrunk" with Concord team. This has major effect on data structure for curnits (projects).
- Implications: Tony will focus on implementing the EDITORS for each Step Type in the weeks ahead. Scott will focus on implementing OTrunk in the core.
4. 5 Point Weekly Plan
Matt will discuss a plan to start having all team members offer a "5 Point Weekly Plan" that we'll use for improved visibility and support across the team, plus an increased focus on milestones that are achieveable on a weekly basis. Matt will give an overview of the plan
Results: x
5. CNAME for test portal
from turadg:
"something at .berkeley.edu takes a request to CNS. It's not too
difficult, but it's a little slow.
I'd recommend using the wisetest.org domain. Hiroki can set up a
CNAME record to the Toronto site."
6. Light, Noise, Heat attic