Agenda for Wednesday, August 17 Meeting 1) Thoughts on survey and lessons learne...
Agenda for Wednesday, August 17 Meeting
1) Thoughts on survey and lessons learned
2) Review track and session ideas
3) Process for soliciting and managing the tracks and sessions
4) Program Cmte. meetings – time/dates
My rough notes from the meeting Sakai Conference Call Notes: Wednesday, August 1...
My rough notes from the meeting
Sakai Conference Call Notes: Wednesday, August 17, 2005
Goals
Portfolio status
Initiatives around pedagogy -others mentioned
Implementation activities (reports)
Specific tool work
Framework - developers
Sakai Foundation - leadership
Prepare people to be productive open source contributors
– Code & community
Clarify the transition of the Sakai
Track ideas
Something for top-level administrators doing implementations on their campuses
Same goes for Sakai
Using and supporting tools - what it
Implementation - how to make it work on my campus
Choosing Sakai or OSPI - how do you make a decision to adopt
Designing Tools - ui & requirements
Developing Tools - JSR coding
Teaching with Sakai -
Open source licensing
Technology vs. education vs. management
e Research Track - conscious discussion about how Sakai is being used and how they want to be used in support of research
Consider combining research & teaching
Note that private meetings need time too
Management and Governance are often confused - need clarity between these topics
Who attended Baltimore (by position or responsibility)? May have that information (John Norman did some sort of survey that may have asked position information). Should look at this carefully - one thing is sure, there were few faculty present (at pedagogy session only three or four people raised their hands as faculty). It's a question as to whether this segment of the community can be engaged; whether Sakai is ready and able to do that.
Weekly planning meetings will follow. We need to get up the rough outlines of the tracks arranged around the themes:
Research and Education
Technology
Management
Leadership and Governance
We need a structure that makes time for focused attention that we expect everyone will want to spend on core themes of the conference; that is, presentations which will not be in competition with other track offerings or events. We can't afford too many of these, but some, particularly around governance, leadership and process going forward probably make sense.
We hould work backwards from the conference date to identify when major milestones need to be achieved.
Trent has agreed to be Mara's co-chair for the conference in Dec.
August 17 Meeting Notes from Mara I am posting decisions and action items that I...
August 17 Meeting Notes from Mara
I am posting decisions and action items that I believe emerged from our meeting. I am hoping that this will help us fairly quickly clarify issues and move forward. Please make additions or edits using the "Reply to This" feature.
Decisions:
Top level categories or tracks:
Education & Research
Technology
Management
Community Source
Topic categories need to be fleshed out (these may be applied to different categories). Some that were mentioned are:
Newbie
Overview
Hands-on
Implementation
Design
Develop
Pedagogy
EResearch
Governance
OSP sessions will be integrated throughout the conference with an overview or plenary session at the start of the conference.
C-Level needs to have a CIO or other Senior Admin(s) to draw more of the other C-Level folks
Governance discussions should be broken into discrete sessions, some being clearly marked as decision-making sessions and others being more about information sharing, licensing and open source being an example.
Program Cmte. will meet weekly to start off
Sept. 1 registration will go up online
Call for session and demo proposals will go out within the next couple of weeks (after next week's meeting is goal).
We will have some repeat sessions for critical overview sessions
Action Items
Susan will send around data regarding the roles of Baltimore conference attendees
Form for call for sessions and demos will be developed and shared with group by next week
Committee should review and comment on project plan (front worksheet in Austin Template under Documents) by next week.
Other important points in discussion
We need to define the goals for the conference. Some goals that came up (my apologies for the paraphrasing!):
Motivate and prepare people to be productive open source contributors
Expand the engagement in the Sakai community through induction of new groups and new members
Build confidence in the Sakai foundation and the community and product as we transition from the Mellon grant
(Also posted in "session ideas" track) Talking points for Friday August 26 Phone...
(Also posted in "session ideas" track)
Talking points for Friday August 26 Phone Conference
Mara is out of the office this week, so I'm offering talking points for tomorrow's phone conference. I'm sure Mara will be back in full swing next week (right, Mara?).
1. If we have between 500 and 800 attendees - and we do need in the next few weeks to settle on a number target to work with for planning – we are looking at a minimum of 10 and as many as 14 concurrent sessions during each set of sessions (the number affects how targeted we want our sessions to be). I'm assuming that our meeting rooms won't hold more than 50 - but please correct me if this is wrong - although one or two rooms might be available during each session-block that can hold more. Nor do I think it's good to have sessions with more than 50 since Q&A loses value beyond that point.
2. With somewhere between 10 and 14 sessions, speaking on behalf of OSP, I'd like 4 to 6 sessions focused on portfolios in each time slot, 2 or 3 appropriate to both Sakai and OSPI, and 4 to 6 sessions focused on Sakai. I'm speaking for myself and OSPI only. I don't know yet what Mara's thinking is on this.
3. I advocate for multiple OSP sessions because portfolios are strongly "coming of age" this year. At least 18 US companies, including Oracle and IBM, are already in or entering the market this fall, most of whom focus almost entirely on electronic portfolios. You will not find one higher ed institution that is not thinking of or actually implementing a portfolio this year (or which has already done so). This is the "year of the portfolio." And, of course, OSP 2.0 was just introduced in June, so interest is high on that account as well.
4. In other words, information about portfolio information will be in demand at SEPP.
5. Finally, "portfolios" is an umbrella term that includes reflective portfolio, assessment management systems, advising management systems, citizen portfolios, resume-builders, faculty portfolios, showcase portfolios, student development portfolios and a few other instantiations of portfolio technology. This means SEPP attendees will arrive with a range of portfolio-information needs which should be addressed with a range of presentations.
Summary of OSPI suggestions for this email and recent discussions:
*plenary portfolio summary, 30 minutes at beginning of conference
*a substantial % of sessions in each time slot focused on portfolios
*And, some repeated sessions, especially for OSP developers and implementers
*And, meeting times and spaces at 2 or 3 times set aside for the "OSPNext" group to meet
OSPI will have sessions appropriate for all four main tracks:
Teaching, Learning, Research, and Assessment
Technology
Community Source
Management and Implementation
Some sessions will address both projects, such as how both open source and commercial can be proprietary and therefore what "support" means in the community source arena. But others, such as implementing assessment management portfolios for tracking student outcomes will be specific to OSP.
Title:
conversation starters (to include OSPI):
SEPP/OSPI Winter Conference
SEPP Winter Conference with OSPI
SEPP Winter Conference Including OSPI
etc.
Maybe none of these is good, but the goal is to identify to OSPI former attendees that this is their next conference.
These talking points are very OSPI-centric, so must be balanced with committee input on behalf of Sakai.
August 25 Meeting Notes from Mara Agenda # Conference Track/Session # Review Sc...
August 25 Meeting Notes from Mara
Agenda
Conference Track/Session
Review Schedule
F2F in Educause
Number of tracks/Rooms
Decisions:
Top level categories or tracks revised:
Teaching, Learning & Assessment (new name)
Technology
Management & Campus Implementation (NOTE the addition of Campus to help distinguish from tech implementation.)
Sakai Foundation, Community Source & Governance (new name)
Research & Collaboration (New)
The Program Cmte. (with the help of some others) will act as conveners for each session, setting context, providing structure, and acting as time keepers and providing summaries.
We will start adding content as soon as possible (we can add the sessions we have "called for" and not wait until all sessions defined).
Program Cmte. will convene in a f2f meeting at Educause on Oct. 18. Mary will help us find a Suite/Space.
There will be 5 different session formats supported:
Panels
Workshops (How-To)
Discussions (Round-tables)
Lecture Sessions (Trad. Papers)
Poster session(s)
Action Items
The organizing cmte. will get back to us on the # of rooms. Mara will meet with them to determine room availability and start to flesh out the conference template. There should be at least 8 rooms, with possibly 12.
Form for call for sessions and demos will be developed and shared with group by next week
Discussion regarding naming and a way to "Celebrate the coming together of Sakai and OSP" so as to ensure that the portfolio track is visible to both Sakai and OSP folks will continue via email and be on the agenda for next week.
Other important points in discussion
Ways to engage the learning and pedagogy folks in paradigm that makes sense, speaks in their language, and leads to impactful efforts. Maybe some sort of thread through the TLA track...
Motivate and prepare people to be productive open source contributors
Is there a way to use response systems for use with panels or other sessions?
Comments (5)
Aug 16, 2005
Mara Hancock says:
Agenda for Wednesday, August 17 Meeting 1) Thoughts on survey and lessons learne...Agenda for Wednesday, August 17 Meeting
1) Thoughts on survey and lessons learned
2) Review track and session ideas
3) Process for soliciting and managing the tracks and sessions
4) Program Cmte. meetings – time/dates
Aug 17, 2005
Phillip Long says:
My rough notes from the meeting Sakai Conference Call Notes: Wednesday, August 1...My rough notes from the meeting
Sakai Conference Call Notes: Wednesday, August 17, 2005
Goals
Portfolio status
Initiatives around pedagogy -others mentioned
Implementation activities (reports)
Specific tool work
Framework - developers
Sakai Foundation - leadership
Prepare people to be productive open source contributors
– Code & community
Clarify the transition of the Sakai
Track ideas
Something for top-level administrators doing implementations on their campuses
Same goes for Sakai
Using and supporting tools - what it
Implementation - how to make it work on my campus
Choosing Sakai or OSPI - how do you make a decision to adopt
Designing Tools - ui & requirements
Developing Tools - JSR coding
Teaching with Sakai -
Open source licensing
Technology vs. education vs. management
e Research Track - conscious discussion about how Sakai is being used and how they want to be used in support of research
Consider combining research & teaching
Note that private meetings need time too
Management and Governance are often confused - need clarity between these topics
Who attended Baltimore (by position or responsibility)? May have that information (John Norman did some sort of survey that may have asked position information). Should look at this carefully - one thing is sure, there were few faculty present (at pedagogy session only three or four people raised their hands as faculty). It's a question as to whether this segment of the community can be engaged; whether Sakai is ready and able to do that.
Weekly planning meetings will follow. We need to get up the rough outlines of the tracks arranged around the themes:
We need a structure that makes time for focused attention that we expect everyone will want to spend on core themes of the conference; that is, presentations which will not be in competition with other track offerings or events. We can't afford too many of these, but some, particularly around governance, leadership and process going forward probably make sense.
We hould work backwards from the conference date to identify when major milestones need to be achieved.
Trent has agreed to be Mara's co-chair for the conference in Dec.
Rough notes by longpd@mit.edu
Aug 19, 2005
Mara Hancock says:
August 17 Meeting Notes from Mara I am posting decisions and action items that I...August 17 Meeting Notes from Mara
I am posting decisions and action items that I believe emerged from our meeting. I am hoping that this will help us fairly quickly clarify issues and move forward. Please make additions or edits using the "Reply to This" feature.
Decisions:
Action Items
Other important points in discussion
Aug 25, 2005
Trent Batson says:
(Also posted in "session ideas" track) Talking points for Friday August 26 Phone...(Also posted in "session ideas" track)
Talking points for Friday August 26 Phone Conference
Mara is out of the office this week, so I'm offering talking points for tomorrow's phone conference. I'm sure Mara will be back in full swing next week (right, Mara?).
1. If we have between 500 and 800 attendees - and we do need in the next few weeks to settle on a number target to work with for planning – we are looking at a minimum of 10 and as many as 14 concurrent sessions during each set of sessions (the number affects how targeted we want our sessions to be). I'm assuming that our meeting rooms won't hold more than 50 - but please correct me if this is wrong - although one or two rooms might be available during each session-block that can hold more. Nor do I think it's good to have sessions with more than 50 since Q&A loses value beyond that point.
2. With somewhere between 10 and 14 sessions, speaking on behalf of OSP, I'd like 4 to 6 sessions focused on portfolios in each time slot, 2 or 3 appropriate to both Sakai and OSPI, and 4 to 6 sessions focused on Sakai. I'm speaking for myself and OSPI only. I don't know yet what Mara's thinking is on this.
3. I advocate for multiple OSP sessions because portfolios are strongly "coming of age" this year. At least 18 US companies, including Oracle and IBM, are already in or entering the market this fall, most of whom focus almost entirely on electronic portfolios. You will not find one higher ed institution that is not thinking of or actually implementing a portfolio this year (or which has already done so). This is the "year of the portfolio." And, of course, OSP 2.0 was just introduced in June, so interest is high on that account as well.
4. In other words, information about portfolio information will be in demand at SEPP.
5. Finally, "portfolios" is an umbrella term that includes reflective portfolio, assessment management systems, advising management systems, citizen portfolios, resume-builders, faculty portfolios, showcase portfolios, student development portfolios and a few other instantiations of portfolio technology. This means SEPP attendees will arrive with a range of portfolio-information needs which should be addressed with a range of presentations.
Summary of OSPI suggestions for this email and recent discussions:
*plenary portfolio summary, 30 minutes at beginning of conference
*a substantial % of sessions in each time slot focused on portfolios
*And, some repeated sessions, especially for OSP developers and implementers
*And, meeting times and spaces at 2 or 3 times set aside for the "OSPNext" group to meet
OSPI will have sessions appropriate for all four main tracks:
Teaching, Learning, Research, and Assessment
Technology
Community Source
Management and Implementation
Some sessions will address both projects, such as how both open source and commercial can be proprietary and therefore what "support" means in the community source arena. But others, such as implementing assessment management portfolios for tracking student outcomes will be specific to OSP.
Title:
conversation starters (to include OSPI):
SEPP/OSPI Winter Conference
SEPP Winter Conference with OSPI
SEPP Winter Conference Including OSPI
etc.
Maybe none of these is good, but the goal is to identify to OSPI former attendees that this is their next conference.
These talking points are very OSPI-centric, so must be balanced with committee input on behalf of Sakai.
Cheers
Trent
Aug 26, 2005
Mara Hancock says:
August 25 Meeting Notes from Mara Agenda # Conference Track/Session # Review Sc...August 25 Meeting Notes from Mara
Agenda
Decisions:
Action Items
Other important points in discussion