For this page: https://inkscape.org/contribute/report-bugs/
I had 6 or 7 detailed comments/edits explained for the new contents under
"Search the bug trackers" which were added, but now I think I can say it easier
this way. Most of that info either repeats info that's already mentioned
elsewhere on the page, or can be.
Could I just edit the page, but not publish? Or would you like me to explain
every change which I would suggest?
Why is it suggested that users who find a bug already mentioned in LP, to
transfer it to GL? Aren't all the LP bugs going to be moved to GL anyway?
All best,
brynn
-----Original Message-----
From: Maren Hachmann
Sent: Thursday, January 17, 2019 12:13 PM
To: brynn ; inkscape-de...@lists.sourceforge.net ; Inkscape-Docs
Subject: Re: [Inkscape-docs] [Inkscape-devel] Issue tracking for Inkscape moves
to Gitlab
Brynn, bug experts,
I've now updated these pages:
https://inkscape.org/develop/bug-management/
https://inkscape.org/develop/getting-started/
https://inkscape.org/contribute/translations/
https://inkscape.org/contribute/report-bugs/
https://inkscape.org/learn/faq/
which contained link and mention of the launchpad bug tracker (most
still do).
Please review, and let me know when they are finalized (enough) for
translation.
Maren
Am 15.01.19 um 18:07 schrieb brynn:
If either 0.92.4 or 1.0 alpha is about to be released, can't the edits
just say 'from now on'? (Not really "from now on" specifically, but in
effect it would be - here's where new bug reports go now.) Because users
wouldn't be reporting bugs for 0.92.3 or older, after 0.92.4 is
released, would they?
Thanks,
brynn
-----Original Message----- From: Maren Hachmann
Sent: Tuesday, January 15, 2019 9:19 AM
To: brynn ; inkscape-de...@lists.sourceforge.net ; Inkscape-Docs
Subject: Re: [Inkscape-docs] [Inkscape-devel] Issue tracking for
Inkscape moves to Gitlab
Am 15.01.19 um 17:08 schrieb brynn:
I could try to do that. But I need specifics.
- Thank you, Brynn.
Is the only thing that needs to be changed is the link (and supporting
text around the link, if necessary)?
- No, the new policy about both bug trackers needs to be mentioned and
explained on the 'report bugs' page, at least.
However, for that we still need a reply from Bryce about the Inkscape
version that applies to. Wait for that before you start, please.
I can see why he said 0.92.4 and higher - because that's what is
currently under development. I don't know what Marc's rationale is for
only intending to do this for alpha and higher. Maybe there was some
kind of misunderstanding in their communication earlier, dunno, just
know that we need to know before we make any changes, and even before we
publish the release news article...
On the other pages, probably a simple switch is sufficient, or change to
a link to report bugs page if suitable, to have 1 central place that
needs to be updated instead of multiple places.
Should the link go to
https://gitlab.com/inkscape/inkscape/issues, or directly to open a new
Issue form?
- Better allow users to search for duplicates first, so not the new
issue form.
Of course I'll list every change for translators and send it to you :-)
- Thank you, that will be awesome.
I'm probably not the best person to update the wiki. I'm not very
familiar with it.
- If you find something that needs updating, you can let us know here,
then.
Maren
All best,
brynn
-----Original Message----- From: Maren Hachmann
Sent: Tuesday, January 15, 2019 8:08 AM
To: inkscape-de...@lists.sourceforge.net ; Inkscape-Docs
Subject: Re: [Inkscape-docs] [Inkscape-devel] Issue tracking for
Inkscape moves to Gitlab
Hi,
could someone help web content editors by browsing the website and
looking for places that require updating?
I think it's probably FAQ, the bug report page, contribute testing, and
develop pages.
Then there must also be some Wiki pages.
I'm currently a bit busy with other stuff, so I'd appreciate if someone
gave me a list with links + screenshots or similar.
Or, if someone updated the pages, that would be cool - but then I'd
still need a list (preferably with screenshots), for being able to
notify translators.
Maren
Am 15.01.19 um 10:56 schrieb Bryce Harrington:
Hi all,
As of this week, the Inkscape project is shifting to Gitlab for issue
tracking in place of Launchpad.
https://gitlab.com/groups/inkscape/-/issues
We've been using Gitlab for our code hosting and other purposes for a
year and a half now[1], and have found it to be reliable and
convenient. We didn't migrate Issue Tracking until now, so we could
take time to make sure we had a plan:
1. Going forward, new bug reports should be filed only in Gitlab.
2. Launchpad will remain available as a historical archive of our bug
reports. Filing bugs there will remain possible for now, but
discouraged.
3. Bugs in Launchpad that are still reproducible in Inkscape 0.92.4 or
newer can be re-filed on Gitlab and closed on Launchpad.
We are planning efforts to help organize the migration work and keep
track of progress. More info on this will be coming soon.
Eventually, when the necessary bugs have been migrated, bug reporting in
Launchpad will be shut off.
We're enthused about this change, and hope you too will find gitlab a
more user friendly way to report issues, and we'd love your help
triaging and solving Inkscape bugs.
Bryce
1: https://inkscape.org/news/2017/06/10/inkscape-moves-gitlab/
_______________________________________________
Inkscape-devel mailing list
inkscape-de...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
_______________________________________________
Inkscape-docs mailing list
Inkscape-docs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-docs
_______________________________________________
Inkscape-docs mailing list
Inkscape-docs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-docs
