Thanks to Jon Hunt for taking notes during the meeting. -Oliver

• Spend next few months figuring out what we are going to do
  • Combination of brand new and existing work
  • Figure out unified structure
  • Getting ready for changes in Athena, printing, energy, using students
  • We should be plenty busy!
• Athena 10 going live this summer.
• Jon Reed does a lot of Athena stuff, training Athena consultants; work with students; lot of work with DebAthena
• Ranjani - DCAD web and DB consultant - very project based, has transitioned all of projects; worked at Tufts in academic technology
• Brian making it up here about every other Monday
• Student staff - FSX does have charter to strongly engage students and should have lots of students in the group
  • Trying to figure out how much technical student staff should stay with Service Desk and...
  • What kind of student work / support should go with this group (FSX)
    Team Logistics:
• Wiki space - dumping bucket for everything we are working on - FSX - most of it is publicly visible
• This group is small
  • 9 people doesn't scale up to do hands on technical support for all faculty/students
  • That can be a difficult conversation
  • If we're open about projects & responsibilities, then we can share with the clients and explain the limitations
• Take a look at FSX wiki space; populate with projects working on
• Will be working with HR with Role and Position Descriptions
  • Very different than job description
  • Detailed list of things being worked on and responsibility
  • Aim for drafts done in next 3 weeks to a month
  • Keep in the wiki
• Calendar page for outages - list them in the wiki until everyone is on Exchange (or whatever)
• Team mailing list: ist-fsx@mit.edu (fsx@mit.edu is an alias)
• Need to consolidate various RT queues and mailing lists into a simpler way to contact and interact with this group
• One on One meetings
  • Setup with Oliver on biweekly schedule
  • Sounds like everyone is on TechTime for now for meeting scheduling
• Regular team meetings
  • Will aim for one hour weekly
  • Cancel if no agenda
• Would like to create profile pages for each of us
  • Really like the MIT medical version of that
  • Nice way to communicate a group of professionals out to the communities
• Not everyone uses Jabber

On the horizon:

• Fall Readiness
• Cluster refresh this summer bigger than normal due to replacement of Suns
• Websites consolidation/look and feel changes for go live July 8
• Task Forces recommendations - IT @ MIT and Educational Technology expected in the October timeframe - there will be some recommendations that we will need to move forward on around Athena clusters and printing
• Come up with standard set of questions when we interact with Faculty on a certain issue, we can follow up. Have a place to collect that information.
• We'll need to come up with metrics to know if we have achieved team goals. How do we measure a project's success and that it is done?

Outreach:

• YES
• 6 or so groups - ACCORD, OEIT, ISTAB, SIPB, and so on
• Actual implementation to be determined. OEIT & Libraries ready to go, already offered to come. Some doing rounds. Start with going out to meet with existing groups like OEIT, Libraries and Faculty Support. Derek Jaeger's group and so forth.
• DLC and Faculty - mix of looking for projects and going out on escalated issues for non-standard road blocks