« Return to Thread: dwr "extras" area

dwr "extras" area

by mikewse :: Rate this Message:

Reply to Author | View in Thread

Hello devs,
 
I think we should consider adding an area on the DWR site, and SVN repo, for user-contributed DWR extension libraries, as per the recent discussion about Ext.Direct on the users mailing list. My suggestion from that thread below:
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... ;-)
I thought we could discuss this a little, and then end the discussion with a vote.
 
1) Is this philosophically a good or bad idea? (Ie, is it good or bad for DWR?)
 
2) Is this in practice a good or bad idea? (Ie, will it mean an unwanted workload that will take the focus from more important stuff?)
 
3) What precedents can we look at? (Dojo's dojox, JQuery plugins, ...?)
 
4) What should we name this area? (DWR extras, DWRX, DWR contributions, ...?)
 
5) How could we best separate the "extras" area from core in SVN? (Folder in same SVN tree or separate SVN tree, should "extras" commiters have rights in core, ..?)
 
Best regards
Mike

 « Return to Thread: dwr "extras" area