This is a re-up of https://dev.getsol.us/T5376 which was rejected due to inactivity. The scene has changed a bit since then so I'd appreciate if this could be looked into again.
Name: github-desktop
Description: GitHub Desktop App (Electron)
Homepage: https://desktop.github.com/
Why: Github Desktop is a friendly, well-polished frontend for Github which allows new developers to ease them into the world of repository management and pull requests. The reason this should be included is because it fulfills a different purpose to alternatives such as gitg, git-cola, and Git-Kraken: no prior knowledge on git repositories is assumed and the program guides new users through the process of adding/cloning repositories, making branches and creating pull requests. The other UIs assume a more comprehensive understanding of the topic and are aimed more at power-users. Github Desktop also focuses specifically on Github, and not other hosts, so terminology is consistent (which is a valuable thing for new developers). It is the frontend recommended by Batocera for new contributors.
Open source: Yes. MIT license.
How many will use: Most developers of Batocera and Batocera-EmulationStation already use Github Desktop to make contributions. Solus is one of the operating systems recommended for its compilation (https://wiki.batocera.org/compile_batocera.linux#docker and https://github.com/batocera-linux/batocera-emulationstation#building respectively), and right now Github Desktop is recommended to be installed with its AppImage. It works well, but it's a bit clunky to first setup especially for new devs.
Link to source: Although Github Desktop has their main repository at https://github.com/desktop/desktop, a new fork of this repo aimed at Linux support has appeared at https://github.com/shiftkey/desktop (the most recent releases can be found at https://github.com/shiftkey/desktop/releases). The maintainer is active in their updates and commits are merged in from upstream almost immediately, making this the definitive edition for Linux distros to use.
Description
Related Objects
- Mentioned Here
- T5376: github-desktop
Event Timeline
Not sure what Solus' official POV is on these situations, but Shiftkey is available as a flatpak already.
https://github.com/flathub/io.github.shiftey.Desktop
https://flathub.org/apps/details/io.github.shiftey.Desktop
The original request was for the original Github Desktop available from https://github.com/desktop/desktop , while this request is about Shiftkey's identically named Github Desktop available from https://github.com/shiftkey/desktop . This distinction was made in this request.
I was not aware that there was also a flatpak available, it certainly isn't advertised on any of Github's references to Github Desktop. Thank you for the suggestion, but direct integration is preferred due to the browser dependency.
Task T5376 wasn't rejected due to inactivity, it was rejected because no answer was given about the added value of this project compared to the alternatives that were already available in the repository.
If you think the situation has evolved or if you think the forked version brings some added value compared to the original one and/or to the alternatives that are already in the repo, you can mention it there.
If the project was forked under a different name it would have make sense open a new task for it to ease the search but here name was unchanged so having multiple tasks for the same package request only adds some confusion. Even if there are multiple forks actively maintained, it is better to mention them in the same tasks because if the request is accepted anyhow only 1 of them would go in the repository so it is much easier to have all the info at the same place and not spread across multiple requests !
Thanks for your understanding.
This is a request for different software, I just mentioned that previous ticket due to its similarity but lack of identical intent. For instance, how would I indicate that the package is at a different URL than the one provided in the request? It'd feel like hijacking someone else's request for different software.
With that said it is basically the same and I would have no qualms about moving this information over to it. It's just a matter of how strictly the definition of "identical software" is enforced, which will always be a debatable topic.
By the way, I've since tried the flatpak version suggested by samteezy but as I suspected it is non-functional as its browser integration is indeed broken.
For instance, how would I indicate that the package is at a different URL than the one provided in the request?
Simply mentioning the fork and new URL in the original task is fine, like you did now. Worst case someone asks additional questions ^^
Since these tasks are read by humans, not robots, we can handle variation, and there is some flexibility in how you can present your information ?