[Dev] contributing code back to other projects?

Mitch Kapor mitch at kapor.com
Sun Nov 3 17:15:11 PST 2002


We've already started to do this and have the intention to do more.  I'll 
ask John Anderson to post the details, but I do remember we had a staff 
meeting in which I made exactly the point you did.  We get a lot, we should 
be contributing something back.

In addition, if we discover there are needed extensions to components we 
depend on and there are already people in place who could do the work and 
want to do the work, we MIGHT be able to make modest grants to facilitate 
this.  No promises, but we would consider this.


At 12:27 PM 11/3/2002, Kevin Altis wrote:
>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
>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 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.
>_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>Open Source Applications Foundation "Dev" mailing list

More information about the Dev mailing list