Page Comparison

2 min

• How did it go? Reporting out on progress
  • List is up on GitHub!
    • Added Code4Lib’s CodeofConduct4Lib to contributing guidelines
    • Added new section for APIs and Scripts and moved the list items that Justin and Tina had left comments on or bolded the words ‘scripts’ or ‘API’ in the description to this section
    • Added our conversation about ongoing maintenance of the list to the Ownership and credits section
  • Everyone reviewed it!
    • Removed General Resources category
    • Any additional comments?
  • "Announced" list to community!
• TAC Retrospective
• Address any issues that have arisen
• Other?

Putting up on GitHub:

• Which repo? 
  • Do we have necessary permissions?
  • Maggie is following up with Laney on this
• Initial populating: Maggie
• Double checking: All
  • Maggie will send link and ask for feedback when it's up

Discuss ongoing maintenance of lists.

• Has an owner been identified?
  • Vice Chair of TAC
• Do we need to pass on any information to them? How to communicate that info?
  • scope of the list and project – should be all detailed in the READ ME
  • make sure that we're updating it, continuing to solicit feedback so that list is actually helpful
  • general recommendation for owner – respond to all pull requests, monitoring of the list serve and adding new content as you come across it. 
  • every couple of years a new working group to do an in-depth review of the list
    • put a note in the ReadMe
    • every two years?

 – June

Check-in on the community's reception of the list? Any participation? Any improvements we can make?

What else do we have left to do?

Final meeting! Thank you!!

Reflect on two questions via email:

• What did we do well this year?
• What didn't go well, or what could we do better next year?
• and: How has your experience on a TAC ad hoc working group been?

Anything, small or large, task- or process-oriented or more existential, is welcome.