16:25:00 <jflory7> #startmeeting Fedora CommOps (2016-09-06)
16:25:01 <zodbot> Meeting started Tue Sep  6 16:25:00 2016 UTC.  The chair is jflory7. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:25:01 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
16:25:01 <zodbot> The meeting name has been set to 'fedora_commops_(2016-09-06)'
16:25:08 <jflory7> #meetingname commops
16:25:08 <zodbot> The meeting name has been set to 'commops'
16:25:13 <jflory7> #nick commops
16:25:19 <jflory7> #topic Agenda
16:25:25 <jflory7> #link https://fedoraproject.org/wiki/Meeting:CommOps_2016-09-06
16:25:30 <jflory7> #info (1) Roll Call / Q&A
16:25:34 <jflory7> #info (2) Announcements
16:25:39 <jflory7> #info (3) Action items from last meeting
16:25:44 <jflory7> #info (4) Tickets
16:25:49 <jflory7> #info (5) Wiki Gardening
16:25:53 <jflory7> #info (6) Community Blog
16:25:58 <jflory7> #info (7) Release Schedule
16:26:04 <jflory7> #info (8) Open Floor
16:26:15 <jflory7> #topic Roll Call / Q&A
16:26:15 <jflory7> #info Name; Timezone; Sub-projects/Interest Areas
16:26:22 <jflory7> #action commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ]
16:26:26 <jflory7> If this is your first time at a CommOps meeting, feel free to introduce yourself to everyone and say hello! If anyone has any questions before we get started with the rest of the agenda, now is also a good time to ask.
16:26:48 <jflory7> #info Justin W. Flory; UTC-4; CommOps, Marketing / Magazine, Ambassadors, Diversity Team, Join SIG, sysadmin-badges, and more
16:27:36 <dhanesh95> #info Dhanesh B. Sabane; UTC+5:30; CommOps, RPM Packaging, ML, Linux Kernel, Python
16:28:03 <skamath> .hello skamath
16:28:05 <zodbot> skamath: skamath 'Sachin S Kamath ' <sskamath96@gmail.com>
16:28:19 <FranciscoD> .hellomynameis ankursinha
16:28:20 <zodbot> FranciscoD: ankursinha 'Ankur Sinha' <sanjay.ankur@gmail.com>
16:28:22 <skamath> #info Sachin S. Kamath; UTC +5.30 ; GSoC, Metrics, CommOps
16:28:33 <skamath> Hi all :)
16:28:36 <jflory7> Hiya, everyone!
16:28:39 <trishnag> .hello trishnag
16:28:40 <zodbot> trishnag: trishnag 'Trishna Guha' <trishnaguha17@gmail.com>
16:28:46 <jflory7> #chair dhanesh95 skamath FranciscoD trishnag
16:28:46 <zodbot> Current chairs: FranciscoD dhanesh95 jflory7 skamath trishnag
16:28:58 <FranciscoD> hiya!
16:29:03 <dhanesh95> trishnag, skamath, jflory7 and CommOps o/
16:29:39 * skamath waves to dhanesh95
16:29:52 <jflory7> This time definitely works much easier for me now - hope it's not too much later for some of you :)
16:30:04 <jflory7> FranciscoD: Happy to see you join us!
16:30:32 <skamath> FranciscoD is doing really great job in the join SIG :D
16:30:35 <skamath> FranciscoD++
16:30:40 <jflory7> we'll wait another 3-5 minutes for some more folks to arrive.
16:30:48 <FranciscoD> :)
16:30:49 <jflory7> skamath: +1 to that :)
16:31:06 <FranciscoD> it's only 30 past now - you folks are a tad early :P
16:31:37 <skamath> FranciscoD, the meeting?
16:31:53 <jflory7> FranciscoD: I usually start roll call a few minutes early.
16:31:58 <FranciscoD> yea, I figured :)
16:32:15 <jflory7> Gives some time for people to ask any questions should they have any too. :)
16:32:46 * jflory7 is just happy he prepared the agenda on time for this week :P
16:33:14 <skamath> Way ahead of time i'd say :P
16:33:44 <jflory7> Maybe a little bit of compensation for last week!
16:33:59 <jflory7> Last week was a rush of lots of things.
16:34:52 <jflory7> Alrighty, we can go ahead and get started now. :)
16:34:54 <jflory7> #topic Announcements
16:35:00 <jflory7> #info === [Reminder] CommOps has moved to Pagure ===
16:35:05 <jflory7> #link https://pagure.io/fedora-commops
16:35:11 <jflory7> #info 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!
16:35:26 <jflory7> Marketing also moved over on Monday... it's starting a trend :)
16:35:31 <jflory7> #info === "Announcing the release of Fedora 25 Alpha!" ===
16:35:36 <jflory7> #link https://lists.fedoraproject.org/archives/list/announce@lists.fedoraproject.org/thread/OV3APVA63F4EM5FDLBN5DK5OKEZJWROJ/
16:35:43 <jflory7> #info 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.
16:35:48 <jflory7> #info === "Welcoming our new Fedora Community Action and Impact Coordinator" ===
16:35:53 <jflory7> #link https://fedoramagazine.org/welcoming-new-fedora-community-coordinator/
16:36:00 <jflory7> #info "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)!"
16:36:05 <jflory7> bexelbie++
16:36:11 <skamath> jflory7++ for the Pagure move \o/
16:36:11 <jflory7> #info === "Keeping Fedora beautiful: contribute your wallpaper!" ===
16:36:16 <jflory7> #link https://fedoramagazine.org/keeping-fedora-beautiful-contribute-wallpaper/
16:36:22 <jflory7> #info 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.
16:36:24 <jflory7> eof
16:36:29 <jflory7> That's all the announcements I have.
16:36:34 <jflory7> Anyone else have something they would like to add?
16:36:40 <skamath> Nothing here
16:37:10 <jflory7> Call for announcements, going once...
16:37:20 <jflory7> Going twice...
16:37:25 <jflory7> Thrice...
16:37:34 <jflory7> #topic Action items from last meeting
16:37:39 <jflory7> #link https://meetbot.fedoraproject.org/fedora-meeting/2016-08-30/commops.2016-08-30-15.58.html
16:37:45 <jflory7> #info 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.
16:37:52 <jflory7> #info === [IN PROGRESS] jflory7 bee2502 Take workshop feedback and parse it into more accessible data (e.g. tickets / commits / CommBlog posts / metrics / etc.) ===
16:38:00 <jflory7> #action jflory7 bee2502 Take workshop feedback and parse it into more accessible data (e.g. tickets / commits / CommBlog posts / metrics / etc.)
16:38:07 <jflory7> #info === [COMPLETE] jflory7 Review emails for pending posts on the CommBlog ===
16:38:14 <jflory7> #action jflory7 Review emails for pending posts on the CommBlog
16:38:14 <bee2502> .hello bee2502
16:38:16 <zodbot> bee2502: bee2502 'Bhagyashree Padalkar' <bhagyashree.iitg@gmail.com>
16:38:18 <skamath> bee2502, o/
16:38:19 <jflory7> They just keep coming! ;)
16:38:24 <jflory7> #chair bee2502
16:38:24 <zodbot> Current chairs: FranciscoD bee2502 dhanesh95 jflory7 skamath trishnag
16:38:26 <jflory7> bee2502: Hiya!
16:38:33 <jflory7> #info === [INCOMPLETE] jflory7 Update Community Blog writing guide for writing a new article based on what's actually happening in 2016 now ===
16:38:40 <jflory7> #action jflory7 Update Community Blog writing guide for writing a new article based on what's actually happening in 2016 now
16:38:48 <jflory7> #info === [INCOMPLETE] jflory7 Sort through ideas on reviewing old contributor discussion, form proposals in the ticket, share at next meeting ===
16:38:56 <jflory7> #action jflory7 Sort through ideas on reviewing old contributor discussion, form proposals in the ticket, share at next meeting
16:39:06 <jflory7> #info === [INCOMPELTE] skamath File a ticket in Fedora Infra Trac for proposing an official migration from fedora-infra GitHub organization into Pagure ===
16:39:06 <bee2502> !
16:39:13 <jflory7> #action skamath File a ticket in Fedora Infra Trac for proposing an official migration from fedora-infra GitHub organization into Pagure
16:39:19 <jflory7> bee2502: Sure, go ahead.
16:39:22 <bee2502> jflory7 : What do we need to do to close this ? Take workshop feedback and parse it into more accessible data (e.g. tickets / commits / CommBlog posts / metrics / etc.
16:40:29 <jflory7> bee2502: I think we should probably aim to make a final pass of the Etherpad and see if what's left in the pad that hasn't been covered somewhere else. We took the notes out of the Python SIG, but I think we can bring some of the notes / ideas about elections, maybe metrics, and Ambassadors into tickets or wiki
16:40:49 <jflory7> bee2502: Truthfully, for some of it, I'll probably need to rewatch the recording, especially for the tail-end
16:41:17 <jflory7> bee2502: We could try to do a Hangout if that's easiest or something else.
16:41:37 <a2batic_> .hello a2batic
16:41:38 <zodbot> a2batic_: a2batic 'None' <kmurarka@redhat.com>
16:41:39 <bee2502> jflory7 : yes, that would be great - sometime this week so we can close it before next meeting
16:41:45 <jflory7> a2batic_: o/
16:41:52 <jflory7> #chair a2batic_ a2batic
16:41:52 <zodbot> Current chairs: FranciscoD a2batic a2batic_ bee2502 dhanesh95 jflory7 skamath trishnag
16:41:56 <a2batic_> jflory7, \o
16:42:10 <jflory7> bee2502: Sounds good to me - let's sync up after the meeting or on Telegram to find a time that works well.
16:42:34 <bee2502> cool jflory7
16:42:37 <jflory7> #action jflory7 bee2502 Arrange for some personal hacking to close out Flock items
16:42:44 <jflory7> #info === [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 ===
16:42:45 <jflory7> #link https://pagure.io/fedora-commops/issue/82
16:42:55 <jflory7> #info === [COMPLETE] jflory7 Follow up on Pagure importer tool for use with decause's CommOps toolbox repositories ===
16:42:56 <jflory7> #link https://pagure.io/fedora-commops/issue/82
16:43:01 <jflory7> #info === [COMPLETE] jflory7 Remove Ticket #81 from meeting agenda ===
16:43:08 <jflory7> #info === dhanesh95 Start IRC / mailing list discussion on wiki gardening for Python SIG ===
16:43:14 <jflory7> dhanesh95: Any updates you want to add here?
16:43:20 <jflory7> I know you reached out in the IRC channel.
16:43:26 * jflory7 also has this ticket on the agenda for today too
16:44:50 <jflory7> Hmmm, dhanesh95 might not be at the keyboard - I'll reaction for a mailing list follow-up after we get him some feedback on his changes
16:45:08 <jflory7> #action dhanesh95 Start mailing list discussion on wiki page changes for Python SIG
16:45:14 <jflory7> #info === [COMPLETE] jflory7 Do some srs ticket triaging / updating this week ===
16:45:22 <jflory7> #info The CommOps Pagure is completely triaged and migrated to work well in Pagure versus Trac
16:45:27 * jflory7 is especially happy about this one
16:45:33 <jflory7> #info === [COMPLETE] amitsin6h Double-check subscription to the mailing list and make sure you are receiving mail from the list ===
16:45:45 <jflory7> #info === [COMPLETE] jflory7 Come up with a more fitting introductory item to place into the meeting ===
16:45:55 <skamath> jflory7++ Received a flood of Pagure mails the other day
16:46:17 <jflory7> ^^ This was in context of wiki gardening - now there's an action item at the start for mailing list introductions.
16:46:24 <jflory7> skamath: Heh, yeah, it was probably a little bit noisy.
16:46:30 <jflory7> #info === [COMPLETE] jflory7 Revisit Join page and edit / alter section about wiki page ===
16:46:36 <jflory7> #link https://fedoraproject.org/wiki/CommOps/Join
16:46:54 <jflory7> Pretty sure dhanesh95 or skamath did most of the work here, though. :) ^^
16:46:57 <jflory7> #info === [COMPLETE] skamath Garden the CommOps wiki page to remove mention of Trac and replace with Pagure (and update hyperlinks) ===
16:47:03 <jflory7> #link https://fedoraproject.org/wiki/CommOps
16:47:06 <jflory7> #link https://fedoraproject.org/wiki/CommOps/Join
16:47:10 <jflory7> #info === [COMPLETE] downey Migrate the member table from https://fedoraproject.org/wiki/CommOps#Interest_Areas to https://fedoraproject.org/wiki/CommOps/Members ===
16:47:15 <jflory7> #link https://fedoraproject.org/wiki/CommOps/Members
16:47:23 <jflory7> Okay, and that's all remaining action items from last week.
16:47:41 <skamath> downey++
16:47:55 <jflory7> Now to the real portion of the meeting:
16:47:55 <jflory7> #topic Tickets
16:48:04 <jflory7> #link https://pagure.io/fedora-commops/issues?tags=meeting
16:48:17 <jflory7> #info === Ticket #19 ===
16:48:24 <jflory7> #info "Improve automation of Elections communication"
16:48:31 <jflory7> #link https://pagure.io/fedora-commops/issue/19
16:48:35 <jflory7> New ticket to the meeting agenda! This one focuses on Fedora Elections that happen (roughly) each release cycle. Focusing on ways to improve automation, but first steps maybe identifying key steps in communication (e.g. what makes an election more obvious)? Can we improve how the questionnaire is collected? jkurik and bee2502 may have thoughts here. The CommOps workshop also was helpful for this.
16:49:27 <jflory7> While the ticket deals strictly with automation, before we get to that, I think we should probably spend some time on identifying what makes for a successful election. I think it's a good idea to compare between the December 2015 and July 2016 elections for participation levels and what did or did not happen.
16:49:43 <jflory7> I think we were definitely noisier in December but we also had some more community involvement too
16:49:55 <jflory7> We had a lot of useful brainstorming on this at Flock too, let me dig up those notes
16:50:36 <jflory7> bee2502: Did jkurik get back to you on that email?
16:50:39 <jflory7> #link https://etherpad.gnome.org/p/flock-2016-commops-workshop
16:51:06 * skamath is yet to watch the workshop video
16:51:09 <jflory7> The email draft at the bottom has the most helpful format of the key points
16:51:32 <jflory7> skamath: It's a long one, that's for sure.
16:51:53 <skamath> jflory7, Yep. I finished watching almost all the talks
16:52:01 <skamath> Saving the best for the last :)
16:52:22 <jflory7> Heh, you've been busy then!
16:52:34 <jflory7> I'll summarize some of the points from the Etherpad here
16:52:48 <bee2502> jflory7 : no
16:53:09 <jflory7> #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
16:53:30 <jflory7> bee2502: Hmm, maybe we should resend - I know he was on vacation for a time so maybe it got buried.
16:53:59 <jflory7> #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
16:54:41 <jflory7> #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
16:54:59 <bee2502> jflory7 : I think we can put it all in a ticket first and then mail him with a link to ticket.
16:55:12 <jflory7> #idea "I voted!" badge: Awarding the badge during / after election, utilizing fedmsg to deliver the badge, one or per release cycle
16:55:27 <jflory7> bee2502: Yeah, I think ticketing it away would be best. I think #19 is probably the best place for it.
16:55:38 <jflory7> #idea Sending statistics related to voting metrics daily to improve voter turnout and keep contributors engaged
16:55:51 <skamath> jflory7, we were talking about setting up a Limesurvey instance in the join SIG. If it can be of use to multiple groups, we can definitely move forward with the idea and talk to infra about it
16:56:00 <jflory7> bee2502: Do you want to work on adding the info to the ticket or should I?
16:56:10 <skamath> FranciscoD, ^^
16:56:33 <jflory7> skamath: That could be interesting. I know decause had done some wrangling with tatica on the diversity survey with LimeSurvey - not sure where all that is now.
16:56:42 <FranciscoD> like we spoke of before - it depends on the effort/requirement ratio
16:56:45 <jflory7> i.e. a shared Fedora instance or just one per team
16:56:55 <FranciscoD> (like everything else)
16:57:16 <skamath> FranciscoD, right now CommOps, Join and Diversity requires some sort of survey mechanism
16:57:51 <skamath> So, why not :)
16:58:11 <skamath> I can try to set up a LimeSurvey instance on the CommOps cloud instance
16:58:16 <FranciscoD> as long as someone's happy to do the packaging and infra deployment/maintenance, why not :)
16:58:18 <skamath> And see how it goes
16:58:40 <skamath> jflory7, what do you think?
16:59:14 <bee2502> jflory7 : we can do it during the hangouts ?
16:59:29 <jflory7> It would be good to know what the needs of the survey would be for finding the solution. For Diversity, a lot of planning has been put into that (and still more needed). Once we get this info parsed into a ticket and get jkurik's thoughts, we can begin identifying and discussing the needs for an Elections survey.
16:59:31 <jflory7> bee2502: +1
16:59:52 <bee2502> add an action item please jflory7
16:59:54 <jflory7> #action bee2502 jflory7 Work on moving election-specific information from Flock into ticket #19, share with jkurik after
16:59:58 <jflory7> Done :)
17:00:24 * dhanesh95 is playing catch up after a heavy dinner :P
17:00:25 <jflory7> For now, I think this should be enough - once we have this info easily shared and open for feedback, it will be easier to move on. And I think having jkurik involved is important too
17:00:31 <jflory7> dhanesh95: o/
17:00:34 <skamath> jflory7, is it okay to set up a LimeSurvey instance on commops cloud?
17:00:36 <FranciscoD> skamath: would also help to look at what survey software there is - limesurvey maybe one option
17:00:40 <dhanesh95> jflory7: o/
17:00:42 <skamath> FranciscoD, nod nod
17:01:06 <bee2502> regarding the cloud instance for surveys, better plan and open a ticket with infra before moving forward with anything.
17:01:19 <skamath> Ack.
17:01:25 <jflory7> skamath: I don't know the details on LimeSurvey (thought it was proprietary / paid service), but I have no objections to playing around with it and experimenting. I have no experience or knowledge on LimeSurvey. Anything official, like bee2502 said, should probably be an Infra ticket.
17:01:40 <skamath> jflory7, Limesurvey is open sourced :)
17:01:52 <skamath> #link http://limesurvey.org/
17:02:04 <jflory7> Ahh, then today I learned. Maybe the paid part was just the hosting instance decause was trying to set up long ago then
17:02:09 <jflory7> We can play with specifics later.
17:02:24 <jflory7> Anyways, I think we're probably good on this ticket.
17:02:36 <jflory7> #info === Ticket #34, 52, 84 ===
17:02:42 <jflory7> #info #34: "[Onboarding Series] [MASTER TICKET] Creating sub-project on-boarding badge series"; #52: "Quality Assurance"; #84: "Python SIG"
17:02:48 <jflory7> #link https://pagure.io/fedora-commops/issue/34
17:02:51 <jflory7> #link https://pagure.io/fedora-commops/issue/52
17:02:56 <jflory7> #link https://pagure.io/fedora-commops/issue/84
17:03:02 <jflory7> Quality Assurance: New ideas from a2batic and sumantrom on where the Quality Assurance team on-boarding could be improved and where badges would be useful. A FAS group sponsorship (easy), a Bugzilla-related badge series (trickier), and a series awarded for release validation testing (manually awarded).
17:03:08 <jflory7> #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.)
17:03:33 <c0mrad3> .hello dhanvi
17:03:34 <zodbot> c0mrad3: dhanvi 'Tummala Dhanvi' <dhanvicse@gmail.com>
17:03:41 * c0mrad3 sorry for the delay!
17:03:43 <skamath> jflory7, I can try tackling that
17:03:44 <jflory7> I was reviewing the criteria for Bugzilla fedmsg queries, and it looks like it should be possible to construct a query that looks at a bug reporter's email address. The one caveat we have here is if the Bugzilla email is different from FAS.
17:03:48 <jflory7> c0mrad3: o.
17:03:50 <jflory7> * o/
17:03:52 <jflory7> #chair c0mrad3
17:03:52 <zodbot> Current chairs: FranciscoD a2batic a2batic_ bee2502 c0mrad3 dhanesh95 jflory7 skamath trishnag
17:04:13 <jflory7> skamath: Okay, cool. You mean digging into constructing that query?
17:04:20 <skamath> jflory7, Yep
17:04:34 <jflory7> a2batic_: Also, to be sure, did you or sumantrom already file any tickets in Fedora Badges Trac for these ideas?
17:04:35 <dhanesh95> Isn't Bugzilla account connected to FAS?
17:04:44 <jflory7> dhanesh95: Not quite. It's its own instance.
17:05:17 <skamath> dhanesh95, It does have fedmsg listeners though :)
17:05:30 <jflory7> As of recently, yes :)
17:05:34 <dhanesh95> jflory7: nod nod
17:05:38 <dhanesh95> skamath: Cool!
17:06:44 <a2batic> jflory7, we have commented on the tickets mentioned only, I am not sure about  tickets in Fedora Badges Trac but
17:07:35 <bee2502> is datagrepper down ? can anyone access it ?
17:08:00 <jflory7> a2batic: Okay, if you have only commented so far, that's fine. :) We can help with the badges.
17:08:01 <dhanesh95> bee2502: Service unavailable
17:08:13 <jflory7> bee2502: I also get service unavailable - maybe a ping in #fedora-admin?
17:08:18 * jflory7 isn't aware of scheduled maintenance
17:08:36 <jflory7> skamath: Would you be okay with taking an action item for the Bugzilla datagrepper queries?
17:08:40 <skamath> bee2502, It's up
17:08:49 <skamath> jflory7, I'll take that
17:09:00 <jflory7> Oh, it's up for me now too
17:09:01 <jflory7> Strange
17:09:05 <dhanesh95> Datagrepper back in action!
17:09:09 <skamath> Need to do a bit of research on bugzilla fields :)
17:09:10 <bee2502> yaay
17:09:33 <jflory7> #action skamath Research Bugzilla datagrepper queries for new bug report tickets
17:09:35 <jflory7> sumantro: o/
17:09:35 * sumantro is here
17:09:53 <jflory7> sumantro: Hiya! We were just talking about the QA series badges. :)
17:09:54 <sumantro> o/ :D
17:10:20 <sumantro> yes kanika just called me :D
17:10:51 <skamath> jflory7, I am afraid the mailman blocker will hit bugzilla badges too :(
17:10:52 <jflory7> sumantro, a2batic: To give a quick summary, skamath is going to do some research into the datagrepper queries for Bugzilla to automatically award a badge for bugs filed. In the meanwhile, do you think either of you two would be up for filing the tickets in the Fedora Badges Trac for the three ideas you commented on in our Pagure? I think they
17:11:04 <jflory7> * they're excellent ideas for badges. :)
17:11:24 <skamath> jflory7, I did see your ping in the Pagure ticket about the blockers. I'll add my comments in a while
17:11:41 <sumantro> yes sure we will be filing :)
17:12:03 <jflory7> skamath: Hmmmm... I don't know, though - Mailman can resolve to FAS usernames, but Bugzilla has no usernames, only emails. Would there be any way to resolve emails to FAS usernames in a query? Or something like that?
17:12:12 <jflory7> sumantro: Awesome, I will action this to you both then. :)
17:12:20 <skamath> jflory7, we do have a email->username resolving mechanism
17:12:33 <sumantro> done! jflory7
17:12:35 <skamath> But that assumes your fas email == bugzilla email
17:13:00 <jflory7> #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
17:13:15 <skamath> jflory7, we can resolve to usernames if the fas email is the bugzilla e-mail
17:13:19 <jflory7> sumantro: Oh, awesome, make sure to CC me to all of them too so I keep track of them as well. :)
17:13:24 <jflory7> sumantro++
17:13:39 <sumantro> sure jflory7
17:13:57 <jflory7> skamath: Yeah, we'll probably have to accept that sometimes it will fail for those that use different addresses between the two
17:14:07 <jflory7> Having a way to handle that will be important if there isn't a way already
17:14:16 <bee2502> I am going to pop out for some time now - be back in half an hour !
17:14:20 * jflory7 has much to learn in the way of datagrepper
17:14:26 <jflory7> bee2502: Okay, sounds good - see you in a bit!
17:14:52 <jflory7> Anything else to cover on the QA series?
17:15:10 <jflory7> I think for now, skamath, sumantro, and a2batic will have some tasks to move forward on. :)
17:15:21 <skamath> nod nod
17:15:32 * sumantro nods
17:15:37 <a2batic> yeah :)
17:15:51 <dhanesh95> skamath, jflory7: Is it not possible to mention in the join page to use the same email ID used for FAS while registering on BugZilla?
17:15:58 <jflory7> Awesome. :) Then we can switch gears over to the Python SIG next.
17:16:06 <jflory7> dhanesh95: We can definitely recommend users to do that.
17:16:13 <jflory7> A note about it somewhere will be helpful
17:16:14 <jflory7> Python SIG: dhanesh95 made big changes to the proposed wiki page, and more feedback is needed. We want to propose this page to the Python SIG - quick look now for feedback to pass to dhanesh95?
17:16:20 <jflory7> #link https://fedoraproject.org/wiki/User:Dhanesh95/SIGs/Python
17:16:25 <jflory7> #link https://fedoraproject.org/wiki/User:Dhanesh95/SIGs/Python/Join
17:16:36 <skamath> dhanesh95, Join page of?
17:16:43 <dhanesh95> skamath: QA
17:16:56 <jflory7> mhroncok / pviktori: ping, either of you happen to be around?
17:17:06 <mhroncok> yep
17:17:09 <skamath> dhanesh95, I don't think all bugzilla users visit the QA Join page. Do they?
17:17:35 * mhroncok reads the links
17:17:47 <jflory7> mhroncok: Would you mind taking a look at the two above links? dhanesh95 tried rewriting the Python SIG wiki page to be more current, and he was hoping to get some feedback on it. If you're tied up now, there's also a ticket on this that you could leave feedback in later.
17:17:47 <dhanesh95> skamath: If we are talking about Onboarding new contributors, I think a thorough read of the join page is necessary
17:18:01 <jflory7> mhroncok++ awesome.
17:18:26 <skamath> dhanesh95, Possible. But how will you award badges to existing users if that is the case. It's definitely an edge case/
17:18:57 <dhanesh95> skamath: If we can't change the current status, at least we can avoid such situations in the future.
17:19:08 <mhroncok> I don't think "Build your portfolio" should be the first reason for joining
17:19:29 <dhanesh95> mhroncok: Roger that!
17:20:19 <jflory7> skamath, dhanesh95: In the context on onboarding new QA contributors, a mention on the QA team Join page wouldn't hurt as that's likely the audience of many who might be searching for the badges. Including a note in Bugzilla itself isn't as straightforward.
17:20:25 <mhroncok> Python Features section needs some love, but it needed that before anyway
17:20:32 <mhroncok> we can adress that later
17:20:55 * jflory7 nods
17:21:00 <dhanesh95> mhroncok: Python Features needs a lot of love and I'm not sure how to provide that :P
17:21:11 <mhroncok> that makes sense
17:21:33 <mhroncok> the join part has no mention of the fas group, which is good
17:21:48 <mhroncok> is you can somehow solve that the Python SIG badge is currently related tio the group
17:22:09 <jflory7> dhanesh95: On the Join page, I think we could try to target specific information for newcomers to include in their self-introductions that would be helpful for SIG members to know where someone fits in the Python community and what their expertise is
17:22:25 <mhroncok> I don't see why Get "Bootstrapped"! is there
17:22:32 <dhanesh95> jflory7: nod nod
17:22:49 <mhroncok> jflory7: yes
17:22:56 <mhroncok> dhanesh95++
17:22:56 <zodbot> mhroncok: Karma for dhanesh95 changed to 7 (for the f24 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
17:22:56 <jflory7> mhroncok: Earlier we discussed the ideas of two FAS groups for Python: "python-sig" and "python-security". The security group would get the notifications on potentially critical bugs. Have any thoughts on that?
17:23:08 <dhanesh95> mhroncok: New contributors get an idea of the complete Fedora environment
17:23:17 <mhroncok> jflory7: python-packagers works better for me
17:23:34 <jflory7> python-packagers, cool - so you like the idea of possibly splitting it into two FAS groups?
17:23:50 <dhanesh95> +1 for two groups
17:24:02 <mhroncok> well the only purpuse of the new python-sig grpoup would be to get the badge?
17:24:18 <mhroncok> can we do that upon mailing list subsribing or something like that?
17:24:23 <jflory7> #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
17:24:50 <jflory7> mhroncok: Ideally, I think there would be some sort of "bringing in" process before getting sponsored, e.g. if someone is hanging around and helping with Python things, they would be sponsored
17:24:51 <mhroncok> ...and mostly, push to the pakages git
17:25:03 <jflory7> It wouldn't have any access to anything that I can think of immediately
17:25:12 <mhroncok> got it
17:25:39 <mhroncok> I'm fine with that, but please summarize it and send it to python-devel list, so others can provide their feedback as well
17:25:45 <jflory7> Okay, cool, this feedback is especially helpful - thanks for the quick review. :) mhroncok++
17:25:54 <jflory7> mhroncok: Yep, we will definitely be communicating on list there. :)
17:25:58 <dhanesh95> mhroncok: Thanks a lot for your feedback!
17:26:02 <dhanesh95> mhroncok++
17:26:02 <zodbot> dhanesh95: Karma for churchyard changed to 5 (for the f24 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
17:26:08 <mhroncok> dhanesh95: np, thanks for the proposals
17:26:38 <jflory7> dhanesh95: For this one, think a good #action item would be to add changes based on feedback, then share your drafts with the python-devel mailing list?
17:26:51 <dhanesh95> jflory7: +1
17:26:54 <jflory7> (along with explaining the idea of two FAS groups)
17:26:58 <jflory7> dhanesh95++ Awesome.
17:27:04 <dhanesh95> jflory7: Consider it done
17:27:54 <jflory7> #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)
17:28:04 <skamath> dhanesh95++
17:28:11 <skamath> mhroncok++
17:28:11 <zodbot> skamath: Karma for churchyard changed to 6 (for the f24 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
17:28:30 <jflory7> Okay, great - I think we can move on past the onboarding tickets then!
17:28:36 <jflory7> Lots of things happening all around. :)
17:28:42 <jflory7> #info === Ticket #67 ===
17:28:46 <skamath> Lot of *awesome* things :D
17:28:47 <jflory7> #info "[Objective] Owning the Release Announcements Process"
17:29:02 <jflory7> #link https://pagure.io/fedora-commops/issue/67
17:29:06 <jflory7> Older ticket about an objective for CommOps, but wanted to raise to discussion. Release announcements are a uniquely marketing task… doesn't seem like writing them fits along with CommOps tasks. However, there are inefficiencies with communication between working groups / SIGs for new info in release. Are there ways we could maybe help improve the communication flow between these groups and Marketing?
17:29:31 <jflory7> I wanted to revise this ticket from "owning" the entire process to "improving" the communication process.
17:30:12 <jflory7> Was curious to know others' thoughts on this
17:31:29 * skamath didn't quite follow the discussion about this
17:32:12 * dhanesh95 is clueless ATM
17:32:18 <jflory7> Okay, I can do a quick recap:
17:32:57 <jflory7> So I think decause was hoping for the entire release announcement process to become something completely managed by CommOps, e.g. writing the big post for Alpha, Beta, and final release.
17:33:20 <jflory7> Traditionally, this has always been a Marketing / person-who-does-it-last-minute sort of task.
17:33:34 <skamath> I see.
17:33:41 <jflory7> However, I don't think it's something CommOps should necessarily *own*
17:33:49 <skamath> But how is Alpha/Beta announcements a Marketing task?
17:33:52 <jflory7> Because to me, the release announcement still feels uniquely "marketing"
17:33:58 * dhanesh95 nods in agreement
17:34:33 * sumantro concurs with justin
17:34:35 <jflory7> skamath: It's focusing on communicating the next big release or announcement of a testing version of Fedora with the greater community. The key thing I see different is that it's more about outreach. Or, engaging with people outside of the Fedora community. Which to me is more of a marketing thing.
17:34:40 <jflory7> cc: mailga too, if you're around
17:34:46 <jflory7> However...
17:34:49 <skamath> Nod nod
17:34:54 <skamath> That makes sense
17:35:10 <jflory7> I think there's ways we can help with this process. One of the painful parts of this in Marketing is having to wrangle talking points from all of the different working groups and SIGs for the editions and spins
17:35:35 <jflory7> Sometimes it involves going person to person to meeting to mailing list to person to get the right info
17:36:13 <jflory7> If there's something we could help with, I think it's creatively coming up with ideas on how to make that more intuitive and simpler
17:36:25 <skamath> jflory7, Or we can have a wiki page for each of the team and ask them to populate that page with relevant information
17:36:42 <jflory7> skamath: That's kind of what we have now. https://fedoraproject.org/wiki/Fedora_25_talking_points
17:36:56 <jflory7> skamath: you wouldn't believe how long it takes for that page to look even like that. :D
17:37:02 * skamath clicks
17:37:18 <skamath> Wew.
17:37:25 <dhanesh95> jflory7: Maybe we can decide a format which will be uniform throughout the Fedora working groups / SIGs and these groups can push them on a Pagure repo owned by the marketing team
17:38:01 <jflory7> #idea Using a single format for fill-in-the-blank type of information gathering for use by all involved working groups / SIGs
17:38:13 <jflory7> #idea Using a Pagure repo to centralize this information over the wiki
17:38:24 <jflory7> dhanesh95: I like the idea of coming up with a single format for everyone to folloe
17:38:26 <jflory7> * follow
17:38:36 <skamath> +1 to templating
17:38:39 <dhanesh95> jflory7: Thanks
17:38:41 <skamath> -1 to Pagure repo
17:38:53 <jflory7> e.g. "Big Feature of Server": *____ this has changed; *_____ is new, etc.
17:39:10 <dhanesh95> jflory7: Exactly! ^^
17:39:41 <jflory7> I think for now, the next task on this ticket should be to create that format.
17:39:46 * jflory7 takes note of the time
17:39:48 <skamath> Pagure repo = push permissions = lot of people on a repo. It'll only lead to confusion
17:39:58 <jflory7> skamath: That's true - a wiki is much more open.
17:40:20 <jflory7> For now, shall we agree to developing a single format and discuss details either during this week or at the next meeting?
17:40:24 <skamath> +1
17:40:26 <dhanesh95> +1
17:40:41 <jflory7> Since we're wrapping on this process now for Marketing, I think it's a low priority task for now, but having it in place for F26 would be ***awesome***
17:41:04 <skamath> Ah, F26 milestone ticket :)
17:41:09 <dhanesh95> ***+1***
17:41:10 <jflory7> #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)
17:41:18 * jflory7 will skip #83 due to time today
17:41:23 <jflory7> #info === Ticket #86 ===
17:41:28 <dhanesh95> Aww...
17:41:30 <jflory7> #info "Adjust meeting time by 30 minutes"
17:41:34 <jflory7> #link https://pagure.io/fedora-commops/issue/86
17:41:42 <jflory7> dhanesh95: Feel free to leave some comments in that ticket, though :)
17:41:45 <jflory7> We delayed the meeting by 30 minutes today, but can we vote to make this official? Can update and close ticket after this meeting.
17:41:45 <skamath> I thought this was passed in the last meeting?
17:41:53 <skamath> +1 again
17:41:57 <jflory7> skamath: I think everyone in the meeting today also voted in the meeting last week
17:42:04 <dhanesh95> +1 from my side
17:42:13 <sumantro> +1
17:42:14 <jflory7> I created a ticket for it officially now to help communicate it.
17:42:21 <skamath> +1 form jflory7 again.
17:42:24 <skamath> *from
17:42:28 <skamath> So passed :P
17:42:38 <mailga> +1 :D
17:42:42 <jflory7> If you all can leave your vote in the ticket, I'll close the ticket out this week after the 72 hours we agreed on as the voting time. :)
17:42:49 <skamath> nod nod
17:43:08 <jflory7> #action skamath dhanesh95 sumantro Leave vote in ticket #86 for revised meeting time
17:43:16 <skamath> Done
17:43:20 <dhanesh95> jflory7: Roger that!
17:43:29 <jflory7> #action jflory7 Close ticket #86 no sooner than 2016-09-08
17:43:43 <jflory7> Okay, and that wraps up all the tickets for today!
17:43:45 <jflory7> #topic Wiki Gardening
17:43:57 <jflory7> Anyone have any pages to call to attention that weren't already part of a ticket?
17:44:07 <skamath> The garden looks fresh :)
17:44:11 <jflory7> I think the Python SIG pages are getting a lot of focus in the wiki gardening world right now :)
17:44:28 <jflory7> skamath: lolol, that's good news to me!
17:44:47 <skamath> jflory7, Hah, it sure is
17:44:57 <jflory7> Since we have CommBlog left and hardly 15 minutes, I'm just going to switch over to that.
17:45:02 <jflory7> #topic Community Blog
17:45:08 <jflory7> #info 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!
17:45:15 <jflory7> #info === This Week in CommBlog ===
17:45:19 <jflory7> #info (1) "Fedora 24 Release Party in Singapore"
17:45:25 <jflory7> #link https://communityblog.fedoraproject.org/fedora-24-release-party-singapore/
17:45:31 <jflory7> #info Total Views (Aug. 24 - Sep. 5): 100
17:45:37 <jflory7> #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=2010
17:45:38 * dhanesh95 is already done with his dinner. Ice-cream anyone? :P
17:45:39 <jflory7> GIANT_CRAB++
17:45:47 <jflory7> #info (2) "Modularity Infrastructure Design"
17:45:52 <jflory7> #link https://communityblog.fedoraproject.org/modularity-infrastructure-design/
17:45:56 <jflory7> #info Total Views (Aug. 25 - Sep. 5): 109
17:46:03 <jflory7> #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=2154
17:46:09 <jflory7> #info (3) "Globalization improvements in Fedora 24"
17:46:15 <jflory7> #link https://communityblog.fedoraproject.org/globalization-improvements-fedora-24/
17:46:21 <jflory7> #info Total Views (Aug. 30 - Sep. 5): 383
17:46:27 <jflory7> #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=2212
17:46:30 <jflory7> cpacheco++
17:46:33 <jflory7> pravins++
17:46:39 <jflory7> #info (4) "FOSS Wave: Delhi, India"
17:46:45 <jflory7> #link https://communityblog.fedoraproject.org/foss-wave-delhi-india/
17:46:57 <jflory7> #info Total Views (Aug. 31 - Sep. 5): 26
17:46:57 <jflory7> #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=2145
17:47:11 <jflory7> #idea Social media booster on FOSS Wave tag for all articles in this series?
17:47:16 <jflory7> #info (5) "Say no to wiki SPAM!"
17:47:21 <jflory7> #link https://communityblog.fedoraproject.org/say-no-to-wiki-spam/
17:47:26 <jflory7> #info Total Views (Sep. 1 - Sep. 5): 89
17:47:31 <jflory7> #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=2208
17:47:40 <jflory7> sumantro++
17:47:42 <jflory7> bexelbie++
17:47:48 <jflory7> #info (6) "Want to be Fedora contributor? Start with Fedora 25 translation sprint!"
17:47:58 <jflory7> #link https://communityblog.fedoraproject.org/fedora-25-translation-sprint/
17:48:02 <jflory7> #info Total Views (Sep. 2 - Sep. 5): 327
17:48:07 <jflory7> #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=2330
17:48:19 <jflory7> pravins++
17:48:20 <jflory7> #info (7) "FUDCon Phnom Penh: Call for Papers"
17:48:25 <jflory7> #link https://communityblog.fedoraproject.org/fudcon-phnom-penh-call-for-papers/
17:48:35 <jflory7> #info Total Views (Sep. 3 - Sep. 5): 81
17:48:41 <jflory7> #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=2305
17:48:45 <jflory7> gnokii++
17:48:50 <jflory7> #info (8) "FOSS Wave: Women in Technology (Part 2)"
17:48:54 <jflory7> #link https://communityblog.fedoraproject.org/foss-wave-women-in-technology-part-2/
17:49:00 <jflory7> #info Total Views (Sep. 5): 30
17:49:05 <jflory7> #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=2241
17:49:08 <jflory7> a2batic++
17:49:13 <jflory7> #info === Coming Up in CommBlog ===
17:49:16 <skamath> Wow, that's a lot :O
17:49:20 <jflory7> #info (1) "Event Report: WWFS-FWD’2016, Kolkata "
17:49:25 <jflory7> #link https://communityblog.fedoraproject.org/?p=2046&preview=1&_ppp=4423883c9d
17:49:30 <jflory7> #info (2) "Onboarding Kickoff – Fedora QA, Bhopal"
17:49:32 <dhanesh95> GIANT_CRAB++ pravins++ sumantro++ bexelbie++ a2batic++
17:49:32 <zodbot> dhanesh95: Karma for woohuiren changed to 5 (for the f24 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
17:49:34 <jflory7> #link https://communityblog.fedoraproject.org/?p=2188&preview=1&_ppp=f0ebdc1766
17:49:35 <zodbot> dhanesh95: Karma for pravins changed to 9 (for the f24 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
17:49:38 <zodbot> dhanesh95: Karma for sumantro changed to 3 (for the f24 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
17:49:40 <jflory7> #info (3) "FOSS and Fedora #FOSS Wave BLR IN"
17:49:41 <zodbot> dhanesh95: Karma for bex changed to 7 (for the f24 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
17:49:44 <zodbot> dhanesh95: Karma for a2batic changed to 6 (for the f24 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
17:49:45 <jflory7> #link https://communityblog.fedoraproject.org/?p=2282&preview=1&_ppp=17dea148f1
17:49:51 <jflory7> #info (4) "Fedora 24 release party in Paris"
17:49:56 <jflory7> #link https://communityblog.fedoraproject.org/?p=2380&preview=1&_ppp=f15bf599d2
17:50:15 <jflory7> skamath: Yes, it has been *very* busy in the CommBlog lately :)
17:50:23 <jflory7> Shout out to all of the awesome authors contributing content
17:50:53 <jflory7> I have nothing else for the CommBlog :)
17:51:20 <jflory7> Community Blog, going once...
17:51:30 <jflory7> Going twice...
17:51:35 <jflory7> Thrice...
17:51:40 <jflory7> #topic Release Schedule
17:51:44 <jflory7> #link https://fedorapeople.org/groups/schedule/f-25/f-25-key-tasks.html
17:51:56 <x3mboy> .fas x3mboy
17:51:57 <zodbot> x3mboy: x3mboy 'Eduard Lucena' <eduardlucena@gmail.com>
17:52:02 <x3mboy> Sorry i was late
17:52:05 <jflory7> #info (1) Beta Freeze (Tue 2016-09-27, 00:00 UTC)
17:52:05 <x3mboy> Toooo late
17:52:23 <jflory7> #info (2) Beta Release Public Availability (Tue 2016-10-11)
17:52:33 <skamath> x3mboy, o/
17:52:34 <jflory7> x3mboy: Hiya! We're about to wrap up, but no worries.
17:52:37 <jflory7> #chair x3mboy
17:52:37 <zodbot> Current chairs: FranciscoD a2batic a2batic_ bee2502 c0mrad3 dhanesh95 jflory7 skamath trishnag x3mboy
17:52:43 <x3mboy> skamath, o/
17:52:46 <jflory7> #topic Open Floor
17:52:48 <jflory7> #chair sumantro
17:52:48 <zodbot> Current chairs: FranciscoD a2batic a2batic_ bee2502 c0mrad3 dhanesh95 jflory7 skamath sumantro trishnag x3mboy
17:52:59 <jflory7> Alrighty. Anything else that anyone would like to bring up here?
17:53:01 <skamath> I've got nothing.
17:53:17 <jflory7> We've got some fair time until the beta will arrive, so lots of time to prepare up to then :)
17:53:29 <jflory7> We definitely have a lot happening this week regardless.
17:53:45 <skamath> Yeah :)
17:53:50 <skamath> A busy week for CommOps
17:53:55 <jflory7> commops++
17:53:57 <dhanesh95> I still don't receive Community Blog updates on my mail.. :/
17:54:13 <jflory7> dhanesh95: Hmmm, are you supposed to receive email updates? Strange...
17:54:31 <jflory7> dhanesh95: Not sure what the issue is with that.
17:54:42 <dhanesh95> I've registered my mail address a dozen times now
17:54:56 <jflory7> I think this was an issue we've run into on the Magazine as well
17:55:03 <jflory7> I need to dive into it a little bit deeper
17:55:07 <skamath> dhanesh95, try a RSS Reader instead
17:55:13 <jflory7> RSS should do the trick, true
17:55:21 <jflory7> As a temporary workaround
17:55:39 <skamath> https://communityblog.fedoraproject.org/feed/
17:55:44 <jflory7> #help Community Blog should be sending out email notifications to subscribers - related to Magazine problems as well?
17:55:46 <dhanesh95> I'm not much of a RSS guy, but I'll give it a try
17:56:28 <dhanesh95> Community Blog has a Follow by email option but it doesn't work
17:56:40 <dhanesh95> via*
17:57:17 <jflory7> Alrighty, if nothing else, we'll go ahead and wrap up in another moment.
17:57:36 <jflory7> And now I can go hunt out some vitamin C and other powerfruits...
17:57:50 <skamath> +1
17:58:13 <skamath> Thank you jflory7 for chairing :)
17:58:20 <jflory7> Thanks again everyone for coming out today! See you all in channel, on the list, or elsehwere. ;)
17:58:22 <jflory7> #endmeeting