============================================ #fedora-commops: Fedora CommOps (2018-04-30) ============================================ Meeting started by jwf at 14:30:32 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-commops/2018-04-30/commops.2018-04-30-14.30.log.html . Meeting summary --------------- * Agenda (jwf, 14:30:37) * LINK: https://infinote.fedoraproject.org/cgit/infinote/tree/meeting-templates/fedora-commops-meeting-next (jwf, 14:30:44) * (1) Roll call / Q&A (jwf, 14:30:44) * (2) Announcements (jwf, 14:30:44) * (3) Action items from last meeting (jwf, 14:30:45) * (4) Tickets (jwf, 14:30:48) * (5) Open floor (jwf, 14:30:50) * Roll call / Q&A (jwf, 14:30:55) * Name; Timezone; Sub-projects/Interest Areas (jwf, 14:30:57) * ACTION: commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ] (jwf, 14:30:57) * Justin W. Flory; UTC-5; CommOps, Diversity & Inclusion Team, Ambassadors, Mindshare (jwf, 14:31:23) * Alberto Rodriguez Sanchez;UTC-5; CommOps, Marketing, dotNet sig, Ambassadors and more (bt0, 14:33:35) * Announcements (jwf, 14:39:12) * === "Commitment to community: Fedora CommOps FAD 2018" === (jwf, 14:39:26) * LINK: https://communityblog.fedoraproject.org/fedora-commops-fad-2018/ (jwf, 14:39:26) * The 2018 CommOps FAD event report is now published. Understand your Fedora sub-project with charts / graphs and see how to thank other contributors for Fedora Appreciation Week. (jwf, 14:39:27) * === "How to use Fedora Wiki as your wiki whiteboard" === (jwf, 14:39:39) * LINK: https://communityblog.fedoraproject.org/how-to-fedora-wiki-whiteboard/ (jwf, 14:39:40) * Get a quick overview of using the Fedora Wiki and its syntax from wesleyotugo. (jwf, 14:39:40) * === "Top Badgers of 2017: Carl George" === (jwf, 14:39:46) * LINK: https://communityblog.fedoraproject.org/top-badgers-2017-carl-george/ (jwf, 14:39:47) * Check out the last post in 'Top Badgers of 2017' series by lroca. roca++ for creating and driving this interview series! (jwf, 14:39:47) * === Fedora 28 releases tomorrow! === (jwf, 14:40:40) * LINK: https://communityblog.fedoraproject.org/fedora-28-release-dates-schedule/ (jwf, 14:40:55) * Fedora 28 comes out tomorrow! Get ready to try out the latest and greatest that the Fedora community has put together over the last six months. (jwf, 14:41:16) * Action items from last meeting (jwf, 14:42:05) * LINK: https://meetbot.fedoraproject.org/fedora-commops/2018-04-23/commops.2018-04-23-14.26.html (jwf, 14:42:11) * 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. (jwf, 14:42:11) * === [COMPLETE] "@x3mboy File a new ticket in Mindshare Pagure to propose student pack idea and start discussion in Mindshare Committee" === (jwf, 14:42:30) * LINK: https://pagure.io/mindshare/issue/16 (jwf, 14:42:31) * x3mboy started this discussion in the Mindshare Committee Pagure. Subscribe to the issue there to keep up with the student pack planning. (jwf, 14:42:31) * === [COMPLETE] "x3mboy Submit new PR with README for contributor-stories repository" === (jwf, 14:42:43) * LINK: https://pagure.io/fedora-commops/contributor-stories/blob/master/f/README.md (jwf, 14:42:43) * Basic description of Contributor Stories now live on the README. (jwf, 14:42:44) * === [COMPLETE] "x3mboy File a ticket in CommOps Pagure about a new podcast interview / episode on the CommOps team" === (jwf, 14:42:53) * LINK: https://pagure.io/fedora-commops/issue/155 (jwf, 14:42:53) * Figuring out the plan for the podcast; will discuss later in meeting. (jwf, 14:42:53) * === [COMPLETE] "bee2502 dhanesh95 jonatoni wesleyotugo x3mboy Review the CommOps FAD event report draft this week, leave feedback in CommOps ticket #125" === (jwf, 14:43:01) * LINK: https://communityblog.fedoraproject.org/fedora-commops-fad-2018/ (jwf, 14:43:01) * FAD report is now published. (jwf, 14:43:02) * Tickets (jwf, 14:43:35) * LINK: https://pagure.io/fedora-commops/issues?status=Open&tags=next+meeting (jwf, 14:43:39) * === Ticket #110: "Fedora Appreciation Week 2017" === (jwf, 14:43:55) * LINK: https://pagure.io/fedora-commops/issue/110 (jwf, 14:43:55) * LINK: https://screenshots.firefox.com/NDyEhhKzQJ4WpXr4/etherpad.persephone.cloud (jwf, 14:43:55) * LINK: https://communityblog.fedoraproject.org/?p=5376&preview=1&_ppp=dbe0f8ee96 (jwf, 14:44:06) * Contributor Stories introduction publishes tomorrow morning. (jwf, 14:44:06) * HELP: We can support the publishing of the post with social media and posting to the announce- list. (jwf, 14:44:06) * AGREED: Article publishes tomorrow and we will do some outreach to build awareness. jwf covers Twitter/FB/G+, jonatoni covers Instagram, bt0 covers the announce@ mailing list (jwf, 14:47:27) * ACTION: jwf After May 1, promote "Introducing contributor stories" CommBlog article on Twitter and round up others to help with FB / G+ (jwf, 14:47:57) * ACTION: jonatoni After May 1, promote "Introducing contributor stories" CommBlog article on Instagram (jwf, 14:48:07) * ACTION: bt0 After May 1, promote "Introducing contributor stories" CommBlog article by writing an email draft for announce@lists.fp.o (jwf, 14:49:01) * === Ticket #117: "How to create on-boarding guidelines for your team" === (jwf, 14:51:12) * LINK: https://pagure.io/fedora-commops/issue/117 (jwf, 14:51:12) * Purpose is to write guidelines on creating effective onboarding guidelines for Fedora sub-projects. We won't write guidelines for someone, but we will try to give them a resource to do it well. (jwf, 14:51:17) * IDEA: Read through existing onboarding / joining guidelines for different Fedora sub-projects / teams and identify similarities (jwf, 14:53:58) * AGREED: The end result of this task is a huge, so we need to break it down into smaller, more manageable pieces (jwf, 15:09:52) * dhanesh95 notes idea of including specific advice for different *types* of teams, e.g. development and outreach (jwf, 15:10:14) * IDEA: Keep it all to one document, but include a special section or subheading with specific advice for development / programming teams and SIGs, and then another for outreach-related teams, etc. (jwf, 15:10:44) * AGREED: Next step is to split up the work into smaller pieces, and make #117 into a master / tracking ticket (jwf, 15:12:32) * ACTION: jwf Split up onboarding guidelines ticket (#117) into smaller sub-tickets for different steps of work to produce the final deliverable (jwf, 15:12:58) * === Ticket #155: "Fedora Podcast Episode" === (jwf, 15:14:03) * LINK: https://pagure.io/fedora-commops/issue/155 (jwf, 15:14:03) * x3mboy expressed interest in a Fedora podcast interview with CommOps team. Need to come up with a loose script and topics to cover during the interview. (jwf, 15:14:03) * HELP: Need help writing an outline of topics for the CommOps podcast interview session with x3mboy (jwf, 15:14:03) * IDEA: Did You Know fact for podcast: CommOps team members are split across five continents! (jwf, 15:18:25) * LINK: https://communityblog.fedoraproject.org/fedora-commops-fad-2018/ (jwf, 15:19:59) * LINK: https://public.etherpad-mozilla.org/p/FedoraDiversityPocast (jwf, 15:21:16) * ACTION: bt0 Create an outline / rough script of questions and topics to cover in a Fedora podcast interview with x3mboy; request feedback before Monday, May 14, 2018 meeting (jwf, 15:25:30) * AGREED: Will determine a recording day and time after the outline / script is approved (jwf, 15:25:49) * Open floor (jwf, 15:26:47) * bt0 will chair the next two meetings on Monday, May 7 and Monday, May 14, in lieu of jwf's absence (jwf, 15:29:18) Meeting ended at 15:32:22 UTC. Action Items ------------ * commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ] * jwf After May 1, promote "Introducing contributor stories" CommBlog article on Twitter and round up others to help with FB / G+ * jonatoni After May 1, promote "Introducing contributor stories" CommBlog article on Instagram * bt0 After May 1, promote "Introducing contributor stories" CommBlog article by writing an email draft for announce@lists.fp.o * jwf Split up onboarding guidelines ticket (#117) into smaller sub-tickets for different steps of work to produce the final deliverable * bt0 Create an outline / rough script of questions and topics to cover in a Fedora podcast interview with x3mboy; request feedback before Monday, May 14, 2018 meeting Action Items, by person ----------------------- * bt0 * bt0 After May 1, promote "Introducing contributor stories" CommBlog article by writing an email draft for announce@lists.fp.o * bt0 Create an outline / rough script of questions and topics to cover in a Fedora podcast interview with x3mboy; request feedback before Monday, May 14, 2018 meeting * commops * commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ] * jonatoni * jonatoni After May 1, promote "Introducing contributor stories" CommBlog article on Instagram * jwf * jwf After May 1, promote "Introducing contributor stories" CommBlog article on Twitter and round up others to help with FB / G+ * jwf Split up onboarding guidelines ticket (#117) into smaller sub-tickets for different steps of work to produce the final deliverable * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * jwf (226) * dhanesh95 (33) * bt0 (19) * zodbot (10) * jonatoni (9) * fcommops-tg (7) * commopsbot (6) * algogator (0) * commops (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot