============================================ #fedora-commops: Fedora CommOps (2018-06-18) ============================================ Meeting started by bt0 at 14:44:51 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-commops/2018-06-18/commops.2018-06-18-14.44.log.html . Meeting summary --------------- * Agenda (bt0, 14:45:29) * LINK: https://infinote.fedoraproject.org/cgit/infinote/tree/meeting-templates/fedora-commops-meeting-next (bt0, 14:45:43) * (1) Roll call / Q&A (bt0, 14:45:43) * (2) Announcements (bt0, 14:45:43) * (3) Action items from last meeting (bt0, 14:45:44) * (4) Tickets (bt0, 14:45:46) * (5) Open floor (bt0, 14:45:48) * Roll call / Q&A (bt0, 14:46:02) * Name; Timezone; Sub-projects/Interest Areas (bt0, 14:46:31) * ACTION: commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ] (bt0, 14:46:47) * Alberto Rodriguez S; UTC-5;CommOps (Metrics, Community engagement), DotNet (Testing), Infrastructure(Apprentice), Marketing (Member), Ambassadors (Member), Cats (lover) (bt0, 14:47:45) * Ankur Sinha, UTC +1: Packaging, classrooms, join (FranciscoD, 14:55:36) * Announcements (bt0, 14:57:39) * === "Fedora Classroom Session: Fedora QA 101/102" === (bt0, 14:58:32) * LINK: https://fedoramagazine.org/classroom-session-qa-2018-06-19/ (bt0, 14:58:42) * === "Happiness Packets and Fedora GSoC 2018" === (bt0, 14:59:52) * LINK: https://communityblog.fedoraproject.org/happiness-packets-fedora-gsoc-2018 (bt0, 15:00:04) * Action items from last meeting (bt0, 15:04:45) * LINK: https://meetbot.fedoraproject.org/teams/commops/commops.2018-06-11-14.41.html (bt0, 15:05:00) * How This Works: We look at past #action items from the last meeting for quick follow-up. If a task is completed, we move on to the next one. If it isn't, we get an update and re-action if needed. If no status, we'll try to get a quick update and move forward. (bt0, 15:05:14) * === [In Progress] "bt0 Split up onboarding guidelines ticket (#117) into smaller sub-tickets for different steps of work to produce the final deliverable" === (bt0, 15:05:40) * ACTION: "bt0 Split up onboarding guidelines ticket (#117) into smaller sub-tickets for different steps of work to produce the final deliverable" (bt0, 15:06:02) * === [COMPLETED] A session proposal was submitted for the FLOCK === (bt0, 15:11:38) * LINK: https://pagure.io/fedora-commops/issue/160#comment-517032 (bt0, 15:11:44) * Tickets (bt0, 15:13:47) * LINK: https://pagure.io/fedora-commops/issues?status=Open&tags=next+meeting (bt0, 15:13:57) * Ticket #110: "Fedora Appreciation Week 2017" (bt0, 15:14:48) * LINK: https://pagure.io/fedora-commops/issue/110 (bt0, 15:14:59) * LINK: https://screenshots.firefox.com/ZTV0ZlHbq16vevZt/etherpad.persephone.cloud (bt0, 15:15:12) * LINK: https://communityblog.fedoraproject.org/?p=5376&preview=1&_ppp=dbe0f8ee96 (bt0, 15:15:30) * IDEA: invite the podcast audience to write their own CS (bt0, 15:26:07) * Ticket #155: "Fedora Podcast Episode" (bt0, 15:31:08) * LINK: https://pagure.io/fedora-commops/issue/155 (bt0, 15:31:16) * ACTION: bt0 will add one or two lines to the script about invite the podcast audience to write their own CS (bt0, 15:33:01) * Ticket #160: "Plan a CommOps session for Flock 2018" (bt0, 15:42:56) * LINK: https://pagure.io/fedora-commops/issue/160 (bt0, 15:43:14) * LINK: https://pagure.io/fedora-commops/issue/160#comment-517032 (bt0, 15:43:42) * LINK: https://pagure.io/flock/issue/51 (bt0, 15:45:58) * Open floor (bt0, 15:52:26) * LINK: https://pagure.io/fedora-commops/issue/161 (bt0, 15:54:33) * Selecting new CommOps Mindshare representative for F29-F30 (bt0, 15:54:55) Meeting ended at 16:00:27 UTC. Action Items ------------ * commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ] * "bt0 Split up onboarding guidelines ticket (#117) into smaller sub-tickets for different steps of work to produce the final deliverable" * bt0 will add one or two lines to the script about invite the podcast audience to write their own CS Action Items, by person ----------------------- * bt0 * "bt0 Split up onboarding guidelines ticket (#117) into smaller sub-tickets for different steps of work to produce the final deliverable" * bt0 will add one or two lines to the script about invite the podcast audience to write their own CS * commops * commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ] * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * bt0 (93) * fcommops-tg (19) * zodbot (12) * FranciscoD (2) * wesleyotugo (1) * bee2502 (0) * commops (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot