#fedora-commops: Fedora CommOps (2018-04-30)

Meeting started by jwf at 14:30:32 UTC (full logs).

Meeting summary

  1. Agenda (jwf, 14:30:37)
    1. https://infinote.fedoraproject.org/cgit/infinote/tree/meeting-templates/fedora-commops-meeting-next (jwf, 14:30:44)
    2. (1) Roll call / Q&A (jwf, 14:30:44)
    3. (2) Announcements (jwf, 14:30:44)
    4. (3) Action items from last meeting (jwf, 14:30:45)
    5. (4) Tickets (jwf, 14:30:48)
    6. (5) Open floor (jwf, 14:30:50)

  2. Roll call / Q&A (jwf, 14:30:55)
    1. Name; Timezone; Sub-projects/Interest Areas (jwf, 14:30:57)
    2. ACTION: commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ] (jwf, 14:30:57)
    3. Justin W. Flory; UTC-5; CommOps, Diversity & Inclusion Team, Ambassadors, Mindshare (jwf, 14:31:23)
    4. Alberto Rodriguez Sanchez;UTC-5; CommOps, Marketing, dotNet sig, Ambassadors and more (bt0, 14:33:35)

  3. Announcements (jwf, 14:39:12)
    1. === "Commitment to community: Fedora CommOps FAD 2018" === (jwf, 14:39:26)
    2. https://communityblog.fedoraproject.org/fedora-commops-fad-2018/ (jwf, 14:39:26)
    3. 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)
    4. === "How to use Fedora Wiki as your wiki whiteboard" === (jwf, 14:39:39)
    5. https://communityblog.fedoraproject.org/how-to-fedora-wiki-whiteboard/ (jwf, 14:39:40)
    6. Get a quick overview of using the Fedora Wiki and its syntax from wesleyotugo. (jwf, 14:39:40)
    7. === "Top Badgers of 2017: Carl George" === (jwf, 14:39:46)
    8. https://communityblog.fedoraproject.org/top-badgers-2017-carl-george/ (jwf, 14:39:47)
    9. 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)
    10. === Fedora 28 releases tomorrow! === (jwf, 14:40:40)
    11. https://communityblog.fedoraproject.org/fedora-28-release-dates-schedule/ (jwf, 14:40:55)
    12. 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)

  4. Action items from last meeting (jwf, 14:42:05)
    1. https://meetbot.fedoraproject.org/fedora-commops/2018-04-23/commops.2018-04-23-14.26.html (jwf, 14:42:11)
    2. 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)
    3. === [COMPLETE] "@x3mboy File a new ticket in Mindshare Pagure to propose student pack idea and start discussion in Mindshare Committee" === (jwf, 14:42:30)
    4. https://pagure.io/mindshare/issue/16 (jwf, 14:42:31)
    5. 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)
    6. === [COMPLETE] "x3mboy Submit new PR with README for contributor-stories repository" === (jwf, 14:42:43)
    7. https://pagure.io/fedora-commops/contributor-stories/blob/master/f/README.md (jwf, 14:42:43)
    8. Basic description of Contributor Stories now live on the README. (jwf, 14:42:44)
    9. === [COMPLETE] "x3mboy File a ticket in CommOps Pagure about a new podcast interview / episode on the CommOps team" === (jwf, 14:42:53)
    10. https://pagure.io/fedora-commops/issue/155 (jwf, 14:42:53)
    11. Figuring out the plan for the podcast; will discuss later in meeting. (jwf, 14:42:53)
    12. === [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)
    13. https://communityblog.fedoraproject.org/fedora-commops-fad-2018/ (jwf, 14:43:01)
    14. FAD report is now published. (jwf, 14:43:02)

  5. Tickets (jwf, 14:43:35)
    1. https://pagure.io/fedora-commops/issues?status=Open&tags=next+meeting (jwf, 14:43:39)
    2. === Ticket #110: "Fedora Appreciation Week 2017" === (jwf, 14:43:55)
    3. https://pagure.io/fedora-commops/issue/110 (jwf, 14:43:55)
    4. https://screenshots.firefox.com/NDyEhhKzQJ4WpXr4/etherpad.persephone.cloud (jwf, 14:43:55)
    5. https://communityblog.fedoraproject.org/?p=5376&preview=1&_ppp=dbe0f8ee96 (jwf, 14:44:06)
    6. Contributor Stories introduction publishes tomorrow morning. (jwf, 14:44:06)
    7. HELP: We can support the publishing of the post with social media and posting to the announce- list. (jwf, 14:44:06)
    8. 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)
    9. 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)
    10. ACTION: jonatoni After May 1, promote "Introducing contributor stories" CommBlog article on Instagram (jwf, 14:48:07)
    11. 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)
    12. === Ticket #117: "How to create on-boarding guidelines for your team" === (jwf, 14:51:12)
    13. https://pagure.io/fedora-commops/issue/117 (jwf, 14:51:12)
    14. 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)
    15. IDEA: Read through existing onboarding / joining guidelines for different Fedora sub-projects / teams and identify similarities (jwf, 14:53:58)
    16. 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)
    17. dhanesh95 notes idea of including specific advice for different *types* of teams, e.g. development and outreach (jwf, 15:10:14)
    18. 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)
    19. AGREED: Next step is to split up the work into smaller pieces, and make #117 into a master / tracking ticket (jwf, 15:12:32)
    20. 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)
    21. === Ticket #155: "Fedora Podcast Episode" === (jwf, 15:14:03)
    22. https://pagure.io/fedora-commops/issue/155 (jwf, 15:14:03)
    23. 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)
    24. HELP: Need help writing an outline of topics for the CommOps podcast interview session with x3mboy (jwf, 15:14:03)
    25. IDEA: Did You Know fact for podcast: CommOps team members are split across five continents! (jwf, 15:18:25)
    26. https://communityblog.fedoraproject.org/fedora-commops-fad-2018/ (jwf, 15:19:59)
    27. https://public.etherpad-mozilla.org/p/FedoraDiversityPocast (jwf, 15:21:16)
    28. 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)
    29. AGREED: Will determine a recording day and time after the outline / script is approved (jwf, 15:25:49)

  6. Open floor (jwf, 15:26:47)
    1. 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 (full logs).

Action items

  1. commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ]
  2. jwf After May 1, promote "Introducing contributor stories" CommBlog article on Twitter and round up others to help with FB / G+
  3. jonatoni After May 1, promote "Introducing contributor stories" CommBlog article on Instagram
  4. bt0 After May 1, promote "Introducing contributor stories" CommBlog article by writing an email draft for announce@lists.fp.o
  5. jwf Split up onboarding guidelines ticket (#117) into smaller sub-tickets for different steps of work to produce the final deliverable
  6. 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

  1. bt0
    1. bt0 After May 1, promote "Introducing contributor stories" CommBlog article by writing an email draft for announce@lists.fp.o
    2. 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
  2. commops
    1. commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ]
  3. jonatoni
    1. jonatoni After May 1, promote "Introducing contributor stories" CommBlog article on Instagram
  4. jwf
    1. jwf After May 1, promote "Introducing contributor stories" CommBlog article on Twitter and round up others to help with FB / G+
    2. jwf Split up onboarding guidelines ticket (#117) into smaller sub-tickets for different steps of work to produce the final deliverable


People present (lines said)

  1. jwf (226)
  2. dhanesh95 (33)
  3. bt0 (19)
  4. zodbot (10)
  5. jonatoni (9)
  6. fcommops-tg (7)
  7. commopsbot (6)
  8. algogator (0)
  9. commops (0)


Generated by MeetBot 0.1.4.