Thanks for the info. >> One thing we experimented with last year was accepting some sponsorship for >> a feature (improved SLD interoperability between QGIS and GeoServer) and >> then requesting proposals. You may wish to look at how this is turning out >> and consider if the approach would work in your case?
> someone is willing to sponsor, and the module is a community one, thus > unsupported, a part of the codebase where no proposals are needed. So it sounds like this would be split up into two parts; the first would be a proposal for some core-changes allowing POST-requests to be accepted by the scripting plugin and allowing it to return the full spectrum of HTTP-style status-codes (depending on where in the code any interference with this might be occurring). I'd write a GSIP at the outset to clarify requirements and provide a basis for discussion/negotiation on specifics, and I'd also specify how much funding is available. The other part would be to commission work for community-module-updates, which would be less formal, since these don't need central approval. (Discussions about that work don't necessarily need to take place on-list, correct?) > I believe the blockers in this case are two: > * Need to find someone familiar enough with the module to do the > job > * Need to figure out how much money would be needed (or someone > starts with a blind donation to get things started like in the QGIS raster > symbolizer export case) I've already got one (strong!) candidate who can handle the community-module aspect of the work, so we're in good standing on your first point. To address the second bullet, I will write the aforementioned proposal once the dollar-amount we can commit to supporting changes becomes clear. I can (shall) expressly state what this amount is in the footnotes of the GSIP itself to avoid any funny business. So again, I'll only release a proposal once funds are in-hand, so I'm not soaking up time before I know what can be promised on our end. Does it sound like I have that straight? Thanks again, - Patrick
_______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
