This week the good folks from Creative Commons moved into the OSAF space in downtown San Francisco. They join growing group of non-profits, including the Level Playing Field Institute and the Mitchell Kapor Foundation sharing space in S.F.'s only green office building.
We had long admired Creative Commons' efforts in helping people on the Internet who want to "share their work -- and the power to reuse, modify, and distribute their work -- with others on generous terms." These are the same objectives of the open source movement, and one of the core principals of OSAF -- contributing individual intellectual effort for the benefit of the community. In fact, OSAF was in the middle of a project to adopt the Creative Commons licenses for the content on our own website and the various OSAF Wikis when this opportunity came up. And it turned out, we had some extra space available.
Talk about compatibility! It's a great fit. We love having them in the neighborhood, and already feel the synergy at work.
OSAF will be at OSCON (the O'Reilly Open Source Convention) in Portland, OR, next week. A number of us will be there, so if you're planning to attend, please chat us up.
The team hit the .4A milestone. It took an extra week and we got 90% of the way there, not 100%, but it was an impressive performance. The new planning and scheduling system is working, and we're on track for the rest of 0.4B (August) and 0.4 itself (October).
We've started the 0.5 planning process and there is a first draft from Product Management being reviewed by Engineering. Therefore we haven't yet ratified even the top-level goals or the schedule, but my hope is that the 0.5 calendar is something we at OSAF can use on a day-to-day basis in the first quarter of 2005.
At yesterday's staff meeting, we saw the first demo of email running inside Chandler's GUI. As well, the old calendar code we had has been re-done under CPIA (Chandler's GUI-builder framework), and we could see day, week, and month views, as well as a month-at-at-time thumbnail populated with real event data from the repository. Under the hood, it means we have end-to-end functionality integrating the diverse infrastructure components.
Now that we're starting to add application functionality at a more rapid pace (and this is something which will continue), I've asked the team to think about how it's going to impact out development process. It probably means more time spent stabilizing the code as we go so that the features work reliably. It may mean more attention to the visual appearance sooner rather than later, as it is still really raw, but this is to be determined. We also have to decide about whether to tackle or how long to defer certain engineering issues we have to face. A list is being drawn up.
As an added bonus, Morgen Sagen showed off a weekend hacking project he had built, a photo blog parcel for Chandler. It uses Chandler's repository as the back end, and Twisted's web server, which is now integrated into our code, to serve up the photos. The parcel itself is a Python servlet that manages the photos, their captions and the display. Not much integration into the chandler UI yet, but an impressive display of Chandler extensibility, given Morgen said he spent only a couple of hours on it.
If you download and install the most current Chandler, there’s a lot you won’t see. Here’s a peek under the hood at three core infrastructure components we’ve got going.
Core email functionality has been enabled by the integration of the
Twisted networking libraries. Downloading email from multiple IMAP accounts works and was demoed by Brian Kirsch, who did the work, at a recent staff meeting.
The PyLucene full-text indexing engine which Andi Vajda worked on, has been integrated for some time but it is also not hooked up either to the repository or the UI yet. We’ve also made PyLucene its own separate open source project.
Last week, Heikki Toivonen integrated OpenSSL and M2crypto libraries. Chandler can create X.509 certificates which will be used as part user authentication.
Twisted, Lucene (which is the basis of PyLucene), and OpenSSL are all well-established open source projects we are building on top of.
Email functionality will be to appear in the UI in the 0.4 release, about which I will be saying more shortly.
The common conviction is that there is an urgent need to change a political system is not working. We need a new architecture of citizenship and real democratic reform. Thomas Jefferson meets the Internet, again.
Check it out.