|
|
Subscribe / Log in / New account

Open Source Applications Foundation restructures

From:  announce-AT-osafoundation.org
To:  announce-AT-osafoundation.org, general <general-AT-osafoundation.org>, OSAF Design list <design-AT-osafoundation.org>, Chandler <chandler-dev-AT-osafoundation.org>, Cosmo <cosmo-dev-AT-osafoundation.org>
Subject:  [Announce] OSAF Transitions
Date:  Tue, 08 Jan 2008 20:51:13 -0800
Message-ID:  <478452C1.3010003@osafoundation.org>

OSAF and the Chandler project are going through some big transitions. 
Yesterday, January 7, we restructured the organization. This is the 
biggest change since the inception of project six and a half years ago.

In September 2007 we delivered a Preview release of Chandler Desktop, 
Chandler Server and the Chandler Hub web application. Since then we've 
been gradually acquiring users and building a community of people 
interested in the project. We now have hundreds of people participating 
in our users mailing list and thousands of users downloading Chandler 
and creating accounts on Chandler Hub.

Chandler is an open source, standards-based calendar and task manager 
built around small group collaboration and a core set of information 
management workflows modeled on Inbox usage patterns. Users manage and 
share calendars, tasks, messages, and notes with the Chandler Desktop 
application and with the Chandler Hub web application.

The next phase of the project is about growing the user base, building 
the community, and diversifying our funding sources. OSAF has been 
primarily funded by one person up to this point, Mitch Kapor. Our goal 
going forward is to modify our organization and our funding model to 
grow into a publicly supported community project, not propelled by one 
individual.

I will be leading the next phase of the project, and Mitch will be 
winding down his role on the project. Mitch will provide transitional 
financial assistance to support the organization through 2008. Mitch 
will step down from the board, and I will replace him.

OSAF will maintain a smaller staff during the next phase of the project. 
While figuring out the new funding model, it is prudent for the 
organization to reduce expenses. OSAF's paid staff will go from 27 
people to 10 people. While I expect that most former staff members will 
move on to other endeavors, we certainly welcome them to remain involved 
with OSAF and Chandler in some capacity. Developers will retain commit 
privileges, for example.

Strategically, we find ourselves at a crossroads. The new Chandler team 
will continue to address the needs of informal groups sharing calendars 
and managing projects together. We've gotten a lot of great feedback 
from our current users, and intend to use that to fix usability problems 
and shape the next set of feature work. We have several options before 
us and will be ironing out a more focused plan for the next phase. We 
will keep everyone updated on this blog.

The Chandler team did a fantastic job shipping the Preview release. 
Building on this accomplishment, the project has many great 
possibilities ahead. While saddened to see such a great team come to an 
end, I'm excited about the project's opportunities and looking forward 
to next chapter.

Katie
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "Announce" mailing list
http://lists.osafoundation.org/mailman/listinfo/announce



to post comments

What a bad example

Posted Jan 9, 2008 21:41 UTC (Wed) by BrucePerens (guest, #2510) [Link] (4 responses)

OSAF was a classic example of how not to do an Open Source project, by applying big-company software engineering practices and spending lots of money, over lots of years. I'm glad they have something to show, and hope the project can attain a real community with a different paradigm.

Somehow a number of the same people managed to get the Mozilla foundation going, which is a much bigger achievement (although it also has some big-company problems now).

Bruce

Mozilla

Posted Jan 10, 2008 2:10 UTC (Thu) by roc (subscriber, #30627) [Link] (1 responses)

It's hard to serve 100M users and get a lot of things done without *some* big-company
problems.

Mozilla may have (had) some board overlap with OSAF, but there's never been any real overlap
in the driving forces behind the organizations.

Mozilla

Posted Jan 10, 2008 16:32 UTC (Thu) by BrucePerens (guest, #2510) [Link]

Well, Mitchell Baker and Mitch Kapor were the overlap, that's pretty significant.

What a bad example

Posted Jan 14, 2008 3:26 UTC (Mon) by emk (subscriber, #1128) [Link] (1 responses)

Well, at the beginning of Chandler, I spent an afternoon reading their design documents. Even
in the commercial world, I've seen very few organizations dedicated to such generalized and
abstract software.

This is a pretty risk path to take--it's nice to have a clean architecture, but if you can
make enough simplifying assumptions, you'll get a product out the door much sooner.

What a bad example

Posted Jan 14, 2008 21:41 UTC (Mon) by hazmat (subscriber, #668) [Link]

i've been watching the project since its inception, have contributed several patches. i think
its more than just the architecture abstractions, although that was definitely a strong sign
of some of the issues. it was also poor technology choices (wx, chandlerdb) in addition to
poor management that lead to this road, imo. and inexperience with python, mucky internal api
(verbose xml initially).. it had the feel of abstracte java apis in python.. much of which was
cleaned up at with philiby eby working (peak, setuptools) as a contractor with them, but the
writing was on the wall.

in general watching chandler and osaf, was like watching a slow moving train wreck.

there server side story is much better (servlet cal-dav repo w/ sharing and  web ui), and was
built fairly rapidly by a small team. 


Copyright © 2008, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds