That would be an appropriate use of a GSIP: Thoughts: - We do recommend writing a proposal to verify an approach prior to starting work, in the past when the idea was associated with pending funding this was made note of (so folks do not get their hopes up). - This a subtle trap where if a GSIP for a good idea is proposed there can be a temptation to hang back and let someone else pay for it - In geotools we use proposals to explore an idea and also secure a commitment for each task (to ensure a contributor is in position to do the work, you could do something similar with funding targets).
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? -- Jody Garnett On Fri, 8 Feb 2019 at 14:15, P O'Toole <[email protected]> wrote: > All - > > My little outfit has been a user of the WPS/Python-scripting plugin for a > long time, but we're currently maintaining some modified/recompiled > library-files alongside a (hackish) fork of Geoserver (described in > https://sourceforge.net/p/geoserver/mailman/message/35410958/) to allow > compatibility with the POST method to allow for large requests and to > provide improved security. Although I pull Geoserver updates across from > the official repo from time to time, this is messy, and I have not sunk the > hours into figuring out how to return status-codes other than 200 OK or 500 > Internal Server Error, as it seems that anything /other/ than a 200 coming > out of Flask is rewritten to a 500 by the Java code it runs inside of. > Basically, what I have works okay but there are a lot of potential > maintenance-gotchas. > > Since first setting up the scripting plugin and joining Geoserver > listservs a few years back, I've seen semi-frequent questions appear about > the Python/WPS plugin and whether there's a maintainer to answer questions, > etc. When I checked last, there was no designated maintainer, the web-UI > component (which I didn't even know about until someone mentioned there > used to be one that worked) was broken, and contrib/community-files and > docs were out of date. > > Would it be within GSIP-scope to propose some related fixes and pay to > make support available for the plugin? > > - Patrick O'Toole > > Full-Stack Developer > Wyoming Natural Diversity Database > UW Berry Biodiversity Conservation Center > Department 3381, 1000 E. University Av. > Laramie, WY 82071 > P: 307-766-3018 > > > _______________________________________________ > Geoserver-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/geoserver-devel >
_______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
