Migrate poppler to gitlab
Checklist
-
Project contacts filled by by requestor -
CoC section filled by requestor -
Git repo information filled by requestor (or N/A) -
Bugzilla information filled by requestor (or N/A) -
Mailman information filled by requestor (or N/A) -
Web hosting information filled by requestor (or N/A) -
Migration request acked & scheduled by admin -
Migration in progress
Project contacts
Primary project admin (GitLab username): tsdgeos
Additional project contacts (GitLab usernames): carlosgc
Code of Conduct
-
My project agrees to the Code of Conduct
I guess there's no way to disagree, I already complained this was forced on projects without any kind of discussion, but complaining more seems useless at this point so i guess we'll agree
-
Where reasonable, we have placed links to the CoC within our project
I don't see anywhere i would add such links
CoC contacts (if different from overall project contacts):
Git repository migration
-
Migrate: cgit.fd.o/poppler/poppler
->gitlab.fd.o/poppler/poppler
-
Migrate: cgit.fd.o/poppler/poppler-data
->gitlab.fd.o/poppler/poppler-data
-
Migrate: cgit.fd.o/poppler/test
->gitlab.fd.o/poppler/test
There's also https://cgit.freedesktop.org/poppler/poppler-glibmm/ but up to today i never knew it existed, so that is "not us", so i'd say let it die there.
Bugzilla
-
Migrate bugs: all from Bugzilla product poppler
-> GitLab projectpoppler/poppler
Mailman
-
Mailman list: poppler@lists.fd.o
Web hosting
No, https://poppler.freedesktop.org/ is not a wiki and i think it's fine if it stays as it is; https://freedesktop.org/wiki/Software/poppler/ probably would make sense to be migrated or either die :D
[@daniels, 2018-10-20: fixed formatting]