Why GitLab? In short, we felt it would likely be more acceptable to
most members of the Sage community; this was a feeling we had even
before the Microsoft's acquisition of GitHub was announced. First of
all, GitLab is open-core, meaning that the majority of their software
is open source, but for paying customers there are additional features
that are not made open source. This, in addition to providing higher
level of support to paying customers, is the basis of their business
model. But IMO it is more inherently open source-friendly than, say,
GitHub.
For an immediate use case
of this that I have in mind, I would like to make it easier for users
to submit documentation fixes: https://trac.sagemath.org/ticket/25914
What does everyone think? Is there anyone opposed to going ahead and
opening up merge requests?
On Tue, Aug 21, 2018 at 11:21 AM Daniel Krenn <kr...@aon.at> wrote:
>
> On 08/21/2018 10:43 AM, Erik Bray wrote:
> > https://gitlab.com/sagemath/sage
>
> How do I become a member of the SageMath group (or the project) in
> Gitlab? (username: dakrenn)
Just ask, like you just did :)
* using gitlab's servers
* self-host gitlab
The latter case this would mean replacing trac, which does not age too well, as we see, with something much more modern and designed for using git from ground up.
[...] Something that regularly happens on the Sage Trac:
1. Somebody creates an issue
2. Somebody (the same or other person) adds a branch
3. Somebody else forks that branch and adds a reviewer patch
In the GitHub model, you now have 1 issue and 2 pull requests for
exactly the same issue. Even if cross-links are added, you still end up
with spaghetti discussions.
julian
a very quick correspondence between trac and github/lab terms is as follows:
trac ticket, no git branch - issue
trac ticket, with a git branch - pull (merge, on gitlab) request
github has a command line tool, called hub, allowing one to e.g. create pull requests and issues, without using a browser.
https://hub.github.com/hub-pull-request.1.html
https://hub.github.com/hub-issue.1.html
I don't know whether gitlab has something akin to hub.
On Tue, Aug 21, 2018 at 10:43 AM Erik Bray <erik....@gmail.com> wrote:
> What does everyone think? Is there anyone opposed to going ahead and
> opening up merge requests?
4x +1 (not including myself, which is an additional +1)
1x +0 (how I am interpreting Dima's response, which did not include
an explicit +1 but seems positive; he can correct me)
2x -0 (how I am interpreting Jeroen and Simon's responses, pending
some explicit correction from them)
2x -0 (how I am interpreting Jeroen and Simon's responses, pending
some explicit correction from them)
To answer again some of the concerns that have been raised, if I am to
be honest I am in favor, long term, of moving away from Trac entirely.
However, that is *not* what is being proposed here, and I have no
concrete plan for a full move off of Trac. If this does lead to a
"slippery slope" of more people wanting to move to GitLab from Trac I
see that as a positive thing: For all the advantages of Trac, if
enough people see a net positive to using a new tool, then so be it.
However, it will be hard for the community to even get a feel for
other tools if we don't (optionally) incorporate them into our exiting
workflow at some level.
I'll leave this open for more comments until the end of this week
before making any moves.
P.S. If anyone has additional comments, positive or negative, on
https://trac.sagemath.org/ticket/25914 they would be most appreciated
P.P.S. See PEP-581 (https://www.python.org/dev/peps/pep-0581/) for an
argument in favor of moving from CPython's legacy Roundup-based issue
tracker entirely to GitHub. With the exception of a few
Roundup-specific issues, I feel that the argument applies largely the
same for Sage/Trac.
--
You received this message because you are subscribed to the Google Groups "sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+...@googlegroups.com.
To post to this group, send email to sage-...@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.