Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updating Guide Issues #131

Open
Tracked by #138
edwardsarah opened this issue May 26, 2023 · 5 comments
Open
Tracked by #138

Updating Guide Issues #131

edwardsarah opened this issue May 26, 2023 · 5 comments

Comments

@edwardsarah
Copy link
Member

Overview

Guide Issues Need to be Replaced with new format for instructions

Action Items

Review guide issues across CoPs and identify all of the issues that are in the gather examples phase.
Update them with the new instructions

Resources/Instructions

https://github.com/hackforla/guides/wiki/How-to-Gather-Examples

@edwardsarah
Copy link
Member Author

edwardsarah commented May 26, 2023

Instructions might look something like:

I'll work on temp pages for now and we can go back and edit them as the decks are finished. Peer Review & Leadership Review are just temp pages right now
Add wiki page explaining trail closed, only add gather examples stuff to issues.

@edwardsarah
Copy link
Member Author

edwardsarah commented May 26, 2023

Simplify & make it as clear as possible

Milestones

  • Phase: 1-Gather Examples
    • has been replaced with labels
  • Trail Closed (Everything Beyond Gather Examples)
  • Phase: 2-Drafting a Guide
    • has been replaced with labels (phase 3)
  • Phase: 3-Peer Level 1 Review (other people at CoP)
    • has been replaced with labels (phase 4)
  • CoP Guides Review (someone who has gone through gather examples training)
    • has been replaced with labels (phase 4, level 2)
  • Leadership Review (random sampling)
    • has been replaced with labels (phase 5)
  • Ready to Publish (guides team says it's ready
    • has been replaced with labels (phase 6)
  • Published

(formerly milestones) now cleanup (expected to be one time)

  • Needs to be Triaged
    • Guides team project board cleanup on CoP
  • Issue Rewrite Required
    • old template
    • too broad
    • unclear what its about

Work Status

  • Prioritized Backlog (nobody owns the issue)
  • In Progress (someone is working on this issue, either gathering examples, writing the guide, or rewriting the guide)
  • Ready for Review (needs a peer reviewer or leadership review, depending on label?)
  • Being Reviewed
  • Questions (for CoP leads or guides team)
  • Done (issue is closed, nobody else is going to work on it, which means it's on the website)

Ready for review & ready for rewrites important to highlight guides that are transitioning from one person to another. Either from writer to reviewer, or reviewer to writer.

  • labels for CoP lead review & guides team if there's something they need to look at, regardless of column.

Labels:

Phase: 1-Gather Examples Solo

  • status: needs wiki examples
  • status: needs project board examples
  • status: needs issues examples
  • status: needs slack examples

Phase: 2-Gather Examples Collaborative

  • status: needs communication with teams
  • status: needs special issue/check with admin (is this an optional label)

Phase: 3-Drafting a Guide

  • status: 3.1 needs draft
  • status: 3.2 unfinished draft
  • status: 3.3 needs template
    (is it important to discuss labels for this now? should we just focus on the gather examples labels?)

Phase: 4-CoP Peer Review

  • status: 4.1 needs peer review level 1*
  • status: 4.1 needs peer review level 2*
    *labels assigned based on what you need
  • status: 4.2 needs edits (after completing edits, repeat 4.1)
  • status: 4.3 sign off by peers

Phase: 5-Leadership Review

  • status: 5.1 needs CoP leads review
  • status: 5.2 needs edits (after completing edits, repeat 5.1)
  • status: 5.3 sign off by CoP leads
  • status: 5.4 needs guides team review

Phase: 6-Ready to Publish

  • status: needs staging

@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Jun 23, 2023

Milestones

01 Compliance
02 Security
03 Org Requirements
04 Project Management
05 Team Workflow
06.01 HfLA Guides: MVP knowledge
06.02 HfLA Guides: All teams do
06.03 HfLA Guides: Some teams do
06.04. HfLA Guides: We Must Do in future
06.05 HfLA Guides: We Should Do in future
06.06 HfLA Guides: We Could Do in future
06.07 HfLA Guides: We Won't Do in future unless something changes
Lightning Talks
Speaker
Mentor Night
Open Networking

@edwardsarah
Copy link
Member Author

Example issue with new template
hackforla/knowledgebase-content#24

@edwardsarah
Copy link
Member Author

Work status, milestones, and labels (through phase 4) have been added to knowledgebase-content repo & project board. held off on additional labels until we confirm the leadership review process

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: New Issue Approval
Development

No branches or pull requests

3 participants