houston
houston copied to clipboard
elementary
Support Codeberg repositories
We've gotten some people asking to support Codeberg as a source for repositories. While you can set up a mirror on GitHub (and that's my current recommendation), some are opposed to using GitHub at all.
@cassidyjames Could you imagine adding this issue to the AppCenter For Everyone Sprint? https://github.com/orgs/elementary/projects/72
Exactly, I don't want to use GitHub for my own development for ethical reasons. This also prevents me from getting more and more involved.
Codeberg is based on https://en.wikipedia.org/wiki/Gitea. So a Codeberg integration also means Gitea support, right? Gitea is self-hostable.
This is something I'm adamant about supporting mainly because it would be the in-road to allowing elementary to interact with the broader open source community that attempts to reduce their engagement with organizations like ICE. I'm familiar with the API exposed by Gitea and from what I can gather about Houston's use of GitHub, it can definitely be compatible with it.
I'd ask if elementary, as a team, is open to this because it's not a small undertaking (I can imagine a lot of bits about GitHub being hard-coded into Houston) at all.
Looking at the code in https://github.com/elementary/houston/blob/v2/src/lib/service/github.ts, it doesn't look too impossible!
Sorry about the delay (I get way too many notifications on GitHub). I appreciate the work, and this is something we definitely want to support. But the next iteration of houston (with flatpak support) will most likely be a rewrite of this code base in a different language with some core differences to support other source controls besides GitHub.
Hey @btkostner,
Sorry about the delay (I get way too many notifications on GitHub).
Heh, I declare bankruptcy on them once a month!
I appreciate the work, and this is something we definitely want to support. But the next iteration of houston (with flatpak support) will most likely be a rewrite of this code base in a different language with some core differences to support other source controls besides GitHub.
Is it possible for the community to contribute to this? I have a vested interest in this and would have no problem contributing time.
@jalcine The server side of the project will be here https://github.com/elementary/houston-server. We were planning on figuring everything out at the AppCenter for Everyone sprint, but that was sadly postponed. Luckily Dan, Cassidy, and I are planning a mini sprint all next week to figure out what we need to do for the next iteration of houston. I should have more details for you after that week and hopefully a pretty good place for you to start building out Gitea support.
Excellent, super-excited to hear about that - thank you!
On Thu, May 6, 2021 at 10:08 AM, Blake Kostner @.***> wrote:
@jalcine The server side of the project will be here https://github.com/elementary/houston-server. We were planning on figuring everything out at the AppCenter for Everyone sprint, but that was sadly postponed. Luckily Dan, Cassidy, and I are planning a mini sprint all next week to figure out what we need to do for the next iteration of houston. I should have more details for you after that week and hopefully a pretty good place for you to start building out Gitea support.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.
Oh nice, it's in Elixir too! I've enjoyed that language a lot (as well as Rust).
On Thu, May 6, 2021 at 10:08 AM, Blake Kostner @.***> wrote:
@jalcine The server side of the project will be here https://github.com/elementary/houston-server. We were planning on figuring everything out at the AppCenter for Everyone sprint, but that was sadly postponed. Luckily Dan, Cassidy, and I are planning a mini sprint all next week to figure out what we need to do for the next iteration of houston. I should have more details for you after that week and hopefully a pretty good place for you to start building out Gitea support.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.
Yep! I use it a lot at work at System76 and have fallen in love with it. I'd rather have the backend and web interface use that instead of node. Especially with how fast node moves. Most of the code in this houston repo is super out of date because it was written years ago. Ain't nobody have time for that maintenance work
Should this issue be transferred to https://github.com/elementary/appcenter-dashboard?
@jalcine Could you imagine continuing your work on this now that AppCenter Dashboard exists?