Monday, November 3, 2014

Committee Meeting Tuesday, 4 November

Committee Meeting
Tuesday, 4 November 10:15 am
Trustees Room - McFarland Hall


  • A few housekeeping items
  • Feedback from South Shore Voke...a Google Apps school
  • The Issues List
    • Review
    • Common Understanding of what lies ahead
  • Planning process
    • Consultants - status
    • create a rough timeline
    • forming task groups to solve issues

Tuesday, October 21, 2014

Meetings notes 10/21/14

Tech committee meeting October 21, 2014
In attendance: M. Hauck, L. Lynch, D. Parker, T. Quinn, P. Conis, B.J. Chauvin, S. Green,

1. Discussion of tech plan report card: Mike will set up a shared document for all people to comment on and provide feedback on

2. Google apps for education implementation:
3 tracks: technical, promotional (getting info out), PD (training and tutorials)
5 steps to project planning: research through execution, evaluation, and adjustment- is this something that the consultant help us with? We don't currently have one on board and should start.  Will consultant be project manager? How are we going to use the consultant? Discussion of whether we will continue with mecnet or switch everyone over to google mail. Get consultants in over two days to make presentations and then just pick one. Rick is attending an informational workshop in Franklin. He will forward information about it to the group so others can attend if interested.  Question asked about whether or not we are required to archive student email.
Technical resources on "going Google" shared by Mike. Google has a lot or information and resources available to help schools plan.  Lots of online training through Google and other sources for training and PD. Available for free.

3. Brainstorming some of the questions issues we will face as we plan to implement (looking at three tracks posted in #2). Mike distributes a list with some beginning thoughts.  Will create a shareable document online for people to add questions/ issues to. Within the next week, people should ADD to Mike's list.  He will reorganize list and share it back.  At next meeting, we will review and discuss the updated list.
Brief discussion of whether we are staying with ipass/edline for next year or are we moving to a new student information system.  Potentially starting a subgroup to explore other options- consensus seems to be to leave ipass/edline.

Discussion of interfacing between our SIS and Google.

4. Announcement at 10/27 faculty meeting regarding Google- the the plan to be fully implemented for 15-16 school year. Make a basic announcement with the plan to make  more elaborate presentation with more information at the 11/4 faculty meeting

Next meeting: 11/4 at 10:15 in the trustees room

Monday, October 20, 2014

Tech Committee Meeting October 20, 2014

Technology Committee Agenda

October 20, 2014  12:00 pm
Trustee’s Conference Room

  1. Technology Plan Report Card
    1. set-up shared document for input
  2. Google Apps for Education Implementation
    1. status on school visits
    2. set-up a repository site for resources and documents
    3. creating a detailed project plan (timeline, sequencing, critical path)
      1. GANTT and CPM plans
      2. step 0: define a basic structure
      3. step 1: brainstorm critical tasks/decisions
  3. Planning process/participants
  4. Faculty Meeting (10/27) announcement

Thursday, October 9, 2014

Tech Committee meeting October 9, 2014

Technology Committee Agenda
October 9, 2014  10:15am
Trustee’s Conference Room

  1. Status on Technology Plan
    1. submitted 11/7/2013
    2. annual review; quinquennial re-plan
  2. Google Apps for Education Next Steps
    1. setting a process to create an implementation plan
    2. establish a goal and general timeline for implementation
    3. getting the tech team on-board and engaged
  3. Defining an overall Computing Architecture for the school
    1. coordinate with GAfE implementation
    2. inventory computing requirements for the full community



Minutes (P. Conis)
Trustees' room
10:15

In attendance: M. Hauck, S. Green, R. Fitzpatrick, T. Quinn, B. Chauvin, L. Lynch, D. Parker, P. Conis

1. Status of tech plan-
Discussion about the nature/ role of the plan that the plan the tech committee developed. Is this an internal document? Is it intended to replace the document we are required to submit to the DESE? Plan is for all committee members to re-review the document before the next meeting and come to a decision on this question at the next meeting
Also, need a "report card" on the status of the six benchmarks in the plan. Where are we at and what should be our action items for this school year. Plan is to review the document for the next meeting to come up with this "report card."

2. Google apps for education
Decision has been made to move to becoming a Google school. We need input from teachers with a range of technology experience and expertise and from a range of departments about what they want/need from Google. Discussion of how to get this input- creating some sort of "working group" that could ask questions and give input. We need to find out what teachers are expecting from the process and what their needs will be.
We have a list of consultants from the google apps summits to whom we could talk. We would additionally look to speak to schools that are already Google apps schools so we can know how this has worked elsewhere.

Discussion of whether it should be rolled out school-wide or only in certain departments.
Discussion of archiving email through Google- costs $10 per staff member. What about students? What about retrieval costs?
Mike plans to go speak to nearby schools that are already Google schools to discuss their process and  seek advice.
Significant changes needed to be made to the AUP
Mike will work with coordinators to get people for the working group. Using faculty and department meeting time for this.
Mike will use feedback from other schools and Google to create a plan/ timeline.
Timeline: be fully ready for September 2015.
November faculty meeting to introduce this information to the faculty.
Plan for PD for this so that it is targeted at people's individual comfort levels with tech.

Next meeting: 1:00 pm Tuesday, October 21, 2014. Trustees' room

Wednesday, June 11, 2014

Meeting Notes 6/9

Tech committee meeting notes
June 9, 2014

In attendance: Mike H, Barbara-Jean C, Paula C

Review of Mike's presentation at the last faculty meeting regarding dig curriculum

Plan to create a website for the program with all information, resources, etc- goal is to give people as much as possible to work with so they can find what works for them

Continue to find materials and resources and those will be included in the website- Mike will show drafts to the committee for feedback throughout the development process

Next steps: assessment? How do we evaluate students' levels of "citizenship"

Creating drivers licenses/badges/passports

Badges can be for each concept students demonstrate understanding of

There is an existing one through Mozilla project.  Who monitors students' progress? Can we connect online privileges to achievement of badges?

use curriculum map to connect each area to a subject so that that subject has primary responsibility for teaching and assessing students in that area

Use time on the 26th to work on mapping so everyone can have a voice/say in process

More research on how other schools are implementing this is needed.

Kids can use study time and x block time to work on some of the self-guided/self-paced aspects of the learning

Ideally, we strictly connect access to earning badges to make earning badges desirable. Limit access for those students who haven't.

Make a connection to the premise of an OSHA 10 card






Monday, June 9, 2014

Meeting for June 9, 2014

Agenda for Monday, June 9 at 2:30 in the Library

This will probably be our last meeting for the school year.  Unfinished business will carry over to next year.

There are a couple of key items to finish up on the Digital Citizenship curriculum and we should be thinking about what next year's significant initiative should be.


  1. feedback & comments from last Monday's faculty meeting presentation
    1. what are you hearing from you colleagues
  2. collecting & curating materials, lessons, etc.
    1. create a website for teacher access with self-training, resources, etc.
  3. Student assessment
    1. digital driver's license
    2. digital badges
    3. digital passport
    4. extra privilege to those who have demonstrated success

Wednesday, May 21, 2014

Meeting notes 5/21/14

Tech Committee Meeting Notes
5/21/14
In attendance: M. Hauck, T. Quinn, M. Joyce, P. Conis, K. Roos

Agenda topic: Digital Literacy curriculum

Discussing the existing curriculum outline. More sample lessons and ideas added, more still needed.
Action Item:  Members are encouraged to find and collect additional planned lessons and/or materials (handouts, videos, websites).  Contribute into the Google Drive folders created to store the info.

Attaching ideas and lessons to subject and grade.  Michael will refine chart (add 4 grade levels for each subject area) and republish.
Action Item: members should review lesson materials and suggest where on the curriculum map (subject & level) a lesson unit 'primarily' falls (who is the lead responsible to ensure this is learned material).

Presenting this outline at the June 2 faculty meeting.  Michael will be circulating draft presentation/handouts for feedback, ideas, critique.