The Great Inkscape Bug Migration
Help us migrate bugs by converting them from the LaunchPad bugtracker to the GitLab bug tracker.
Win awards, swag and stickers by discovering special bugs and compete for top Bug Wrangler stats in our Leaderboard.
Become a Bug WranglerTo play, you'll need these things first:
- An account on LaunchPad. Register here if you don't have one.
- An account on GitLab. Register here if you don't have one (Click the "register" tab).
- The latest Inkscape.Download Here.
Find an Open Bug!
- The easiest way to find an open bug is to open this link on LaunchPad.
- Bookmark this page, because it shows a special view with claimed and fixed bugs filtered out.
- For reference, a bug is considered open when:
- (a) It's not tagged "bug-migration"
- (b) Its status is one of the following: 'New', 'Incomplete', 'Opinion', 'Confirmed', 'Triaged', 'In Progress'.
- (c) It's not marked as duplicate.
- If the bug is open, you can start working on it:
- Make sure you are logged in so you can see the editing controls for the bug.
- Edit the bug's tags and add the "bug-migration" tag - doing this immediately minimizes the chances someone else will start working on the same bug.
- Test the bug with the latest Inkscape to reproduce the bug and determine whether the bug needs to be migrated to GitLab, or if it can be closed without further work on LaunchPad (e.g. can not be reproduced, fix released, etc.).
- If the bug needs to be migrated, search for duplicates on Gitlab. In case the issue has already been reported to GitLab, add a comment in the GitLab issue linking to the LaunchPad bug report, and copy over relevant LaunchPad comments. Skip the next paragraph and go to Closing issue without migrating to GitLab.
If the bug needs to be migrated:
- Make a new bug report by clicking the "New Issue" button on GitLab.
- Look at the title of the bug in Launchpad. If the title is very general or does not fit the actual issue reported, don't hesitate to improve it. It will make it significantly easier to find your migrated report and work with it! If the title is fine, copy/paste it into the Title of your new issue on GitLab. Otherwise, type a new and better Title instead into GitLab.
- As the first line of the description, type "Migrated from: " and paste the web address of the bug on Launchpad after it. Example: "Migrated from: https://bugs.launchpad.net/inkscape/+bug/170703".
- Read the description of the bug from Launchpad, and use it to fill in the Gitlab information which is requested in the template. If information is missing, please add it from your own test of the bug.
- Read over the comments associated with the bug in Launchpad, and write a summary comment in your new GitLab bug report, which includes the important information. In particular, collect reproductions of the bug (Inkscape version and operating system), also from duplicates.
- Copy and paste any important comments and examples from Launchpad into your summary comment.
- Check attachments which are associated with the Launchpad bug, and if they are relevant, attach them to your GitLab bug report. Don't hesitate to add your own replication file and/or stacktrace.
- Click the "Submit Issue" button.
Closing on LaunchPad
Closing and migrating to GitLab
On Launchpad, mark the bug Status as "Invalid", and add text like the following in a final comment:
Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here. Please feel free to file new bugs about the issues you're seeing at http://inkscape.org/report. Moved to: https://gitlab.com/inkscape/inbox/-/issues/XXX Closed by: https://gitlab.com/USERNAME
Replace 'XXX' with the new bug number on GitLab, and 'USERNAME' with your GitLab username. The link lets the reporter follow their bug, and the username lets you get credit for the migration.
Closing without migrating to GitLab
On Launchpad, close the bug with the appropriate status (Fix Released, Invalid, Can't Replicate, etc.) and add text like the following in a final comment:
Closing because [insert explanation here]. Closed by: https://gitlab.com/USERNAME
Replace 'USERNAME' with your GitLab username - that lets you get credit for the closure.
Each LaunchPad bug converted to a GitLab bug or closed on LaunchPad will earn you bug points based on the difficulty of the bug. You can check your progress on this leader board (updated every 15 minutes).
Bug Point Medals - When you close bugs, you get points. When you achieve the next level of points, you get an achievement medal. The leaderboard shows how far away you are from the next level - Bronze, Silver, Gold, Platium, and Diamond. This award level is shown next to your name on the Leaderboard.
Collecting Special Bugs - Some bugs (issues on Launchpad) are Special Bugs which will automatically appear in your "specials" area on the leaderboard. They are distributed throughout the entire bug population, so the more bugs you migrate the more opportunities you have to discover and collect them! Additionally, each Special Bug is also worth bonus bug points which will be added to your total.
Once the event is over, we will ship you your award medal stickers and a sticker for each special bug you have collected. Before this, you will have the opportunity to trade special bugs with others on the leaderboard to get the ones you were hoping to find.
Each time a new Special Bug is discovered, an announcement will be made on our social media platforms about who has found the first one, as well as an animated illustration of the bug, which you can find on the Bug Field Guide.
There will also be special prizes (Inkscape shirts & mugs, etc.) awarded to the those who earned the top three highest bugpoint scores. (to be announced)
The goal of this game is to collectively migrate all of the open bugs from Launchpad to GitLab. The game ends when the last bugs have been migrated.