Tobias,
I'm excited to get you involved! Come over and join us on
chat.inkscape.org, which is running Rocket.Chat. This seems like
it would warrant it's own channel on there (which I can get
setup). The prior UI team seems to have dissolved so let's get
something going anew, perhaps more broadly interested in UX. I'm a
designer, but have focused my contributions more on the
outreach/promotion side of things. I'd be happy to provide
feedback via chat as requested, and can perhaps make some visual
design contributions as time permits. Likewise we're going to
start tackling a website revamp here and it would be good to get
some of your feedback as well.
Your points about Launchpad/mailing-lists/IRC resonate with me,
but for now I can at least get the media-friendly, real-time chat
component working better for you and anyone else waiting in the
wings to get involved on the UX side of things. Let me know if
you'd like that.
Hi Bryce, Mailing lists are old-school, and not very productive for discussion in my experience, IRC requires you to be online to see messages and doesn't really work on mobile, and Launchpad is, well, Launchpad ;) It would be nice if IRC could be replaced with Matrix or some other more modern alternative. For design work, I find the most important thing in communication tools is inline image/media support, which makes Email+Launchpad+IRC a particularly bad combination. What I don't quite understand is why all the old bugs need to be migrated before allowing opening new ones on Gitlab. What's the reasoning there? I'd be happy to help out with bug triaging on Gitlab if that's needed. Cheers, Tobias On Fri, Nov 2, 2018, at 01:17, Bryce Harrington wrote:Hi Tobias On Thu, Nov 01, 2018 at 12:17:50PM +0100, Tobias Bernard wrote:Hi all, I'm a UX designer and long-time Inkscape user. I work at Purism, and I'm on the GNOME design team. I've been meaning to get involved with Inkscape for years, but the tools used for development (Launchpad, mailing lists, IRC) don't make it very easy unfortunately.We do have changes afoot for all three of those, but I'd like to better understand what it is about them in particular that you find to be not very easy?I was very happy when I saw the code migrated to Gitlab, because it's a much more modern tool that works great for design issues thanks to inline media (we've been using it in GNOME for the past year and it's been a total game changer). Unfortunately, though the code is on Gitlab now, it's still not possible to open issues there. I was told this would change "soon" earlier this year, but so far this hasn't happened. Is there a timeline for opening issues on Gitlab? What are the current blockers? I'd really like to avoid using Launchpad if at all possible :)In fact, you can see this topic is on the agenda for tomorrow's board meeting, which you're welcome to attend. You have to understand with as many bug reports that Inkscape has, it's not just a flip of a switch to change bug trackers, and it has impact on a lot of different established workflows. Not really a blocker, but one of the major concerns is getting manpower to triage bugs in gitlab. So a way you could help in moving things forward here would be to volunteer to participate in this work. Bryce_______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel