15:58:40 <jflory7> #startmeeting Fedora CommOps (2016-08-23)
15:58:40 <zodbot> Meeting started Tue Aug 23 15:58:40 2016 UTC.  The chair is jflory7. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:58:40 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:58:40 <zodbot> The meeting name has been set to 'fedora_commops_(2016-08-23)'
15:58:44 <jflory7> #meetingname commops
15:58:44 <zodbot> The meeting name has been set to 'commops'
15:58:51 <jflory7> #nick commops
15:58:58 <jflory7> #topic Agenda
15:59:01 <jflory7> #link https://fedoraproject.org/wiki/Meeting:CommOps_2016-08-23
15:59:05 <jflory7> #info (1) Roll Call / Q&A
15:59:09 <jflory7> #info (2) Announcements
15:59:16 <jflory7> #info (3) Action items from last meeting
15:59:20 <jflory7> #info (4) Tickets
15:59:26 <jflory7> #info (5) Wiki Gardening
15:59:30 <jflory7> #info (6) Community Blog
15:59:34 <jflory7> #info (7) Open Floor
15:59:40 <jflory7> #topic Roll Call / Q&A
15:59:44 <jflory7> #info Name; Timezone; Sub-projects/Interest Areas
15:59:46 <skamath> .hello skamath
15:59:47 <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.
15:59:47 <zodbot> skamath: skamath 'Sachin S Kamath ' <sskamath96@gmail.com>
15:59:52 <downey> .hello downey
15:59:53 <zodbot> downey: downey 'Michael Downey' <michael@downey.net>
15:59:54 <JohnMH> .hello johnmh
15:59:56 <zodbot> JohnMH: johnmh 'John M. Harris, Jr.' <johnmh@openblox.org>
16:00:06 <skamath> #info Sachin S. Kamath; UTC +5.30; GSoC, Metrics, CommOps
16:00:10 <jflory7> #info Justin W. Flory; UTC-4; CommOps, Marketing / Magazine, Ambassadors, Diversity Team, Join SIG, and more
16:00:21 <jflory7> Hiya, all! Will leave it to skamath for the next 15 minutes or so :)
16:00:25 <jflory7> #chair skamath downey JohnMH
16:00:25 <zodbot> Current chairs: JohnMH downey jflory7 skamath
16:00:32 * jflory7 is finishing up a class
16:00:42 <skamath> Ack.
16:00:50 <wesleyotugo> Jflory7: how are tasks distributed ?
16:00:54 <downey> #info Michael Downey; UTC -7:00; CommOps, Marketing, also <3 for gsoc, docs, design, *
16:01:40 <skamath> Let's move on to announcements then.
16:01:42 <JohnMH> #info John M. Harris, Jr.; UTC-4; CommOps, Games SIG, Java SIG
16:01:43 <skamath> #topic Announcements
16:01:43 <wesleyotugo> #info Wesley Otugo; GMT +1
16:01:49 <skamath> #info === Fedora 25 Alpha Release: 2016-08-30 ===
16:01:52 <skamath> .chair wesleyotugo
16:01:52 <zodbot> wesleyotugo is seated in a chair with a nice view of a placid lake, unsuspecting that another chair is about to be slammed into them.
16:02:04 <skamath> #link https://fedoraproject.org/wiki/Releases/25/Schedule
16:02:08 <skamath> #info The current targeted date for the Fedora 25 Alpha is for August 30, 2016.
16:02:20 <skamath> It was a no-go last week
16:02:22 <skamath> :(
16:02:28 <skamath> #info === "List of Flock blogs and more" ===
16:02:34 <skamath> #link https://communityblog.fedoraproject.org/list-of-flock-blogs-and-more/
16:02:45 <skamath> #info Brief overview of Flock 2016 with links to individual contributor blog posts and reports about the event. Good way to reflect / review on discussions and focuses from Flock or to see what happened if you were not able to attend.
16:02:53 <downey> #chair wesleyotugo
16:02:53 <zodbot> Current chairs: JohnMH downey jflory7 skamath wesleyotugo
16:03:02 <skamath> #info === "FOSS wave: Bhopal, Madhya Pradesh, India" ===
16:03:07 <skamath> Whoops, thanks downey
16:03:13 <skamath> #link https://communityblog.fedoraproject.org/foss-wave-bhopal-madhya-pradesh-india/
16:03:23 <skamath> #info Ongoing efforts to introduce FOSS, Fedora Quality Assurance, and testing to students across India. Sumantro Mukherjee (sumantrom) is helping lead these efforts. Watch for more information on the Community Blog in coming weeks!
16:03:33 <skamath> #info === REMINDER: Pagure migration, 2016-08-29 ===
16:03:42 <skamath> #info Reminder that the migration from Trac to Pagure is targeted for Monday, August 29th, 2016. We will be abandoning Trac soon. More information to come.
16:03:52 <skamath> ^Something no one will miss moving on from
16:03:57 <downey> :)
16:04:07 <skamath> Anything else to add in here?
16:04:40 <skamath> Announcements, going once..
16:04:45 <skamath> going twice..
16:04:53 <skamath> going thrice..
16:04:58 <skamath> Sold!
16:05:05 <skamath> #topic Action items from last meeting
16:05:13 <skamath> #link https://meetbot.fedoraproject.org/teams/commops/commops.2016-08-16-15.59.html
16:05:20 <skamath> #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:05:33 <skamath> #info === [INCOMPLETE] downey Edit original UnixStickers shirt article to include links / mentions of the women's sizes / editions too ===
16:05:39 * cprofitt waves hello
16:05:41 <skamath> downey, updates?
16:05:45 <downey> skamath: I have a blocker ...
16:05:45 <skamath> cprofitt, o/
16:05:49 <skamath> .chair cprofitt
16:05:49 <zodbot> cprofitt is seated in a chair with a nice view of a placid lake, unsuspecting that another chair is about to be slammed into them.
16:05:50 <downey> skamath: no edit access on the article :)
16:05:57 <skamath> Wut.
16:06:01 <skamath> What's wrong with zod?
16:06:06 <downey> #chair cprofitt
16:06:06 <zodbot> Current chairs: JohnMH cprofitt downey jflory7 skamath wesleyotugo
16:06:13 <skamath> Oh oops
16:06:14 <downey> skamath: try a # instead of a . :-)
16:06:16 <skamath> I was using .
16:06:22 <skamath> hah, yeah.
16:06:23 <skamath> My bad
16:06:27 <skamath> #info === [INCOMPLETE] downey Edit original UnixStickers shirt article to include links / mentions of the women's sizes / editions too ===
16:06:32 <skamath> #undo
16:06:32 <zodbot> Removing item from minutes: INFO by skamath at 16:06:27 : === [INCOMPLETE] downey Edit original UnixStickers shirt article to include links / mentions of the women's sizes / editions too ===
16:06:37 <skamath> #action downey Ping jflory7 for editing article / adding paragraph into article
16:06:44 <skamath> #info === skamath file a ticket on fedmsg repo for the mailman bug ===
16:06:56 * skamath digs for link
16:07:18 <skamath> #link https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/issues/399
16:07:33 <skamath> This one is blocking a couple of onboarding badges
16:07:50 <skamath> And the mailing list badge in general.
16:07:59 <skamath> #info === [INCOMPLETE] jflory7 Work with bee2502 on writing a report / update on the Flock 2016 CommOps workshop ===
16:08:17 <skamath> Not sure if I should re-action this
16:08:31 <skamath> #action jflory7 Work with bee2502 on writing a report / update on the Flock 2016 CommOps workshop
16:08:43 <skamath> #info === [INCOMPLETE] jflory7 bee2502 Take workshop feedback and parse it into more accessible data (e.g. tickets / commits / CommBlog posts / metrics / etc.) ===
16:08:51 <skamath> #action jflory7 bee2502 Take workshop feedback and parse it into more accessible data (e.g. tickets / commits / CommBlog posts / metrics / etc.)
16:09:04 <skamath> bee2502, ping ping
16:09:09 <skamath> #info === [COMPLETE] jflory7 Review emails for pending posts on the CommBlog ===
16:09:21 <skamath> #action jflory7 Review emails for pending posts on the CommBlog
16:09:35 <skamath> #info === [INCOMPLETE] jflory7 File tickets for Python SIG, add feedback for Ambassadors from workshop ===
16:09:53 <skamath> I thought this one was for the Onboarding badge but they already have one
16:10:00 <skamath> I'll just re-action this for now
16:10:06 <skamath> #action jflory7 File tickets for Python SIG, add feedback for Ambassadors from workshop
16:10:29 <skamath> #info === [INCOMPLETE] jflory7 Update Community Blog writing guide for writing a new article based on what's actually happening in 2016 now ===
16:10:38 <skamath> #action jflory7 Update Community Blog writing guide for writing a new article based on what's actually happening in 2016 now
16:10:41 <bee2502> .hello bee2502
16:10:43 <zodbot> bee2502: bee2502 'Bhagyashree Padalkar' <bhagyashree.iitg@gmail.com>
16:10:46 <Guest_84847> allah is doing
16:10:47 <skamath> Hmm, jflory7 has a lot of things to do.
16:10:51 <skamath> And he is super busy
16:10:54 <Guest_84847> sun is not doing allah is doing
16:10:57 <skamath> #chair bee2502
16:10:57 <zodbot> Current chairs: JohnMH bee2502 cprofitt downey jflory7 skamath wesleyotugo
16:11:00 <skamath> bee2502, o/
16:11:02 <Guest_84847> moon is not doing allah is doing
16:11:07 * skamath got it right this time
16:11:09 <Guest_84847> stars are not doing allah is doing
16:11:18 <Guest_84847> planets are not doing allah is doing
16:11:38 <skamath> #info === [INCOMPLETE] jflory7 Sort through ideas on reviewing old contributor discussion, form proposals in the ticket, share at next meeting ===
16:11:42 <Guest_84847> galaxies are not doing allah is doing
16:11:45 <skamath> #action jflory7 Sort through ideas on reviewing old contributor discussion, form proposals in the ticket, share at next meeting
16:11:48 <wesleyotugo> Is anyone seeing Guest_84847:
16:11:49 <Guest_84847> oceans are not doing allah is doing
16:12:01 <skamath> Guest_84847, try #flood instead
16:12:01 <Guest_84847> mountains are not doing allah is doing
16:12:13 <Guest_84847> trees are not doing allah is doing
16:12:15 <skamath> #info === [COMPLETE] jflory7 Remove Ticket #10 from meeting agenda, collaborate with bee2502 on sorting through feedback / ideas from Flock ===
16:12:22 <Guest_84847> mom is not doing allah is doing
16:12:39 <Guest_84847> dad is not doing allah is doing
16:12:45 <Guest_84847> boss is not doing allah is doing
16:12:52 <Guest_84847> job is not doing allah is doing
16:12:54 <skamath> puiterwijk, how do you deal with irc spam?
16:13:01 <Guest_84847> dollar is not doing allah is doing
16:13:05 <JohnMH> The correct way is to ignore him, but uh
16:13:10 <JohnMH> In the middle of a meeting, let's do that
16:13:15 <skamath> thank you nirik :)
16:13:36 <skamath> Okay, that was it.
16:13:50 <skamath> Anyone wants to discuss any ticket?
16:14:01 <skamath> Or we can move on to this weeks' ticket
16:14:46 <wesleyotugo> Yes, move on
16:15:02 <skamath> #topic Tickets
16:15:11 <skamath> #link https://fedorahosted.org/fedora-commops/report/9
16:15:18 <skamath> #info === Ticket #78 ===
16:15:23 <skamath> #info "Automating a check-in to evaluate activity of members"
16:15:29 <skamath> #link https://fedorahosted.org/fedora-commops/ticket/78
16:15:51 <skamath> This was discussed in the last weeks meeing and we had some really good points coming up
16:15:57 * jflory7 is back
16:15:59 * jflory7 scrolls up
16:16:06 <skamath> jflory7, just in time :)
16:16:15 * skamath passes on the mic to jflory7
16:16:53 <jflory7> wesleyotugo: Tasks are distributed by merit - if there's something that interests you or you think you could help contribute to, feel free to add your thoughts or try tackling a ticket. It's never a bad idea to ask for advice or help in #fedora-commops too. :)
16:17:29 <jflory7> Also, wesleyotugo, cprofitt, bee2502 o/
16:17:32 <jflory7> nirik++
16:18:16 <jflory7> re: my action items, I have a lot of remaining actions from last week that I haven't been able to follow up on yet due to moving, but things are starting to settle down a bit, so I should be able to do some catching up this week
16:18:24 <cprofitt> hello jflory7
16:18:45 <skamath> jflory7, no worries. I can help
16:19:03 <wesleyotugo> Thanks for clearing that out jflory7
16:19:12 <jflory7> skamath: Definitely would be interested in trying to make some of these more open tasks instead of blocking on one person (i.e. me). :)
16:19:15 <jflory7> wesleyotugo: No problem!
16:19:21 <jflory7> So, on the topic of this ticket...
16:19:46 <jflory7> We had a *lot* of really good ideas from last week that are noted in last week's logs.
16:19:59 <jflory7> I have not yet had a chance to go through and turn them into proposals for member activity.
16:20:24 <jflory7> For now, I would like to skip over this ticket into some of the raw ideas from last week are in a more "digestable" form where we can discuss and compare proposals.
16:20:39 <jflory7> This is something I can also update on the mailing list before next meeting since it's one of the big things we've been discussing.
16:20:55 <jflory7> If it's alright, I'd like to propose to defer discussion on this one since we did a lot of covering of it last week.
16:22:37 <jflory7> #proposal Due to lots of raw ideas and discussion from last week's meeting, would like to defer further discussion until there are more solid proposals to discuss / agree on
16:22:38 <jflory7> +1
16:22:47 <bt0> +1
16:22:51 <downey> +1
16:23:08 <JohnMH> +1
16:23:36 <jflory7> Going once...
16:23:43 <jflory7> Going twice...
16:23:49 <wesleyotugo> +1
16:23:52 <jflory7> Going thrice...
16:24:00 <jflory7> #agreed Due to lots of raw ideas and discussion from last week's meeting, would like to defer further discussion until there are more solid proposals to discuss / agree on
16:24:04 <jflory7> Also, hi bt0!
16:24:38 * jflory7 notes that he put all the tickets notated for meetings in the wiki, but jflory7 wanted to remove some of them from the agenda before the meeting started
16:24:43 <jflory7> So I might do some skipping around
16:25:01 <jflory7> e.g. the Pagure ticket doesn't have any new updates other than being aware it's happening next week, so going to skip over it for now
16:25:06 <jflory7> Along with the vFAD ticket
16:25:14 <jflory7> #info === Ticket #34 ===
16:25:19 <jflory7> #info "[Onboarding Series] [MASTER TICKET] Creating sub-project on-boarding badge series"
16:25:24 <jflory7> #link https://fedorahosted.org/fedora-commops/ticket/34
16:25:34 <jflory7> downey can probably relate to the moving process being quite rigorous :)
16:25:44 * downey nods with a tear
16:25:45 * jflory7 digs for last week's minutes really fast for reference on this one
16:25:55 <jflory7> Heheh. :)
16:26:17 <jflory7> Oh, right, this one was also blocking on me...
16:26:22 <jflory7> I was going to file a ticket for the Python SIG
16:26:52 <jflory7> Well, since I don't have a ticket and I haven't yet explained some of the ideas behind Flock, I'd like to take a moment to recap on what exactly I'd like to target and focus on for the Python SIG now so we're all on the same page.
16:27:05 <jflory7> mhroncok might be able to spot-check me on some of these details.
16:27:10 * jflory7 goes for his Flock notes really fast
16:28:06 <jflory7> #info Last meeting, we agreed that next target group (outside of final follow-up on tickets awaiting badges) would be the Python SIG due to discussions that happened at the CommOps workshop at Flock 2016
16:28:31 <jflory7> ^ which, by the way, the video for the workshop is uploaded to the Fedora Project YouTube channel! Even though it missed decause's introduction via phone...
16:29:24 <jflory7> #info Background on the Python SIG: Around 20 members, handles reviewing Python packages in Fedora, deals with Python-specific technical decisions in Fedora, also sometimes handles security-critical issues with Python packages in Fedora
16:30:13 <wesleyotugo> 30 minutes mark
16:31:09 <jflory7> #info Noted at Flock that the on-boarding process for new members has difficulties: Unclear process for newcomers to follow, distinguishment between mailing lists (one public, one private for security bugs) unclear, need more items to be able to help guide newcomers to, sometimes there are "human" decisions that need to be made when reviewing new applicants
16:31:29 <jflory7> wesleyotugo: We recently extended the time an extra 30 minutes, so we have an hour left from here. But thanks for the heads-up regardless. :)
16:31:49 <jflory7> #idea Revamping wiki page / establishing numbered steps for newcomers to follow to become involved
16:32:17 <jflory7> #idea Making it clear what info is needed from newcomers for current members of the SIG to understand what newcomers are familiar with, interested in contributing towards, or able to do
16:33:21 <jflory7> #idea Coming up with creative solutions for how something that sometimes requires a subjective, "human" review process to follow general guidelines or points for evaluating newcomers (with context to revealing security bugs or issues)
16:33:29 <jflory7> These were some of the ideas we hashed out at Flock.
16:34:05 <jflory7> So even though there's no ticket yet, I hope this makes it a little bit more transparent about some of my thoughts and takeaways from Flock with regards to the Python SIG. :)
16:34:29 <jflory7> mhroncok: Hope I got it all right. :P Feel free to interject anything if you're around.
16:35:19 <jflory7> Anyways, so now that this is explained, if you have ideas or thoughts on this (or need some time to look around first), feel free to either add your thoughts here now or check out the following links to learn more about the SIG.
16:35:26 <jflory7> #link https://fedoraproject.org/wiki/SIGs/Python
16:35:41 <jflory7> #link https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org/
16:35:45 <wesleyotugo> As a new user within the last five months, those were my very trouble
16:35:53 <jflory7> #link https://admin.fedoraproject.org/pkgdb/packager/group::python-sig/
16:36:05 <jflory7> wesleyotugo: How do you mean? Specific to the Python SIG or more general?
16:36:17 <jflory7> #link https://fedoraproject.org/wiki/SIGs/Python/Members_list
16:36:30 <jflory7> #link http://fedora.portingdb.xyz/
16:37:35 <jflory7> Also, anyone else have any thoughts they want to offer out here now? Otherwise, once wesleyotugo finishes his thoughts, we can move on the next ticket.
16:37:42 <wesleyotugo> Jflory7: Generally
16:38:24 <jflory7> wesleyotugo: So your struggle was with having clear, ordered steps to follow in order to become more involved?
16:38:33 * jflory7 wants to understand your thoughts and perspective on this :)
16:40:15 <wesleyotugo> Jflory7: the wiki is very confusing to me, it was more confusive than directive due to its grammar-tology
16:41:17 <jflory7> wesleyotugo: So the format of the wiki was the confusing part for going through and understanding where to go next. Was there a team that you thought was more confusing than others? What about a team that you thought did it best?
16:41:42 <jflory7> I'd be curious to know which teams had a more clear or transparent process and worked better than others, so we could try to incorporate that into improving the process for all teams.
16:41:52 <wesleyotugo> Jflory7: i think what sorted me out was whatcanidoforfedora.com
16:41:57 * jflory7 nods
16:42:03 <jflory7> I see, that makes sense.
16:42:11 <wesleyotugo> Jflory7: SIGs for DEs
16:42:26 <jflory7> Fortunately, this should all become easier with Fedora Hubs, which takes from the lesson learned from whatcanidoforfedora.org.
16:42:34 <pviktori> I think what's most confusing is that while the Python SIG is open to anyone, the python-sig FAS group is a bit of a secret cabal (which it needs to be since mambers may get info about embargoed security issues)
16:42:51 <jflory7> Yes, sometimes the SIGs can have the most difficult process since there's no standardization for how each SIG can operate.
16:43:34 <jflory7> pviktori: Perhaps something similar to an Apprentice-esque approach (like Infrastructure) could be effective, for people wanting to become involved with Python efforts in Fedora but maybe don't have enough experience or proof to justify access for security bugs?
16:43:44 <pviktori> To join Python SIG, subscribe to python-devel@l.fp.o and be active. To join the FAS group, you need to know someone who can vouch for you
16:44:30 <jflory7> I think the idea of sponsorship is most confusing in this case. The idea of being in a group, officially, gives the idea of being involved or a member. But I know you all have the wiki page which is *supposed* to replicate that.
16:44:42 <jflory7> So maybe improved communication about the wiki page being more accurate than the FAS group...
16:45:05 <jflory7> #idea Improving communication about Python SIG member list being on the wiki over a FAS group (and that's the official source for people involved with the Python SIG)
16:45:23 <jflory7> #idea An apprentice-esque type approach for newcomers to Python SIG???
16:45:38 <jflory7> pviktori: Would you want to be CC'd to the ticket about this discussion as well?
16:45:50 <pviktori> Yeah, I think the Wiki page needs to de-emphasize the FAS group.
16:45:55 <pviktori> jflory7: yes, please
16:45:57 * jflory7 is realizing we're spending a lot of time on this and does want to cover other agenda items
16:46:08 <jflory7> I think this is all a lot of good foundation for productive discussion going forward. :)
16:46:14 <jflory7> pviktori++ Awesome, I will be sure to do so!
16:46:15 <zodbot> jflory7: Karma for pviktori changed to 2 (for the f24 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
16:46:33 <jflory7> Okay, any other closing comments that we want to make about the Python SIG or on-boarding in general?
16:46:54 <pviktori> none here
16:47:06 <jflory7> wesleyotugo: I'd definitely like to get some of your perspective / ideas logged somewhere, I think your experience is unique compared to some other people who have been around longer. :)
16:47:11 <jflory7> Alrighty, going once...
16:47:20 <jflory7> Going twice...
16:47:25 <jflory7> Thrice...
16:47:53 * jflory7 skips FOSS Student Pack because that ticket was to be removed from today's agenda for the same reasons as the reviewing old members discussion
16:47:55 <jflory7> #info === Ticket #82 ===
16:48:00 <jflory7> #info "Move CommOps toolbox to Pagure"
16:48:04 <jflory7> #link https://fedorahosted.org/fedora-commops/ticket/82
16:48:10 <jflory7> skamath: So this one is yours :)
16:48:23 <skamath> jflory7, Thanks. Yes
16:48:35 <jflory7> skamath: Curious, did you have a chance to read my comment yet?
16:48:38 <skamath> I wanted the toolbox unified in one place.
16:48:44 <skamath> jflory7, Yes I did
16:48:47 * jflory7 nods
16:49:13 <jflory7> For the technical resources, it would be nice to have them together in one place. When possible, I'd prefer to centralize the resources and avoid having them in personal accounts where possible.
16:49:17 <skamath> jflory7, do we really need infra intervention for moving the tools?
16:49:41 <skamath> It's anyway on GitHub so it'll be like we are making a "fork" of it on Pagure
16:49:47 <skamath> I didn
16:49:53 <jflory7> I know a lot of decause's tools are in GitHub, so we would want to ping him about migrating them to Pagure and granting access to, say, the CommOps group. Since their his projects and he might be interested in maintaining them beyond just our use, I'd like to get his opinion on it.
16:50:09 <skamath> nod nod
16:50:22 <skamath> jflory7, and what about the ones under fedora-infra?
16:50:25 <downey> jflory7: or perhaps fork them if he wants to continue them more generically?
16:50:39 <skamath> downey, they are on GitHub
16:50:44 <skamath> and we have to move it to pagure
16:50:53 <jflory7> skamath: For the Infrastructure-specific repositories, I would definitely want to insist on working upstream on these projects where possible. If we are making changes and modifying the tools to fit our own needs, we would want to make sure that the changes we're making can be used and benefit other users of the repository too. Since Infra is using GitHub to maintain these resources, to me, it would make the most sense to keep activity there.
16:51:11 <jflory7> Whenever possible, it's best to keep working in the upstream, especially with regards to our own projects inside of Fedora. :)
16:51:16 <skamath> Gotcha.
16:51:27 <jflory7> However, it could be a good idea to propose an official migration of Fedora Infrastructure GitHub to Pagure
16:51:34 <jflory7> And have the GitHub organization become "legacy"
16:51:35 <skamath> jflory7, or we could mirror the repos
16:51:37 <downey> skamath: hopefully it's just a matter of moving the code :)
16:52:00 <jflory7> Ah, we could mirror them, but that would require a person actively updating both the original and mirrored repository actively.
16:52:04 <jflory7> Or it could be automated, actually...
16:52:11 <skamath> Yep, hooks.
16:52:23 <jflory7> In either case, for this topic, I'd like to make a ticket in the Fedora Infra Trac about possibly a large-scale migration from GitHub to Pagure.
16:52:35 <jflory7> I think this was once discussed, but Pagure was too meta at the time for it to be realistic
16:52:35 <skamath> jflory7++ Sounds good to me
16:52:39 <jflory7> Pagure has come a long way since
16:52:53 <jflory7> So I think now, this proposal comes at a time that makes more sense.
16:52:59 <jflory7> skamath: Is that a ticket you think you might want to file?
16:53:10 <skamath> jflory7, Sure.
16:53:22 <jflory7> skamath: Okay, awesome. Be sure to CC me on that too. :)
16:53:33 <skamath> thumbs up
16:54:00 <jflory7> #action skamath File a ticket in Fedora Infra Trac for proposing an official migration from fedora-infra GitHub organization into Pagure since it has stabilized since the last time this was discussed (to jflory7's knowledge, anyways ;) )
16:54:06 <jflory7> skamath++
16:54:07 <jflory7> Awesome
16:54:19 <jflory7> I think for now, the two main actions are following up with Infra and then pinging decause.
16:54:24 <jflory7> I could reach out to decause about this one.
16:54:30 <skamath> jflory7, Awesome
16:54:39 <skamath> Sounds like a plan
16:54:46 <jflory7> #action jflory7 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:54:51 * jflory7 nods
16:55:01 <jflory7> For now, I think this should suffice on this ticket...
16:55:15 <jflory7> Anyone else have any ideas about our toolbox they would like to throw out? Or in general, other ways it could be improved?
16:55:31 <jflory7> It definitely needs some updating, e.g. the Fedora Magazine images repo shouldn't really go there.
16:55:41 * jflory7 can't remember if he added that, but if he did, he was maybe a little biased
16:56:10 <jflory7> Anyways... anything else to add here?
16:56:25 <jflory7> Going once...
16:56:35 <jflory7> Going twice...
16:56:40 <jflory7> Going thrice...
16:56:43 <skamath> Nothing from me
16:56:45 <jflory7> #topic Wiki Gardening
16:56:52 <jflory7> #action commops New members, make sure you add your timezone / interests on CommOps wiki [ https://fedoraproject.org/wiki/CommOps ]
16:57:10 <jflory7> Hmmm, this action item could be worth updating for current times because of the wiki changes.
16:57:19 <jflory7> Which reminds me of bexelbie's comment he wanted for us to discuss here
16:57:33 <jflory7> So even though we closed and discussed Ticket #80, our role on communication may have been dropped a bit
16:57:48 <jflory7> I wanted to originally follow up on the Infrastructure list, but totally lost track of it this week.
16:58:04 <jflory7> nirik: Ping... happen to be around and have 10 minutes to spare?
16:59:11 <nirik> Im around, but in several things... if you don't mind me being slow to answer I can try
16:59:31 <jflory7> nirik: Would email be better? Isn't something that has to be covered now.
16:59:40 <nirik> whats the question?
16:59:42 * nirik reads up
16:59:43 * jflory7 wanted to reply on the Infra list but was curious if IRC might be easier
17:00:01 <jflory7> nirik: It was about the wikieditor FAS group. We had some discussion on the same topic about a week before the group was created. https://fedorahosted.org/fedora-commops/ticket/80
17:00:08 <nirik> oh right.
17:00:15 <nirik> so, I don't think we disagree here...
17:00:31 <nirik> in general we should try and have groups not depend on wiki editing for onboarding
17:00:50 <nirik> but there's going to be some small group that needs editing acess but doesn't fit into any larger group...
17:01:11 <nirik> so I made a wikiedit group for those corner case people, we shouldn't use it as a 'add everyone to this so they can edit and then go on to a group'
17:01:14 <jflory7> Ahhh, okay... so maybe the wikieditor group is more for edge cases and for situations where it's a more plausible solution to have a user added to a FAS group
17:01:18 * jflory7 nods
17:01:39 <jflory7> Okay, that clarifies a lot then.
17:01:42 <nirik> yeah, so the first person I added was a remixer... he has no interest in joining some other group, but wants to keep the remix page in order
17:02:12 * nirik still needs to try and talk to ambassadors, they have a hard requirement of wiki editing before adding people
17:03:20 <jflory7> #info wikieditor FAS group: Group created not as a default "join to get access" kind of context, but more for edge cases where it's more plausible to add them to a standalone FAS group versus onboarding in a group (also might not have a FAS group). Example used was remixer who maintains a wiki page but nothing else.
17:03:23 <jflory7> nirik++
17:03:34 <jflory7> nirik: I think that's a discussion the Ambassadors are actively having now.
17:03:47 <jflory7> I can help keep you in on the loop for that one. But for now, I'm not sure if they've decided either.
17:04:01 <nirik> cool. thanks.
17:04:05 <jflory7> There's some major discussions going on about restructuring mentoring as a whole, so some changes might fit into the wiki editing requirement.
17:04:17 <jflory7> Yup, thanks for the quick update, nirik!
17:04:50 <jflory7> Anything else we want to cover here for wiki gardening?
17:04:55 <jflory7> General or otherwise?
17:05:00 <jflory7> Going once...
17:05:07 <nirik> if you like I can add you as a sponsor on wikiedit...
17:05:10 <jflory7> Going twice...
17:05:17 <jflory7> nirik: That might be useful for now, if you don't mind.
17:05:17 <nirik> otherwise nope. ;)
17:05:25 <jflory7> Going thrice...
17:05:40 <jflory7> #topic Community Blog
17:05:48 <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:05:53 <jflory7> #info === This Week in CommBlog ===
17:05:58 <jflory7> #info (1) "FOSS wave: Bhopal, Madhya Pradesh, India"
17:06:04 <jflory7> #link https://communityblog.fedoraproject.org/foss-wave-bhopal-madhya-pradesh-india/
17:06:10 <jflory7> #info Total Views (Aug. 18 - Aug. 22): 18
17:06:16 <jflory7> #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=2096
17:06:22 <jflory7> #action jflory7 Do a social media blast promoting the FOSS Wave article for Bhopal
17:06:27 <jflory7> #info (2) "List of Flock blogs and more"
17:06:31 <jflory7> #link https://communityblog.fedoraproject.org/list-of-flock-blogs-and-more/
17:06:36 <jflory7> #info Total Views (Aug. 18 - Aug. 22): 54
17:06:41 <jflory7> #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=2185
17:06:52 <jflory7> #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=2185
17:06:53 <jflory7> #undo
17:06:53 <zodbot> Removing item from minutes: <MeetBot.items.Link object at 0x25e0aa10>
17:06:56 <jflory7> #info === Coming Up in CommBlog ===
17:07:03 <jflory7> #info (1) "FOSS Wave: Delhi, India" - scheduled 2016-08-23
17:07:09 <jflory7> #link https://communityblog.fedoraproject.org/?p=2145&preview=1&_ppp=143a11a08f
17:07:15 <jflory7> #info (2) "Fedora 24 Release Party in Singapore" - scheduled 2016-08-24
17:07:21 <jflory7> #link https://communityblog.fedoraproject.org/?p=2010&preview=1&_ppp=1df831e1a4
17:07:33 <jflory7> #info (3) "Modularity Infrastructure Design" - scheduled 2016-08-25
17:07:39 <jflory7> #link https://communityblog.fedoraproject.org/?p=2154&preview=1&_ppp=7146c2ee3c
17:07:45 <jflory7> #info (4) "Say No to Wiki SPAM!"
17:07:50 <jflory7> #link https://communityblog.fedoraproject.org/?p=2208&preview=1&_ppp=1cf79eb584
17:08:01 <jflory7> #action jflory7 Revisit wiki spam article with context of current situation with FAS groups
17:08:07 <jflory7> #info (5) "Globalization improvements in Fedora 24"
17:08:13 <jflory7> #link https://communityblog.fedoraproject.org/?p=2212&preview=1&_ppp=005a502ebc
17:08:20 <jflory7> #info (6) "Modularity and Containers"
17:08:25 <jflory7> #link https://communityblog.fedoraproject.org/?p=2235&preview=1&_ppp=4da4ccff52
17:08:30 <jflory7> #info (7) "What are Personas and Why Should you Care?"
17:08:35 <jflory7> #link https://communityblog.fedoraproject.org/?p=2230&preview=1&_ppp=33758937f3
17:08:41 <jflory7> #info (8) "Heroes of Fedora (HoF) - F24 Alpha"
17:08:46 <jflory7> #link https://communityblog.fedoraproject.org/?p=2091&preview=1&_ppp=98aec2b146
17:08:56 <jflory7> #info (9) "Heroes of Fedora (HoF) - F24 Beta"
17:09:01 <jflory7> #link https://communityblog.fedoraproject.org/?p=2142&preview=1&_ppp=405ee85506
17:09:06 <jflory7> #info (10) "Heroes of Fedora (HoF) - F24 Final"
17:09:10 <jflory7> #link https://communityblog.fedoraproject.org/?p=2204&preview=1&_ppp=0c855ab7c8
17:09:13 <jflory7> Phew!
17:09:17 <jflory7> These articles keep coming. :)
17:09:42 <jflory7> Special shout-outs for this week's articles go to: sumantrom++ nardasev++ cpacheco++
17:09:58 <jflory7> Any other Community Blog business we want to cover here?
17:10:11 <jflory7> Outside of some of the previous actions for updating old content, like the how-to-write page
17:11:12 <a2batic> jflory7, I wrote one on women activity !!
17:17:25 <jflory7> a2batic: Oh, yeah! It must be in the drafts?
17:17:31 <jflory7> a2batic: you posted to the list about it, right?
17:18:01 <jflory7> a2batic: If you posted to the list, I will definitely be sure to edit it and get it out on a timely order. The way I'm processing the queue right now is in the order they were posted to the mailing list asking for review since there's so many right now.
17:18:39 <a2batic> jflory7, ya, i posted in mailing list , yeah, thanks :)
17:19:13 <jflory7> a2batic++ Perfect.
17:19:16 <jflory7> I will get it then!
17:19:23 <jflory7> Okay, I AFK'd for a second, so going to move to open floor.
17:19:29 <jflory7> #topic Open Floor
17:19:37 <jflory7> Anything anyone else wants to cover or go over here?
17:21:58 <wesleyotugo> 2weeks ago, the fedora commops meeting was not held... any reason to that
17:22:06 <JohnMH> Flock
17:22:13 <jflory7> wesleyotugo: That was the week of Flock. We had agreed the previous week to skip the meeting that week.
17:22:23 <JohnMH> We skipped many meetings that week.
17:22:27 <jflory7> wesleyotugo: See here: https://flocktofedora.org/
17:22:58 <jflory7> You can also read my report with details on the CommOps workshop here. https://blog.justinwflory.com/2016/08/fedora-flock-2016/
17:23:11 * jflory7 is getting hungry for lunch... :)
17:23:25 <jflory7> Last call for anything else before we close?
17:23:30 <jflory7> Going once...
17:23:33 <wesleyotugo> Thanks jflory7
17:23:40 <jflory7> Going twice...
17:23:45 <jflory7> wesleyotugo: Of course, no problem! :)
17:23:50 <jflory7> Going thrice...
17:23:59 <jflory7> Okay, thanks everyone! See you in channel or next week. :)
17:24:01 <jflory7> #endmeeting