Presentation is loading. Please wait.

Presentation is loading. Please wait.

OSAF Directors Meeting February 10, 2003. Agenda Product Organization Community Higher Education Initiative Mozilla.org Discussion Patent Issues Other.

Similar presentations


Presentation on theme: "OSAF Directors Meeting February 10, 2003. Agenda Product Organization Community Higher Education Initiative Mozilla.org Discussion Patent Issues Other."— Presentation transcript:

1 OSAF Directors Meeting February 10, 2003

2 Agenda Product Organization Community Higher Education Initiative Mozilla.org Discussion Patent Issues Other Updates

3 Product Update

4 Chandler in a Nutshell Open Source Personal Information Manager –Email, calendar, contacts, tasks, free-form data –Easy sharing of all information Next generation information management platform

5 Deployment Cross-platform application: Macintosh, Linux, Windows Local and remote access to data Peer-to-peer and server-based Architecture extensible to PDA’s and phones

6 Openness Public Availability of Source Code Built on Open Source Components Python, wxWindows, OpenSSL... Using Open Standards iCalendar, RDF, Jabber... Free and Commercial Licenses Goals Catalyze a new software ecology Jump-start innovation

7 Target Users Early Adopters –PIM fanatics –Users with heavy email and calendar needs –Outlook refugees Initial Institutional target: higher education –Ongoing discussions –Possible foundation support

8 Data Model: Items Chandler inherits the spirit of Lotus Agenda Everything is an item: –Email message, event, contact, task, attachment, web page, note... Items have properties & a payload –Universal: creator, last modified, person, group, project, topic... –Specific: Home telephone, start time, recipient... –User-defined: status, urgency... Items can be linked, annotated, dynamically grouped into views Schema (in RDF) –used to represent item types, properties, and their relations

9 Storage Model: Repository Items are held in a repository –Item histories maintained Repository may be local or remote, either in a peer PC or on a server Repositories are automatically synchronized in whole or in part

10 User Interface: Views View is formed by a query on a repository, which returning an item or set of items View formats include table, outline, address card, calendar columnar view, various detail views To the user each view generates a page Web-style navigation: local and remote access via URI, forward and back buttons, bookmarks

11 Innovations Fast, convenient search Automatic recognition of names, dates, locations Transparent, robust security Integrated instant messaging and presence management –Opportunistic scheduling

12 Sharing Repository browsing – Look up a contact or see a calendar – Access a shared document Subscribe to external data source –Add class schedule to my calendar –Automatic updates of contacts Public & private data

13 Extensibility Plug-ins – transports, parsing, indexing, spam and virus handling, view types, etc. Scripts, filters, and agents UI customization Schema evolution

14 Status Architecture, design, coding all underway 13 full-time staff (9 paid, 4 volunteer) Significant input from community contributors Early alpha release April, 2003

15 Chandler Architecture Database (e.g. BDB) Indexes/ Full Text Parcels Core Chandler App e.g. Prefs Full-text Search API Introspection Agent Framework Language Parsing Engine Web Servlets PDA Sync & services HTML Engine Table Widget Media Handlers HTML, Image, Sound, etc. Canvas Viewer Parcel API Sample View Projects Email Contacts Tasks Calendar Middleware Server Networking EmailWebLDAPFTP Client Jabber RDF Schem a RDF Object s Query Extensible RDF Schema Management Authorization¿Replication? Garbage Collection/ Compaction Versioning Transactions Server Intelligence Repository Access Protocol TBD Protocol Documents Python Obj Cache RDF Access User-Defined Calendar ¿Resource Discovery? ? ?

16 Deployment Scenarios Server + Server Intelligence PC-centric Personal PCCampus Server Server + Server Intelligence Kiosk Middleware + Client Campus Server Server + Server Intelligence Server + Server Intelligence Personal PC Middleware + Client Middleware + Client PC within campusKiosk-mode within campus

17 Organization

18 Current Headcount: 13 (9 employees, 4 volunteers, 1 contract consultant) Open Positions –Development Manager –Security Developer –Graphic and Interaction Designer Additional Hires Planned for2003 –QA Manager, 2 Developer/Designers

19 Developers and Staff John Anderson Andy Hertzfeld Morgen Sagen Katie Capps Parlante Jed Burgess Rys McCusker Lou Montulli Aleks Totic Mitchell Baker, Community Chao Lam, Product Management Pieter Hartsook, Marketing Specialist Jurgen Botz, Information Systems

20 Higher Education Initiative

21 Background Andrew W. Mellon Foundation mission in higher education Mellon IT funding initiatives at MIT, Dartmouth, etc. led by Ira Fuchs Fuchs invited OSAF to meet members of Common Solutions Group (CSG), consortium of major research universities CSG has critical calendaring needs

22 Action Plan Two full-day meetings established mutual interest in CSG-OSAF collaboration OSAF has submitted application for three month planning grant to develop requirements for “Chandler on Campus” Intent is to get Mellon funding for follow-on implementation phase Universities to become first organizational deployment target

23 Patents IP mine field (no news here) Biggest external threat to OSAF (and other OS projects) Time for joint action? Need Board guidance

24 Other Updates Facilities –Move planned this summer to 543 Howard St., San Francisco –Share space & staff with other Kapor-Klein entities Marketing / Pulbic Relations –Engaging sparkPR for more leveraged and consistent public image


Download ppt "OSAF Directors Meeting February 10, 2003. Agenda Product Organization Community Higher Education Initiative Mozilla.org Discussion Patent Issues Other."

Similar presentations


Ads by Google