Move lingering issues from old guides repos to new guide repo

[christophermather]

A description of the work

Background: there are some lingering issues in the old guides repos. These should be moved over to the new Guides repo so that we can sort through, prioritize and/or eliminate.

This whole ticket may not be doable in this increment, but we should prioritize getting admin access and moving the issues over so that we don't forget about them.

Guides

Guide	# of issues	Contact	Done?
Accessibility	4	@jasnakai	🟢
Agile	0	@adunkman	🟢
Brand	10	@igorkorenfeld	🟢
Content	0	@michelle-rago	🟢
De-risking	5	@adunkman	🟢
Engineering	11	@amymok	🟢
Engineering Hiring	8	@amymok	🟢
Product	1	@allisonnorman	🟢
User Experience	35	@juliaklindpaintner	🟢
Methods	25	@MelissaBraxton	🟢
Total	99

Point of contact on this issue

@christophermather

Reproduction steps (if necessary)

• Get admin access to old guides repos
• Review issues
• Move any that seem viable over to new guides repo

Skills Needed

• Any Human
• Design
• Content
• Engineering
• Acquisition
• Product
• Other

Does this need to happen in the next 2 weeks?

• Yes
• No

How much time do you anticipate this work taking?

1 week

Acceptance Criteria

• @christophermather has admin access to old guides repos
• Issues from old guides repos have been moved over to new guides repo
• The issues have been reviewed and prioritize (and some possibly deleted)

[christophermather]

Tracking these issues in this spreadsheet.

Issues from old Guides repos have all been moved over to the consolidated Guides repos. They all have labels identifying their origin repos. Methods issues have not yet been moved.

The issues from Guides need a little bit of sorting and prioritizing. I think they should be sorted in two ways:

1. Batch issues for code owner review. Some - maybe most - issues should get a review from the old repos' code owners, especially old issues that may no longer be relevant. We're looking for validation that "yes, this issue is worth holding onto".
2. Group like issues in epics. These issues may span across different guides. They may be driving towards similar outcomes (improve accessibility, update IA) or simply be addressing similar needs (broken links, etc.).

[amymok]

Hi @christophermather. Can you help me understand what I need to do here? Do you want me to look thru all the engineering items and say yes or no to hold onto? And where should I record that in the spreadsheet or else where? Thank you!

[christophermather]

Hi @amymok! No action at the moment - apologies for the premature notification!

I'm going to organize some tasks in our backlog for your review in a separate issue that will have some instructions. Hoping to actually have something your way by end of day today.

Thanks for asking!

[christophermather]

This work is done. For more info, see #393