On 12/11/18 8:38 PM, Josh Smeaton wrote:
Jamesie: please see "Why not Gitlab?" [0]. While it might be better from
a technical standpoint, it would not be better than GH Issues from an
onboarding perspective.
[0]https://www.python.org/dev/peps/pep-0581/#why-not-gitlab
Note that they didn't
On 12/12/18 12:34 AM, Jamesie Pic wrote:
Thanks Josh, love your link, seems like it dates from 2017 during the
period when GitLab UI was redesigned. But GitLab is still emerging as
a standard tool no matter what.
I'm currently attempting to move some issues from github to gitlab. The
rant
Thanks Josh, love your link, seems like it dates from 2017 during the
period when GitLab UI was redesigned. But GitLab is still emerging as
a standard tool no matter what.
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django
Hey i do also code in django can we talk ?
On Fri, 26 Oct 2018 at 7:15 PM, Carlton Gibson
wrote:
> Hi All.
>
> OK, so last week I was at DjangoCon US in San Diego. (Thank you if you
> organised that! Hi! if we met and chatted.)
> I gave a talk ("Your web framework needs you!") inspired by the
>
For what it's worth, I agree. I think we should consider using GitHub
issues. I don't think there's anything in Trac, from a user perspective,
that we couldn't really do with Issues. The main issue, I think, would be
allowing non-committers (organisational members) to triage tickets and
change
Gitlab should be mentioned as a vastly superior alternative to trac +
GitHub + jenkins.
Le mar. 11 déc. 2018 à 14:01, Hanne Moa a écrit :
> Whenever I've had to move from one issue-system to another, the main
> pain point has always been issue/comment ownership[*]. This is because
> many
Whenever I've had to move from one issue-system to another, the main
pain point has always been issue/comment ownership[*]. This is because
many systems want a login-capable, verified user for every single
person that have ever made an issue or comment. If there is no 1-to-1
mapping, the
> The only reason Github issues would be a consideration is if the group
thought the onboarding experience (being where users already are with a
tool they're already familiar with) would have more value than sticking
with with the status quo which is strictly better from a feature
perspective than
I don't think something like Jira would even be a consideration.
The only reason Github issues would be a consideration is if the group
thought the onboarding experience (being where users already are with a
tool they're already familiar with) would have more value than sticking
with with the
