├── .github └── ISSUE_TEMPLATE │ └── new-work-day-checklist.md └── README.md /.github/ISSUE_TEMPLATE/new-work-day-checklist.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: New Work Day Checklist 3 | about: This template is for creating new Work Day Checklists 4 | title: 'Checklist for: ' 5 | labels: '' 6 | assignees: '' 7 | 8 | --- 9 | 10 | ## Goal 11 | _Briefly introduce the goal of this issue_ 12 | 13 | ## Description 14 | _Briefly provide a description and/or context of this issue_ 15 | 16 | ## Action Items 17 | _Set of actions required in order to mark this issue as closed_ 18 | 19 | - [ ] action item 1 20 | - [ ] action item 2 21 | - [ ] action item 3 22 | - [ ] action item 4 23 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | [![todo contributors](https://img.shields.io/badge/TODO-Contributors-%23ecf87f)](https://github.com/todogroup) 2 | [![todo newcomers](https://img.shields.io/badge/TODO-Newcomers-%23adb6ff)](https://todogroup.org/community/) 3 | [![todo newcomers](https://img.shields.io/badge/TODO-Maintainer-%234120a9)](https://todogroup.org/community/) 4 | 5 | # Working Hours Documentation 6 | 7 | This repo is for tracking activities that we work on during OSPOlogy Working Hours. 8 | 9 | - [What are working hours?](#what-are-working-hours) 10 | - [Schedule and meetings](#schedule-and-meetings) 11 | - [Calendar invites](#calendar-invites) 12 | - [Process](#process) 13 | 14 | ## What are working hours? 15 | 16 | Working Hours are primarily for doing cleanup on the various issues and PRs in the [TODO Group GitHub organisation](https://github.com/todogroup). We've found that if we don't regularly set aside time to do these tasks, they never get done. 17 | 18 | Here is a list of things that we expect people to work during the WDA meetings. The list is sorted by TODO project contribution level, in descending order: 19 | 20 | ### *"I'm new" tasks* 21 | 22 | * 📩 Add [OSPONews content for next month](https://github.com/todogroup/ospology/tree/main/newsletter#how-to-contribute-to-osponews) 23 | * 🧑‍💻 Capture [new OSPO Job Descriptions](https://github.com/todogroup/job-descriptions) 24 | * 📌 Add [new tech & open source conferences](https://github.com/todogroup/presentations/blob/main/2022-tech-events.md) to the 2022 list 25 | * 🔭 Add new tools for [Awesome OSS Management tooling list](https://github.com/todogroup/awesome-ospo#awesome-oss-management-) 26 | * 🧭 Work on [OSPO Mind Map](https://github.com/todogroup/ospology/tree/main/ospo-mindmap) structure 27 | * 💚 Add new OSPOs or tooling to the [OSPO Landscape](https://github.com/todogroup/ospolandscape) 28 | * 💬 Help with translations! 29 | 30 | ### *"I'm in a working group" tasks* 31 | 32 | * 📝 Work on [WIP 2022 TODO Guides](https://github.com/todogroup/todogroup.org/issues?q=is%3Aissue+is%3Aopen+label%3Aguide) 33 | * 📘 Work on [WIP 2022 Whitepapers](https://github.com/todogroup/outbound-oss) 34 | 35 | ### *"I have time and want to improve outdated TODO resources" tasks* 36 | 37 | * 📖 [Improve OSPO 101 Courses (training) with more modules](https://github.com/todogroup/ospo101) 38 | * 🧩 [Update old](https://todogroup.org/guides/#ospo-case-studies) or [create new OSPO Case Studies](https://github.com/todogroup/todogroup.org/issues?q=is%3Aissue+is%3Aopen+label%3A%22use+case%22) 39 | 40 | ### *"I have long term experience with TODO repo and GH project" tasks* 41 | * ⚙️ Clean up access to repos 42 | * ✅ Resolve outstanding pull requests from the following repos: `ospo-landscape` `todogroup.org` `ospology` `repo linter` 43 | * ✍️ Fix README files (like this one!) 44 | 45 | ## Schedule and meetings 46 | 47 | Work days occur once a month and scheduled for two hours. 48 | 49 | **WORK DAYS ARE SCHEDULED FOR:** 50 | 51 | | 🌏 Meeting | 💬 Facilitator | 🕙 Day & time | 52 | | --- | --- | --- | 53 | | AMER | Duane | [Second Wednesday of the month at 16:30 PM UTC](https://zoom.us/j/96680666202?pwd=UVNJdVhHS1JiSVRtZFBDTjBVTEFQUT09) | 54 | | EMEA & APAC | Ana| [Second Monday of the monthat 10:00 AM UTC](https://zoom.us/j/91954003389?pwd=Qk4rR3drQ0UwSXdBWDE3eE1za3V5Zz09)| 55 | 56 | 57 | ## Calendar invites 58 | 59 | Calendar invites are sent via TODO Mailing list ([Community](https://docs.google.com/forms/d/e/1FAIpQLSeU0YGM_IJ6gY8E5IIiwXKD_FZi3kAVc4E9_-3dtTDyKMSjdA/viewform) and General Member) and notified at [TODO Slack general channel](https://slack.todogroup.org/). 60 | 61 | Also, we provide an ICS calendar file for both, AMER and EMEA & APAC, to easily import the meeting series in any agenda at todogroup.org/community. 62 | 63 | 64 | ## Process 65 | 66 | 1) Read this README documentation 67 | 2) Choose the section you wish to work on today (guides, ospology, whitepapers, etc) 68 | 3) Go to the dedicated repo and check the open issues available 69 | 70 | Typically people will send event reminders via Slack and email in advance of the event, so you can start thinking of what you'd like to work on. 71 | 72 | On the work day itself, we all gather in the Zoom meeting and touch base, sharing what we plan to work on and asking anyone whether they'd like some help with their chosen tasks. We hang out on the Zoom (creating breakout rooms if needed), typing away on our tasks, asking questions, and generally hanging out productively. 73 | 74 | ## Join us! 75 | 76 | Working Hours are a great way to see and make friends in TODO while also contributing to the community. It's very casual but also productive. Come be a part of the fun! 77 | --------------------------------------------------------------------------------