Hey folks, chiming in here as I am the original author of the module in question. I do freelance GeoServer consulting work so I'd be happy to engage with you Patrick to get this work done. As Andrea mentioned the code in question here is in a community module which normally doesn't require a formal proposal to do work in, at least not at this time.
If you're game Patrick I suggest we work out the details offline and then update the developer list with a plan of sorts, elicit feedback, etc... That said if the PMC and core developers have an interest in tackling this work as a collective group (similar to other initiatives in the past) I would happily step aside and allow things to go that route. On Fri, Feb 15, 2019 at 10:00 AM Andrea Aime <[email protected]> wrote: > On Fri, Feb 15, 2019 at 5:50 PM Jody Garnett <[email protected]> > wrote: > >> 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). >> > > Jody, I would discourage usage of proposals this way, people have already > tried to do that in the hopes of getting an idea "accepted" and then > pretending to see it implemented only because of that, without funds. > Proposals were created exactly to verify that the activity had enough > resources behind to make it happen. > > Here we are starting the opposite, someone is willing to sponsor, and the > module is a community one, thus unsupported, a part of the codebase > where no proposals are needed. > > >> 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? >> > > Yep, that would work... but in that case we started with a given amount of > money (which was not enough to do the full job) and then the GeoServer PSC > and others pitched in to reach > a threshold that made it doable. > 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) > > Cheers > Andrea > > == > > GeoServer Professional Services from the experts! Visit > http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf > Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa > (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 > http://www.geo-solutions.it http://twitter.com/geosolutions_it > ------------------------------------------------------- *Con riferimento > alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - > Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni > circostanza inerente alla presente email (il suo contenuto, gli eventuali > allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i > destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per > errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le > sarei comunque grato se potesse darmene notizia. This email is intended > only for the person or entity to which it is addressed and may contain > information that is privileged, confidential or otherwise protected from > disclosure. We remind that - as provided by European Regulation 2016/679 > “GDPR” - copying, dissemination or use of this e-mail or the information > herein by anyone other than the intended recipient is prohibited. If you > have received this email by mistake, please notify us immediately by > telephone or e-mail.* > _______________________________________________ > 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
