4 ms·

(I wish github does not become one but sadly gitlab is beset with constant pain) - no proper communication - unclear future plan - poor documentation See for

by throwaway2056 3y ago

(I wish github does not become one but sadly gitlab is beset with constant pain) - no proper communication - unclear future plan - poor documentation See for example https://gitlab.com/gitlab-org/gitlab/-/issues/380872 https://gitlab.com/gitlab-org/gitlab/-/issues/380872

worldsavior 3y ago
Slow UI, JS is a must, looks bad.
- simse 3y ago
  the almost haiku!
vbezhenar 3y ago
Use gogs.
- pahool 3y ago
  I'm currently looking at alternatives for self-hosting. Do you prefer gogs to gitea? why, if so?
  - turnsout 3y ago
    I’ve been using gitea for years and I love it. I heard about gogs after migrating to gitea, but it seems like gitea is mostly an improved gogs.
  - vbezhenar 3y ago
    I prefer projects maintained by single or few developers. Gogs seems to be that kind of project. Gitea is maintained by some kind of community. Other than that, I think they don't differ that much. Gitea is Gogs fork after all.
burnished 3y ago
I feel like if gitlab were worse it would be less frustrating because my expectations would be considerably lower.
Lutger 3y ago
I've looked at your example, but all I'm seeing is a deprecation process for a feature with an alternative workflow, and all sorts of warnings, a timeline and even a shifting timeline to allow users to update. Can you specify exactly what you find lacking? Is it the fact that there is a breaking change? I'm not familiar with this case, but from a glance I see proper communication, a clear future plan and adequate documentation. I'm not affiliated with gitlab btw.
- throwaway2056 3y ago
  If one runs the command until last week or so it exited (with failure) but pointed out that it is deprecated and provided a link to https://docs.gitlab.com/runner/register/index.html https://docs.gitlab.com/runner/register/index.html gitlab-runner register documentation pages that once again stated the obvious. No difference at all. Then you rerun the command - same bounce out. No clue. The docs linked at the URL still say to use the --registration-token. finally (after digging into stackexchange and gitlab issue) one needs to run the command without --non-interactive No where in the documentation it (until last week) that this should be removed for registering a runner as of today (last few months).
- mardifoufs 3y ago
  That's the thing though! They announced one of the most critical part of the runners (the token auth) to be deprecated for months before the replacement was even available for teams to switch to. Very bizarre

worldsavior 3y ago

Slow UI, JS is a must, looks bad.

simse 3y ago
the almost haiku!

vbezhenar 3y ago

Use gogs.

pahool 3y ago
I'm currently looking at alternatives for self-hosting. Do you prefer gogs to gitea? why, if so?
- turnsout 3y ago
  I’ve been using gitea for years and I love it. I heard about gogs after migrating to gitea, but it seems like gitea is mostly an improved gogs.
- vbezhenar 3y ago
  I prefer projects maintained by single or few developers. Gogs seems to be that kind of project. Gitea is maintained by some kind of community. Other than that, I think they don't differ that much. Gitea is Gogs fork after all.

burnished 3y ago

I feel like if gitlab were worse it would be less frustrating because my expectations would be considerably lower.

Lutger 3y ago

I've looked at your example, but all I'm seeing is a deprecation process for a feature with an alternative workflow, and all sorts of warnings, a timeline and even a shifting timeline to allow users to update. Can you specify exactly what you find lacking? Is it the fact that there is a breaking change? I'm not familiar with this case, but from a glance I see proper communication, a clear future plan and adequate documentation. I'm not affiliated with gitlab btw.

throwaway2056 3y ago
If one runs the command until last week or so it exited (with failure) but pointed out that it is deprecated and provided a link to https://docs.gitlab.com/runner/register/index.html https://docs.gitlab.com/runner/register/index.html gitlab-runner register documentation pages that once again stated the obvious. No difference at all. Then you rerun the command - same bounce out. No clue. The docs linked at the URL still say to use the --registration-token. finally (after digging into stackexchange and gitlab issue) one needs to run the command without --non-interactive No where in the documentation it (until last week) that this should be removed for registering a runner as of today (last few months).
mardifoufs 3y ago
That's the thing though! They announced one of the most critical part of the runners (the token auth) to be deprecated for months before the replacement was even available for teams to switch to. Very bizarre