Re: [RFE] Migration to gitlab

[Eli Zaretskii]

> From: Alex Gramiak <address@hidden>
> Cc: Dmitry Gutov <address@hidden>,  address@hidden,  address@hidden,  
> address@hidden
> Date: Fri, 10 May 2019 15:56:25 -0600
> 
> Eli Zaretskii <address@hidden> writes:
> 
> > I wonder if I'm the only one here who feels that way.  I mean, one of
> > the more important advantages of Emacs is that it lets you do many
> > things only tangentially related to editing program sources, and now
> > we suddenly are willing to give that up?  Really??
> 
> I imagine that most of the people advocating for a switch to platforms
> like Gitlab don't want to give that up; instead, the browser would just
> be an alternative for people who don't (perhaps yet) want to (or know
> how to) do it in Emacs all the time.

I believe you are talking about a system with dual interface: one via
a browser, and another that allows to use Emacs for most of the tasks.

That'd be OK at least with me, but the problem is I don't yet see how
this could be done with GitLab or any other system that was mentioned
in the discussions so far.

> A problem here seems to be that Gitlab, outside of its browser workflow,
> doesn't currently offer some niceties that are to be expected, but
> hopefully this discussion helps to nudge the right people to work on
> these features there.

I really hope so.

> If switching to Gitlab was given the OK by you and other core
> contributors after the desired features are available in Gitlab

For this, we'd need to agree on the list of the desired features,
probably prioritized by their importance.  Once we have that, we could
decide that having all the features whose priority is greater than
some agreed-upon number N is enough to switch.  Theoretically, I don't
see any problems with this decision; the devil is as always in the
details: to come up with a list of the features, agree on their
priorities, and implement them.

Thanks.