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 make it too easy
to file, we'll get low-quality bug reports.)
Yes, we could add the email address to the form, but publishing it on
Launchpad is probably an unwanted side effect.
And Hey, If the user cannot effort the time to sign in to Launchpad, why
should we effort time to fix the bug he is suffering. :-P
Am 17.11.2017 um 17:18 schrieb Sean M. Pappalardo - D.J. Pegasus:
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. Registering a second account is
anoying, and stops user from filing bugs.
On that note, I'm working on consolidating logins as much as possible.
https://bugs.launchpad.net/mixxx/+bug/1732715
My plan is to get down to two: Launchpad and GitHub. (Because neither of
those allow authentication from another provider.)
On the other Hand Launchpad has our history, and no other tool offers
the same rich bug states, that we have adopted in our process.
To wit, we started using LP for bug tracking even before we moved the
code there.
We have hundreds cross linkes, between GitHub, Forum, Wiki, and
Launchpad. Losing this had to be well considered compared to some
missing convenient features.
I totally agree. Never mind the work it would take to do a migration,
work that would be better spent on Mixxx itself, IMO.
So the question is: how much more productive would we be if bug and
blueprint tracking was integrated with code hosting? Put another way,
how much is the current separation impairing productivity?
(Keep in mind that Launchpad supports Git now, so it would be possible
to move code hosting back there, solving this particular concern.)
Filing Bug inside Mixxx would be the most convenient solution.
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 make it too easy to file, we'll get low-quality bug
reports.)
We already have the "submit feedback" Google form which seems to be
working well as it has hundreds of responses. (I need to check on how to
publish them.) And indeed some are not useful.
Launchpad offers to communicate via email. Maybe there is a solution
to send Emails from Mixxx to Launchpad?
Even better, it has a full Web API: https://help.launchpad.net/API/
(Which could be used for migration too.)
Sincerely,
Sean M. Pappalardo
"D.J. Pegasus"
Mixxx Developer - Controller Specialist
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Get Mixxx, the #1 Free MP3 DJ Mixing software Today
http://mixxx.org
Mixxx-devel mailing list
Mixxx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mixxx-devel
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Get Mixxx, the #1 Free MP3 DJ Mixing software Today
http://mixxx.org
Mixxx-devel mailing list
Mixxx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mixxx-devel
