« Return to Thread: dwr "extras" area
My opinion is that DWR is an integration product which benefits a lot from being already prepared for interfacing to other products and frameworks. My ideal scenario (sans the work of actually setting it up) is that we have an area in SVN for additional integrations and demos that are outside the core distribution. This would allow us to have a liberal policy for letting contributors add new stuff, but wouldn't force us having the same licensing rules or release cycles.I imagine the result would look something like this:
core dev team maintains a number of integrations and demos that are included in the core distribution a larger set of contributors add stuff to the new "extras" area and these projects are built to separate jar files (or similar) we have some kind of voting before adding a new project to the extras area if possible administration-wise, any "extras" demo jar files could be deployed as separate apps on the same appserver as running DWR's core demos in DWR docs we
maintain a list of contributed integrations with information on how stable/up-to-date they are, who is maintaining, compat with different DWR versions etc link to each sub-project's doc or demo pages in the extras area- integrations in core distribution should be actively maintained, when they are not they should move out to the "extras" area
- I'm expecting ~10 projects. If in reality it becomes 100, I think we should think about another solution... ;-)
« Return to Thread: dwr "extras" area
| Free embeddable forum powered by Nabble | Forum Help |