#fedora-meeting: Fedora CommOps (2016-09-06)

Meeting started by jflory7 at 16:25:00 UTC (full logs).

Meeting summary

  1. Agenda (jflory7, 16:25:19)
    1. https://fedoraproject.org/wiki/Meeting:CommOps_2016-09-06 (jflory7, 16:25:25)
    2. (1) Roll Call / Q&A (jflory7, 16:25:30)
    3. (2) Announcements (jflory7, 16:25:34)
    4. (3) Action items from last meeting (jflory7, 16:25:39)
    5. (4) Tickets (jflory7, 16:25:44)
    6. (5) Wiki Gardening (jflory7, 16:25:49)
    7. (6) Community Blog (jflory7, 16:25:53)
    8. (7) Release Schedule (jflory7, 16:25:58)
    9. (8) Open Floor (jflory7, 16:26:04)

  2. Roll Call / Q&A (jflory7, 16:26:15)
    1. Name; Timezone; Sub-projects/Interest Areas (jflory7, 16:26:15)
    2. ACTION: commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ] (jflory7, 16:26:22)
    3. Justin W. Flory; UTC-4; CommOps, Marketing / Magazine, Ambassadors, Diversity Team, Join SIG, sysadmin-badges, and more (jflory7, 16:26:48)
    4. Dhanesh B. Sabane; UTC+5:30; CommOps, RPM Packaging, ML, Linux Kernel, Python (dhanesh95, 16:27:36)
    5. Sachin S. Kamath; UTC +5.30 ; GSoC, Metrics, CommOps (skamath, 16:28:22)

  3. Announcements (jflory7, 16:34:54)
    1. === [Reminder] CommOps has moved to Pagure === (jflory7, 16:35:00)
    2. https://pagure.io/fedora-commops (jflory7, 16:35:05)
    3. All of our tickets and data from Trac was migrated to Pagure last week. We will no longer use Trac for task management / tickets. Please sign into Pagure with your FAS account and check out the repository if you have not done so yet! (jflory7, 16:35:11)
    4. === "Announcing the release of Fedora 25 Alpha!" === (jflory7, 16:35:31)
    5. https://lists.fedoraproject.org/archives/list/announce@lists.fedoraproject.org/thread/OV3APVA63F4EM5FDLBN5DK5OKEZJWROJ/ (jflory7, 16:35:36)
    6. The Fedora Project is pleased to announce the availability of the Fedora 25 Alpha, an important milestone on the road to our Fedora 25 release in November. (jflory7, 16:35:43)
    7. === "Welcoming our new Fedora Community Action and Impact Coordinator" === (jflory7, 16:35:48)
    8. https://fedoramagazine.org/welcoming-new-fedora-community-coordinator/ (jflory7, 16:35:53)
    9. "Good news, everybody! I’m pleased to announce that we have completed our search for a new Fedora Community Action and Impact Coordinator, and he’ll be joining the Open Source and Standards (OSAS) team to work with Fedora as of 3 October. Please give a warm welcome to Brian Exelbierd (bexelbie)!" (jflory7, 16:36:00)
    10. === "Keeping Fedora beautiful: contribute your wallpaper!" === (jflory7, 16:36:11)
    11. https://fedoramagazine.org/keeping-fedora-beautiful-contribute-wallpaper/ (jflory7, 16:36:16)
    12. The Fedora 25 supplementary wallpaper dropbox is now open. Submit up to two wallpapers to be voted on by the Fedora community for inclusion in F25 supplementary wallpapers! A great way to participate in the Fedora release process. (jflory7, 16:36:22)

  4. Action items from last meeting (jflory7, 16:37:34)
    1. https://meetbot.fedoraproject.org/fedora-meeting/2016-08-30/commops.2016-08-30-15.58.html (jflory7, 16:37:39)
    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 it if needed. If no status, we'll try to get a quick update and move forward. (jflory7, 16:37:45)
    3. === [IN PROGRESS] jflory7 bee2502 Take workshop feedback and parse it into more accessible data (e.g. tickets / commits / CommBlog posts / metrics / etc.) === (jflory7, 16:37:52)
    4. ACTION: jflory7 bee2502 Take workshop feedback and parse it into more accessible data (e.g. tickets / commits / CommBlog posts / metrics / etc.) (jflory7, 16:38:00)
    5. === [COMPLETE] jflory7 Review emails for pending posts on the CommBlog === (jflory7, 16:38:07)
    6. ACTION: jflory7 Review emails for pending posts on the CommBlog (jflory7, 16:38:14)
    7. === [INCOMPLETE] jflory7 Update Community Blog writing guide for writing a new article based on what's actually happening in 2016 now === (jflory7, 16:38:33)
    8. ACTION: jflory7 Update Community Blog writing guide for writing a new article based on what's actually happening in 2016 now (jflory7, 16:38:40)
    9. === [INCOMPLETE] jflory7 Sort through ideas on reviewing old contributor discussion, form proposals in the ticket, share at next meeting === (jflory7, 16:38:48)
    10. ACTION: jflory7 Sort through ideas on reviewing old contributor discussion, form proposals in the ticket, share at next meeting (jflory7, 16:38:56)
    11. === [INCOMPELTE] skamath File a ticket in Fedora Infra Trac for proposing an official migration from fedora-infra GitHub organization into Pagure === (jflory7, 16:39:06)
    12. ACTION: skamath File a ticket in Fedora Infra Trac for proposing an official migration from fedora-infra GitHub organization into Pagure (jflory7, 16:39:13)
    13. ACTION: jflory7 bee2502 Arrange for some personal hacking to close out Flock items (jflory7, 16:42:37)
    14. === [COMPLETE] skamath Reach out to decause about the idea of migrating his tools in the CommOps toolbox to Pagure and granting access to the CommOps group === (jflory7, 16:42:44)
    15. https://pagure.io/fedora-commops/issue/82 (jflory7, 16:42:45)
    16. === [COMPLETE] jflory7 Follow up on Pagure importer tool for use with decause's CommOps toolbox repositories === (jflory7, 16:42:55)
    17. https://pagure.io/fedora-commops/issue/82 (jflory7, 16:42:56)
    18. === [COMPLETE] jflory7 Remove Ticket #81 from meeting agenda === (jflory7, 16:43:01)
    19. === dhanesh95 Start IRC / mailing list discussion on wiki gardening for Python SIG === (jflory7, 16:43:08)
    20. ACTION: dhanesh95 Start mailing list discussion on wiki page changes for Python SIG (jflory7, 16:45:08)
    21. === [COMPLETE] jflory7 Do some srs ticket triaging / updating this week === (jflory7, 16:45:14)
    22. The CommOps Pagure is completely triaged and migrated to work well in Pagure versus Trac (jflory7, 16:45:22)
    23. === [COMPLETE] amitsin6h Double-check subscription to the mailing list and make sure you are receiving mail from the list === (jflory7, 16:45:33)
    24. === [COMPLETE] jflory7 Come up with a more fitting introductory item to place into the meeting === (jflory7, 16:45:45)
    25. === [COMPLETE] jflory7 Revisit Join page and edit / alter section about wiki page === (jflory7, 16:46:30)
    26. https://fedoraproject.org/wiki/CommOps/Join (jflory7, 16:46:36)
    27. === [COMPLETE] skamath Garden the CommOps wiki page to remove mention of Trac and replace with Pagure (and update hyperlinks) === (jflory7, 16:46:57)
    28. https://fedoraproject.org/wiki/CommOps (jflory7, 16:47:03)
    29. https://fedoraproject.org/wiki/CommOps/Join (jflory7, 16:47:06)
    30. === [COMPLETE] downey Migrate the member table from https://fedoraproject.org/wiki/CommOps#Interest_Areas to https://fedoraproject.org/wiki/CommOps/Members === (jflory7, 16:47:10)
    31. https://fedoraproject.org/wiki/CommOps/Members (jflory7, 16:47:15)

  5. Tickets (jflory7, 16:47:55)
    1. https://pagure.io/fedora-commops/issues?tags=meeting (jflory7, 16:48:04)
    2. === Ticket #19 === (jflory7, 16:48:17)
    3. "Improve automation of Elections communication" (jflory7, 16:48:24)
    4. https://pagure.io/fedora-commops/issue/19 (jflory7, 16:48:31)
    5. https://etherpad.gnome.org/p/flock-2016-commops-workshop (jflory7, 16:50:39)
    6. IDEA: New ways to encourage questions: Utilizing social media as a way for the user community to participate in the elections, comments on Community Blog for taking questions (jflory7, 16:53:09)
    7. IDEA: Visual Summary of all Candidate Interviews: Improved format for "what kind of issues" at the table, chart / table for where candidates fall on some of these issues or topics (jflory7, 16:53:59)
    8. IDEA: Sending surveys after election for feedback and suggestions: Measuring voter satisfaction over what was successful and what was ineffective, For Survey collecting tools / follow-up with Diversity Team, open vs. closed tools, what options are available (jflory7, 16:54:41)
    9. IDEA: "I voted!" badge: Awarding the badge during / after election, utilizing fedmsg to deliver the badge, one or per release cycle (jflory7, 16:55:12)
    10. IDEA: Sending statistics related to voting metrics daily to improve voter turnout and keep contributors engaged (jflory7, 16:55:38)
    11. ACTION: bee2502 jflory7 Work on moving election-specific information from Flock into ticket #19, share with jkurik after (jflory7, 16:59:54)
    12. http://limesurvey.org/ (skamath, 17:01:52)
    13. === Ticket #34, 52, 84 === (jflory7, 17:02:36)
    14. #34: "[Onboarding Series] [MASTER TICKET] Creating sub-project on-boarding badge series"; #52: "Quality Assurance"; #84: "Python SIG" (jflory7, 17:02:42)
    15. https://pagure.io/fedora-commops/issue/34 (jflory7, 17:02:48)
    16. https://pagure.io/fedora-commops/issue/52 (jflory7, 17:02:51)
    17. https://pagure.io/fedora-commops/issue/84 (jflory7, 17:02:56)
    18. HELP: Need info and research on writing datagrepper queries with Bugzilla hooks to be used for badge series on filing bugs (1 bug = badge, 5 bugs = badge, etc.) (jflory7, 17:03:08)
    19. ACTION: skamath Research Bugzilla datagrepper queries for new bug report tickets (jflory7, 17:09:33)
    20. ACTION: sumantro a2batic File tickets in Fedora Badges Trac for filing Bugzilla bugs, for completing release validation testing, and getting sponsored to the QA group (jflory7, 17:13:00)
    21. https://fedoraproject.org/wiki/User:Dhanesh95/SIGs/Python (jflory7, 17:16:20)
    22. https://fedoraproject.org/wiki/User:Dhanesh95/SIGs/Python/Join (jflory7, 17:16:25)
    23. IDEA: Two FAS groups for Python: python-sig for interested members contributing to Python in Fedora, python-packagers for proven members of the community who can receive security-related bugs (jflory7, 17:24:23)
    24. ACTION: dhanesh95 Make changes to Python SIG pages based on feedback, post to python-devel mailing list requesting feedback on the rewrites, explain idea of splitting Python SIG into two FAS groups (python-sig for interested members, python-packagers for security-related bugs / pushing to packages git) (jflory7, 17:27:54)
    25. === Ticket #67 === (jflory7, 17:28:42)
    26. "[Objective] Owning the Release Announcements Process" (jflory7, 17:28:47)
    27. https://pagure.io/fedora-commops/issue/67 (jflory7, 17:29:02)
    28. IDEA: Using a single format for fill-in-the-blank type of information gathering for use by all involved working groups / SIGs (jflory7, 17:38:01)
    29. IDEA: Using a Pagure repo to centralize this information over the wiki (jflory7, 17:38:13)
    30. AGREED: Focus on developing a single format to be used to collect info from all involved working groups / SIGs (e.g. fill-in-the-blank sort of template as much as possible) (jflory7, 17:41:10)
    31. === Ticket #86 === (jflory7, 17:41:23)
    32. "Adjust meeting time by 30 minutes" (jflory7, 17:41:30)
    33. https://pagure.io/fedora-commops/issue/86 (jflory7, 17:41:34)
    34. ACTION: skamath dhanesh95 sumantro Leave vote in ticket #86 for revised meeting time (jflory7, 17:43:08)
    35. ACTION: jflory7 Close ticket #86 no sooner than 2016-09-08 (jflory7, 17:43:29)

  6. Wiki Gardening (jflory7, 17:43:45)
  7. Community Blog (jflory7, 17:45:02)
    1. How This Works: There is a quick blast of information about what was published in the past week with some metrics, followed by posts that are being drafted. After the information blast, the floor is opened for any Community Blog-related discussion. Here we go! (jflory7, 17:45:08)
    2. === This Week in CommBlog === (jflory7, 17:45:15)
    3. (1) "Fedora 24 Release Party in Singapore" (jflory7, 17:45:19)
    4. https://communityblog.fedoraproject.org/fedora-24-release-party-singapore/ (jflory7, 17:45:25)
    5. Total Views (Aug. 24 - Sep. 5): 100 (jflory7, 17:45:31)
    6. https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=2010 (jflory7, 17:45:37)
    7. (2) "Modularity Infrastructure Design" (jflory7, 17:45:47)
    8. https://communityblog.fedoraproject.org/modularity-infrastructure-design/ (jflory7, 17:45:52)
    9. Total Views (Aug. 25 - Sep. 5): 109 (jflory7, 17:45:56)
    10. https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=2154 (jflory7, 17:46:03)
    11. (3) "Globalization improvements in Fedora 24" (jflory7, 17:46:09)
    12. https://communityblog.fedoraproject.org/globalization-improvements-fedora-24/ (jflory7, 17:46:15)
    13. Total Views (Aug. 30 - Sep. 5): 383 (jflory7, 17:46:21)
    14. https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=2212 (jflory7, 17:46:27)
    15. (4) "FOSS Wave: Delhi, India" (jflory7, 17:46:39)
    16. https://communityblog.fedoraproject.org/foss-wave-delhi-india/ (jflory7, 17:46:45)
    17. Total Views (Aug. 31 - Sep. 5): 26 (jflory7, 17:46:57)
    18. https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=2145 (jflory7, 17:46:57)
    19. IDEA: Social media booster on FOSS Wave tag for all articles in this series? (jflory7, 17:47:11)
    20. (5) "Say no to wiki SPAM!" (jflory7, 17:47:16)
    21. https://communityblog.fedoraproject.org/say-no-to-wiki-spam/ (jflory7, 17:47:21)
    22. Total Views (Sep. 1 - Sep. 5): 89 (jflory7, 17:47:26)
    23. https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=2208 (jflory7, 17:47:31)
    24. (6) "Want to be Fedora contributor? Start with Fedora 25 translation sprint!" (jflory7, 17:47:48)
    25. https://communityblog.fedoraproject.org/fedora-25-translation-sprint/ (jflory7, 17:47:58)
    26. Total Views (Sep. 2 - Sep. 5): 327 (jflory7, 17:48:02)
    27. https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=2330 (jflory7, 17:48:07)
    28. (7) "FUDCon Phnom Penh: Call for Papers" (jflory7, 17:48:20)
    29. https://communityblog.fedoraproject.org/fudcon-phnom-penh-call-for-papers/ (jflory7, 17:48:25)
    30. Total Views (Sep. 3 - Sep. 5): 81 (jflory7, 17:48:35)
    31. https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=2305 (jflory7, 17:48:41)
    32. (8) "FOSS Wave: Women in Technology (Part 2)" (jflory7, 17:48:50)
    33. https://communityblog.fedoraproject.org/foss-wave-women-in-technology-part-2/ (jflory7, 17:48:54)
    34. Total Views (Sep. 5): 30 (jflory7, 17:49:00)
    35. https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=2241 (jflory7, 17:49:05)
    36. === Coming Up in CommBlog === (jflory7, 17:49:13)
    37. (1) "Event Report: WWFS-FWD’2016, Kolkata " (jflory7, 17:49:20)
    38. https://communityblog.fedoraproject.org/?p=2046&preview=1&_ppp=4423883c9d (jflory7, 17:49:25)
    39. (2) "Onboarding Kickoff – Fedora QA, Bhopal" (jflory7, 17:49:30)
    40. https://communityblog.fedoraproject.org/?p=2188&preview=1&_ppp=f0ebdc1766 (jflory7, 17:49:34)
    41. (3) "FOSS and Fedora #FOSS Wave BLR IN" (jflory7, 17:49:40)
    42. https://communityblog.fedoraproject.org/?p=2282&preview=1&_ppp=17dea148f1 (jflory7, 17:49:45)
    43. (4) "Fedora 24 release party in Paris" (jflory7, 17:49:51)
    44. https://communityblog.fedoraproject.org/?p=2380&preview=1&_ppp=f15bf599d2 (jflory7, 17:49:56)

  8. Release Schedule (jflory7, 17:51:40)
    1. https://fedorapeople.org/groups/schedule/f-25/f-25-key-tasks.html (jflory7, 17:51:44)
    2. (1) Beta Freeze (Tue 2016-09-27, 00:00 UTC) (jflory7, 17:52:05)
    3. (2) Beta Release Public Availability (Tue 2016-10-11) (jflory7, 17:52:23)

  9. Open Floor (jflory7, 17:52:46)
    1. https://communityblog.fedoraproject.org/feed/ (skamath, 17:55:39)
    2. HELP: Community Blog should be sending out email notifications to subscribers - related to Magazine problems as well? (jflory7, 17:55:44)


Meeting ended at 17:58: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. jflory7 bee2502 Take workshop feedback and parse it into more accessible data (e.g. tickets / commits / CommBlog posts / metrics / etc.)
  3. jflory7 Review emails for pending posts on the CommBlog
  4. jflory7 Update Community Blog writing guide for writing a new article based on what's actually happening in 2016 now
  5. jflory7 Sort through ideas on reviewing old contributor discussion, form proposals in the ticket, share at next meeting
  6. skamath File a ticket in Fedora Infra Trac for proposing an official migration from fedora-infra GitHub organization into Pagure
  7. jflory7 bee2502 Arrange for some personal hacking to close out Flock items
  8. dhanesh95 Start mailing list discussion on wiki page changes for Python SIG
  9. bee2502 jflory7 Work on moving election-specific information from Flock into ticket #19, share with jkurik after
  10. skamath Research Bugzilla datagrepper queries for new bug report tickets
  11. sumantro a2batic File tickets in Fedora Badges Trac for filing Bugzilla bugs, for completing release validation testing, and getting sponsored to the QA group
  12. dhanesh95 Make changes to Python SIG pages based on feedback, post to python-devel mailing list requesting feedback on the rewrites, explain idea of splitting Python SIG into two FAS groups (python-sig for interested members, python-packagers for security-related bugs / pushing to packages git)
  13. skamath dhanesh95 sumantro Leave vote in ticket #86 for revised meeting time
  14. jflory7 Close ticket #86 no sooner than 2016-09-08


Action items, by person

  1. a2batic
    1. sumantro a2batic File tickets in Fedora Badges Trac for filing Bugzilla bugs, for completing release validation testing, and getting sponsored to the QA group
  2. bee2502
    1. jflory7 bee2502 Take workshop feedback and parse it into more accessible data (e.g. tickets / commits / CommBlog posts / metrics / etc.)
    2. jflory7 bee2502 Arrange for some personal hacking to close out Flock items
    3. bee2502 jflory7 Work on moving election-specific information from Flock into ticket #19, share with jkurik after
  3. commops
    1. commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ]
  4. dhanesh95
    1. dhanesh95 Start mailing list discussion on wiki page changes for Python SIG
    2. dhanesh95 Make changes to Python SIG pages based on feedback, post to python-devel mailing list requesting feedback on the rewrites, explain idea of splitting Python SIG into two FAS groups (python-sig for interested members, python-packagers for security-related bugs / pushing to packages git)
    3. skamath dhanesh95 sumantro Leave vote in ticket #86 for revised meeting time
  5. jflory7
    1. jflory7 bee2502 Take workshop feedback and parse it into more accessible data (e.g. tickets / commits / CommBlog posts / metrics / etc.)
    2. jflory7 Review emails for pending posts on the CommBlog
    3. jflory7 Update Community Blog writing guide for writing a new article based on what's actually happening in 2016 now
    4. jflory7 Sort through ideas on reviewing old contributor discussion, form proposals in the ticket, share at next meeting
    5. jflory7 bee2502 Arrange for some personal hacking to close out Flock items
    6. bee2502 jflory7 Work on moving election-specific information from Flock into ticket #19, share with jkurik after
    7. jflory7 Close ticket #86 no sooner than 2016-09-08
  6. skamath
    1. skamath File a ticket in Fedora Infra Trac for proposing an official migration from fedora-infra GitHub organization into Pagure
    2. skamath Research Bugzilla datagrepper queries for new bug report tickets
    3. skamath dhanesh95 sumantro Leave vote in ticket #86 for revised meeting time
  7. sumantro
    1. sumantro a2batic File tickets in Fedora Badges Trac for filing Bugzilla bugs, for completing release validation testing, and getting sponsored to the QA group
    2. skamath dhanesh95 sumantro Leave vote in ticket #86 for revised meeting time


People present (lines said)

  1. jflory7 (329)
  2. skamath (77)
  3. dhanesh95 (39)
  4. zodbot (25)
  5. mhroncok (18)
  6. bee2502 (13)
  7. sumantro (9)
  8. FranciscoD (9)
  9. x3mboy (4)
  10. c0mrad3 (2)
  11. a2batic (2)
  12. a2batic_ (2)
  13. trishnag (1)
  14. mailga (1)
  15. commops (0)


Generated by MeetBot 0.1.4.