Transfer Repository to the elementary Organization

[ryonakano]

I'll transfer this project under the elementary Organization in near future as I discussed with @danirabbit in Discord. This issue lists tasks before and after transferring the repository.

Before Transferring Repository

• Drop support for .Devel manifests because no elementary apps do this → Drop support for development build #116
  • Delete build-aux folder
  • Stop updating these manifests in flatpak-x-checker.yml
  • Remove development option from meson
  • The config RESOURCE_PREFIX is also no longer needed
• Drop support to build without Granite because publishing on Flathub is not planned → Meson: remove optional Granite #113, Flatpak: Remove Flathub manifest #117, and Assume on Pantheon #122
  • Remove granite option from meson
• Remove about action, this will never used as an elementary app → Remove AboutDialog #115
• Final release as my third-party app at some point → Release 3.1.1 #120
• Delete the project from Hosted Weblate
• Make back the app name translatable → Make back the app name translatable #127
• Do not use mnemonics → MainWindow: Do not use mnemonics #128
• Re-separate the translation domain for metadata into extra → Re-separate the translation domain for metadata into 'extra' #131
• Cleanup no longer used translations → Re-separate the translation domain for metadata into 'extra' #131
• Remove Contributing, Get Support section from README → Update documentations #119
• Delete RELEASE_HOWTO.md because this does not match with the release flow of elementary apps → Update documentations #119
• Delete CONTRIBUTING.md to respect https://github.com/elementary/.github → Update documentations #119
• Only leave the installation method by flatpak-builder in README like https://github.com/elementary/videos/blob/1c896ff28cdfbe55304eacd7b04eb25bd964838d/README.md → Update documentations #119

After Transferring Repository

• Re-RDNN application ids and filenames to io.elementary.maps → Change project owner to elementary and rename to Maps #134
• Update URLs in the source code that point to the repository before migration https://github.com/ryonakano/atlas → Change project owner to elementary and rename to Maps #134
• Update developer tag in the metainfo → Change project owner to elementary and rename to Maps #134
• Add elementary to the copyright headers → Add elementary, Inc. to the copyright headers #149
• Setup project in elementary Weblate
• Setup Release action → Actions: Add gettext-flatpak #136 and Actions: Add release #137
• Publish Maps as Flatpak → Actions: Add deploy #145
• Ship Atlas in elementary OS by default
  • Setup deb-packaging branch to add package name io.elementary.maps
  • Import branch and setup daily and stable recipes on Launchpad: https://code.launchpad.net/~elementary-os/elementaryos/+git/maps
  • Add io.elementary.maps package to https://github.com/elementary/seeds/blob/73fb204bd7210165bd9ade4eaeecb8a00e7f0462/pantheon → pantheon: Add Maps seeds#144

[teamcons]

Very unexpected news, and to be fair i dont understand it

• Why ? A map application is pretty nonstandard as default. I may as well submit my colour picker.
• Why a deb ? Pantheon pretty much doesnt even expose the ability to uninstall them. It isnt the preferred format. If it works as flatpak it is pretty much a regression

[ryonakano]

Why ? A map application is pretty nonstandard as default. I may as well submit my colour picker.

This would be better to be answered by @danirabbit because I wasn't told the reason actually. But other DEs or OSes e.g. GNOME, macOS, Windows, etc. have a default map viewer so I think it would be worth reusing an existing third-party map app on AppCenter as our default map viewer.

Why a deb ? Pantheon pretty much doesnt even expose the ability to uninstall them. It isnt the preferred format. If it works as flatpak it is pretty much a regression

Sorry, I didn't explain too much above since no one other than me and Danielle would look at this issue and I assumed that would be enough for Danielle to understand.

I mean, Atlas still runs on Flatpak after migration so you can uninstall it from AppCenter if you don't like or unnecessary. Debian packaging just provides scripts that install or uninstall Atlas via the flatpak command. And wrapping Flatpak and app with Debian packaging allows us to easily ship it by default by just adding its package name into a file called "seed".

This is how Flatpak apps on elementary OS e.g. Calculator, Camera, Screenshot, File Roller, Fonts, Web, etc. are shipped by default and I just intended to follow this way.

[teamcons]

Aaah. Alright. I didnt know they were managed this way!

[danirabbit]

@teamcons Maps are pretty standard now on mainstream operating systems and it would be nice to have a default handler for geo:// links. I also generally would like to be working towards a mobile/tablet future since that's how regular folks mostly use personal computers these days as opposed to workstations.

Like Ryo said it makes sense to bring in an existing code base from a core contributor than to write something from scratch

And yup the packaging branch is just a quirk of how seeds/metapackages are managed and makes it easy to pull in a new app as an update

[teamcons]

Maybe The Last Update could have a dialog for flathub users mentioning people could add the eOS flatpak repo if they want to continue having updates ?

It would be a nice way to not only keep some of that audience, but also do some mini elementary OS advertising. Over time some may be tempted by the clean UI to go switch over and maybe contribute. Or overall remind people eOS exists.

[teamcons]

Like Ryo said it makes sense to bring in an existing code base from a core contributor than to write something from scratch

I hope however with eOS lacking resources, that you can manage this additional load...

[danirabbit]

@teamcons usually a good way to attract new contributors is to have more exciting things to work on :)