Skip to end of metadata
Go to start of metadata

Time and Location

Project Coordination sessions will run from 9am - 4pm on Sunday, June 13, and start in Grand Mesa A (2nd floor). There will be coffee in the morning and boxed lunches at noon.

On Friday the sessions will run from 9am - 2pm, and will start in Grand Mesa A (1st floor). There will again be coffee and boxed lunches.

There will be rooms reserved for Project Coordination Meetings bracketing the 2010 conference in Denver: on Sunday, June 13 and Friday, June 18. These will be working meetings focused on the planning and coordination of Sakai development work.

We are also prepared to help make windows of time and space for smaller working meetings on Monday and Thursday, where they will be useful or where travel schedules may interfere with the other two days.

Specific Goals

  1. To have a clear 2.8 release plan proposal (with scope, resource plan, calendar, etc.) available for public comment by the end of the conference
  2. To acquire clear institutional commitment of resource to deliver on this plan (and if adequate resource cannot be recruited, to alter the plan accordingly)
  3. To achieve (1) and (2) for Sakai 3 as well

Guidelines

  1. Things don't get decided at the project coordination meetings, they get worked up into proposals to go on-list. No one should feel that they have to attend a particular project coordination session in order to have a voice on a given topic. We just use the sessions to make rapid, f2f progress toward concrete proposals that include a diversity of perspectives. They are not the last word.
  2. The sessions are meant to be working meetings that make progress toward some practical consensus. Debate that is not leading that direction may be tabled or directed elsewhere.
  3. In order to keep the sessions productive, a certain baseline of familiarity with Sakai and its processes - the kind possessed by those active in Sakai development and its release processes - is assumed. Those new to Sakai may find it hard to follow along, and other sessions throughout the conference (especially the orientation sessions on Monday) may be more appropriate.

Topics

Specific Agenda TBD

A more detailed agenda will emerge in discussion with working groups in the weeks leading up to the conference. A number of these sessions should be organized and led by particular working groups.

  1. 2.x planning
    • Maintenance team
    • Functional scope: feature additions, deprecations, etc.
    • Security
    • QA resource planning
  2. Sakai 3 project planning
    • Roadmap and project plan
    • Front-end development coordination
    • Nakamura coordination
    • Deployment strategies (whether migration or otherwise)
    • Sharing and coordinating parallel and/or satellite projects

Attendees

If you are thinking about attending, please add your information below.

Likelihood you Will Attend: (tick) = 100%

 

Name

Organization

What you will want to work on

Sunday

Friday

Available Monday or Thursday? Please comment

1

Clay Fenlason

Sakai Foundation

2.8 release and S3 project planning, and anything else I'd be helpful for

(tick)

(tick)

I'm committed to meetings on Monday, but can be available Thursday afternoon.

2

Michael Feldstein

Oracle

Preference for S3, but wherever I'd be useful

(tick)

?

Sunday afternoon for sure; possibly an hour or two on Friday before flight; Thursday is also open.

3

Steve Swinsburg

ANU

2.8 planning, maint team

(tick)

(tick)

Not available Mon or Thurs

4

David Horwitz

UCT

2.8 planning, maint team

(tick)

(tick)

 

5

Jean-François Lévêque

UPMC

2.x committee (release sub-committees, projects status ...), i18n

(tick)

(tick)

?

6

Lance Speelmon

Indiana University / Sakai Foundation

Entity Picker (more support in tools, revisit UX), 2.8 Hybrid code, S3

(tick)

(tick)

Monday: yes. Thursday: afternoon only.

7

Eli Cochran

U.C. Berkeley

S3 front-end dev

(tick)

(tick)

Monday: yes, Thursday, yes

8

Ray Davis

U.C. Berkeley

S3 dev

(error)

(tick)

Monday: no, Thursday, afternoon only

9

Stuart Freeman

Georgia Tech

S3 dev/qa

(tick)

(tick)

 

10

Carl Hall

Hallway Tech / NYU

S3 dev

(error)

(tick)

Monday: afternoon only, Thursday: yes

11

Daphne Ogle

UC Berkeley

S3 design & planning

(error)

(tick)

Can be available Thursday afternoon and Friday most the day

12

John A. Lewis

Unicon

General

(tick)

(tick)

Monday: Yes, Thursday: after closing sessions, Yes

13

Nate Angell

rSmart

2.8 release and S3 project planning, and anything else I'd be helpful for

(tick)

(tick)

Monday: Yes, Thursday: after closing sessions, Yes

14

Joshua Baron

Marist College

S3 design from a teaching and learning perspective

(tick)

(tick)

Monday morning is a possibility as is Thursday after the close of the conf.

15

David Goodrum

Indiana University

S2, S3 and Hybrid targets, planning, and coordination. S3 design from a teaching and learning perspective

(tick)

(tick)

Monday: Afternoon. Thursday: Yes.

16

Lynn Ward

Indiana University

S2, S3 and Hybrid targets, planning, and coordination. S3 design from a teaching and learning perspective

(tick)

(tick)

Monday: afternoon only; Thursday: after 2:30pm.

17

Jacques Raynauld

HEC Montréal

S2 2.8, Open Syllabus, Entity Picker, S3 (including structured pages and guided portfolios)

(tick)

(tick)

Monday, Thursday and Friday Morning

18

Kirk Alexander

UC Davis

2.8, S3, Gradebook 2 and independent release strategies

(tick)

(tick)

Monday, Thursday, Friday morning

19

Lydia Li

Stanford University

2.8, S2/S3 hybrid mode

(error)

(tick)

Monday, Thursday, Friday morning

20

Oliver Heyer

UC Berkeley

S3 project planning

(tick)

(tick)

Monday, Thursday afternoons

21

Megan May

Indiana University

Project Planning and coordination.   2.X (particularly A2 roadmap), S2/S3 hybrid mode, Entity Picker, S3 plans regarding assessment

(tick)

(tick)

Available Monday and Thursday afternoon

22

Jonathan Cook

Indiana University

Project Planning and coordination

(tick)

(tick)

Possibly available Monday and Thursday afternoon

23

Karen Watkins

Indiana University

Project Planning and coordination.   2.X (particularly A2 roadmap), S2/S3 hybrid mode, Entity Picker, S3 plans regarding assessment 

(tick)

(tick)

Can be available Monday and Thursday afternoon

24

Sara Chambers

Indiana University 

Project Planning and coordination.   2.X (particularly A2 roadmap), S2/S3 hybrid mode, Entity Picker, S3 plans regarding assessment 

(tick)

(tick)

Can be available Monday and Thursday afternoon 

25

Seth Theriault

Columbia University

2.8, maint team, security

(tick)

(tick)

Monday: yes, Thursday, yes

26

Makoto Tsuchitani

Stanford University

2.8 release and S3 project planning

(tick)

(error)

Monday: yes, Thursday, yes

27

Keli Amann

Stanford University

S3 project planning

(error)

(tick)

Monday: afternoon, Thurs, yes

28

Stephen Marquard

University of Cape Town

S2 and S3

(tick)

(tick)

Yes except if overlap with Board meetings

29

Zach A. Thomas

Aeroplane Software / NYU

S3

(error)

(tick)

Monday: no, Thurs: yes

30

Anthony Whyte

Sakai Foundation

S2 (2.8, 2.7.1, 2.6.3) maintenance team, security, release management, indie release strategies/review, infrastructure support

(tick)

(tick)

I'm committed to meetings on Monday

31

Noah Botimer

University of Michigan

 

(tick)

(tick)

Available Mon/Thurs, depending on emergent obligations

32

Alan Berg

Sakai Foundation

QA, automation, process improvement

(tick)

(error)

Available Mon/Thurs, depending on emergent obligations

33

Lovemore Nalube

University of Cape Town

S2.x, S3 dev

(tick)

(tick)

Thursady: Only after Course Evaluations BoF

34

Oszkar Nagy

University of Cambridge - CARET

S3 front-end dev

(tick)

(error)

Available on Thursday as well

35

Shoji Kajita

Nagoya University (Japan)

i18 and l10n for S2 and S3

(tick)

(error)

Available Monday and Thursday, depending
on subjects

36

Philip Uys

Charles Sturt University, Australia 

Sakai 3 design, planning and development

(tick)

(tick)

also available Monday afternoon and Thursday afternoon (pending meeting of the T&L Group)

37

David Haines

University of Michigan

Sakai 3 and Sakai 2

(tick)

(tick)

 

38

John Norman

Cambridge

Mostly Sakai 3

(tick)

(tick)

 

39

Matt Morton-Allen

Charles Sturt University, Australia

Sakai 3 planning

(tick)

(tick)

 

40

Yoshihiro Ohta

Nagoya University (Japan)

i18 and l10n for S2 and S3

(tick)

(error)

Available Monday and Thursday, depending
on subjects

41

Raul & David

Universidad Politecnica Valencia (Spainn)

i18 and l10n for S2 and S3

(tick)

(error)

 

2 Comments

  1. IU and HEC Montreal have been discussing lately the need for deep hyperlinks to more entities (e.g. individual assignments, forums, etc)within Sakai 2.x. While the latest S23 hybrid work is exciting and allows for custom workflows, we really need to be able to deep link into tools and not just embed entire tools on a page. This work would serve a dual purpose of making S23 hybrid integration more seamless while at the same time making Sakai2 a more usable system. We would like to use some meeting time to discuss this idea with more community members and develop a plan for development. I believe this means (in one form or another) adding more Entity Broker support to tools and revisiting the Entity Picker UX to make it more refined and work across the Sakai2/3 boundary.

    1. I've done something along these lines in Profile2 with EntityBroker, allowing deep linking. Available to discuss this further at the conference.