Re: [Mixxx-devel] launchpad bugtracker

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 

Re: [Mixxx-devel] launchpad bugtracker

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

Re: [Mixxx-devel] Mixxx manual info

Ok, in that case 2018-01-31 is a good date for manual string freeze. Am 16.11.2017 11:13 nachm. schrieb "Sean M. Pappalardo - D.J. Pegasus" < spappala...@mixxx.org>: On 11/16/2017 01:26 PM, Daniel Schürmann wrote: > I am afraid 2018-01-31 is to short for a polished English Doku and then >

Re: [Mixxx-devel] launchpad bugtracker

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

Re: [Mixxx-devel] launchpad bugtracker

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:

Re: [Mixxx-devel] launchpad bugtracker

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:

Re: [Mixxx-devel] launchpad bugtracker

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

Re: [Mixxx-devel] launchpad bugtracker

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

Re: [Mixxx-devel] launchpad bugtracker

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

Re: [Mixxx-devel] Mixxx manual info

On 11/16/2017 01:26 PM, Daniel Schürmann wrote: > I am afraid 2018-01-31 is to short for a polished English Doku and then > wait for translations. So we need to find a mode to do things in parallel. That's not really possible. Translators depend on the English manual being complete and stable,

Re: [Mixxx-devel] Mixxx release schedule / We need help!

I am afraid 2018-01-31 is to short for a polished English Doku and then wait for translations. So we need to find a mode to do things in parallel. How can we allow to polish the English until 2018-03-31 without loosing translations in other languages? I think for non English speaking users

Re: [Mixxx-devel] Mixxx release schedule / We need help!

Hi Radu, Thank you :-) I think the looping feature deserves an own new chapter. It would also a great help to verify the current manual with the current Mixxx version and it's changes and file GitHub issues for all missing features. Am 16.11.2017 um 20:00 schrieb Radu Suciu: I have some

Re: [Mixxx-devel] Mixxx release schedule / We need help!

I have a big PR in progress for reorganizing the early chapters of the manual: https://github.com/mixxxdj/manual/pull/60 Feedback on that would be helpful. I think we should set a deadline for the manual between the beta and final release to allow more time to get the English version together

Re: [Mixxx-devel] Mixxx release schedule / We need help!

Hi. Yesterday I had a look at the manual after quite a while and found it very hard to read on screen. These issues jump out immediately: - serif font is fine for printing, but sucks on screens - lines are way too long, respectivly: - format is to wide to have it next to or on top of mixxx

Re: [Mixxx-devel] Mixxx release schedule / We need help!

I have some time after next week to do some work on the manual, is there a list of things that need to be updated/written? On Thu, Nov 16, 2017 at 8:23 AM, Daniel Schürmann wrote: > Hi Mixxx developers, > > I am glad to announce a release schedule for Mixxx. We have decided

[Mixxx-devel] Authentication consolidation

Hello everyone. In an effort to reduce the number of sites at which one needs to register for Mixxx's various services, I am in the process of implementing OpenID Connect wherever possible so you will be able to use your existing Facebook, Google or GitHub accounts to log in, starting with the

Re: [Mixxx-devel] launchpad bugtracker

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

Re: [Mixxx-devel] launchpad bugtracker

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

[Mixxx-devel] launchpad bugtracker

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

Re: [Mixxx-devel] Mixxx release schedule / We need help!

To focus efforts on getting things together for the feature freeze at the beta release, I'll temporarily hold off on reviewing controller mappings until the beta release is out. You're welcome to submit them now but they won't be reviewed for a weeks. Mappings may be submitted for inclusion in

[Mixxx-devel] Mixxx release schedule / We need help!

Hi Mixxx developers, I am glad to announce a release schedule for Mixxx. We have decided to switch to a deadline based, 6 month release cycle. Releases: 2018-03-31 Mixxx 2.1 2018-09-30 Mixxx 2.2 and so on. To reach the Mixxx 2.1 date, we have decided to release a 2.1 beta and 2.2 alpha at ->