Transcript Sakai Community and Technology Update

Introducing Sakai
5th Sakai Conference
ANTHONY WHYTE & PETER KNOOP
SAKAI FOUNDATION / UNIVERSITY OF MICHIGAN
Session Outline
AGENDA
MORNING SESSION
Introduction (8:30 - 9:10 am)
Break (9:10 - 9:20 am)
Processes and practices (9:20 - 10:00 am)
Break (10:00 - 10:15 am)
Getting involved (10:15 - 10:55 am)
Break (10:55 - 11:05 am)
Conference hints, setting up accounts, Q & A (11:05 - 11:45 am)
AFTERNOON SESSION
Introduction (1:15 - 1:55 pm)
Break (1:55 - 2:05 pm)
Processes and practices (2:05 - 2:45 pm)
Break (2:45 - 3:00 pm)
Getting involved (3:00 - 3:40 pm)
Break (3:40 - 3:50 pm)
Conference hints, setting up accounts, Q & A (3:50 - 4:30 pm)
Indiana University’s OnCourse
Sakai Defined
WHAT IS SAKAI?
A COMMUNITY — a growing international alliance of universities, colleges and commercial affiliates
working in open partnership with standards organizations and other open-source initiatives to develop
community-source enterprise-scale software applications to enhance collaboration, research and
teaching within higher education.
A FOUNDATION — the Sakai Project, supported generously by the Mellon and Hewlett Foundations
and a number of founding member universities, has given way to the non-profit Sakai Foundation, a
community-funded and community-sustaining institution fostering innovation and a common, open
approach to software development and distribution.
A FRAMEWORK, TOOLS AND SERVICES — The Sakai Collaboration and Learning Environment
(CLE) is an extensible service-oriented architecture for building and deploying enterprise-scale
collaboration, teaching and research tools and services. Sakai's CLE offers interoperability, reliability
and scalability in a system that is free to acquire, use, modify and distribute.
Sakai Defined
WHAT IS SAKAI?
AN IRON CHEF — the famous Hiroyuki Sakai.
Sakai Community
New Academic Partnerships by Quarter, 20042006 (n=93)
ACADEMIC PARTNERS
100
PARTNERS PROGRAM — The Sakai Partners
Program (SPP) is for institutions and organizations
who have a strategic interest in the success of Sakai
and a desire to participate more fully in community
decision-making and governance.
80
Partners
DIVERSE, ROBUST AND GROWING — since 2004
over 105 universities, community colleges, non-profits
and commercial organizations have joined Sakai as
partners.
60
40
20
0
2004
Q1
2004
Q2
2004
Q3
2004
Q4
2005
Q1
2005
Q2
2005
Q3
2005
Q4
2006
Q1
2006
Q2
Sakai Academic Partners by Region (n=93)
3%
8%
13%
FEES — The membership fee is $10,000.00 per year
for three years for academic institutions, non-profits or
commercial partners. For institutions with a student
base < 3000, the fee is $5000.00.
MEMBERSHIP OPTIONAL — Code 100% free,
membership 100% optional.
76%
Africa
Asia-Pacific
Europe
The Am ericas
Sakai Community — cont.
NON-PROFIT AND COMMERCIAL PARTNERS
Offering consulting and other services to the Sakai
Community in the following areas:
Integration
Implementation
Project Management
Hosting & site maintenance
Custom Tool Development
Portals and OOTB Tools
Standards
Content
Sakai Community — cont.
HOT OFF THE PRESS, 27 MAY 2006
Appalachian College Association (ACA) Selects Longsight for
Sakai Services
The ACA, a consortium representing 35 private, liberal arts
colleges and universities and 39,000 students, has selected The
Longsight Group (http://longsight.com) to provide Sakai hosting
and support services as part of a new initiative.
“[T]he ACA had been providing a shared instance of WebCT Vista
to its members, but wanted to move to a more collaborative, open
source platform and selected Sakai. ‘We also wanted to partner
with a company that would host Sakai for us that understood our
challenges. Longsight was just the company we were looking for.
Longsight understands higher education. They understand open
source. Most importantly, they understand collaboration. The
folks at Longsight have been a joy to work with.’"
Longsight Group
Sakai Foundation
SERVING THE SAKAI COMMUNITY
INCORPORATED — in October 2005 as a member-based, nonprofit 501(c3) corporation.
MISSION — act as a legal entity to manage and protect Sakai’s
intellectual property; serve as a liability shield for community;
provide basic infrastructure and small core staff; help coordinate
design, development and distribution work and act as “court of
final appeal” on issues of contention between work groups.
GOVERNANCE — ten board members elected by community
representatives to serve three-year terms.
BUDGET — annual budget of approximately $1 million (USD)
covering 4-6 staffers, administrative services, computing
infrastructure, conferences, the Sakai Fellows program, outreach
activities.
INCOME — Sakai partner program (SPP) contributions of
$10,000.00 (USD); $5,000.00 per annum (USD) for academic
institutions <= 3000 students.
http://www.sakaiproject.org
Sakai Foundation
PEOPLE
BOARD MEMBERS
Joseph Hardin, University of Michigan
Brad Wheeler, Indiana University
Mara Hancock, UC, Berkeley
Lois Brooks, Stanford University
Vivian Sinou, Foothill College
Ian Dolphin, Univ. of Hull
Jutta Treviranus, Univ. of Toronto
John Norman, Univ. of Cambridge
Charles Severance, Univ. of Michigan
Chris Coppola, rSmart Group
KEY ROLES
Mary Miles, Administrative Coordinator
Lon Raley, Finance Administrator
Wendy Morgaine, Conference Coordinator
Peter Knoop, Project Coordinator
Megan May, QA Coordinator
Lance Speelman, Release Manager
Andrew Poland, Code Repository (SVN)
Clay Fenlason, Documentation, QA
Margaret Wagner, Newsletter Editor
Susan Hardin, sakaiproject.org Coordinator
Charles Severance, Chief Architect
Glenn Golden, Framework Architect
Anthony Whyte, Technical Liaison
Joseph Hardin, Board Chair
Sakai Project
A BIT OF HISTORY, 2003-2005
FOUNDING MEMBERS — the University of Michigan, Indiana
University, MIT, Stanford University in partnership with uPortal
and the Open Knowledge Initiative (OKI).
GOALS — implement Sakai, adopt Open/Open licensing,
share software ownership, contribute 5+ team members under
board direction for two years; build community; secure funding,
achieve sustainability.
FUNDING — $4.4 million by institutional staffing (27 FTEs),
$2.4 million Mellon and $300,000 Hewlett grants, additional
investment through partners.
RELEASES — 1.0 (Oct 04); 1.5 (Mar 05); 1.5.1 (May 05); 2.0
(June 05); 2.0.1 (Aug 05).
ACHIEVEMENTS — a vibrant and growing community, stable
releases, enterprise production deployments.
Sakai 1.0.0
The Open Source Approach
THE APACHE SOFTWARE FOUNDATION MODEL
INDEPENDENT PROJECTS — projects are typically selfgoverning, overseen by Project Management Committees (PMC)
that define rules and processes; projects are managed by
consensus; PMC chairs serve as officers of the ASF board.
VOLUNTEERS — projects rely on individual
possessing different rights and responsibilities.
volunteers
Project
Tomcat
Release
Maven
Release
Logging
Release
Incubator
MERITOCRACY — roles defined on the basis of merit not
affiliation.
SAFE HAVEN — The ASF provides business, hardware, and
communications infrastructure, an independent legal entity where
companies and individuals can donate resources, a legal shelter
for individual contributors and brand protection for the “Apache”
name.
Committer
WSRP4J
Sakai Open Source
Community
THE COMMUNITY-SOURCE MODEL
INSTITUTIONS AND INDIVIDUALS — Sakai
builds upon the successful Apache model by
pioneering a hybrid open-source approach
that relies on the interplay between academic
institutions, commercial enterprises and
individuals to ensure sustainability and
stimulate and advance software development
and distribution.
Indiana
Gradebook
Berkeley
Schedule
Archive
Stanford
RWiki
Sakai CLE
Melete
Release
Portfolio
Cambridge
CONTEXT — Sakai is governed by the values
and specific needs of universities and
colleges.
OSP
Framework
Syllabus
Michigan
Lancaster
Foothill
Project
Provisional Project
Contributed Project
Committer
Foundation Staff
Blog
UFP
SiteStats
Release
Release
Why Choose Sakai?
THE VALUE PROPOSITION
FOR ACADEMIC INSTITUTIONS:
LEVERAGE LEADERSHIP AND INNOVATION — join a dynamic
community harnessing the intellectual capital resident both within
higher education and the commercial community to produce
innovative software solutions.
CONTROL YOUR OWN DESTINY — share in software
development, distribution and ownership and sidestep limitations
imposed by proprietary software licensing.
GET BACK MORE THAN YOU GIVE — achieve economies of
scale and cost savings implicit in inter-institutional cooperation
and collaboration.
Universitat de Lleida
Why Choose Sakai? — cont.
THE VALUE PROPOSITION
FOR COMMERCIAL ENTERPRISES:
ENHANCE BRAND/NAME RECOGNITION — take advantage of the
growing interest in open source software solutions in general and Sakai
in particular to elevate one’s business profile in the marketplace.
GAIN NEW CLIENTS — establish and deepen business relationships
within a growing academic community of Sakai adopters.
GENERATE REVENUE — develop new revenue streams by providing
goods and services to the Sakai community (e.g., implementation and
integration, consulting, hosting and support services, custom tool
development).
Unicon’s http://www.testdrivesakai.net/
Sakai License
EDUCATIONAL COMMUNITY LICENSE
OPEN LICENSING — Sakai’s software is made available
under the terms of the Education Community License (ECL),
a variant of the Apache license.
NO FEES OR ROYALTIES — Sakai is free to acquire, use,
copy, modify, merge, publish, distribute and sublicense for
any purpose provided the copyright notice and disclaimer are
included in all copies of the original or derivative work(s).
NO “COPYLEFT” RESTRICTIONS — unlike the GPL license,
derivative works that are redistributed are neither required to
adopt the Sakai license nor publish the source code as opensource.
http://www.opensource.org/licenses/ecl1.php
WIDE RANGE OF USE — The ECL is designed to
encourage a wide range of use including the production of
derivative work in the commercial space.
Sakai Tools
Upcoming 2.2 release will feature OSP portfolio integration
ENTERPRISE BUNDLE
Announcements
Assignments
Chat Room
Drop Box
Email Archive
Gradebook
Help
Message Of The Day
News/RSS
Preferences
Presentation
Profile/Roster
Resources
Schedule
Section Mgmt
Syllabus
Threaded Discussion
Web Content
Worksite Setup
WebDAV
Universitat de Lleida
Sakai Tools — cont.
PROVISIONAL AND CONTRIBUTED TOOLS
PROVISIONAL TOOLS
Melete (content editor)
Quiz & Tests (Samigo)
Roster
RWiki
SU (Super User admin tool)
Sakaiscript (web services)
TwinPeaks (external repository searching while using the
WYSIWG editor)
CONTRIBUTED TOOLS
Goal Mgmt
MailTool
SiteStats
UserMembership
Foothill College’s Melete
Sakai Distributed Development
SAKAI 2.1: AN INTERNATIONAL INITIATIVE
DEVELOPERS
Individual committers = 36
Academic Institutions = 10
Commercial Partners = 2
Continents = 4
QA
Individuals testers = 52
Academic institutions = 27
Continents = 3
COMMITTER LIST (2006)
Individual committers = 88
University of Cape Town’s Vula
Sakai Enterprise Technologies
TECHNOLOGY STACK
DESIGNED FOR THE ENTERPRISE — Sakai can support
institutions and organizations with user communities in excess
of 100,000.
JAVA — Sakai consists of technologies common to Java
enterprise environments.
APP SERVER — Apache Tomcat
Sakai 2.x
JavaServer Faces
Java
1.4/1.5
Velocity
Spring
Hibernate
Tomcat 5.5
UI FRAMEWORK — JavaServer Faces and Apache Velocity
(legacy tools).
COMPONENT MGMT — Spring
RELATIONAL OBJECT MAPPING — Hibernate
DATABASE — Oracle, MySQL and HSQL (for demos).
Oracle 9i/10g
MySQL 4.1
HSQL (demo)
Apache
SSL
mod_jk
WEBISO
Virtual
hosting
Sakai Component-based Expansion
LOOKING TO THE FUTURE
GET THE FRAMEWORK — download the Sakai Application
Framework (SAF) and install.
SELECT — choose and install tools, supporting services and
database that meets your requirements.
INTEGRATE — connect Sakai to local student and course
information systems (SIS), single-sign-on systems (SSO), etc.
CUSTOMIZE — add local customizations, adjust the look and feel,
choose default language, etc.
DEPLOY — implement a production-ready CLE utilizing tools,
services and other capabilities contributed by members of the Sakai
Community yet tailored to your needs.
Tools
Sakai Framework
Services
Customization
Configuration
Sakai Application Framework (SAF)
SERVICE-ORIENTED ARCHITECTURE
TOOLS
Responsible for Graphical User Interface (GUI);
Built-in persistence mechanisms prohibited
Utilization of SAF presentation services encouraged
SERVICES
Service-to-Service communication via APIs only
(not via data models)
Service
Documented API required
Interface
(APIs)
Presentation agnostic
FRAMEWORK
Registrar for tools and services
Provider of common capabilities
No knowledge of domain objects
Presentation Services (SAF)
Abstract Tool Layout
Tool Code (Java)
Application Services
Common Services (SAF)
Kernel (SAF)
Sakai Presentation Services
JAVASERVER FACES CUSTOM TAG SET
CLEAN & SIMPLE — Sakai provides a custom JSF tag set for developers to use that enforces style guide
compliance, accessibility, internationalization, etc. The goal is to minimize tool code and simplify development of UI
components/widgets.
<sakai:view_container title="#{msgs.sample_title}">
<sakai:group_box
title="#{msgs.sample_one_groupbox}">
<sakai:tool_bar>
<sakai:tool_bar_item/>
</sakai:tool_bar>
<h:inputText
value="#{MyTool.userName}"/>
<sakai:instruction_message
value="#{msgs.sample_one_instructions}"/>
<sakai:date_input
value="#{MyTool.date}"/>
<sakai:button_bar>
<sakai:button_bar_item action="#{MyTool.processActionDoIt}
value="#{msgs.sample_one_cmd_go}"/>
</sakai:button_bar>
Sakai Web Services
AN EVOLVING CAPABILITY
WS Client
Presentation
Presentation
Abstraction
Web Svcs
Axis
Layout
ToDo Layout
Framework
WS End Point
Other Tools
ToDo Code
Application
Other Services
SAF—Common Services
SAF—Kernel
ToDo Service
Service
Interface
(i.e. API)
Sakai in Production
EARLY ADOPTERS
PRODUCTION SCHOOLS
Indiana University
Universidade Fernando Pessoa
Universitat de Lleida
University of Cape Town
University of Michigan
University of California, Merced
University of South Africa
Yale University
PLANNED PRODUCTION RELEASES, FALL 06
Boston University, School of Mgmt
Etudes Alliance (15-21 community colleges)
Lübeck University of Applied Sciences
Portland State University
Rice University
Roskilde Universitetscenter
Rutgers University
Stanford University
University of California, Berkeley
University of Cambridge
Virginia Tech
Sakai Production — cont.
EARLY ADOPTERS: PILOTS
Charles Sturt University
Coastline Community College
Community College of Southern
Nevada
Columbia University
Franklin & Marshall University
Hong Kong University of Science and
Tech.
Johns Hopkins University
Lancaster University
MIT
Moody Bible Institute
Northwestern University
Pacific Lutheran University
New York University
Ohio University
Oxnard College
Stockholms universitet
SURF, Universiteit van Amsterdam
Texas State University, San Marcos
UCLA
Universidad del Valle de Guatemala
University of Arizona
University of British Columbia, Land and Food Systems
University of California, Davis
University of East Anglia
University of Illinois at Urbana-Champaign
University of Missouri
University of Nebraska-Lincoln
University of North Texas
University of the Pacific
University of Virginia
Universiteit Twente (Fall 06)
Walsh University
Whitman College
Wofford College
Sakai in Production — cont.
A FEW NUMBERS
INSTITUTION
USERS
WEB
SITES SERVERS
Indiana*
121,468
53,979
UNISA
92,000
Michigan
67,281
Yale
14,569
17,453
16
PeopleSoft
4
Novell, ActiveDirectory
8
UMIAC, Kerebos
4
Banner, CAS
2
PeopleSoft, Novell Nsure
Banner, uPortal
Fernando Pessoa
5,250
2,000
UCT
4,040
48
Etudes Alliance**
2,560
79
UC, Merced
1,230
305
1
308,398
73,864
34
Totals
SYS
INTEGRATION
*Indiana University: as of Feb. 2006, 108,190 users have accessed OnCourse CL.
**Etudes Alliance: 15-21 community colleges, 15,000 students, 450 sites (F 06).
Yale University’s classes* v2
Sakai at the University of Michigan
CASE STUDY: CTOOLS TECHNOLOGY STACK
APP SERVER CLUSTER
8 X Dell PowerEdge 2650, dual 2.4-3.2 GHz CPU 32 bit, 4 GB RAM
Red Hat Enterprise Linux (RHEL-AS3)
Apache 1.3/cosign/mod_jk
Tomcat 5.5.x
Java 1.4.2
Sakai 2.1.2
Bandwith allocation 1 Gbps
AFS: 1 TB file storage
DATABASE CLUSTER: PRIMARY & REPLICATED
2 X SunFire V480, quad 900 MHz CPU 32 bit, 20 GB RAM
3 X StorEdge 3310 SCSI RAID Arrays w/12 73 GB disks
Solaris 8
University of Michigan’s CTOOLS
Sun RAID Mgmt tools
Oracle 10g
Standby mode (replication server)
LOAD BALANCERS: PRIMARY & FAILOVER
Bandwith allocation 1 Gbps
2 X NetScaler RS9800 Secure Application Switch,
Tape backups, off-site storage
High availability, 10/100/1000 Mbps copper, 1 GB Mem
Sakai at UNISA
CASE STUDY: MySQL & STRUTS
MySQL — first production release of Sakai running MySQL
4.1. Worked closely with Rutgers and other members of the
community on MySQL performance tuning and query
optimization.
STRUTS TOOLS — leveraging local expertise, UNISA
utilized Struts rather than JSF to build a set of locally
produced Struts-based tools fully supported by the Sakai
application framework.
SERVER ENVIRONMENT — 4 X HP ProLiant DL380 G4
rack mount servers, 2 X 3200Mhz CPU, 2 GB RAM, 1 GB
Ethernet configured as follows:
2 X Diskless Nodes (CentOS 3.3, Apache 2.0.46, Java 1.4.2,
Tomcat 5.5.12, Sakai 2.0.1)
1 X Fileserver/NFS/MySQL/DHCP/DNS (CentOS 3.6)
1 X LinuxVirtualServer Load Balancer
2 X Intel Xeon 2 X 2.4 GHz, 4 GB RAM provide additional
diskless nodes.
University of South Africa’s myUNISA
Sakai at UC Merced
CASE STUDY: uPortal INTEGRATION
OOTB STRATEGY — UC Merced adopted an “out of the
box” configuration strategy to simplify Sakai/uPortal
integration and shorten their rollout time frame.
PORTAL — Sakai is integrated as a single portlet (iFrame
in this case). The portal has no awareness of course
rosters and roles. Merced’s UCB Mail is exposed via an
iChannel portlet rather than a JSR-168 portlet.
SIS INTEGRATION — to simplify deployment UC Merced
chose to limit integration with their Banner student
information system to Sakai only.
University of California, Merced
The Future (short-term)
NEW TOOLS, SERVICES AND TECHNOLOGIES
Blog
JForum
IMS Tool Interoperability
MailTool
Message Center
Multipoint Audio/Video
PostEM
Sakaibrary
Shared Display
Shared Whiteboard
TwinPeaks Refinements
Pluggable WYSWIG
RSS
Accessibility improvements
Hierarchy
Course Management
Portal-friendly Tool Id URLs
Section Awareness
Unit Test Framework
JSR-168 Portlet
WSRP Consumer
WSRP Producer Portal
Lancaster University’s Shared Whiteboard
The Future (mid-term)
NEW TOOLS, SERVICES AND TECHNOLOGIES
Sakai/uPortal integration
Enhanced LAMS integration
SCORM support
IMS Content Packaging Import/Export
IMS Common Cartridge
JSR-170 Java Content Repository
Lucene
Resource Description Framework (RDF) support
OWL Web Ontology Language support (Semantic Web)
Sakai-LAMS Integration, 2005
The Future (long-term)
INTEROPERABILITY AND DATA PORTABILITY
Personal
Learning
Environment
Portal
Environment
Agile
Development
Collaboaration
Environment
Authoring
Environment
Enterprise
Directory
Student
Information
Content
Management
Data
Repository
Sakai DGs and WGs
SELF-ORGANIZING PRINCIPLE AT WORK
DISCUSSION GROUP (DG) — foster both communication on particular
topics and work project incubation.
DG LIFECYCLE — chartered initially for one year; inactive groups are
retired and archived.
DG FORMATION — draft proposal, recruit >= five participants, designate
leader to facilitate discussion, set up Collab/Confluence workspace,
coordinate activities with Board.
WORK GROUP (WG) — usually formed by members of one or more DGs to
concentrate effort on specific projects.
WG LIFECYCLE — finite; defined by charter.
Gradebook WG Planning Space
WG FORMATION — draft charter, secure funding, designate project leader,
define scope of work, work up schedule, set up Collab/Confluence
workspace.
Sakai DGs and WGs — cont.
SOME EXAMPLES
DISCUSSION GROUPS
Accessment Tools
Content and Authoring
Development
Enterprise
European Sakai Community
I18N & L10N (internationalization)
Library & Repositories
Migration
Production
Strategy and Advocacy
User
User Interaction (UI)
Web Services
Web Video and Audio Tools
WORK GROUPS
Accessibility
Community Practices
Course Mgmt
Default Skin
Framework
Gradebook
JSF
Licensing
Programmer’s Cafe
Requirements
QA
SCORM
UI Design Stds
Web services
DG: European Sakai Community
“. . . facilitates communications among those
in Europe who are Sakai users, who are
interested in Sakai projects, and who may
be interested in the discussion of pedagogy
and technology. One of the goals is to assist
participants in their European-specific
applications of education technology in
European universities. The communications
should encourage collaboration among
European users, including informal meetings
and conferences. . . .”
Sakai Community Practices
ARTICULATING A COMMON APPROACH
OBJECTIVES — the creation of a set of community
practices that are specific, consistent, transparent,
comprehensive, maintainable and sustainable.
SCP Panel Discussion
Thur, 1 June
10:15-11:15 AM
Rm Jr D
OVERSIGHT — the development of a set of published
Sakai community practices is overseen by the Sakai
Community Practices (SCP) work group.
The SCP
coordinates the process wherein practice documents are
generated and approved by the community.
RFCs — proposed practices are always put out for public
comment and your input is crucial to the process.
PRACTICES — Sakai Software Organization (approved),
Criteria for Provisional Status, Group Management Process,
License Management (approved), Sakai Fellows.
SCP milestones
Sakai Collab
COMMUNITY COLLABORATION SITE
JOIN DGs/WGs — create an account and join
Sakai Discussion Groups and Work Groups.
DOCUMENTS — download documents and other
resources.
EMAIL — select email delivery preferences.
PROJECTS — create project sites to support
community efforts.
DEMO — try out tools & other capabilities.
Sakai Collab
LOCATION — http://collab.sakaiproject.org
Sakai JIRA
ISSUES TRACKING, WARTS AND ALL
BUGS — create, assign, track and resolve.
FEATURE REQUESTS — logged and tracked.
RELEASE NOTES — known issues, enhancements, fixes
posted.
REQUIREMENTS — use cases defined and promoted.
CONTRIB AND OTHER PROJECTS — teams developing
new tools, documentation, etc. and who wish to take
advantage of JIRA’s powerful capabilities are welcome to
create a JIRA project to manage their work.
http://bugs.sakaiproject.org
Sakai Requirements Process
POLLING THE COMMUNITY
PURPOSE — gather and prioritize community requirements
and general use cases. Requirements submission and polling
is open to all members of the community. An iterative process,
requirements polling will likely precede work on each major
Sakai release (itself an annual event).
PROCEDURE — use cases submitted to JIRA “Requirements”
project; duplicates consolidated and language refined by
members of the Sakai Requirements WG and original
submitters. The first round generated 385 requirements.
POLLING — two polls held; one community-wide followed by a
second canvassing the priorities of Sakai partner reps. Results
available at: https://sakaiproject.org/requirements/results.php
MATCH-MAKING — Sakai Project Coordinator attempts to
match high priority items with volunteer teams of developers.
Requirements Voting Results
Sakai Requirements Process — cont.
EXAMPLES
REQ-26 Emails Should Contain Site URL and Item URL
REQ-65 Email Archive should be deep-linkable/bookmarkable
REQ-109 Search across site and sites
REQ-124 Add SCORM Player to Sakai
REQ-129 Support for Learning Design and other Work Flow Engines
REQ-159 Graphical content in rich text editor
REQ-173 Chat should allow users to search for messages from a particular user
REQ-282 Users should have more information and control over site import
REQ-375 Timed Release of documents/files in Resources tool
Discussion: Sakai Requirements
Wed., 31 May 2006
3:00 - 4:30 PM
Rm Jr D
Speakers: Mara Hancock, Peter Knoop, Aaron Zeckoski
Sakai Confluence
COMMUNITY WIKI
WORKSPACES — Discussion Group, Work Group, Project team
planning, discussions and documents.
DOCUMENTATION — Sakaipedia, release information, code
documentation, community practices, production information.
MANAGEMENT/PROJECT COORDINATION — important dates,
status summary, activities directory, project teams, meeting times
LOCATION — http://issues.sakaiproject.org/confluence/
Project Mgmt & Coordination Space
JIRA/Confluence
CREATE AN ACCOUNT AND PARTICIPATE
http://bugs.sakaiproject.org/jira/secure/Signup!default.jspa
Getting Involved in the Community
VOLUNTEERS AND RESOURCES REQUESTED
COMMUNITY PROCESSES — contact Mark Norton, Sakai Community Process WG Chair
([email protected]).
DEVELOPMENT — join Sakai-Dev DG; review existing projects, requirements, feature requests or contribute new
tools and/or services; contact Peter Knoop, Project Coordinator ([email protected]), or Anthony Whyte, Sakai
Technical Liaison ([email protected]).
INFRASTRUCTURE — QA servers, JIRA/Confluence hosting, contact Peter Knoop.
QA — join QA Work Group, contact Megan May, QA Coordinator ([email protected]).
REQUIREMENTS & USE CASE DEVELOPMENT — join the Requirements WG; contact Mara Hancock, REQ WG
chair ([email protected]).
5th Sakai Conference
SEA TO SAKAI, COMMUNITY SOURCE WEEK
DATES — Sakai and OSP, 30 May - 2 June 2006; uPortal, 4-6 June 2006
KEYNOTE — Mitchell Baker, Mozilla
TRACKS — Faculty, Community, Implementation, Multiple Audiences,
Technology.
BOFs — “Birds of a Feather” sessions; informal gatherings on topics of
interest to members of the community
TECHNOLOGY DEMOS — new ideas, new applications.
SCHEDULE — http://sakaiproject.org/conference/schedule.html
PODCASTS, SLIDES — http://sakaiproject.org/conference/wiki.html
TAGS (Flicker, del.icio.us) — SakaiVancouver06
Vancouver Conference Wiki Space
5th Sakai Conference — cont.
SEA TO SAKAI, COMMUNITY SOURCE WEEK 30 MAY - 6 JUNE 2006
http://www.sakaiproject.org/
ENJOY THE CONFERENCE!