On Mon, Jul 07, 2008 at 05:05:38PM -0500, Eric Rabinowitz wrote: > It's very worth discussing so that the work (or ANY future potential > contributions) are not for a single point distribution in time and > then it is lost work & effort. You will always have forks - that's the hole point of free software - modify it as you see fit. Keep your changes as separate patches/source tree until they are merged upstream - especially easy with a distributed VCS like mercurial or git.
We had and have several changes in pykerberos/calendarserver to make it work on better on Linux and add more funtionality. All of this is in trac and so far things got merged eventually. Although it would certainly be nice if the developers with SVN commit access had a bit more time to work on the bugs (especially those with patches) in trac. So as Helge said: until there's a patch there's no point worrying if it'll get applied. -- Guido _______________________________________________ calendarserver-users mailing list calendarserver-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/calendarserver-users
