Hi Otto, On 5/21/25 03:23, Otto Kekäläinen wrote:
It would be nice to read a writeup of what you plan is, and how the Go team or other DDs in general are expected to relate to this.
I'm packaging forgejo (currently ~21 golang packages are waiting in NEW, another ~10 soon to be finished) to be eventually included in Debian.
To eat my own dogfood, I've setup forgejo.d.n and pushed my own packages there.
Once forgejo is in Debian, I intend to keep using forgejo.d.n as a test-environment for the forgejo packages before an upload happens to Debian, tested with my own "production data" (= my other packages hosted on it).
your plan regarding gains from Forgejo in Debian
I don't have any plans other than to have forgejo included in Debian so users (like myself) who want to use it, can use it from the Debian archive instead of everyone maintaining their manual setup individually.
OIOW, one of the reasons why a lot of packages are in Debian in the first place :)
costs from fragmentation.
I'm not sure I understand what you mean with "fragmentation" in this context. Would you mind explaining?
Perhaps a blog post, Debian news item or other announcement?
Once forgejo is actually in Debian, I'll would like to do so, yes. Regards, Daniel
