The services repository would be a place to store non-core/third party
Turbine services that could be utilized by anyone developing with the
Turbine services framework. There are services that are stored in
the main Turbine CVS that would be good candidates for the services
repository: castor, xmlrpc, xslt, webmacro, freemarker, naming.
These are services that Turbine can function without. Many Turbine
developers have probably created services but have never offered them
to the group because they are somewhat specialized: these services would
be ideal in the repository because they would have a description and
might be a great starting place for another developer. Or even better,
a contributed service might be exactly what another developer needs.
There are also services in other OSS Turbine-based applications that
would be good candidates for the services repository. Tambora has
a rule service and processing service that could be useful for other
Turbine-based B2B solutions, and the URL management and disk caching
services in Jetspeed are also general purpose services that would be
very useful to a wide audience of developers.