E-mailNewport Beach Project Coordination Meeting
This Project Coordination Meeting is for designers, developers, and stakeholders working on the various projects in Sakai. It is being held 1-2 December 2007 (Saturday and Sunday) in Newport Beach, California, prior to the 8th Sakai Conference. The goals of this meetings are to:
- share projects' plans for upcoming releases, and
- discuss cross-project collaborations and aspects of design and development that impact Sakai as a whole.
This meetings is not a replacement for discussion of these topics on appropriate Sakai email lists (e.g., sakai-dev), but rather are an opportunity to facilitate discussions via face-to-face interaction.
Meeting to be held in the Marriott Newportbeach Conference Center, in the Coast Salon 4 and 5 rooms.
Agenda
For all of the agenda topics, on-list discussion or commenting on the pages linked to below is strongly encouraged prior to the meeting; particularly if you are going to be unable to attend in person. If you have any questions or concerns, please contact the Sakai Project Coordinator (Peter A. Knoop).
| Time (Local) | Topics (Links take you to proposals and background information for discussion.) |
|---|---|
| Saturday 9:00am - 10:30am |
* Opening remarks. * Introductions. * Project Team and Working Group updates on plans. * Review agenda. |
| Saturday 10:30am - 10:40am |
Break. |
| Saturday 10:40am - 12:30pm |
* General group discussion on Release Practices and related topics (Framework, QA, Tool Status and Promotion/Deprecation). * Identify break-out group participation. |
| Saturday 12:30pm - 1:30pm |
Lunch on your own. |
| Saturday 1:30pm - 5:00pm |
Breakout Sessions: * Release Practices (Michael) * Framework (Anthony) * QA (Megan) |
| Saturday 5:00pm - 5:30pm |
Report back to group from Breakout sessions. |
| Saturday 5:30pm |
Dinner on your own. |
| Sunday 9:00am - 9:10am |
Review agenda. Identify break-out group participation. |
| Sunday 9:10am - 12:00pm |
Breakout Sessions: * [Enterprise Integration] (Ray) * Assignments (Clay) * Technical Management of Releases (Anthony) |
| Sunday 12:00pm - 12:30pm |
Report back to group from Breakout sessions. |
| Sunday 12:30pm - 1:30pm |
Lunch on your own. |
| Sunday 1:30pm - 4:30pm |
Breakout Sessions: * Cross-Tool Integration (Beth) * Community Processes (Anthony) * Content Hosting Service Re-factor (Jim/Ian) |
| Sunday 4:30pm - 5:30pm |
* Report back to group from Breakout sessions. * Upgrades to consider for 2.6 and Beyond (SAK-11211). * Future Project Coordination meetings. * Identification of to-do tasks and volunteers. |
| Sunday 5:30pm |
Dinner on your own. |
Attendees
The Project Association column lists the projects that I believe you are going to be providing a status report on during the first part of our agenda. (If there is more than one of you listed for a specific project, perhaps you could elect one person to provide the overview?)
Anyone that is a Sakai partner is welcome to observe the meeting, however, space is limited. If we run out of room, we may have to ask those listed below as Observers to entertain themselves otherwise (surfing, anyone?).
| Name | Project Association(s) | |
|---|---|---|
| 1 | Peter A. Knoop (Sakai Foundation) | Project Coordinator |
| 2 | Jean-François Lévêque (Pierre & Marie Curie University, Paris, France) | Internationalization and localization to French (France) |
| 3 | Michael Korcuska (Sakai Foundation) | Executive Director |
| 4 | Megan May (Sakai Foundation) | QA Director |
| 5 | Linda Place (University of Michigan) | Performance Working Group |
| 6 | Oliver Heyer (UC Berkeley) | Development Manager, UCB |
| 7 | John Leasia (University of Michigan) | CTools (Sakai) Product Mgr |
| 8 | Aaron Zeckoski (Cambridge) | [Roadmap], [Kernel] (EntityBroker, etc.), Best Practices, Testing |
| 9 | Antranig Basman (Cambridge) | RSF, ComponentManager |
| 10 | David Haines (University of Michigan) | CTools (Sakai) |
| 11 | Joshua Ryan (Arizona State University) | Page Order, Resource-viewer, ... |
| 12 | Mark Norton (Nolaria Consulting) | Chair. Requirements Committee |
| 13 | Colin Clark (University of Toronto) | Fluid Project and Sakai user experience] |
| 14 | Kirk Alexander (UC Davis) | Gradebook |
| 15 | Clay Fenlason (Georgia Tech, Sakai Foundation Board Member) | Promiscuous meddler |
| 16 | Ray Davis (UC Berkeley) | [User], Component Manager |
| 17 | Beth Kirschner (University of Michigan) | Internationalization, OSP, Schedule |
| 18 | John Lewis (Unicon) | |
| 19 | Lance Speelmon (Indiana) | Quality Assurance, Release Management |
| 20 | John Ellis (rSmart) | Forms, Reports, Data Warehouse, OSP |
| 21 | Carl Hall (Georgia Tech) | |
| 22 | Stuart Freeman (Georgia Tech) | 2.4.x branch manager |
| 23 | Marc Brierley (Stanford) | SAMigo/Tests & Quizzes, User eXperience DG, Homepage |
| 24 | Jason Shao (Rutgers) | I'm certainly a meddler, but refuse to label myself as promiscuous... |
| 25 | Jim Eng (University of Michigan) | Resources/Content |
| 26 | Ian Boston (University of Cambridge) | |
| 27 | Seth Theriault (Columbia University) | |
| 28 | Nate Angell (rSmart) | Community Relations |
| 29 | Hannah Reeves (rSmart) | Documentation/EduTools Review, etc. |
| 30 | Glenn R. Golden (University of Michigan) | Mneme (Test Center) |
| 31 | Steven Githens (University of Cambridge) | JCR |
| 32 | Daphne Ogle (UC Berkeley) | Fluid Project, General Sakai UX, Rethinking resources| |
| 33 | Anthony Whyte (Sakai Foundation/University of Michigan) | Release Management, Security, Community Liaison |
| 34 | John Norman (University of Cambridge) | Sakai Foundation Board Member |
| 35 | Puirta Bristow (University of Windsor) | Observer |
| 36 | Andrew Petro (Unicon, Inc.) | uPortal 2.6 release engineer; looking for alignment with JA-SIG software (uPortal, CAS), generally observing |
| 37 | Charles Severance (University of Michigan) | Presentations, PDA Portal, etc. |
Comments (6)
Oct 02, 2007
Michael Korcuska says:
Given that the last project co-ordination was a bit unwieldy, I'd like to consid...Given that the last project co-ordination was a bit unwieldy, I'd like to consider breaking this into multiple groups, with a joint session at the beginning and/or end to report on outcomes. I don't have a clear idea as to what the two (or more) groups would be...I'm mainly reflecting on the large size of the group in Amsterdam.
One possible grouping is Kernel and Tools. Another is Technical and Requirements.
But before diving into details, I'd be interested in what others thought about splitting up.
Michael
Oct 06, 2007
Aaron Zeckoski says:
I like this idea. I do want to hear what the other groups are doing but we also ...I like this idea. I do want to hear what the other groups are doing but we also need to be able to have discussions that are more focused. It sounds like this would do both.
Oct 02, 2007
Peter A. Knoop says:
In the past we have been both time and space constrained. This time we have two...In the past we have been both time and space constrained. This time we have two full days and multiple rooms available, so I anticipate a roughly half-and-half split between whole-group and topic-specific meeting time. If you have specific topics in mind, please plan to submit a proposal prior to the meeting to allow for discussion and determination of the best topics on which to spend our valuable face-to-face time.
Oct 22, 2007
Marc Brierley says:
On Oct 5, 2007, at 9:25 AM, Marc Brierley wrote to management@collab.sakaiprojec...On Oct 5, 2007, at 9:25 AM, Marc Brierley wrote to management@collab.sakaiproject.org, Re: Save the Date: Project Coordination Meeting, 1-2 December 2007, Newport Beach:
[snip]
> If you have a topic to suggest for the meeting, please plan on sharing a
> description or proposal with this group well prior to the meeting
Perhaps a confluence page could be started to collect these topics and then Michael, Peter and staff could pick the best set?
One thing I would like to suggest is a more efficient way of doing project updates. 2.6 planning should be well underway already, so project teams should be able to at least write down what they are thinking about in the (forthcoming?) "PC-Sakai 2.6 Plans" confluence pages before the meeting. These blurbs could be read before the meeting and specific questions addressed as agenda items. This means PC-Sakai 2.6 Plans should have a deadline so that people could pose those agenda items for this project coordination meeting based on projects' plans.
What do people think?
> to help frame and focus the discussion, and to help determine what is of
> the most interest to everyone for our valuable face-to-face time.
Maybe there could be a chunk of time for specific projects to do planning? (e.g. Michael and I have been batting around having a SAMigo summit.) If we were to have these small meetings, they should probably be on Sunday PM so people who were just interested those meetings won't have to come out too early.
-mARC
Jul 31, 2009
Peter A. Knoop says:
Since most folks were unable to find the time to keep their Confluence pages up-...Since most folks were unable to find the time to keep their Confluence pages up-to-date, we've swtiched for 2.6 to asking activity leads to reply directly to periodic reminder emails with a summary of their plans and status for 2.6. (The first of these reminders went out 24 Oct 2006 and the replies, when they arrive, will be incorporated into the project summary tables in the Management space.) If folks find this method more amenable to sharing information – and do so prior to the meeting – then we should be able to reduce the time we spend on this topic.
Nov 16, 2007
Megan May says:
I would love to see this. Too much time is spent on updates that can easily be...I would love to see this. Too much time is spent on updates that can easily be read beforehand.