Inkscape migration to GitLab

Goals

• using Gitlab efficiently to develop Inkscape

Quick Facts

• Our project is particularly keen on only using open source software

• Timeline. -

• Product. - GitLab.com

• Project's License. **What kind of OSI-approved license does your project use? GPLv3+

Collaborators

Inkscape

@dehesselle , Mac packaging

@ede123 , Windows packaging

@doctormo , Python & Infra

Many others ( @inkscape/devel & @inkscape & others )

GitLab

• Nuritzi Sanchez, @nuritzi
• Greg Myers, @greg

Related Issues

• We tried to gamify the import of our thousands of old issues from launchpad to avoid migrating duplicates and obsolete bugs
• We find the "new" way of .gitlab-ci.yml with rules and "detached" pipelines, much more confusing than the old one, even if looking more powerful, so I'm still not sure what would happen with a rewrite of that file.

Blockers

• gitlab-org/gitlab#17374 is a blocker to using the "release" API --- Status: It looks like there might be a workaround for now because the team would like to see this be implemented upstream: gitlab-org/gitlab#17374 (comment 382064749)

Urgent

• gitlab-org/gitlab#21966 (closed) ( solvable by gitlab-org/gitlab#23308 (closed) )
• gitlab-org/gitlab#35628 (closed)

Important but not urgent

• gitlab-org/gitlab#11648
• gitlab-org/gitlab#228562 (comment 412447165)

Nice to have

• gitlab-org/gitlab#224124 (closed)
• gitlab-org/gitlab#20696 (closed)
• gitlab-org/gitlab#241990 (closed)
• gitlab-org/gitlab#14190 (closed)

---

/cc @nuritzi