Page Comparison

...

1. Roll call (please log in above)
2. Feedback from first docs work session:
   1. Focus on backlog grooming, prioritization.
   2. Better labels: specifically Content vs. Jekyll vs. Organization
3. Project management
   1. Can we get rid of the "Backlog" column? Doesn't seem very useful. The issues list can be the backlog, and the "On Deck" column
   2. Proposal for new ticket lifecycle:
      1. Create Issue => "On Deck" => "In Progress" => PR => "Done"
      2. Don't put PRs on the project board; only tickets. (All PRs should refer to at least one ticket).
      3. If a ticket is not ready, or we don't know if it's ready, then keep it off the project board.
      4. If a ticket is ready, move it to "On Deck"
      5. "On Deck" should be prioritized, ideally.
      6. "On Deck" tickets need not be assigned.
      7. "In Progress" tickets should be assigned.
4. Review project board: https://github.com/projecthydra/projecthydra.github.io/projects/1
   1. Reporting on items completed since last meeting
   2. Review status of in-process tickets
   3. Discuss ready items & groom backlog
      1. Any new items needed?
      2. What should be moved to ready?
5. Other agenda:
   1. Standing working time
6. Pick facilitator / notetaker for next time
   
   1. Notetaker is responsible to copy template agenda into a new agenda for next meeting and add any followup items immediately.

Notes:

Feedback from work session on Friday:  Who was there - what tickets got worked on.  - advise on what happened in that meeting

Would like Work Session to be a normal thing.  Maybe use this time to groom tickets.  

"On Deck" is stuff we're working on.  "Backlog" are potential issues.  Lot of stuff missing from Backlog that isn't on project board.

On POint 2 - if we do some prioritization: labels: Content, Jekyll, Site Organization

New labels:  "New Content" and "Change Content"

People at work session will have different expertise and need to pick up tickets suited for them.  

Move to get rid of Backlog - seconded.  LaRita may know how to do it.  Column removed.

From now on - create issues in GitHub like any other project - as part of this WG meeting, we can groom issues and decide priority.  Can pull into on-deck column as a form of prioritization.  Keep tickets on Project Board and not PR's.  Hard to know what "done" looks like.  Easier if just tracking the ticket.  

Make tickets - make that "done" part is part of the ticket.  LaRita pulled "Done" things into 'Done" Column.  A place to move things out of "In Progress" Column.  Abandon ticket - "Done" or do we just remove it?

Prioritized "On Deck" Column and "In Progress" so we can see who is working on what.

Action items