The first problem that has to be addressed is that very, very little of the Shindig code is actually API oriented.
IMO, it *should* be written this way, but at present it's more of a big application (not even a framework, just an application). Clearly separating out the "API" parts from the "Application" parts would be a useful exercise. We then have to make sure that the API parts are well designed enough to handle the customizations that clients actually want. The number one issue with shindig's design is the tendency towards adding new features by modifying / adding APIs rather than coming up with a clean and clear extensibility pattern. Changing this is more of a social problem than a technical one, and it goes all the way back to the opensocial specification itself. On Thu, Apr 23, 2009 at 6:25 AM, Mark D Weitzel <[email protected]> wrote: > Quick question.... In thinking about the 1.0 release, are there any API > guidelines for Shindig? I know other apache projects and projects at > eclipse have published how they expect the APIs to stabilize over time > (see links). I was looking around for something similar for Shindig but > could not find it. The primary motivation for the question is that I'd > like to make sure I understand what compatibility guarantees we are making > (if any) between versions, e.g. 1.0, 1.0.x, 1.x, and 2.0. This may already > be on the wiki or web site, and I just missed it. > > Thanks, > -Mark W. > > http://apr.apache.org/versioning.html > http://wiki.eclipse.org/API_Central > http://wiki.eclipse.org/Provisional_API_Guidelines > http://wiki.eclipse.org/Provisional_API_Guidelines_Update_Proposal
