I have not looked t these changes as I do not personally follow stackexchange.
We are very much open to contributions and changes: a) for day to day changes and fixes the CONTRIBUTING.md document describes the nuts and bolts of submitting a pull request with QA coverage, and documentation as required b) For API changes (where compatibility is affected) there is a formal change control process - where you write up a proposal for public review. We have setup our procedure to be responsive in order to support consultants working on behalf of a customer. Proposals are not rejected without an alternate way forward provided. The goal is to reduce risk, and to prevent more than one party making competing implementations (and then both finish their budget and cannot work out a compromise leading to hurt feelings). - Proposal first: In your quote to a customer include a design milestone which includes delivering of a proposal to the community; this way you get a public review and assurance that your approach will be accepted; reducing risk. - Proposal second: Do the work and make sure your customer is happy (sometimes the only way to establish scope); and then write it up as a proposal to the community. The risk is if your approach missed out on required tasks then you may be out of budget; with an unhappy customer. We are very understanding if scope changes during implementation, or when a customer firsts looks at it. The idea is to keep communication going. The details of what I describe are in the developers guide: - https://docs.geotools.org/latest/developer/procedures/proposal.html -- Jody Garnett On Fri, Feb 2, 2024 at 5:23 AM Segerstedt, Peter via GeoTools-Devel < geotools-devel@lists.sourceforge.net> wrote: > Dear developers, > > I've made, on the behalf of a customer, small additions to geotools and > geoserver in order to solve what's been previously discussed here: > > > https://gis.stackexchange.com/questions/452624/name-property-for-rules-in-css-styles-alternatives-or-how-to-contribute > https://sourceforge.net/p/geoserver/mailman/message/36050785/ > > The code should be publicly available here: > https://github.com/sweco-sepesd/geoserver/tree/geoserver_css_name_rule > ( > https://github.com/sweco-sepesd/geoserver/commit/7ed3780e377dcb0318bf9f44be2420d2f53d2639 > ) > > https://github.com/sweco-sepesd/geotools/tree/css_named_rule > ( > https://github.com/sweco-sepesd/geotools/commit/2a4d1afcbb6fac7ac9c7798946db50a627aff119 > ) > > Under what circumstances would it be possible for geotools/geoserver to > adopt these changes? > > Best Regards, > > Peter Segerstedt > > > > > _______________________________________________ > GeoTools-Devel mailing list > GeoTools-Devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geotools-devel >
_______________________________________________ GeoTools-Devel mailing list GeoTools-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
