Sakai Conference Welcome!

1. Sakai Conference Welcome! June 8, 2005 Joseph Hardin Sakai Board Chair University of Michigan School of Information KYOU / sakai Boundary, Situation

2. Conference Co-Chairs ? John Norman, University of Cambridge Chuck Powell, Yale University

3. Distributed Help Desk aka – Sakai Board Members Ask Them Anything

4. Conference Growth 100% in 6 months

5. How many were there? Chicago, ‘94 Those that are here will remember this one too. We are at a transition point.

6. The Larger Project • Community software, open source • Open Community + Open Source = Community Source • Distributing ownership – incorporation, foundation • How we run that, the Governance Discussion • Community where we can come together

7. So, What is Sakai? • Sakai is a project – an initial grant for two years • Sakai is an extensible framework - provides basic capabilities to support a wide range of tools and services – teaching and research • Sakai is a set of tools - written and supported by various groups and individuals • Sakai is a product - a released bundle of the framework and a set of tools which have been tested and released as a unit • Sakai is a community – an emerging group of people and resources supporting the code and each other, realizing large scale Open Source efficiencies in Higher Ed

8. Supporting the Class Sakai as Course Management System (CMS)

9. Supporting the Lab Sakai as collaboratories - support for online research teams

10. Research Support - Inside Sakai, across the GRID

11. July 04 May 05 Dec 05 Jan 04 "Best of" Refactoring Sakai Project Timeline Activity: Maintenance & Transition from aproject to a community • Michigan • CHEF Framework • CourseTools • WorkTools • Indiana • Navigo Assessment • Eden Workflow • OneStart • Oncourse • MIT • Stellar • Stanford • CourseWork • Assessment • OKI • OSIDs • uPortal • SAKAI 2.0 Release • Tech Portability Profile • Framework • Services-based Portal • SAKAI Tools • Complete CMS • Assessment • Workflow • Research Tools • Authoring Tools • Partner Tools… • SAKAI 1.0 Release • Tech Portability Profile • Framework • Services-based Portal • Refined OSIDs & implementations • SAKAI Tools • Complete CMS/CLE • Assessment Primary SAKAI Activity Architecting for JSR-168 Portlets, OKI services JSFaces, etc. Developing Sakai 1.0 design, Tech Portability Profile. Primary SAKAI Activity Refining SAKAI Framework,Tool development to TPP. Intensive community building/training

12. Sakai Community Support • Developer and Adopter Support • Sakai Educational Partner’s Program (SEPP) • Commercial Support – for and by vendors For - Open-open licensing – open source, open for commercialization By – Fee-based services from vendors include… • Installation/integration, on-going support, training

13. Sakai Educational Partner’s Program The Community directing the Source. • Membership Fee: US$10K per year, 3 years • Access to SEPP staff • Community development liaison • SEPP developers, documentation writers • Invitation to June ’04 Sakai Partners Conference (Denver) • Developer training for the TPP, tool development • Strategy and implementation workshops • Software exchange for partner-developed tools

14. Carnegie Mellon University Columbia University Cornell University Dartmouth College Foothill-De Anza Community College Harvard University Johns Hopkins University Northwestern University Princeton University Simon Fraser University Tufts University UCal, Berkeley UCal, Davis UCal, Los Angeles UCal, Merced University of Oklahoma University of Virginia Yale University In process Boston University, School of Management Cambridge University University of Delaware University of Colorado University of Hawaii University of Washington University of Wisconsin, Madison University of Western Cape, SA University of Melbourne, Australia Community College of Southern Nevada SEPP Members

15. Arizona State University Boston University School of Management Brown University Carleton College Carnegie Foundation for Advancement of Teaching Carnegie Mellon University Coastline Community College Columbia University Community College of Southern Nevada Cornell University Dartmouth College Florida Community College/Jacksonville Foothill-De Anza Community College Franklin University Georgetown University Harvard University Hosei University IT Research Center Johns Hopkins University Lubeck University of Applied Sciences Maricopa County Community College Monash University Nagoya University New York University Northeastern University North-West University (SA) Northwestern University Ohio State University Portland State University Princeton University Roskilde University (Denmark) Rutgers University Simon Fraser University State University of New York Stockholm University SURF/University of Amsterdam Tufts University Universidad Politecnica de Valencia (Spain) Universitat de Lleida (Spain) University of Arizona University of California Berkeley University of California, Davis University of California, Los Angeles University of California, Merced University of California, Santa Barbara University of Cambridge, CARET University of Cape Town, SA University of Colorado at Boulder University of Delaware University of Hawaii University of Hull University of Illinois at Urbana-Champaign University of Minnesota University of Missouri University of Nebraska University of Oklahoma University of Texas at Austin University of Virginia University of Washington University of Wisconsin, Madison Virginia Polytechnic Institute/University Whitman College Yale University New University of Melbourne, Australia University of Toronto, Knowledge Media Design Institute Sakai Educational Partners – April 1, 2004

16. SEPP Development Process Starting a Discussion Group: coordination, transparency

17. Importance of Discussion Groups • Transparency • Coordination • Seed ground of ideas • Competitive filter for ideas – peer review of suggestions • High level chunking of interests and functional relationships • JISC models are helpful here • Spawning ground of Project Teams – where focus is narrowed, and actual development stream begun – using suggestion gathering process, tool design processes from core activities; Sakai Dev Process (see following chart); also where efforts like support are centered (not all activities are software development)

18. Sakai 1.0 Sakai 1.5 Sakai 2.0 Sakai 2.1 Sakai Releases • Enterprise Quality Teaching and Learning, Research and Collaboration Jan 2004 Jan 2005 Jan 2006 Enterprise “suitability” Collaboration Teaching and Learning

19. See SakaiProject.org • Successful Spring Pilot of ETUDES-NG Early Release Completed • IBM and Marist College to Research and Develop on Demand Digital Media Applications for Higher Ed • HarvestRoad, Ostrakon, Sun, Unisys named new Sakai Commercial Affiliates • Sakai, OSPI, and uPortal Convene Over 650 for First Community Source Week – (looks like more to me) • Jutta Treviranus and Ian Dolphin to join the Sakai Board • Open Source Portfolio Release 2 Now Available

20. Successful Spring Pilot of ETUDES-NG Early Release Completed June 6, 2005 Faculty from 17 California Community Colleges Participate The development and future release of the Sakai-based ETUDES-NG software took an important step forward this month, as the first pilot test was successfully led by Project Director Vivian Sinou of Foothill College. The ETUDES-NG Spring pilot consisted of faculty from 17 California community colleges within the ETUDES alliance. Participating alliance faculty spent several months testing an early release of the software, providing key input back to project engineers to assist in its final development. ETUDES-NG currently runs Sakai 1.5.1 plus Melete, a locally developed lesson-building tool. Sinou, Foothill’s dean of Distance and Mediated Learning, is leading the development of the Sakai-based community open-source software product ETUDES-NG, focusing on tools that support teaching and learning. Sinou serves on the Sakai board and is collaborating closely with Stanford University, University of Michigan, Indiana University, MIT, and UC-Berkeley. Foothill-De Anza Community College District received a $600,000 grant from the William and Flora Hewlett Foundation to pursue this innovative project. ETUDES-NG is an online teaching environment based on the Sakai open course platform. Foothill College, the first institution to partner with the Sakai Project, is collaborating closely with the Sakai technical teams, and is building tools upon the Sakai framework to meet the unique needs of its community college members and users. The Sakai Project is a community source software development effort to design, build and deploy a new online teaching environment for higher education. The project began in January 2004. Scheduled for full release in Spring 2006, the ETUDES-NG software will initially serve 30 current Etudes Alliance community colleges. The software will eventually have the capacity to support many more community colleges.

21. ETUDES Consortium – Sakai Pilots College of the Siskiyous Members Outside CA • Stephen F. Austin State University, TX • Harcum College, PA Mendocino College Santa Rosa Junior College Lake Tahoe Community College Vista College Chabot College Laney College College of Alameda Skyline College Foothill College De Anza College Merritt College San Joaquin Delta College West Valley College Porterville College Gavilan College Bakersfield College West Los Angeles College Los Angeles South West Los Angeles ITV Los Angeles City College Los Angeles Harbor College Los Angeles Pierce College Los Angeles Mission College Los Angeles Trade Tech Los Angeles Valley College East Los Angeles College Taft College Antelope Valley College Cerro Coso Community College Crafton Hills College San Bernardino Community College El Camino College Glendale College Long Beach CC Coastline Community College Imperial Valley College Mira Costa College * 300 faculty from 17 community colleges (highlighted in red) from the ETUDES Alliance have committed to a pilot of ETUDES-NG (Sakai 1.5 + Samigo + Melete) in the spring and summer of 2005. Three colleges will go into production in the fall. More to follow in the spring. All colleges will migrate to Sakai by July 1, 2007.

22. IMS Tool Portability Group • To work on ‘interoperability’ between and among CMS’s/CLE’s • Focus is on making tools portable between systems (Sakai, WebCT, and Blackboard) • Established to further the discussion with commercial and other CMS/CLE providers • Will use web services and IFRAMES • Will show working demonstration at the July 2005 Alt-I-lab -Samigo in Sakai, WebCT, & Blackboard

23. ETH Sakai World • Organized and hosted by Swiss Federal Institute of Technology Zurich • Introduction to eLearning • Sakai Overview • Sakai Architecture • Sakai Version 2.0 • With a focus on Quiz and Testing

24. 1st German Sakai Day

25. 1st German Sakai Day • Organized and hosted by the Lübeck University of Applied Science • May 30, 2005 • About 100 participants • Four countries • Six universities • Two companies • Two agencies

26. 1st German Sakai Day • The University perspective • Sakai Overview • Sakai Architecture • Sakai Software • With a focus on Quiz and Testing _____________________________ • Followed by a Quiz and Testing Workshop

27. The Stanford Team • Marc Brierley – Sakai Software • Ed Smiley – Sakai Architecture • Daisy L. Flemming – Quiz and Testing aided in Zurich by • SEPP Senior Consultant Mark Norton

28. Japan Sakai Tour • Hosei University, Tokyo • Nagoya University • Kumamoto University 50-100 at each talk

29. What’s with the hats?

30. (Aside) What’s in a Name? A little history – the Sakai Project had the Chef Project as one of its precursors. Chef = CompreHensive collaborativEFramework We named it that way for fun – we liked the Japanese ‘Iron Chef’ TV show. SAKAI at one time meant: Synchronized Architecture for Knowledge Acquisition Infrastructure – too big a mouthful! Now it is just ‘Sakai’ without all capital letters. It is just a nice word. We like the sound.

31. But, it is also… The name of a famous Iron Chef. (More fun!) It is also (we think): Which has connotations, we are told, of moving across boundaries, of being involved in a complex situation. (Right?) Appropriate for us.

32. So, in the spirit of Sakai: “go ahead and do it.” Let’s talk to him, and find out.

35. Axes of Discussion • Code/Community • Central/Distributed • Members • Framework/Tools/Bundle • Tell someone to do it/Go ahead and do it • Balance Want to spend as little time as possible in big rooms like this – more in discussions with colleagues/peers, co-workers on these issues

36. Thank You Let’s get to it.