On 11/18/2017 03:24 PM, Daniel Schürmann wrote:
Hi Be,
It's just as unreasonable to expect new contributors to sign up for 7
different accounts (GitHub, IRC, phpBB, Freenode, mailing list,
Launchpad, wiki) as it is to expect long time developers to pay
attention to all of them. It would be easier if there were less things
to pay attention to.
Yes sure. Sean is working on it. But It is reasonable to distinguish
between user support and bug tracking like we do with forums and
Launchpad. User support can help each others, contributors can jump in
for unsupported use cases or bugs, that should be then tracked in a
different domain.
Yes, it is good to distinguish between those, but often times the line
is blurry. Often users come asking for support but they have actually
encountered a bug. It would be nice to easily move a conversation from
user support to the bug tracker in GitLab. GitLab also makes it easy to
move conversations from code review to the bug tracker as well as other
features that would make code review nicer. Please look through
https://docs.gitlab.com/ce/user/discussions/
Looking dated is important. Newcomers are telling us in no uncertain
terms that they don't want to use Launchpad and by and large they
aren't. What features Launchpad has are irrelevant if people don't use
them.
Yes, right. But I am in doubt that this is a impossible hurdle.
Remember, the user asks for free support.
The bigger issue than the old fashioned design is requiring to register
an account on a little known platform that has been in decline for
years. Then when a user goes to sign up for Launchpad to report a bug
for Mixxx, they're brought to a page that says "One account to log in to
everything on Ubuntu". The sign on/register page says nothing about
Mixxx or even Launchpad and has a totally different look and feel from
Launchpad. That is confusing and I suspect turns away people who have no
idea what Ubuntu is, or do know what Ubuntu is and don't trust it (see
https://en.wikipedia.org/wiki/Ubuntu_(operating_system)#Amazon_controversy
), or do like Ubuntu but get confused why they're suddenly at a page
that says nothing about Mixxx or Launchpad. This is a bad user experience.
Can you elaborate on "has more bug states than just open and close"?
What else is needed? GitHub and GitLab both have project-defined tags
that can be used for further organization. GitLab allows projects to
define priorities for custom tags.
...
This gives an explicit info about the bug state during it's live time.
We may use Label/Tags for it but than we loose the original tagging
feature, we use for group bugs under a topic. Or we mix both state and
loose a lot of clarity. If we than add additional tags for blueprints,
we use a single feature for tree purposes, which is at least a
regression compared to Launchpad.
...
> GitLab has a little more issue states.
> The bug states request was rejected in favour of the dashboard:
> https://gitlab.com/gitlab-org/gitlab-ce/issues/17186
I agree, it is nice to have a dedicated field for that apart from other
tags. But I do not think it is essential. I am interested in trying
GitLab's issue board solution.
The GitLab dashboard is only for registerd users with access right > I do not
have discovered it for GitHub
If you compare the Homepages, you will see the difference:
https://github.com/mixxxdj
https://gitlab.com/inkscape/
https://launchpad.net/mixxx
Launchpad is more user focussed and giving the best overview.
I do not know why you can't see the issue board for Inkscape. Perhaps
they haven't enabled the feature for their organization. But I can see
it for the GitLab server software:
https://gitlab.com/gitlab-org/gitlab-ce/boards
I think it could be really helpful to make a GitLab repository for
controller mappings. We could use its issue tracker to take requests
for controller mappings so users could vote for mappings they want.
That would give us data on what hardware is important to map, which
could guide us on what to ask manufacturers for and/or what to spend
donations on.
As we did it for manuals, we may split out mappings from the main repo.
Yes, and GitLab makes it easy to cross reference and move issues between
repositories within an organization. This could help with the issue of
keeping the manual updated as new features get developed without having
to keep it in the same Git repository. Milestones in GitLab can be
defined at the organization level and shared between all the
organization's repositories.
FWIW, GitLab allows importing from GitHub Issues. We could do a
roundabout import from Launchpad to GitHub then GitHub to GitLab.
https://docs.gitlab.com/ce/user/project/import/github.html
This sounds the same as compressing and mp3 with aac :-P
Yeah, I suspect there would be information lost in an annoying way. We
could try it anyway, or alternatively we could start the issue tracker
fresh after the 2.1 release.
------------------------------------------------------------------------------
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
