Codeberg's F-Droid repo #449

Open
opened 5 months ago by silkevicious · 3 comments

It would be cool if Codeberg can set up an F-Droid repository with some/all the apps hosted here.
This would allow app owners a quicker deployment (compared to updates of main F-Droid repo), don't require each of them to setup a repo and maybe attract other app owners eventually.
If needed i offer my help to do so.

Similar proposal was embedded into another issue by @vanous in #23
but i think it deserves a separated issue/feature req.

btw the list of apps currently hosted here at that moment is #23

It would be cool if Codeberg can set up an F-Droid repository with some/all the apps hosted here. This would allow app owners a quicker deployment (compared to updates of main F-Droid repo), don't require each of them to setup a repo and maybe attract other app owners eventually. If needed i offer my help to do so. Similar proposal was embedded into another issue by @vanous in https://codeberg.org/Codeberg/Community/issues/23#issuecomment-165595 but i think it deserves a separated issue/feature req. btw the list of apps currently hosted here at that moment is https://codeberg.org/Codeberg/Community/issues/23#issuecomment-181690
fnetX added the
infrastructure
service
labels 5 months ago

Great idea! As opposed to the main F-Droid repository Codeberg could actually host "nightly" and "edge" artifacts so that users could profit from brand-new features and bug fixes more quickly. Instant deployments would probably also improve user experience and user feedback.

Great idea! As opposed to the main F-Droid repository Codeberg could actually host "nightly" and "edge" artifacts so that users could profit from brand-new features and bug fixes more quickly. Instant deployments would probably also improve user experience and user feedback.

The big question here is should these apps be built from source or taken as binary artifacts (Built and signed by the apps developer.) Or re-built by the codeberg servers but still signed by the original deveopers. These three options involve different trust anchors for users as well as different effort on maintaining this service.

The big question here is should these apps be built from source or taken as binary artifacts (Built and signed by the apps developer.) Or *re-built* by the codeberg servers but still signed by the original deveopers. These three options involve different trust anchors for users as well as different effort on maintaining this service.
Collaborator

Reproducable builds would be best!

+ So App devs coulsd sign and siggnature between e.g. PlayStore and Codebergs F-Droid repo would be same -> the trust you get what you see is ensured by automation ...

- I's not always posible ...

Reproducable builds would be best! `+` So App devs coulsd sign and siggnature between e.g. PlayStore and Codebergs F-Droid repo would be same -> the trust you get what you see is ensured by automation ... `-` I's not always posible ...
Sign in to join this conversation.
No Milestone
No Assignees
4 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.