Moving the blog issue tracker to www-gitlab-com
Discussion
It's my understanding that we are willing to move all the issues from this project to www-gitlab-com.
- Question: is this decision opened to discussion?
- Question: are we still interested in doing this?
- We'd have issues, code, and MRs in the same project, applying the GitLab Workflow accordingly
- We'd filter them to transfer only good issues and close the ones that don't make sense anymore (or are not important anymore)
- It will be time-consuming transferring them (moving, applying new labels, creating new labels, etc). Up-for grabs issues would have to be moved all at once so we could change the link to them on the blog handbook and on the community writers page.
- Both community and team members would land in this tracker and ignore closed issues (but most of these issues were just transferred, not necessarily closed). We might loose good opportunities here.
- We'll "overload" the www-gitlab-com project with tons of issues.
- The only way to track blog posts issues would be via labels/issue board. Contributors would add issues with no labels and they may get lost in the tracker. While here, in this project, we know they're all here.
More cons and pros? Please add to the discussion!
Plan of action
If we stick with the decision to move, this would be the plan of action (thoughts?):
-
Day 1: Create a task force to close the issues we don't want to pursue, starting with the ones labeled up-for-grabs -
Day 1: Transfer all the remaining up-for-grabs to www-gitlab-com at once (move and add labels) -
Day 1: Update the blog handbook and the community writers page -
Day 2: Task force to close the issues labeled with up-for-grabs-GitLab that we don't want to pursue -
Day 2: Transfer the remaining ones to www-gitlab-com (and re-label them) -
Day 2: Update the blog handbook -
Day 2: Announce on the team call -
Day 3: Task force to close all the other issues -
Day 3: Task force to move all the other issues (and label them) -
Day 3: Arquive this project -
Day 4: Announce on the team call
Task force: gather 1 or 2 functional group team members to volunteer - (DevRel, Lead Gen, Publishing/Branding)
cc/ @sytses @timanglade @SeanPackham @afolson @erica @afolson @connorshea @axil
Edited by Achilleas Pipinellis