Bug#792101: (no subject)
Control: retitle -1 ITP: gitea -- A painless self-hosted git service.
New URL: https://github.com/go-gitea/gitea
New package name: gitea
Provides: gogs
Rationale:
While slowly working through this lovely dependency mess, I've been learning
how to build better packages. In doing so, I've been attempting to work with
the gogs author to address some concerns. My hope was to find simple solutions
instead of having to get clever and maintain a mess. The author was quick to
respond when presented with a compliment but fell completely silent otherwise.
After looking through the PR/issue queue, I noticed a problem when it comes to
working with any attempt at a community. I noticed an unnerving trend of not
responding in any way to concerns/complains. I saw some PR's ignored for months
and then closed because they no longer merged cleanly.
The primary fork of gogs is gitea which has quickly built a strong community.
Their View: https://blog.gitea.io/2016/12/welcome-to-gitea/
After everything I've seen, I'm inclined to agree. Gitea appears to have a very
active community that watches their ancestor's commits closely. I've been given
the impression coordinated security releases would be possible with the gitea
"owners" where I would be hesitant to attempt involving the gogs owner.
Because gitea keeps watch of gogs and pulls changes in as needed, I feel it
would sensible to let the gitea provide gogs as a virtual package selecting
gitea. In the event someone wanted to maintain a vanilla gogs, I would be more
than happy to drop that from the packaging, but would otherwise prefer it as a
convenience to new users.
I still have a *lot* of work to do on the dependencies, so lots of room for
discussion if anyone is interested.
--
Michael Lustfield
Reply to: