r4 - 29 Jun 2005 - 16:30:49 - LisaDusseaultYou are here: OSAF >  Journal Web  >  TWikiUsers > LisaDusseault > LisaDusseaultNotes > LisaDusseault20050127
This is a draft of a ChandlerServerProject? page to live in the main part of the Wiki shortly

Chandler Server Project

The Chandler Server Project is an effort to develop a server that can host Chandler sharing for a workgroup of users up to hosting 10000 users. We plan to base the Chandler server on Slide and contribute useful extensions back to Slide wherever possible.

People

Scheduled Work

The server development will not follow the Chandler milestones and release cycle, being more constrained by Slide release schedules. However we can speak of goals relating to the same timeframes as Chandler milestones. The currently scheduled work is for the 0.6 timeframe.

Our goal for Chandler sharing for the 0.5 timeframe is to make sure that it works, identify client or server bugs and document how people can use Slide with the 0.5 Chandler client.

  • See my notes 1,2 about trying to install and use Slide on Windows XP. -- HeikkiToivonen - 28 Jan 2005

For the 0.6 timeframe, sharing should be TODO. This implies that we need to help people download Slide, install it and configure it such that it's suitable for use with the 0.6 Chandler client.

Task Status Milestone sort
With IT -- install and configure Slide server for client testing started 0.4.07?
Test and document Slide installation and configuration for use with Chandler not started 0.4.08
Revise and publish Slide usage information for Chandler workgroups not started 0.4.09

Early investigations:

  • how easy is it to create accounts in Slide?
  • What configuration might need to be done to make Slide work best with Chandler? Strong ETag support is default?

Planning for 0.6

Design's 0.6 planning page? has some tasks for Chandler client sharing. How do server goals fit into this?

  • What kind of account creation and privilege administration will we need for 0.6?
  • Can the server help provide a way to map email addresses to WebDAV account names?
  • What would make Slide easier to install?
  • Does anybody have Slide scalability numbers, so that we can know whether and when to work on improving scalability?
  • start coordinating with ISAMET and other Slide CalDAV implementors
  • Can Slide already handle user accounts and quotas?

Related pages and sites

Outside resources

Chandler planning, feature, project pages

Unplanned features

These are features we envision being very useful in Chandler sharing but we haven't yet specified or chosen release dates to include these features

  • Allow support for extranet sharing
    • possibly through adding support for tickets
    • Alternatively, consider other functionality e.g. certificate sharing
  • CalDAV support -- already in progress
  • Is there something the server can do to provide sharing status to a bunch of people on a share?
  • Account sign-up
    • Web page sign-up for account (a la www.sharemation.com)
    • Protocol for automated client signup for account?
  • Implement quota draft
  • Bandwidth limiting and metering enforcement?
  • User directory (LDAP) integration?
  • Advanced authentication -- SASL, Shibboleth?
  • ServerProductPlanning (lots more feature ideas)

Non-feature work

  • Publish ideal requirements to act as "Chandler Sharing Server" so that commercial implementations can be compared
  • Investigate hosting requirements, next steps, hurdles (backup/restore, fault-tolerance, account disablement, diagnostics, handling forgotten passwords)
Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r4 < r3 < r2 < r1 | More topic actions
 
Open Source Applications Foundation
Except where otherwise noted, this site and its content are licensed by OSAF under an Creative Commons License, Attribution Only 3.0.
See list of page contributors for attributions.