Re: "If you're still seeing problems, please reopen." [Was: bug#25148:]

[João Távora]

On Thu, Nov 21, 2019 at 3:06 PM Dmitry Gutov <address@hidden> wrote:
>
> On 21.11.2019 17:00, João Távora wrote:
> > But in the GitLab/GitHub model, there is that
> > main repository, which is your duty to protect, and also
> > isolated from it, one for each "JR Random Hacker", a_fork_
> > (maybe Gitlab calls  it a "clone") that JR can randomly hack
> > away in.
>
> I wanted to say this myself, but then tried forking in EMBA. And that
> process is still stuck. So apparently forking is slow in GitLab:
> https://gitlab.com/groups/gitlab-org/-/epics/607

This is a problem, as cheap forks are a cornerstone of
this model. In other words, in my view, it doesn't make
much sense to migrate to GitLab's issue tracker without
the integration with the forking system.  Presuming that
integration is similar to Github's, of course.

João