|
8 posts total
 Yesterday we released version 20.2 of @vespucci_editor that's the 37th major or minor release that I've authored. Time to recap how we (currently) version the app. While we use semantic versioning, that is our version numbers are of the format major.minor.patch (actually we have a fourth field that is non-0 just for beta/test releases). This is not particularly meaningful for end user applications and more geared towards the use in APIs and libraries. Currently a big WTF because of https://location.foursquare.com/resources/blog/products/foursquare-open-source-places-a-new-foundational-dataset-for-the-geospatial-community/obviously Foursquare releasing the data is a good thing, but Apache 2.0 is not a data licence and IMNALO it is totally unclear how it should be applied. Not even considering compatibility as an inbound license with other licenses that are typically used for data. Ping @luis_in_brief in case you've not seen the announcement. On the eve of #OpenStreetMap's 20th anniversary, it is slightly upsetting to see the pivotal piece of software that stopped OSM from vanishing in to obscurity and that was, between 2006 and 2014, the 1st contact with editing OSM for most contributors, considered not-notable by @wikipedia https://en.wikipedia.org/w/index.php?title=Potlatch_(software)&oldid=1019457995  @simon @wikipedia @richlv @seav @edward Another example of the arbitrariness of Wikipedia. I'd think TBL spending a minute or two in a TED talk in 2010 demonstrating editing with Potlatch, might suggest it had a huge cultural impact. Currently slightly torn between gloating over (not nearly enough) karma payback for @nlnet, sympathy for the affected projects, and observing that the pecunia non olet approach to financing OSS projects might not be quite as sustainable as some people thought. https://kolektiva.social/@hackstub/112762068812732277 The EU moving funds to silly stuff for industry policy reasons actually has a ~35 year old tie in to the @nlnet angle of this BTW. If you really want to get upset about something going on in open source / open data space, I would suggest considering Niantic. After years of refusing any communication with #OpenStreetMap, not to mention -any- kind of support. Niantic joined the Linux Foundations Overture (for substantial amounts of money), but its customers continue to vandalize OSM, burning lots of volunteer time at multiple levels. https://community.openstreetmap.org/t/beware-of-fake-beaches-pokemon-go/112413 #OpenStreetMap I got a couple of good laughs from our tech overlords at the @linuxfoundation during SOTM-EU over the weekend see https://www.openstreetmap.org/user/SimonPoole/diary/402813   @simon @vespucci_editor congrats! Maybe we should do a podcast interview to celebrate and discuss the state of OSM editors generally? The downsides of being frugal. The #OpenStreetMap Foundation spends, even with a slightly more ambitious budget this year than previously, less than %1 of what WMF/Wikipedia does, but is struggling to make ends meet. There is no threat a la the infamous Wikipedia ads that the project will shut down, but without the funds activities will have to be cut back significantly. If you consider OSM valuable consider https://supporting.openstreetmap.org/
Show previous comments
@simon if only shadow had the money currently to support all the projects they use they would... but for now a reply and boost is the best shadow can do |
Gregory's Server
Currently the semantics 😎 we use are:
major: new functionality, bumped typically once per year, currently synchronized with the age of #OpenStreetMap , saved state changes only happen for major releases.
minor: new functionality, typically 3-4 times a year, at least once prior to August for the mandatory update of the Android version we compile against, which can be anything from weeks of work to harmless.
patch: configuration updates and bug fixes.