Everyone please take a look at the list of problems with LP at the top
of https://mixxx.org/wiki/doku.php/launchpad_migration and add any you
feel are missing.
After a few days, I'll create bugs for each (and link them to an
"Improve/Replace Launchpad" blueprint ;) ) then we can all vote on those
Sure. The only problem is that we would have no way to communicate back to the
user (since the bug filer would be a bot account) without having to create a
separate E-mail thread. That would be quite a step backwards, especially since
it's not hard (anymore) to create an LP account. (Plus if we
On 11/17/2017 06:37 AM, Daniel Schürmann wrote:
> Here it is hard to rule GitHub. Nearly every developer has a GitHub
> account, and it is just click to clone Mixxx and starting to
> contribute.
GitLab does offer login with a GitHub account, FWIW.
> For Launchpad bug, suffers the same. Registe
We already have CI that every forker can use to test before PR.
just connect to travis-ci and appveyor with your github account, select
your fork, and you're done & you have CI on your fork.
we could be easier without the need to first register to travis and
appveyor, but it works well, I use
GitLab looks great. Unfortunately the last feature does not count.
What counts is getting things done.
Here it is hard to rule GitHub. Nearly every developer has a GitHub
account, and it is just click to clone Mixxx and starting to contribute.
If we ever leave GitHub, we will suffer the same issu
On 11/17/17 11:38, Be wrote:
What projects have you used GitLab for? What do you like about it
compared to GitHub?
I used it in my previous and current company for internal projects. I
was even the administrator in the previous one doing the upgrades etc.
Mostly small internal projects that al
What projects have you used GitLab for? What do you like about it
compared to GitHub?
On 11/17/2017 04:35 AM, Daniel Poelzleithner wrote:
Hi,
> That arcane and bizarre process for applying to use it for an open
> source project is immediately off-putting to me and gives me little
> confiden
Hi,
> That arcane and bizarre process for applying to use it for an open
> source project is immediately off-putting to me and gives me little
> confidence in the UX design of the software.
we could consider gitlab as a all inclusive solution. Used it for years
now and it's a good to use peace
That arcane and bizarre process for applying to use it for an open
source project is immediately off-putting to me and gives me little
confidence in the UX design of the software.
On 11/17/2017 01:12 AM, Sébastien Blaisot wrote:
Le 16/11/2017 à 18:44, Sean M. Pappalardo - D.J. Pegasus a écrit
Le 16/11/2017 à 18:44, Sean M. Pappalardo - D.J. Pegasus a écrit :
On 11/16/2017 09:11 AM, Daniel Poelzleithner wrote:
is there a particular reason from using the launchpad bug tracker
anything other then historic reasons ?
It does some things better than GitHub Issues. I have created a wiki
pa
I took a closer look at GitLab and I'm pretty convinced we should switch
to it for issue tracking, code hosting, and continuous integration after
the 2.1 release. It has come a long way in the last few years and seems
to be better than GitHub at this point. I have compiled a list of
GitLab's fe
Of course. It would be silly to switch to GitLab for issues without also
switching to it for code hosting. Looking more at GitLab, it seems to
have quite a few nice features that GitHub does not. I am working on
comparing them on the wiki, feel free to contribute:
https://mixxx.org/wiki/doku.ph
Moving to gitlab for issues while sticking to github for code would come
with all the annoyances of having to switch systems without any of the
benefits of having code and issues in the same place..
On Thu, Nov 16, 2017 at 5:41 PM, Sean M. Pappalardo - D.J. Pegasus <
spappala...@mixxx.org> wrote:
On 11/16/2017 03:14 PM, Joan Marcè i Igual wrote:
> has anyone taken a look at GitLab and what may be the pros and cons
> compared to the other issue trackers?
It looks like RJ did awhile back, around the time we were looking to
move to git: https://gitlab.com/mixxxcommunity
(The branches in the
Yeah, GitLab and GitHub are similar AFAIK. I think GitLab lagged behind
GitHub in features in the past but they're pretty even at this point. I
like that the GitLab server software is free, so I'd personally start a
new project on GitLab, but I haven't found a convincing reason why it
would be
Hi,
has anyone taken a look at GitLab and what may be the pros and cons
compared to the other issue trackers?
Regards,
Joan
On Thu, 16 Nov 2017 at 19:18 Radu Suciu wrote:
> Regarding disadvantages of GitHub
>
> *Doesn't explicitly support rich states other than just open/closed*
> If for progr
Regarding disadvantages of GitHub
*Doesn't explicitly support rich states other than just open/closed*
If for progress tracking - milestones are great for this.
*Not possible to link related issues*
Maybe not in the same way, but you can links commits to issues in a really
nice way
*Not possible
On 11/16/2017 09:11 AM, Daniel Poelzleithner wrote:
> is there a particular reason from using the launchpad bug tracker
> anything other then historic reasons ?
It does some things better than GitHub Issues. I have created a wiki
page to enumerate the problems people have with it as well as pros
Hi,
is there a particular reason from using the launchpad bug tracker
anything other then historic reasons ?
I suggest migrating to github issues so it is easier to follow the
project and don't have everything on many different services.
kind regards
poelzi
---
19 matches
Mail list logo
