Meeting Agenda - Thursday, April 2

Technology Committee Agenda

Thursday, April 2

2:30 pm Library

• Training 4/6 Update & Status
• logistics, training agenda
• user accounts created
• Educator U trainers
• Year 0 Training Plans
• make-up for 4/6
• Educator U 1/2 day tech training
• second "boot camp" - Sites, Chrome, YouTube  (May 4th?)
• focused seminars May & June
• Migration & Transition
• parallel systems through 6/19/15
• some will move ASAP, others will hang on 'til 6/19
• new users should be advised there may be wrinkles
• process to field questions, issues, suggestions (Form?)
• creating migration/transition resource guide (on website & FAQ)
• frequent communications with user community
• Adding pilot student accounts (Matt; others?)
• Previous Items:
• Service Provisioning Issues List
• Promotion Plan

Meeting notes 3/25

Tech Committee meeting
3/25/15
2:30-3:30
In attendance: B. Chauvin, C. Grabke, T. Quinn, D. Parker, L. Lynch, M. Joyce, M. Hauck, P. Conis, S. Green

Discussion of sharing provisions on teachers's websites. Issues around being able to share documents with parents, who are outside the domain. BJC trying to share co-op documents, Matt trying to share stuff for his classes on sites. Easy to share things that are Google docs, but harder with things that aren't google docs. To share outside domain, you need to share point to point. Discussion of global settings of private/public.

Classroom is accessible, but teachers need to be verified by administrator in order to be able to use it.

Matt proposes setting up a dummy class that is filled with teachers so that teachers can see what it will look like.

In youtube, need google+ implemented for teachers so teachers can create YouTube channels. People don't need additional training or information to use google+. We simply need to enable Google+ for teachers so they can use YouTube functionality. Google+ may go away in the future, but we don't have a timeline for that, so in the meantime it helps teachers ONLY to have access to it. Suzanne asks about security risks related to opening Google+ for teachers.

Discussion of calendar sharing- request that the default be set to private, so that not everything is not shared with everyone.  The individuals can share as they want/need.

Request to set up the text reminder option in calendar that is currently disabled at the global level. This way text reminders of calendar appointments can be sent to users phones, if they request.

Matt proposes setting up some students on this to test how things work from the student perspective. Suzanne proposes student council students as our potential "beta testers." Propose that we use some of Matt's students since he has his Google up and running.

Training program: EducatorU set for 4/6
Groups are ready to go based on responses to survey
Mike shares EducatorU curriculum
EducatorU will do two groups.  Mike will do group 3.
Session 1 boot camp on the 6th. May 4th for secons training (sites and YouTube). Mike will do extra help sessions in between.  Half-hour sessions on Tuesday and Thursday targeted to specific topics. Test and certificate at the end as the goal for everyone.

Brief discussion about training potential new hires over the summer.

Marketing/promoting the move to Google. Mike has created a website that provides news and info. Will add a YouTube channel/playlist with helpful videos. Also a weekly newsfeed. Purpose is to create awareness. MIke needs help with weekly newsfeed- wants to tie it to teaching tasks to create the hook.

Meeting Agenda for 3/25

Tech Committee Meeting Agenda

Wednesday, March 25, 2015

2:30pm

Library

• Updates on Service Provisioning for users
• open issues status
• new items & feedback
• Training Program (proposed program)
• status on 4/6 'Boot Camp'
• activation of users prior to training
• Phase I (2015) - primary objective(s)
• establish/enforce baseline standard
• Marketing Program (draft)
• primary objective(s) for 2015
• key elements
• roles and responsibilities

3-18-2015 Meeting Agenda & Minutes

Agenda

Wednesday March 18, 2015

2:30pm

Trustees Room, McFarland Hall

• Training program
• faculty, staff, administration
• define, resource, plan/timeline
• minimum standards of performance?
• Promotional Program
• generate excitement, convey vision
• define, roles & responsibilities, plan/timeline
• Roll-out Timeline (broad strokes) Timeline handout
• Objectives
• fully functional by 6/25/15 (last day)
• all admin, faculty and staff have received basic training for Mail, Calendar, Docs&Drive
• all faculty have received basic training for Sites, Classroom
• User and Public document migration to Drive
• activities, responsibilities, timeline/dependencies
• Housekeeping
• using group: Aggie Google Domain
• provisioning services
• stuff I learned at the N.E. Summit (Google+, Hangouts, YouTube)
• issues that have come up recently
• set up a training account, a developer account
• Google Apps site (https://sites.google.com/site/gafetrial/)
• your feedback on content, flow, layout welcome
• New England Google Apps for Ed Summit

Tech committee meeting notes

3/18/15

2:30-3:30 

Trustees' Room

In attendance: M. Hauck, M. Joyce, B. Chauvin, T. Quinn, C. Grabke, P. Conis

-Discussion about levels/types of permissions for sharing documents within and outside of the domain, also sharing non-native google documents inside and outside of the domain

Housekeeping:
- We will use the Aggie Google Domain instead of the blog to share some comments/issues/questions as they arise from our initial use of google
- Mike learned that we will need to allow google+ for teachers in order for them to be able to use youtube (channels and playlists)
- Compromise on hangouts: set up full use for only teachers
- Mike would like members of the committee to look at the google apps site he has set up for information/publicity purposes and give him feedback


Training program:
- Break faculty into 3 groups by ability level
- Use google's existing curriculum
- initial training on mail, doc, and drive
- next level on sites, chrome, youtube
- five total hours for training
- seminars held Tuesday and Thursday after school for extra help, catch up, etc
- load in users and get dual delivery going so they can get their accounts going when they go to the first training on 4/6
- discussion of how to migrate forms from APubPerm over to google and creating templates for teacher/class sites so everyone doesn't feel like they are starting from scratch
- EducatorU will help do some of the training on the 6th and any other day we use after that


Promotional Program:
- We need to market/sell this!

Meeting Minutes for March 10, 2015

Tech Committee
Tuesday March 10, 2015
2:30pm Principal's Office, McFarland Hall

attending: BJ Chauvin, P. Conis, S. Green, M. Hauck, M. Joyce, L. Lynch, D. Parker, T. Quinn, K. Roos

• Finalize decision on user provisioning: reviewed the latest decisions on user provisioning (document).  All approved.  Some discussion of clarification on a few points but no objections or disagreements. Key points:
• Sites, Blogger, and Groups should be visible (accessible) from outside the domain (at the discretion of the owner);
• YouTube full service available to all teachers;
• Hangouts should be within the domain and initiated and moderated by a teacher; Laura will investigate implementing this privilege status;
• Gmail - Suzanne wants to continue to use Outlook as her email client
• Document migration: many users have existing content in their personal google accounts that they have been using for school.  We need to make sure they are able to transfer privilege and access between domains.  This is an admin console setting. Laura will investigate.
• EdLine - we will be terminating EdLine service this year.  From the Google Apps perspective, our responsibility will be to pick up the website functions - the school website and teacher websites.
• Roll-Out plan: Michael emphasized that despite all the snow on the ground, it's an illusion that we have a lot of time to meet our deadline of being fully functional by end of school year (which is only 16 weeks away including Spring Break!).
  There was a general discussion of the prospective roll-out plan (document).  Key Points:
• most critical next step is to launch the training program.  This will also require making all non-student accounts active. We need to devise an aggressive training campaign which will raise 100% to a (to be defined) minimal level of performance (how to measure?)
• Laura expressed a concern that before loading in all non-student users she would like to have all Tech Comm people on first, test out the functionality, fix issues and then load other users.  It was agreed this was a sensible approach.
• second most critical item is to create a promotional campaign - marketing - to establish awareness, capture attention, build enthusiasm & excitement.  This must be built around a theme of " how & why Google will improve your teaching and student learning; how work gets easier".
• we will target to add the student population in late June.  This will allow students to get familiar and to transfer their content.  One less task (that could go wrong) in the Fall.
• Housekeeping
• we moved the standing time for the Committee meeting to Wednesday at 2:30.  Next meeting will be Wednesday, March 18.
• Google Apps for Education New England Summit is this weekend in Burlington, MA at the Marshall Simmonds Middle School.

Meeting adjourned at 3:40

Meeting Tuesday March 10

Agenda

Tuesday March 10, 2015

2:30pm

Trustees Room, McFarland Hall

• Provisioning Users
• quick review of past discussion/ open issues
• wrap-up and final decisions
• handout
• Migration of user documents
• current Google users are outside the domain
• Edline: Keep it or Leave it?
• if we leave, what functions will need to be duplicated in Google?
• what needs to be done?
• Roll-out Timeline (broad strokes) Timeline handout
• Objectives
• fully functional by 6/25/15 (last day)
• all admin, faculty and staff have received basic training for Mail, Calendar, Docs&Drive
• all faculty have received basic training for Sites, Classroom
• User and Public document migration to Drive
• Housekeeping
• 3/17 is Faculty Meeting; meet afterwards or another day
• New England Google Apps Summit 3/14 & 15 in Burlington

meeting notes 3/3/15

Tech committee meeting
March 3, 2015 2:30-3:30 trustees' room
In attendance: M. Hauck, D. Parker, P. Conis, K. Roos, B.J.Chauvin, T. Quinn, R. Fitzpatrick

Set a standing date and time for meeting?  We need weekly meeting in the short term because we have a lot to do to be ready for Sept.  Tuesdays at 2:30 starting 3/10/15.

Provisioning users:
- email for everyone
- blogger available within domain
- sites available within domain
- classroom available to students, faculty, alumni

Review of answers to questions from Educator U
With the presumption that faculty will have access to everything listed below here, discussion around student access to the following items was had.

- allowing students to email outside the domain?  just juniors and seniors (they need to) or all grades? All members present at the meeting vote to allow ALL students to email outside the domain.  Final decision should involve Supt.  We recommend to her that all students be allowed to email outside domain.
- Drive, calendar, sites on for all student groups
- Discussion regarding whether or not students can be allowed to use Hangouts.  Educationally sound or potentially dangerous? Mike raises the point that comments are not anonymous.  We can find out who is saying what when and where.  BJC talks about teaching students use it safely, much as we do with other tools and equipment.  Group members present vote to approve opening hangouts to students within domain. Decision should involve supt.  We recommend to her that students e alowed to use hangouts within domain.
- Discussion of opening up chrome store for student users.  Students can add extensions to their chrome.  Many educational services.  Again, group votes yes on this.  Recommendation to supt to say yes.
- Google+ is a non-issue, as it is "going away"
- Google wallet- NO
- Allowing students to receive emails from outside domain? same decision as above for students sending emails outside domain
- YouTube? Open up  youtube for education for students.  Teachers have full youtube access.  Teachers can add what they want to their channel (outside of youtube for education) and then kids can access the videos.
- Google groups- allows users to set up groups for discussion, sharing documents, etc.  Clubs and sports teams could use it.  Students only have access within domain.  Teachers have access outside domain.
- Google keep- simple application for taking notes.  clip things from websites, emails, etc.  Kind of like sticky notes.  Teachers can share notes with a class/group-  Yes
- Google books- Yes
- Google scholar- Yes

Next steps: HOW DO WE TRAIN PEOPLE?

- traditional inservice training does not work
- designate "go-to> people who get google certified on certain apps, who are then resident experts that others can go to for help/traiing
- Tammy brings up the point that teachers need an incentive to be trained.  We struggle with getting people to learn something new
-Mike asks group to think unconventionally about how training can happen
- Create project-specific seminars that have a project at the end and build the training around that (student portfolio idea)
- adoption begins at the top.  we have to take on the challenge of maximizing the use of digital technolog Set the tone that this is the way we are going.

Do we need to keep edline?  Google can do this stuff, but we need to make sure this is all set up

March 3 Meeting Agenda

Meeting Agenda

Thursday, Mar 3, 2015

2:30 PM in Trustees Room, McFarland Hall

• Decide on standing meeting time
• continuation of Provisioning Users discussion from last meeting:
• initial proposal
• review what we've done (see minutes from 1/20/15)
• Educator U worksheet comments
• User Training
• getting creative to make it happen effective and comprehensive
• approaches from other schools
• Do we keep EdLine?
• What functions does it fulfill
• cost saving
• if no, migration/transition issues
• Migrating User and Public content to our Google Domain