#fedora-meeting-2: Fedora CommOps (2018-02-19)

Meeting started by jwf at 15:30:09 UTC (full logs).

Meeting summary

  1. Agenda (jwf, 15:30:20)
    1. https://infinote.fedoraproject.org/cgit/infinote/tree/meeting-templates/fedora-commops-meeting-next (jwf, 15:30:27)
    2. (1) Roll call / Q&A (jwf, 15:30:27)
    3. (2) Announcements (jwf, 15:30:27)
    4. (3) Action items from last meeting (jwf, 15:30:27)
    5. (4) Tickets (jwf, 15:30:28)
    6. (5) Open floor (jwf, 15:30:29)

  2. Roll call / Q&A (jwf, 15:30:44)
    1. Name; Timezone; Sub-projects/Interest Areas (jwf, 15:30:49)
    2. ACTION: commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ] (jwf, 15:30:49)
    3. Justin W. Flory; UTC-5; CommOps, Diversity Team (jwf, 15:31:09)
    4. Alberto Rodríguez S.; UTC-5; CommOps, dotNet, Marketing, Infra, Ambassadors, cats (bt0_, 15:31:16)
    5. Dennis W. Otugo; UTC+1; CommOps, Infra (wesleyotugo, 15:32:34)

  3. Announcements (jwf, 15:39:33)
    1. === "EMEA Ambassadors: 2017 Year in Review" – by edgates++ === (jwf, 15:39:38)
    2. https://communityblog.fedoraproject.org/emea-ambassadors-2017-year-review/ (jwf, 15:39:43)
    3. Quick highlights of the EMEA Ambassadors' activity in 2017. Includes goals for improved event report coverage and tracking metrics to measure success. (jwf, 15:39:43)

  4. Action items from last meeting (jwf, 15:41:25)
    1. https://meetbot.fedoraproject.org/fedora-meeting-2/2018-02-12/commops.2018-02-12-15.30.html (jwf, 15:41:32)
    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, 15:41:32)
    3. === [INCOMPLETE] "x3mboy Open new CommOps ticket with expanded idea on improving communication from public to Ambassadors" === (jwf, 15:41:50)
    4. ACTION: x3mboy Open new CommOps ticket with expanded idea on improving communication from public to Ambassadors (jwf, 15:41:50)
    5. === [IN PROGRESS] "jwf Work on first draft of FAD event report, share with team for feedback by 2017-02-16" === (jwf, 15:42:00)
    6. https://pagure.io/fedora-commops/issue/125#comment-494519 (jwf, 15:42:03)
    7. ACTION: jwf Work on first draft of FAD event report, share with team for feedback by 2017-02-23 (jwf, 15:42:07)
    8. === [COMPLETE] "commops Review Fedora Appreciation Week template to collect contributor stories, leave any feedback in the Etherpad" === (jwf, 15:42:12)
    9. https://etherpad.persephone.cloud/p/commops-faw-2018-template (jwf, 15:42:16)
    10. Template is ready; need to add template into tooling for Pagure repo (jwf, 15:42:19)
    11. === [COMPLETE] "bee2502 jonatoni Start discussion with Fedora Infra on requirements to host our own Happiness Packet site (inc. Python / Django, PostgreSQL, etc.)" === (jwf, 15:42:24)
    12. https://pagure.io/fedora-infrastructure/issue/6690 (jwf, 15:42:28)
    13. Idea generally approved; bee2502 and jonatoni to clarify on hardware needs once we get through the applicant phase of GSoC and Outreachy (jwf, 15:42:31)
    14. === [IN PROGRESS] "skamath Finish installing Grimoire on CommOps cloud instance by 2018-02-19, share link to mailing list when finished" === (jwf, 15:42:36)
    15. http://commops.fedorainfracloud.org/app/kibana (jwf, 15:42:40)
    16. ACTION: skamath Document log-in instructions to Grimoire on CommOps cloud instance (jwf, 15:42:44)
    17. === [COMPLETE] "skamath file an issue in mentored-projects repo for including perceval project in Outreachy" === (jwf, 15:43:16)
    18. https://pagure.io/mentored-projects/issue/25 (jwf, 15:43:21)
    19. === [COMPLETE] "skamath Follow-up with a2batic and sumantro on GSoC projects for Outreachy" === (jwf, 15:43:25)
    20. https://screenshots.firefox.com/KcVsMWBWRGi5vS3e/www.outreachy.org (jwf, 15:43:29)
    21. Perceval fedmsg plugin and Android projects are officially added as Summer 2018 Outreachy projects (jwf, 15:43:32)

  5. Tickets (jwf, 15:44:20)
    1. https://pagure.io/fedora-commops/issues?tags=meeting (jwf, 15:44:24)
    2. === Ticket #137: "New CommBlog article: Fedora accepted into GSoC 2018" === (jwf, 15:44:30)
    3. https://pagure.io/fedora-commops/issue/137 (jwf, 15:44:31)
    4. HELP: Great task for beginner. Need to write an announcement that Fedora is participating in Google Summer of Code 2018. Past example is in ticket. (jwf, 15:44:35)
    5. ACTION: wesleyotugo Write first draft of "Fedora accepted into GSoC 2018" on CommBlog; write to mailing list when ready for review (final draft due: 2018-02-26) (jwf, 15:49:15)
    6. === Ticket #110: "Fedora Appreciation Week 2017" === (jwf, 15:49:43)
    7. https://pagure.io/fedora-commops/issue/110 (jwf, 15:49:48)
    8. https://screenshots.firefox.com/Gahbf6ED4lAVP9b8/etherpad.persephone.cloud (jwf, 15:49:59)
    9. https://pagure.io/fedora-commops/contributor-stories (jwf, 15:49:59)
    10. https://etherpad.persephone.cloud/p/commops-faw-2018-template (jwf, 15:49:59)
    11. According to timeline, in February, we create the template for contributors to submit stories and add the template to repo. Template was out for review since last meeting; will move forward to incorporate template into repo (jwf, 15:50:20)
    12. ACTION: jwf Add FAW template in Etherpad as Pagure issue template in contributor-stories repo (jwf, 15:50:27)
    13. Contributor stories CommBlog intro: (1) What they are; (2) Why we're doing this; (3) How to submit one (jwf, 16:00:21)
    14. ACTION: bt0 Write first draft of Contributor Stories article for CommBlog by Monday, Feb. 26 2018 (jwf, 16:00:58)
    15. === Ticket #114: "Use metrics dashboard to visualize fedmsg data" === (jwf, 16:01:18)
    16. https://pagure.io/fedora-commops/issue/114 (jwf, 16:01:19)
    17. https://screenshots.firefox.com/Gahbf6ED4lAVP9b8/etherpad.persephone.cloud (jwf, 16:01:22)
    18. Revisiting timeline goals; how do we want to document this information? (jwf, 16:01:25)
    19. ACTION: skamath Research (possibly implement) Guard to manage granular permissions between accounts in Kibana by Monday, 2018-02-26 (jwf, 16:06:36)
    20. Documentation is blocked by understanding how we will manage accounts; need to look into third-party plugin by Elastic team called Guard to have advanced permissioning for multiple users in Kibana; skamath to research this by next Monday's meeting (jwf, 16:07:26)
    21. === Ticket #133: "Creating summer coding "best practices" docs for mentors" === (jwf, 16:08:01)
    22. https://pagure.io/fedora-commops/issue/133 (jwf, 16:08:06)
    23. bee2502 mentioned some ideas for advice on supporting mentors in our intern programs; what other helpful topics are there to include? Do we want to champion this task at the 2018 Documentation FAD? (jwf, 16:08:13)
    24. IDEA: Have on-boarding guidelines for selected applicants (jwf, 16:10:14)
    25. IDEA: Introduce social communication channels for students (jwf, 16:10:20)
    26. IDEA: Do research + use existing documents from other open source communities (e.g. MetaBrainz has a private communication channel for discussions between mentors) (jwf, 16:10:42)
    27. IDEA: Highlight work of selected applicants on Commblog (jwf, 16:10:56)
    28. http://write.flossmanuals.net/gsoc-mentoring/what-makes-a-good-mentor/ (jwf, 16:13:23)
    29. https://docs.fedoraproject.org/mentored-projects/gsoc/2018/index.html#how-to-work-with-students (jwf, 16:13:33)
    30. skamath linked a helpful guide written by FLOSS Manuals (sponsored by Google) for mentoring and administering Google Summer of Code. Instead of reinventing the wheel, point this as a reference and only document Fedora-specific details in our own mentor docs (jwf, 16:15:27)
    31. ACTION: jwf Bring #133 as a work task to Docs FAD; pre-prep by reaching out on Docs list for feedback (?) (jwf, 16:16:15)

  6. Open floor (jwf, 16:17:40)


Meeting ended at 16:20:08 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. x3mboy Open new CommOps ticket with expanded idea on improving communication from public to Ambassadors
  3. jwf Work on first draft of FAD event report, share with team for feedback by 2017-02-23
  4. skamath Document log-in instructions to Grimoire on CommOps cloud instance
  5. wesleyotugo Write first draft of "Fedora accepted into GSoC 2018" on CommBlog; write to mailing list when ready for review (final draft due: 2018-02-26)
  6. jwf Add FAW template in Etherpad as Pagure issue template in contributor-stories repo
  7. bt0 Write first draft of Contributor Stories article for CommBlog by Monday, Feb. 26 2018
  8. skamath Research (possibly implement) Guard to manage granular permissions between accounts in Kibana by Monday, 2018-02-26
  9. jwf Bring #133 as a work task to Docs FAD; pre-prep by reaching out on Docs list for feedback (?)


Action items, by person

  1. bt0
    1. bt0 Write first draft of Contributor Stories article for CommBlog by Monday, Feb. 26 2018
  2. commops
    1. commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ]
  3. jwf
    1. jwf Work on first draft of FAD event report, share with team for feedback by 2017-02-23
    2. jwf Add FAW template in Etherpad as Pagure issue template in contributor-stories repo
    3. jwf Bring #133 as a work task to Docs FAD; pre-prep by reaching out on Docs list for feedback (?)
  4. skamath
    1. skamath Document log-in instructions to Grimoire on CommOps cloud instance
    2. skamath Research (possibly implement) Guard to manage granular permissions between accounts in Kibana by Monday, 2018-02-26
  5. wesleyotugo
    1. wesleyotugo Write first draft of "Fedora accepted into GSoC 2018" on CommBlog; write to mailing list when ready for review (final draft due: 2018-02-26)
  6. x3mboy
    1. x3mboy Open new CommOps ticket with expanded idea on improving communication from public to Ambassadors


People present (lines said)

  1. jwf (185)
  2. skamath (36)
  3. zodbot (12)
  4. wesleyotugo (11)
  5. bt0_ (9)
  6. bt0 (8)
  7. bt0__ (2)
  8. commops (0)
  9. x3mboy (0)


Generated by MeetBot 0.1.4.