[2023/2024] Project Documentation - Backlog from 2022

[aleesteele]

Summary

This issue is to log ongoing documentation needs on the governance and project level - also can be tied to #1777

What needs to be done?

• Create ACCESSIBILITY.md file #3145
• Update GOVERNANCE.md file (already created), but needs to be updated for our current structure. #3188
• Related to Formalising a TTW infrastructure working group #2690 (infra, translation & localisation, and other working groups), Governance Taskforce initial proposal draft and process for The Turing Way #2035, Recruiting community members in visible roles in The Turing Way #2230, Adding the initial notes for the Governance planning #2036
• Update CONTRIBUTING.md file (already created), with updated pathways
• Related to Contributing guidelines [Join the conversation] #16 Draft Code of conduct & contributing guidelines #17 Add a ways of working document #26
• Create a history page for The Turing Way #1731 - cowriting history with testimonies
• Add slack policy to Community Handbook, with a general guide to channels as they are currently.
• Update Book Dash policy in Community Handbook for application/review process
• Update the Fireside Chat checklist and description to account for shifts in the past year
• Create a Collaboration Cafe case study (as discussed in [NEW CHAPTER] - Collaboration Cafe case study (AIM RSF) #3059)
• Add CW21 abstract and invite volunteers to co-lead this #1738
• also tied to Update files in the repo to avoid any outdated information #2031 (draw from information from onboarding HackMD: https://hackmd.io/pBysnLn2QxKMCHqPKvj9uA?view
• Add "Emergence as The Turing Way's" strategy to the Book: https://hackmd.io/kVkwKSYuSLWWhLzlNSuT0g #3545
• Summarise different fireside chats as subchapters in community handbook #2344
• Adding 2021-2023 TTW Fireside chat organisers/speakers to contributors table #3032
• Update 'Suggested Citation' section on the TTW Index page #3187
• Update Contributors table and Contributors record to make it easier for newcomers to find reference points for chapters & topics
• Document how HackMD is used by TTW Community for Community Handbook (noted by @BatoolMM) - or framapad, etherpad, etc
• Document how to write alt-text for scriberia images in the Community Handbook
• Add platform research/auditing document/chart to Community Handbook
• Add template planning document for fireside chats to Community Handbook
• Setting up a start page template
• Documenting all the different community calls - currently being addressed by [READY FOR REVIEW] Reorganising community calls and archiving notes about retired calls #3533
• General 'maintenance' chapter - what does it mean, why is it important, etc?
• Add workshop templates and information about teaching that TTW does in the community handbook
• Add template forms for open communications reviews
• Adding accessibility practices for posting/using social media (Slack, Mastodon, Twitter, Linkedin)
• Do's & don'ts for archiving notes (tied to Review Data Protection & practices for different parts of the project #3534)
• Add sample comms plan
• Add platform auditing

Who can help?

Anyone interested in updating our policies as a community, and keeping us as accessible and as open as we can be! I have also been keeping a personal log here: https://hackmd.io/GD_ZBGalRZOtiQjbnlEebg

---

Updates

[BatoolMM]

@aleesteele Let me know if I can help with creating HackMD guides and how it is used by TTW Community for Community Handbook!

[aleesteele]

Add the color palette to the community handbook