[Cosmo-dev] Re: [Scooby-dev] Cosmo/Scooby Merge (Please read and
comment)
Mikeal Rogers
mikeal at osafoundation.org
Fri Jul 14 17:17:00 PDT 2006
> given that we've implemented probably 80% of the protocol, and the
> most useful 80% at that, and that we have demonstrated
> interoperability with a number of clients, i feel reasonably sure that
> a lot of people will get what they need out of what is already in
> cosmo. but the door is wide open for those who need the other 20% to
> contribute patches.
I think this hits directly at the heart of our questions about the
"eco-system".
-Does the eco-system include other clients?
-More importantly, can the eco-system, and the osaf hosted service be
successful without other clients and open interfaces.
Sure, we can say at any point "We're not going to develop this
anymore and if someone else wants to we'd be happy to commit it" but
that presumes that we have made the decision that which ever feature
we stop developing ourselves is not necessary to the success of the
hosted service or part of the "eco-system".
I think that if we are all in agreement that we do need these
interfaces written and tested for the service to be successful, then
we need to include it in the Beta plan and allocate resources to it
appropriately. I for one would be in favor of an item in the Cosmo
development plan that stated "any and all features in cosmo must be
exposed via a public interface in the release the feature is added to
Cosmo", and I know that in QA we can then prioritize our work and
create tools and test scripts that tested this.
At this point I want to draw a distinction between "any and all
features in cosmo" and something like "full caldav compliance".
What I mean is that if there is a Cosmo API, and scooby is getting
information about a calendar with that API that would directly
correlate to a CalDAV REPORT, then we should put in the time to write
the CalDAV REPORT's and test them.
I don't mean that if we support calendaring we should do full caldav
and gdata support in the first release. But what ever we do with the
cosmo internal api's, someone should be able to do via the external
API's.
-Mikeal
More information about the cosmo-dev
mailing list