===================================== # #meeting:fedoraproject.org: commops ===================================== Meeting started by @jflory7:fedora.im at 2024-09-17 14:01:13 Meeting summary --------------- * TOPIC: Agenda (@jflory7:fedora.im, 14:01:21) * INFO: (1) Intros, welcomes, hellos (@jflory7:fedora.im, 14:01:34) * INFO: (2) Team announcements & news (@jflory7:fedora.im, 14:01:38) * INFO: (3) Initiative Co-Lead updates to the team (@jflory7:fedora.im, 14:01:41) * INFO: (4) Follow-ups from last meeting (@jflory7:fedora.im, 14:01:43) * INFO: (5) Ticket-driven discussion (@jflory7:fedora.im, 14:01:47) * INFO: (6) Open floor (@jflory7:fedora.im, 14:01:50) * TOPIC: Intros, welcomes, hellos (@jflory7:fedora.im, 14:01:55) * INFO: Present: @jflory7 @gwmngilfen @shaunm @neil (@jflory7:fedora.im, 14:06:48) * INFO: +Present: @nancywrites (@jflory7:fedora.im, 14:07:56) * TOPIC: Team announcements & news (@jflory7:fedora.im, 14:08:08) * INFO: === "Announcing Fedora Linux 41 Beta" === (@jflory7:fedora.im, 14:08:59) * LINK: https://fedoramagazine.org/announcing-fedora-linux-41-beta/ (@jflory7:fedora.im, 14:09:03) * INFO: === "Communishift namespace creation - commops-analytics" === (@jflory7:fedora.im, 14:09:21) * LINK: https://pagure.io/fedora-infrastructure/issue/12101 (@jflory7:fedora.im, 14:09:26) * INFO: Fedora Infra has created a new Communishift environment for some of the sandbox projects we want to work on with analytics work. For now, @jflory7 and @rwright have administrator access and can share access via membership in a new FAS group. (@jflory7:fedora.im, 14:10:02) * LINK: https://accounts.fedoraproject.org/group/communishift-commops-analytics/ (@jflory7:fedora.im, 14:10:40) * INFO: === "Fedora Mentored Projects – Council Hackfest" === (@jflory7:fedora.im, 14:14:12) * LINK: https://communityblog.fedoraproject.org/fedora-mentored-projects-council-hackfest/ (@jflory7:fedora.im, 14:14:16) * INFO: This overview post goes over the Mentored Projects Initiative, progress made to date, and what the closing steps are for the initiative this year. (@jflory7:fedora.im, 14:14:40) * TOPIC: Initiative Co-Lead updates to the team (@jflory7:fedora.im, 14:16:16) * INFO: @rwright and @jflory7 are beginning to discuss the path forward for concluding the Initiative and mapping out team goals that go beyond the Initiative, ultimately transitioning this from an Initiative-driven effort to a full community team. More to come on this soon. (@jflory7:fedora.im, 14:17:02) * TOPIC: Ticket-driven discussion (@jflory7:fedora.im, 14:17:12) * LINK: https://gitlab.com/fedora/commops/home/-/issues/?sort=created_date&state=opened&label_name%5B%5D=meeting%20topic%20request&first_page_size=100 (@jflory7:fedora.im, 14:18:46) * TOPIC: Pending ticket: Support request for Pantheon SIG onboarding and launching new teams in Fedora (@jflory7:fedora.im, 14:23:39) * INFO: Open brainstorm by the team on what makes for a good or bad onboarding experience into a new team in Fedora (or for that matter, any other open source community you have participated in). (@jflory7:fedora.im, 14:26:32) * IDEA: Clear expectations. Knowing what is expected by myself and those around me. Docs? Meetings? Issue trackers? This is key to feeling like I am being useful. (@jflory7:fedora.im, 14:27:13) * IDEA: Clarity. Knowing where to get help when I get stuck. Who do I talk to? Where do I get guidance? Does this happen elsewhere or only for us? (@jflory7:fedora.im, 14:28:42) * IDEA: Going start to finish. Contributing to something from the beginning to the end, so you see the payoff for the effort. This builds confidence and makes me feel like I am being helpful. (@jflory7:fedora.im, 14:29:08) * INFO: +Present: @thisisyaash (@jflory7:fedora.im, 14:31:04) * IDEA: Timeline. Knowing when something needs to be started and when something needs to be finished. We all have different things going on in our lives and we all contribute to Fedora in different capacities. Knowing the timeline for a task or project helps me make the responsible decision about my time commitments and making sure I can meet deadlines. (@jflory7:fedora.im, 14:32:28) * IDEA: Good First Issues. Clear, easily-triaged tasks for newcomers to take on. For newcomers, this is something that is bite-sized, clearly-defined, and there are resources for getting help. For maintainers, this is keeping an eye on tasks in the issue tracker, triaging beginner-friendly tasks accordingly, and prioritizing the creation of beginner-friendly tasks when there are none or few available. (@jflory7:fedora.im, 14:35:06) * IDEA: Maintainers: Know your audience and their motivations. Why would they want to join your SIG? Make sure they can achieve those things. (@jflory7:fedora.im, 14:37:04) * IDEA: Clear entrypoints. It is confusing today about the various git forges where we work. Pagure? GitLab? It is hard to know where to start or whom to ask for help. (@jflory7:fedora.im, 14:40:44) * IDEA: Maintainers: Do you need to start a SIG to do something meaningful? Or are there other channels to lean into before trying to start something new? Explore around more before starting something new. (@jflory7:fedora.im, 14:45:27) * IDEA: Is there a SIG already that fits this need? (@jflory7:fedora.im, 14:45:59) * ACTION: @jflory7 Open a new CommOps issue for SIG onboarding support and documentation, use meeting brainstorm as a starting point (@jflory7:fedora.im, 14:50:06) * TOPIC: Open floor (@jflory7:fedora.im, 14:50:53) * INFO: https://support.mozilla.org/en-US/contribute is decent (@gwmngilfen:ansible.im, 14:52:57) * LINK: https://gitlab.com/fedora/commops/home/-/merge_requests (@jflory7:fedora.im, 14:53:18) * LINK: https://gitlab.com/fedora/commops/home/-/merge_requests/21 (@jflory7:fedora.im, 14:54:32) * LINK: https://gitlab.com/fedora/commops/home/-/merge_requests/20 (@jflory7:fedora.im, 14:54:37) * INFO: Neil will take #20 and #21 (@nhanlon:beeper.com, 14:56:56) * ACTION: @neil Review CommOps MRs !20 (@moralcode) and !21 (@thisisyaash) (@jflory7:fedora.im, 14:58:47) * ACTION: @jflory7 Close our CommOps MR review on !17 and !18 (@jflory7:fedora.im, 14:59:01) Meeting ended at 2024-09-17 15:00:10 Action items ------------ * @jflory7 Open a new CommOps issue for SIG onboarding support and documentation, use meeting brainstorm as a starting point * @neil Review CommOps MRs !20 (@moralcode) and !21 (@thisisyaash) * @jflory7 Close our CommOps MR review on !17 and !18 People Present (lines said) --------------------------- * @jflory7:fedora.im (164) * @gwmngilfen:ansible.im (38) * @thisisyaash:fedora.im (20) * @nhanlon:beeper.com (13) * @zodbot:fedora.im (7) * @meetbot:fedora.im (3) * @nancywrites:matrix.org (2) * @shaunm:matrix.org (2)