Does anyone know why the Organic Maps Github page is currently in public archive mode? There’s some issues I’d like to open on the Github to improve the app but I can’t open any issues or comment on issues because it is archived.
Has there been a new Github or other code database created for Organic Maps?
Relevant discussion on fedi
They are currently blocked by github and looking into other options. I’m interested to hear more about why this happened once they are back up and running.
they are moving to Forgejo
The existing GitHub repository has turned into a mirror of the new Forgejo repository. They’ve also disabled the issue tracker and wiki. Unfortunately, this breaks links from other repositories, forum discussions, the OSM Wiki, etc. When they migrated issues and pull requests to Forgejo, they retained the issue numbers, so I was able to update most of the wiki’s references to the old GitHub repository to point to Forgejo instead:
| GitHub | Forgejo |
|---|---|
https://github.com/organicmaps/organicmaps/issues/4147 |
https://git.omaps.dev/organicmaps/organicmaps/issues/4147 |
https://github.com/organicmaps/organicmaps/pull/3130 |
https://git.omaps.dev/organicmaps/organicmaps/pulls/3130 |
https://github.com/organicmaps/organicmaps/blob/3eb011ebbc0596f1c885712fc6e7ad029e6c5da5/generator/osm_element_helpers.cpp#L46 |
https://git.omaps.dev/organicmaps/organicmaps/src/commit/3eb011ebbc0596f1c885712fc6e7ad029e6c5da5/generator/osm_element_helpers.cpp#L46 |
https://github.com/organicmaps/organicmaps/commit/3eb011ebbc0596f1c885712fc6e7ad029e6c5da5 |
https://git.omaps.dev/organicmaps/organicmaps/commit/3eb011ebbc0596f1c885712fc6e7ad029e6c5da5 |
https://github.com/organicmaps/organicmaps/blob/master/README.md |
https://git.omaps.dev/organicmaps/organicmaps/src/branch/master/README.md |
https://github.com/organicmaps/organicmaps/issues |
https://git.omaps.dev/organicmaps/organicmaps/issues |
https://github.com/organicmaps/organicmaps/tree/master/data/styles |
https://git.omaps.dev/organicmaps/organicmaps/src/branch/master/data/styles |
https://github.com/organicmaps/organicmaps/releases/tag/2023.11.17-17-android |
https://git.omaps.dev/organicmaps/organicmaps/releases/tag/2023.11.17-17-android |
https://github.com/organicmaps/organicmaps/releases |
https://git.omaps.dev/organicmaps/organicmaps/releases |
https://github.com/organicmaps/organicmaps/wiki/Installing-Organic-Maps-from-GitHub-using-Obtainium |
https://git.omaps.dev/organicmaps/organicmaps/wiki/Installing-Organic-Maps-from-GitHub-using-Obtainium |
https://github.com/organicmaps/organicmaps |
https://git.omaps.dev/organicmaps/organicmaps |
https://github.com/organicmaps/organicmaps/discussions/1489 |
 |
https://github.com/organicmaps/organicmaps/discussions |
|
Some caveats: Links to individual comments are less straightforward, because the named anchors have different hashes on Forgejo. It doesn’t look like this Forgejo instance has any equivalent to GitHub Discussions. Any image or video embedded in an issue comment is gone and didn’t survive the migration. Software Heritage doesn’t archive issues, but the Wayback Machine has archived a handful of issues including multimedia.
Your subscriptions to issues have also been erased. This includes any issue you were subscribed to because you authored, commented on, or were mentioned in it. After creating an account on the Organic Maps Forgejo instance, you’ll need to manually resubscribe to any issues you previously followed. This is a lot easier if you receive GitHub notifications via e-mail and have kept those notifications. If you rely solely on GitHub’s Web interface or application to track notifications, those notifications have probably gone away, but you can at least search the repository for issues that you commented on or that mentioned your user name. Make sure to search “exact”; the “fuzzy” search can be very imprecise for this purpose.