Archive for the 'OSAF' Category

Feeds: RSS | Atom

Preview!

September 11th, 2007 at 10:15 pm (8 months, 1 week ago) by Katie Capps Parlante under Chandler Desktop Development, Chandler Hub Service, Chandler Product News, Chandler Project, Chandler Server Development, OSAF

I’m pleased to announce that the Chandler project has hit our Preview milestone! We now have public-beta quality releases of our products; we believe them to be full featured enough and stable enough for daily use. Check out a full overview of features (including screenshots and screencasts). Download Chandler Desktop, create an account on Chandler Hub. Check out the source. Get involved in the project, help us build a really great 1.0 release.

Chandler Desktop
We released 0.7.0.1 of the Chandler Desktop yesterday, September 10. (In the spirit of responding to user feedback quicky, we fixed a problem with the release found by a user before we made the announcement).

Chandler desktop adds a central dashboard for managing tasks, notes, events, and messages to the basic calendar functionality found in the 0.6 release. You can share calendars, task lists, messages and notes in collections that can hold whatever you choose to put in them, regardless of data type. The performance has improved greatly, the application has basic search functionality, and now there’s a way to to manage and resolve conflicts on shared data. You can collaborate on individual items via email with the ability to edit and update messages you’ve already received or sent. Although Chandler Preview is not meant to replace your email application, you can configure your IMAP account so that Chandler can see some messages from your regular mail client.

We’re currently planning a 0.7.1 release in about a month, to quickly iterate on the Preview release. We’ll make use of user feedback to identify problems and drive priorities.

Chandler Hub
We upgraded Chandler Hub to the 0.7.0 release of Chandler Server on August 27th.

The latest release of Chandler Hub also adds a dashboard for managing tasks (and other kinds of data) to basic web calendaring features. Friends and family can access shared collections from the web without having to create an account or log in. We’ve focused on workflows that let desktop users share data with others using the web; this release is a major step towards realizing the full Chandler vision on the web as well as the desktop.

We’ll be upgrading the service with small fixes on a weekly basis for the next month or so, fixing minor glitches and adding support for Safari.

Chandler Server
The Chandler Server 0.7.0 release is available for download as a ready-to-run bundle. We’ll be creating 0.7.x releases as we improve the Hub service. In parallel, we’re working on a 0.8 release that is focused on interoperability with other calendar applications and services such as iCal, Google Calendar and Evolution.

Try out Chandler
We believe you can now feel confident putting your data in Chandler. We have migration features to make upgrading easier, and will do our best to support people if they run into problems. (The chandler-users@osafoundation.org mailing list is a great forum for support). These releases do have some bugs and rough edges, so Chandler might not yet be appropriate for mission critical uses. We are using the desktop and hub internally day to day for our office calendar, personal calendars, personal project management, and several small group task lists. We hope you’ll join us using Chandler — let us know how you like it! We’ll use your feedback to make a better 1.0 release.

Get Involved
One of our goals for this Preview milestone is to grow outside involvement with the project. We want users to log bugs. We want designers to collaborate with us on ideas. We want developers to submit patches fixing bugs that annoy them, create desktop plugins with their favorite features, and write clients that take advantage of their data on the server. Check out how to get involved.


Chandler Hub as an open service

August 30th, 2007 at 11:00 am (8 months, 2 weeks ago) by Jared Rhine under Chandler Hub Service, Chandler Project, Chandler Server Development, Community, OSAF

The Chandler Project is running an open service named Chandler Hub. Or at least, that’s what we’ve been telling ourselves.

The term “open service” does not have the clear definitions and history of its cousins “open source” and “free software“. We’re trying to figure out, just like everyone else, what it means to be an open service.

There has been a recent surge of chatter about “open services“. The current focus seems to have two branches: 1) attempts to define the term “open service” and 2) discussion of the impact of closed services to the larger Internet public good. This surge was probably triggered by Luis Villa’s recent work for the GNOME Online Desktop project. Luis takes care to catalog excellent references to earlier work as well. There’s a healthy conversation on the Open Knowledge Foundation’s okfn-discuss mailing list, where Rufus Pollack just posted a draft of an open service definition.

How the new titans of web services approach the openness of their offerings has an importance it did not have five years ago. Tim O’Reilly has promoted the view:

…the fundamental challenge of the Web 2.0 era may not be free software but free data, and the right of users to view, delete, modify, or freely transfer to a competing service the data that is stored about them in centralized databases…

OSAF (the Open Source Applications Foundation) with its Chandler Project and related hosted service Chandler Hub, seems positioned within both these areas: free/open software as well as free/open data. The ideals of freedoms and the public good are embedded in OSAF’s DNA and our self-standards are high. We would love to hear about areas we can improve.

A persistent criticism of many of the most popular web services is “Where’s the source?!” Whatever Google’s goals for openness are otherwise, no one realistically expects them to release their revenue-center source code. So people focus on the most important substitute: data access through open standards and open protocols. Groups like MoveMyData envision a generic tool for bulk download/upload of “your data” to sites like Flickr, YouTube, MySpace, and blogger, including your own web servers. Others dream that application-layer protocols like Atompub, CalDAV, or CardDAV, etc will be widely adopted and provide user freedoms through interoperability. Others worry about identity management, so links to treasured pictures online don’t go bad when a service changes operations (the broken URL problem).

The Chandler Hub service though, is the “full package”, multiple open apis for data and fully open source. (We have not quite solved the broken URL problem though.) The Hub is a straight install of Cosmo (the Chandler Server). Cosmo is an Apache 2-licensed open source “PIM sharing server” with a built-in web UI. Coupled with consumer-friendly terms of service, we have the makings of a fully-open hosted service.

OSAF, a non-profit organization, did not build Cosmo specifically to run a service; the original thought was that workgroups might run their own (like SMTP and web servers) and that they would form a loose network of cooperating servers. (The original Chandler vision was even framed in terms of true peer-to-peer, similar to Kragen Sitaker’s 2006 proposal for how to achieve open services).

As OSAF approached its Preview launch, it seemed clear that running a free service, providing easy sharing, synchronization, and a web interface was an important enabler for people trying out the Chandler Project. Some people will not have access to a private server, so without a low-hassle (and free-to-use) service, they would be blocked from using some parts of the Chandler Project.

Whatever the history, we find ourselves today launching a remarkably open service. Do we measure up to emerging definitions of open services?

Villa’s model for open services asks for the full package, source code included. It contains three preconditions:

  1. data access (ability to retrieve data in open formats)
  2. source access (ability to interact with your data locally once retrieved)
  3. hardware access (ability to run on various sized-hardware)

and three rights: use, modify, redistribute.

Users of Chandler Hub have full data access via multiple open standard protocols (Atompub, CalDAV, and Webcal). Full source access available in OSAF’s public subversion repository and hardware access spans from laptops through large, clustered servers. Even our admin scripts and runbook are available.

So it seems fair to say that Chandler Hub rates well on Villa’s preconditions for an open service. Huzzah!

How we’re judged for the three rights of use, modify, and redistribute should depend on our exact and our adherence to those terms. We want to provide every consumer right expected in this area.

The issues in crafting an open terms of service are trickier than they appear: while you own your data, you can’t be mad at us if we “break your stuff” if there were say a server corruption or downtime. It turns out you actually need to grant the service important rights (store, transmit, etc), not the other way around. Also, when you share an item with others where you both have a right to edit, who has a right to delete it later? Some open service definitions expect community-generated data to be licensed under say the Creative Commons licenses, how does that apply to what Chandler Project is doing (with shared, but possibly private data)?

It turns out, that while drafting this post about open services, the Chandler Project just posted our first public terms of service and privacy policy. Experience suggests that there will be at least a couple of places where we did not write down what we actually meant. We’ll need a longer track record before we can be judged on our implementation of our terms, but we encourage you to let us know how our terms of service document looks, how the privacy policy looks, and how you think we’re doing on this critical dimension of an open service.

So there’s our claim: we’re running an open service, providing both open data and open source, backed by a non-profit motivation and consumer-friendly terms. We’d like to accomplish a few things here:

  • Get community feedback on our terms of service and privacy policy
  • Highlight the importance of the other end of the browser connection in Mozilla’s vision of the Open Web
  • Have people working on “open service” definitions consider how the Chandler Hub ranks on their openness scales
  • Encourage open service definitions to address further the thorny problem of appropriate terms of service
  • Plug the Chandler Hub service. Check out our system and tell us what you think!

Thanks in advance for any feedback you can provide and also thanks for your interest in the Chandler Project!


Chandler Hub has been updated to Cosmo 0.7.0

August 28th, 2007 at 4:11 pm (8 months, 3 weeks ago) by Jared Rhine under Chandler Hub Service, Chandler Server Development, OSAF

We just updated Chandler Hub to Chandler Server 0.7.0! The update was smooth and no one has reported significant issues. Enjoy the new feature enhancements!

In particular, Chandler Hub now demonstrates more pieces of the Chandler vision. In particular, the Hub now supports not only tasks, but Chandler item “stamping” which lets a event also be a task and vice versa. Your tasks and events can be viewed and “triaged” on a unified web dashboard.

This Hub update has been tested to support the upcoming Chandler Desktop Preview release. If you’re using older versions of Chandler Desktop, we suggest considering upgrading to a recent release. While the final Chandler Desktop Preview has not been released, RC2 is currently available and is the best available version. If you prefer to wait for the final released version, no problem; that should be coming soon.

You are invited to use Chandler Hub for daily usage or testing of Cosmo 0.7.0. We’re a small service, but we will do our best to keep your data secure and always available for your use.

We should note that are known issues in Safari support for this 0.7.0 version of Chandler Hub. Also, IE 7 users may now receive a dialog upon logging in related to security settings. If ActiveX is disabled via custom settings, you may not be able to use the Hub. We’re working on fixes to both these issues; thanks for your patience!


OSCON wrapups

August 3rd, 2007 at 9:46 pm (9 months, 2 weeks ago) by Ted Leung under Community, OSAF, Public Events

OSCON wrapups from various OSAF folks have started to appear:

Update: added reports from Mikeal Rogers and Matthew Eernisse


Mozilla’s call for a new vision of email

July 30th, 2007 at 4:37 pm (9 months, 2 weeks ago) by Katie Capps Parlante under Chandler Project, Community, Product Design

Mitchell Baker started a conversation about the future of email at Mozilla, looking for people to participate in “a new vision of mail”. OSAF should be engaging in this conversation, looking for ways to collaborate with Mozilla.

We’ve been looking at email as an important part of the Chandler project. Our approach has been to design applications around user problems and goals, in particular for informal groups working together. Our starting point was the observation that people use their Inbox as their task list. Another observation: calendaring is fundamental to task management; integration of messaging with calendaring makes a lot of sense with user workflows. We think that people will benefit from integrating email, tasks, calendar, contacts and other related information in one application, instead of having to do the work of patching together information across software tools, protocols and data formats. We’ve observed people collaborating on shared problems with email; we think there are huge gains to be made by converging personal communication and group collaboration. Email protocols are not the only route for communication; social networking and other messaging paradigms are other important areas to explore.

The Chandler team is currently working on a Preview release expected by the end of August: a usable version of the desktop application, rich web application, and server. We’ll also launch our free hosted service, Chandler Hub (an instance of Chandler Server).

Chandler Desktop will not be a full email client in the Preview release, but great email support is important to our full vision. Our research shows that many people sit in their email client all day as they try and manage their personal information and work on projects with others. Chandler uses email protocols for “sharing” items (calendar events, notes, tasks). It also has enough basic email functionality to allow users to get email into Chandler to manage a task list and calendar, but as a complement to an email client. Filling out Chandler to be a full email client is one of our options for a 1.0 release.

If you want more information about Chandler ideas, you can read the latest draft of our vision document or explore our wiki. A user guide and screencasts will be showing up as well. You can also experience Chandler in action by downloading the desktop, server, and/or creating a free account on Chandler Hub. Even though we haven’t released Preview yet, the recent desktop checkpoints are usable (modulo a few bugs) as is the previous release of the server (it doesn’t have the full Preview feature set). We use it internally to share group task lists and manage an office calendar.

The Chandler team is focused on getting our Preview release out, so we’re pretty busy through August. We anticipate getting interesting feedback from Preview and we’re going to let that guide our next steps.

I’m not yet sure where a collaboration with Mozilla would lead or what it would mean, but I think we’re looking at a similar problem space and it makes sense to see if we can forge a common path and combine resources. We offer a perspective on the problem, a server and a desktop application, and a team of people who are excited about doing creative things with personal information management (including email). Once we have Preview out, I intend for OSAF to participate actively in the conversation about email futures.


Brian’s EuroPython Wrap up!

July 24th, 2007 at 4:41 pm (9 months, 3 weeks ago) by bkirsch under Chandler Desktop Development, OSAF, Public Events

Well I just got back from EuroPython 2007 held in Vilnius, Lithuania.

EuroPython was definitely smaller than our American Pycon counterpart and the diversity of talks more limited.

My favorite talk was on Streaming with Python, Twisted, and GStreamer.

I particularly enjoyed meeting developers on that side of the hemisphere who don’t normal make it to the American conferences. Overall, EuroPython had a very intimate feel.

On July 10th, I gave a lightening talk on Chandler which went very well.

I was trying to figure out how to capture all the functionality of Chandler in 5 minutes or less of speech time. I decided to run our Functional Test Framework while describing the different features Chandler has as the suite was creating new collections, new items, stamping, configuring accounts, sending email, publishing collections, and subscribing to collections. All in all I was able to show a large amount of Chandler functionality this way in under 3 minutes.

I then quit the tests and switch to a running version of Chandler spending the last two minutes demonstrating how internationalization and the plug-in framework work in Chandler. Specifically, I did an Amazon search for Scott Rosenberg and showed the collection results as well as an EVDB search for Opera in San Francisco.

I got a very good reception from the audience. As many people had not been following Chandler in a while they were surprised at how much recent progress had been made.

On July 11th, I gave my Internationalizing in Python: Chandler a case study presentation. It went very well also. There was strong turn out and I think may people were surprised out how hard it is to actually Internationalize / localize an application in Python.

In addition to showing slides I gave code examples of EggTranslations, PyICU, and how to create localization eggs using the Chandler tools.

You can view photos from the conference as well as access my presentation slides at:

http://people.osafoundation.org/bkirsch/europython/

On July 12th and 13th I hosted two days of Sprints on localizing Chandler.

I must say I learned a great deal. One thing that I had not considered is that localizers also make a very good focus group on Chandler usability. Since none of the translators had worked in depth with Chandler before, it was not only an exercise in how easy is the application to localize but also how easy is it for someone to start Chandler and grasp the concepts the application offers.

There were many issued raised at the Sprint including bugs in the Chandler code that are hindering a complete localization, better tools that need to be provided for localization, and ways that we need to better organize our strings in code to create a usable Chandler.pot for translators to work with.

I would classify those two days as providing the last few missing pieces regarding Chandler’s localization strategy.

I am excited to get started on providing the user community with the ability to localize Chandler in our 0.7.1 release which will follow Preview.

I have summarized the entire experience of the Sprints and next steps for Chandler i18n / l10n as well as included a link to the Swedish translation egg created during the Sprints here:

http://people.osafoundation.org/bkirsch/postsprint/

-Brian Kirsch


Chandler at OSCON

July 19th, 2007 at 5:09 pm (10 months ago) by Ted Leung under Chandler Desktop Development, Chandler Server Development, Community, OSAF, Public Events, Windmill

OSCON is next week in Portland and a number of folks from the Chandler project will be there.

Wednesday morning, Ted Leung and Mimi Yin will be giving a presentation “Open Design, Not by Committee”, about our experiences incorporating designers into an open source development process.

Katie Parlante will be giving a Chandler project update during the “State of Lightning Talks” on Thursday morning

Also on Thursday morning, Mikeal Rogers and Adam Christian will be talking about Windmill, the tool that we use to test the AJAX based user interface for Chandler Server (Cosmo).

There will also be a Chandler BOF on Thursday night, so please come by and say “Hi”. Since the Preview release is just around the corner, now would be a great time to check in and find out what’s been happening.


Please move from osaf.us to hub.chandlerproject.org

June 17th, 2007 at 11:59 am (11 months ago) by Jared Rhine under Chandler Hub Service, Chandler Product News, Community

To all users of the osaf.us sharing service:

Thank you for using the free OSAF sharing service, osaf.us. As the August 2007 release of Chandler Preview approaches, the official OSAF sharing service will move to hub.chandlerproject.org.

Please help us by moving your data from osaf.us to hub.chandlerproject.org. We have written instructions for doing this using Chandler Desktop here:

http://chandlerproject.org/Projects/DavToEimMigrationUserDoc

Chandler Preview uses a faster and more capable sharing system named EIM, available for free on hub.chandlerproject.org. So you’ll need to move your data to the new server to use all the features of Chandler Preview.

Going forward, only hub.chandlerproject.org will receive software updates and our fastest servers. Eventually osaf.us will be turned off, so please help us by moving your data when you get a chance.

Moving your data is not difficult to do. You’ll need to create a new account on hub.chandlerproject.org and update your application configuration to publish to the new server. Your sharing URLs will also change so you might need to contact you’re sharing collections with and give them updated info.

If you need any assistance, you can get help by sending a question to the chandler-users mailing list. We really want this move to go smoothly for you and would like to hear your feedback.

Thank you!

– Jared Rhine, OSAF sharing service manager


Chandler Server (Cosmo) 0.6.1 update!!

May 17th, 2007 at 2:36 am (1 year ago) by Priss under Chandler Server Development, Community

We’re please to announce the 0.6.1 update of Chandler Server (Cosmo)!

Chandler Server is a database, server, and web UI for storing and managing personal information such as events and tasks. It implements standards such as CalDAV, WebDAV, Atom, and Atom Publishing Protocol.

Chandler Server 0.6.1 is currently available for download at: http://downloads.osafoundation.org .

This release focuses on the server side communication between Chandler Desktop and the Chandler Server. We have created a new HTTP-based synchronization protocol, Morse Code http://wiki.osafoundation.org/Projects/CosmoMorseCode, which significantly decrease the time it takes to subscribe to and synchronize collections between the desktop and server.

Find download information, installation instructions and release notes at: http://cosmo.osafoundation.org.

Send us feedback at:chandler-users@osafoundation.org

We look forward to hearing from you!!

-Priscilla


Preview Update

April 18th, 2007 at 12:45 pm (1 year ago) by Katie Capps Parlante under Chandler Desktop Development, Chandler Project, Chandler Server Development, Community

The OSAF team has been busily focusing on our “Preview” releases — functional products that are interesting enough for people to try out and give us meaningful feedback. (”Preview” will not be 1.0 — more like a usable public beta). Our original goal was to have these releases ready this month — we’ve adjusted our schedule to June. The countdown to Preview is tracked on our wiki.

Help us!

If you are adventurous and want to help out the project, we’d love to have people trying out the desktop application and the web application even before we get to Preview. Find bugs and help us make it better! Join the users list, download the latest checkpoint of the desktop application, or check out the web application.

Branding

Chandler was originally a code name for the desktop application. After careful consideration, we decided to use the name for the whole group of products (the desktop application, the online service and the server that runs the service). We’ve chosen a domain name (chandlerproject.org), and we’re working on a new logo. We’re also cleaning up our wiki and our websites as we near Preview. We discuss this work on the general mailing list.

Chandler Desktop

The desktop project hit a feature complete milestone on April 9. New features include recurrence and auto-triage of items in the dashboard, editing and updating items via email, Chandler IMAP folders, context menus, a new sharing format, conflict management, and data migration features. The team is working on performance now, and will spend many weeks after that fixing bugs.

Chandler Server (Cosmo)

“Chandler Server” is our new name for Cosmo. The 0.6 release of Chandler server was described in an earlier post. The server team is currently wrapping up the 0.6.1 release, which implements a new sharing format for data exchange with the desktop application. The team has also started on the 0.7 release, which will allow users to view and edit shared tasks and events in a table.

Chandler Hub (osaf.us)

“Chandler Hub” is our new name for the online service hosted by OSAF, running Chandler server. The service is currently running the 0.6 version of the server. We plan on moving to 0.6.1 in a few weeks, and upgrading to 0.7 in June. Once we’re ready to “Launch” Preview, we’ll use our new domain name (chandlerproject.org).