On Wed, Mar 14, 2018 at 12:33 AM, Dima Pasechnik <dimp...@gmail.com> wrote:
> Perhaps it's a silly suggestion, but what does prevent trac from using an
> external git server, as opposed
> to the internal one? Does it need to do git calls which are not possible to
> do remotely?
> If this is possible (perhaps there is even a trac plugin for this?) then it
> would be possible to use, say, github to
> hold branches, and not git.sagemath.org...)
This is something I am working on *in addition to* the existing
git.sagemath.org. I am also investigating using GitLab for this
purpose. The use of GitLab has a couple motivations:
1) Julian Rüth's work on a new continuous integration system for Sage,
particularly using GitLab in nice ways:
https://trac.sagemath.org/ticket/24655
2) Being possibly more politically acceptable to some, at least as
middle-ground (it's all open-source; can move to self-hosted if need
be).
This would not be as a *replacement* to Trac mind you--just a
companion. We might pursue more GitHub integration in addition to
GitLab; I haven't ruled it out (e.g. opening Trac tickets for pull
requests from GH).
More on this as more of the details come into focus.
> On Friday, March 2, 2018 at 12:14:08 AM UTC, Erik Bray wrote:
>>
>> On Mar 2, 2018 01:00, "Erik Bray" <erik....@gmail.com> wrote:
>>
>> I'm not sure what "git trac config" does. If you've configured your SSH
>> key then there's nothing else to do but push branches. There's nothing to
>> use a username or password for.
>>
>>
>> Oh I see now. This is Sage's git extensions for creating tickets on Sage's
>> Trac server. I forgot about this since I haven't used it, but I can see how
>> it's convenient.
>>
>> The GitHub authentication doesn't know anything about your GitHub
>> password. You'll notice that you (probably, unless you needed to log into
>> GitHub) never provided your GitHub password. Instead you just authorize
>> Sage's Trac site to use your existing GitHub credentials to authorize you.
>>
>> So the "git trac" commands won't currently work with this I guess, though
>> I could make that work. In the meantime you can always create tickets
>> through the web interface and use the normal "git push" command to push
>> branches. The only thing "git trac" needs any additional credentials for is
>> creating and updating Trac tickets from the command line.
>>
>>
>> On Mar 1, 2018 10:21, "Dima Pasechnik" <dim...@gmail.com> wrote:
>>>
>>> AFAIK, github login only allows you to comment on tickets. Commit access
>>> to trac git repo needs to be obtained in the old way.
>>>
>>> --
>>> 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.
>>
>>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
--
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
