[Dev] contributing code back to other projects?

[Kevin Altis]

Andy wrote in his Vista prototype document "we're working hard on creating
the real thing now, and expect to have code to release publicly around the
end of the year".

Given that Chandler relies on a quite a large number of open source projects
I was wondering what the plans are for contributing code back to the
projects such as Python, ZODB, wxPython, Jabber, etc.? Will this code become
available before the main Chandler code base becomes public? I expect that
the ambitious goals for Chandler will result in fixes and enhancements that
will benefit the projects Chandler relies on. It may also spur development
on projects such as jabberpy, which hasn't had many enhancements since early
2002.

In particular, there are probably at least a few wxWindows/wxPython UI
controls that might be needed for Chandler, that are not already part of the
standard wxWindows/wxPython 2.3.3.1 set. In other cases, in order to support
a more consistent look across platforms, enhancements or additions to the
Linux/GTK and Mac OS X versions of wxPython controls might be needed.
Regardless, any fixes or additions could be made independent of the main
Chandler release.

This may be more of an administrative management question versus a pure
development issue, but I would like to hear the plan.

Thanks,

ka