https://github.com/mapsme/omim/ was forked in December 2020, with all new changes up to the last commit of Apr 28, 2021 merged into https://github.com/organicmaps/organicmaps/ later. MAPS.ME is alive, but they publish the source code anymore since that.

What have we achieved so far as we approach Christmas 2024:

- ~3M¹ users from all countries of the world

- ~15k ratings and reviews on AppStore and Google Play

- 4.8/4.6 average rating on AppStore/Google Play

- 10k+ stars on GitHub

- 10k (almost) issues + PRs on GitHub

- 1k (almost) forks on GitHub

- 7k+ git commits

- ~100 awesome contributors who made 5+ commits

- $0 spend on marketing - pure Organic growth

(fixed formatting)

Interesting, I will try !

What would you say are the fundamental differences between Organic Maps and OsmAnd?

Pros of Organic Maps compared to OsmAnd -

* Rendering and routing are faster (especially noticeable on older devices)

* Renders 3D buildings

* Far smpler UI, so it's hard for tech-illiterate users to get stuck

* Changes made with the Organic Maps editor become visible in your Organic Maps immediately. In OsmAnd, your edits vanish upon upload, and only appear once there is a map update - this can be as early as in one hour (using OsmAnd Live), or as late as one month.

* Organic Maps is less buggy.

Cons of Organic Maps compared to OsmAnd -

* OsmAnd has far more features, like bus or share taxi routing, aerial imagery, 3D relief, analysis of GPS tracks, radius ruler, etc

* OsmAnd can render a lot more data like street surface, smoothness, access restrictions, lighting, features with FIXME tags, OSM notes, etc.

* Organic Maps only updates data once a month. OsmAnd updates data monthly too, but also has the OsmAnd Live feature to update data every hour.

* OsmAnd's editor supports adding arbitrary keys, whereas Organic Maps' does not.

> Roman noticed this. He undid the changes, made this post, and has now been booted from the organization?

Correct.

Removing the MIT license from the repository and claiming it as 'my code' is not how open source works.

Nope, Roman has actively contributed to this MIT-licensed code since its inception in 2021.

Yeah I mean, of course technically that's not how it's supposed to be done, but if they initially added the code and the licence (the latter by mistake), then I can see how the internal narrative is "here's my code (that Roman has contributed to) and I accidentally added the licence to it - oops, let me remove that before we accidentally make it public".

Of course at that point they should have realised that they weren't the only author of the code any more and that Roman understandably would have the wrong idea. But I see how it's an easy mistake to make, and it would probably also have easily been resolved had Roman reached out about it, rather than just instantly making it public and implying nefarious behaviour ("quietly made a change...discovered by me").

Though luck. Be more careful next time. That's how licences work (not only open source ones, or software ones).

BTW, packagecloud.io is the great hosting for RPM/DEB packages. We've been using it for the last couple years. GitHub + Travis CI + PackageCloud combination allows us build and publish packages for EVERY git commit in 30+ repositories targeting 15 different Linux distributions [1]. There is no more need to hire a special devops guy for that.

[1]: https://github.com/packpack/packpack#packpack

Overhead of localtime() is well-known, just RTFM. Anyway, this article provides very good explanation.

Hi, Tarantool[1] team maintains production-ready fork of LuaJIT [2]. Commercial support contract for Tarantool covers problems with LuaJIT as the integral part of the product.

[1]: http://tarantool.org/ [2]: https://github.com/tarantool/luajit

P.S. there are shortcoming plans to establish a non-profit foundation to continue development of LuaJIT.

// Disclaimer, I'm a contributor of [1]

Tarantool[1], a general-purpose database and app server based on LuaJIT, has Lua/C API to work with 64-bit numbers and even custom cdata objects [2]. I can extract this code into a separate library for you.

[1]: http://tarantool.org/ [2]: https://github.com/tarantool/tarantool/blob/1.7/src/lua/util...

Demo: https://asciinema.org/a/3unm4sw4g889ddk7tr0uettbn

Travis CI allow you to run any particular command, including Docker, on the top of their Ubuntu Precise/Trusty images. There is no way to choose other images from docker hub in the .travis.yml.

Actually, PackPack is not just for Travis, it can be also used locally:

    ~/gitrepo$ OS=fedora DIST=24 packpack        # Build for Fedora 24
    ~/gitrepo$ OS=centos DIST=7 packpack         # Build for CentOS 7
    ~/gitrepo$ OS=debian DIST=stretch packpack   # Build for Debian Stretch
    ~/gitrepo$ OS=ubuntu DIST=xenial packpack    # Build for Ubuntu Xenial

PackPack automatically bumps version in the RPM spec, packs a source tarball, creates a source RPM and then builds binary packages. You only need a proper RPM spec at `rpm/` and `major.minor` annotated git tag.