Aside: I also really admire their sponsorship model; unlocking functionality in the open-source download as goals are reached. That is a nice balance of open source and an insider track for those in position to pay. The insider track still uses MIT license relying on honour system for sponsors to keep the extra features to themselves. Similar approach to RedHat (accept RedHat as a distributor is in a position to push changes upstream).
Could you elaborate a little more on what such sponsorship would do for our project? What improvements will it bring? And is this something that should be done at the project level, at OSGeo level or at a company level?
Aside: I also really admire their sponsorship model; unlocking functionality in the open-source download as goals are reached. That is a nice balance of open source and an insider track for those in position to pay. The insider track still uses MIT license relying on honour system for sponsors to keep the extra features to themselves. Similar approach to RedHat (accept RedHat as a distributor is in a position to push changes upstream).
While there are perks to sponsoring (additional features at $180/year) they would be purchased for the build server and not easily available to developers testing on their local machine. https://squidfunk.github.io/mkdocs-material/insiders
A useful feature would be provide social image for when a documentation page is shared (so it does not pull a random image from the page).
The point however is is the same as geoserver team supporting marlin rasterizer - looking at dependencies that are useful to us and supporting the ones we can.
While mkdocs is not mission critical for the project the way Saxon xml parser is; I do appreciate material for mkdocs professionalism and I can see their funding has been put towards both functionality and very good documentation which made our transition to markdown much easier.
Could you elaborate a little more on what such sponsorship would do for our project? What improvements will it bring? And is this something that should be done at the project level, at OSGeo level or at a company level?
Aside: I also really admire their sponsorship model; unlocking functionality in the open-source download as goals are reached. That is a nice balance of open source and an insider track for those in position to pay. The insider track still uses MIT license relying on honour system for sponsors to keep the extra features to themselves. Similar approach to RedHat (accept RedHat as a distributor is in a position to push changes upstream).
All OSGeo sponsorship levels are now provided (so the lower level sponsorships are not so highlighted anymore)
Recommendations have been provided for each sponsorship level, one heading for individuals one for organisations
A note that sponsorship is for care-and-feeding and maintenance activities and not an alternative to commercial support
More complete examples have been provided on how to sponsor, along with the emails to send to treasurer@anonymised.com
One thing I was not ablate address:
the osgeo budget request is too low to be useful (and the planning activities I listed are not so good). There is some time before a new OSGeo board is established so the team can work on this!
