15:58:17 <skamath> #startmeeting Fedora CommOps (2016-08-30)
15:58:17 <zodbot> Meeting started Tue Aug 30 15:58:17 2016 UTC.  The chair is skamath. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:58:17 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:58:17 <zodbot> The meeting name has been set to 'fedora_commops_(2016-08-30)'
15:58:22 <skamath> #meetingname commops
15:58:26 <skamath> #meetingname commops
15:58:26 <zodbot> The meeting name has been set to 'commops'
15:58:33 <skamath> #nick commops
15:58:41 <skamath> #topic Agenda
15:58:53 <skamath> #link https://fedoraproject.org/wiki/Meeting:CommOps_2016-08-30
15:58:58 <skamath> #info (1) Roll Call / Q&A
15:59:02 <skamath> #info (2) Announcements
15:59:14 <skamath> #info (2) Announcements
15:59:19 <skamath> #info (3) Action items from last meeting
15:59:23 <skamath> #info (4) Tickets
15:59:27 <skamath> #info (5) Wiki Gardening
15:59:31 <skamath> #info (6) Community Blog
15:59:37 <skamath> #info (7) Release Schedule
15:59:41 <skamath> #info (8) Open Floor
15:59:47 <skamath> #topic Roll Call / Q&A
15:59:53 <downey> .hello downey
15:59:54 <zodbot> downey: downey 'Michael Downey' <michael@downey.net>
15:59:56 <downey> #info Michael Downey; UTC -7:00; CommOps, Marketing, also <3 for gsoc, docs, design, *
15:59:56 <skamath> #info Name; Timezone; Sub-projects/Interest Areas
16:00:02 <skamath> 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:00:11 <skamath> downey, o/
16:00:31 <skamath> #info Sachin S. Kamath; UTC +5.30; CommOps, Metrics, GSoC, *
16:00:51 <skamath> We'll wait for a few more folks to join in :)
16:01:12 <skamath> I dont have CommBlog access so I guess jflory7 will have to appear to do it
16:02:37 <devyani7> .hello devyani7
16:02:38 <zodbot> devyani7: devyani7 'Devyani Kota' <devyanikota@gmail.com>
16:02:44 <skamath> #chair downey
16:02:44 <zodbot> Current chairs: downey skamath
16:02:49 <skamath> #chair devyani7
16:02:49 <zodbot> Current chairs: devyani7 downey skamath
16:02:51 <devyani7> skamath, o/
16:02:52 <skamath> devyani7, o/
16:02:57 <devyani7> :)
16:03:10 <skamath> downey, got chair right this time ;)
16:03:17 <downey> progress :)
16:03:26 <skamath> Okay, let's move on to announcements then
16:03:36 <skamath> #topic Announcements
16:03:43 <skamath> #info === Fedora 25 Alpha releases today ===
16:03:50 <skamath> #link https://lists.fedoraproject.org/archives/list/marketing@lists.fedoraproject.org/thread/HMXOXFP2IPRBTD3O72AE67G6XH3LHXFX/
16:03:56 <skamath> #link https://fedoraproject.org/wiki/F25_Alpha_release_announcement
16:04:02 <skamath> #info Fedora 25 Alpha releases today. The alpha release announcement is in final drafting.
16:04:13 <skamath> #info === "The final results of Google Summer of Code '16 has been announced" ===
16:04:21 <skamath> #link http://summerofcode.withgoogle.com/how-it-works/
16:04:53 <skamath> #info The final results of GSoC was announced today. This marks the end of this years' GSoC
16:05:20 <dhanesh95_> #info Dhanesh B. Sabane, UTC+5:30, CommOps, ML, Packaging, Linux Kernel
16:05:24 <skamath> That's all I've got. Anything to add in here?
16:05:29 <skamath> #chair dhanesh95
16:05:29 <zodbot> Current chairs: devyani7 dhanesh95 downey skamath
16:05:35 <skamath> dhanesh95_, o/
16:05:38 <downey> Congrats to all GSoC students & mentors!
16:05:59 <dhanesh95_> skamath: o/
16:06:07 <skamath> dhanesh95_, o/
16:06:09 <dhanesh95_> skamath is chairing today!? Cool!
16:06:27 <skamath> dhanesh95_, jflory7 is super busy with his work I guess
16:06:33 <skamath> dhanesh95, ^
16:06:44 <skamath> Announcements, going once..
16:06:49 <skamath> going twice..
16:06:59 <skamath> going thrice..
16:07:01 <dhanesh95> Sold!
16:07:05 <skamath> #topic Action items from last meeting
16:07:11 <skamath> #link https://meetbot.fedoraproject.org/fedora-meeting/2016-08-23/commops.2016-08-23-15.58.html
16:07:17 <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:07:23 <skamath> #info === downey Ping jflory7 for editing article / adding paragraph into article ===
16:07:37 <skamath> downey, any updates here?
16:07:49 <downey> skamath: I have a new article pending review on magazine, and contains the edits for the old article.
16:07:58 <downey> skamath: ready to go from my end
16:08:12 <skamath> #info downey  a new article pending review on magazine, and contains the edits for the old article and is all set to go
16:08:15 <skamath> downey++
16:08:24 <skamath> #info === jflory7 Work with bee2502 on writing a report / update on the Flock 2016 CommOps workshop ===
16:08:32 <skamath> bee2502, jflory7 any updates?
16:09:09 <dhanesh95> downey++
16:09:09 <zodbot> dhanesh95: Karma for downey changed to 7 (for the f24 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
16:09:14 <skamath> Okay, I'll just re-action this for now.
16:09:24 <skamath> #action jflory7 Work with bee2502 on writing a report / update on the Flock 2016 CommOps workshop
16:09:31 <skamath> #info === jflory7 bee2502 Take workshop feedback and parse it into more accessible data (e.g. tickets / commits / CommBlog posts / metrics / etc.) ===
16:09:44 <skamath> #action jflory7 bee2502 Take workshop feedback and parse it into more accessible data (e.g. tickets / commits / CommBlog posts / metrics / etc.)
16:09:54 <skamath> #info === jflory7 Review emails for pending posts on the CommBlog ===
16:10:06 <wesleydekstar_> #info Wesley Otugo; UTC +1
16:10:18 <skamath> wesleydekstar_, o/
16:10:23 <skamath> #chair wesleydekstar_
16:10:23 <zodbot> Current chairs: devyani7 dhanesh95 downey skamath wesleydekstar_
16:10:47 <skamath> Hmm, jflory7 has a lot of action items on his list. I did see a few follow-ups on articles
16:11:03 <skamath> re-actioning
16:11:11 <skamath> #action jflory7 Review emails for pending posts on the CommBlog
16:11:22 <skamath> #info === jflory7 Update Community Blog writing guide for writing a new article based on what's actually happening in 2016 now ===
16:11:37 <skamath> #action jflory7 Update Community Blog writing guide for writing a new article based on what's actually happening in 2016 now
16:11:47 <dhanesh95> Too many action items for jflory7
16:11:47 <skamath> #info === jflory7 Sort through ideas on reviewing old contributor discussion, form proposals in the ticket, share at next meeting ===
16:12:27 <skamath> He's really busy. I'll catch up with him later and work on re-actioning these to other commops members :)
16:12:38 <skamath> #action jflory7 Sort through ideas on reviewing old contributor discussion, form proposals in the ticket, share at next meeting
16:12:45 <skamath> We did move to Pagure though! :)
16:13:09 <skamath> #link https://pagure.io/fedora-commops/
16:13:16 <downey> +1 to helping jflory7 and +1 to pagure :-)
16:13:20 <skamath> #info === [INCOMPLETE] skamath File a ticket in Fedora Infra Trac for proposing an official migration from fedora-infra GitHub organization into Pagure ===
16:13:29 <skamath> #action skamath File a ticket in Fedora Infra Trac for proposing an official migration from fedora-infra GitHub organization into Pagure
16:13:41 <skamath> I'll be tackling this ticket soon.
16:13:49 <skamath> Just need to figure out what should go in
16:14:02 <skamath> #info === 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:14:17 <skamath> I can take this up
16:14:25 <decause_> .hello decause
16:14:26 <zodbot> decause_: decause 'Remy DeCausemaker' <remy@decausemaker.org>
16:14:26 <skamath> #action 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:14:40 <skamath> decause, o/
16:14:44 <skamath> #chair decause
16:14:44 <zodbot> Current chairs: decause devyani7 dhanesh95 downey skamath wesleydekstar_
16:14:59 <decause> +1 for migrating to pagure
16:15:03 <skamath> decause, What a surprise :D
16:15:04 <decause> lemme know what you need me to do
16:15:12 <dhanesh95> decause: o/
16:15:15 <downey> decause: o/
16:15:23 <skamath> decause, we were planning to move the CommOps tools to Pagure
16:15:25 * decause waves to the commops peeps
16:15:36 <devyani7> decause, o/
16:15:38 <decause> yes, I'm enthusiastically +1
16:15:43 <skamath> decause, need your +1 for moving tools in your repo
16:15:44 <skamath> Awesome
16:15:48 <skamath> decause++
16:15:52 <dhanesh95> decause++
16:16:18 <dhanesh95> skamath: CC me for this ticket..
16:16:27 <decause> we can just fork them to pagure, yeah?
16:16:34 <skamath> decause, Yep.
16:16:46 <decause> yes, +1, do that, don't block on me ;)
16:16:47 <dhanesh95> Should be easy
16:17:01 <jflory7> .hello jflory7
16:17:02 <zodbot> jflory7: jflory7 'Justin W. Flory' <jflory7@gmail.com>
16:17:03 <jflory7> Thought I could swing the time and the agenda but it didn't happen - sorry I'm late...
16:17:04 <skamath> decause, will do it right away!
16:17:05 <jflory7> A lot of these action items I didn't mark up as complete.
16:17:05 <downey> skamath: although the old repo should instruct people where the new canonical home is located :)
16:17:07 <jflory7> decause: Ideally, if you're alright with it, we can port them over
16:17:17 <decause> port them from github to pagure?
16:17:26 <dhanesh95> jflory7: o/
16:17:28 <skamath> decause, that's the plan, yes
16:17:29 <decause> there isn't a way to do that is there?
16:17:38 <decause> like, the issues/prs, can't be forked, can they?
16:17:54 <jflory7> decause: There is actually a handy Pagure importer, now that I think of it...
16:17:58 <jflory7> It supports GitHub
16:17:59 <skamath> decause, as far as I know, there is a import tool available
16:18:02 <jflory7> I could give that a look.
16:18:03 <decause> nice!
16:18:03 <skamath> ^
16:18:12 <decause> you just tell me what I need to do
16:18:16 <skamath> #chair jflory7
16:18:16 <zodbot> Current chairs: decause devyani7 dhanesh95 downey jflory7 skamath wesleydekstar_
16:18:22 * skamath hands over the mic to jflory7
16:18:44 <jflory7> skamath++ Thanks for covering for me - will try to communicate better in the future. ;)
16:18:56 <jflory7> decause: If you're wrapped up, I can check out the importer as long as you're alright with them living on Pagure.
16:19:03 <skamath> jflory7, No worries. I know you are super-busy :)
16:19:09 <jflory7> decause: My main concern was getting your consent and keeping a single upstream.
16:21:09 * jflory7 is digging for last meeting's minutes too
16:21:13 <jflory7> So disorganized today
16:21:13 <skamath> jflory7, For the smaller tools like wordcloud, we can have the Pagure one we will be creating soon as the upstream
16:21:25 <skamath> jflory7, https://fedoraproject.org/wiki/Meeting:CommOps_2016-08-23
16:21:29 <jflory7> skamath++
16:21:38 * jflory7 nods
16:22:18 <jflory7> #action jflory7 Follow up on Pagure importer tool for use with decause's CommOps toolbox repositories
16:22:22 <amitsin6h> what a grate day to join CommOps
16:22:37 <jflory7> amitsin6h: Hello, welcome!
16:22:40 <amitsin6h> Hello guys am Amit from RAnchi jharkhand
16:22:52 <amitsin6h> I want to start contributing to Fedora
16:22:55 <skamath> amitsin6h, hello and welcome :)
16:23:26 <amitsin6h> I have skills in python and have been also contributing to mozilla
16:23:28 <jflory7> #info === [COMPLETE] jflory7 Do a social media blast promoting the FOSS Wave article for Bhopal ===
16:23:45 <jflory7> #info === [COMPLETE] jflory7 Revisit wiki spam article with context of current situation with FAS groups ===
16:24:04 * pravins glad to see decause around :)
16:24:04 <jflory7> #info Article scheduled for Thursday; modified for accuracy with current wikieditor situation
16:24:08 <jflory7> bexelbie++
16:24:10 <amitsin6h> How can get CLA+1
16:24:25 <skamath> amitsin6h, you can introduce during the Open Floor
16:24:31 <skamath> amitsin6h, hold on a bit :)
16:24:37 <decause> pravins: I do my best to stay available in IRC :)
16:24:38 <dhanesh95> amitsin6h: Welcome!
16:24:46 <jflory7> amitsin6h: Awesome! We're in the middle of a meeting right now, so you're more than welcome to follow along. If you're just joining us, please take a look at our wiki page for more info on joining the team. https://fedoraproject.org/wiki/CommOps/Join
16:25:00 <jflory7> skamath: That was all the action items, right?
16:25:14 <jflory7> Anything that lingered, I'll make sure to prep ahead of time on the agenda for next week :P
16:25:15 <skamath> jflory7, Yep
16:25:19 <jflory7> Okay, great!
16:25:25 <skamath> jflory7, this
16:25:34 <skamath> #info === jflory7 Revisit wiki spam article with context of current situation with FAS groups ===
16:25:43 <jflory7> Yup, got that one :)
16:25:53 <skamath> jflory7, I did fill the agenda for this week a bit
16:25:55 <jflory7> #undo
16:25:55 <zodbot> Removing item from minutes: INFO by skamath at 16:25:34 : === jflory7 Revisit wiki spam article with context of current situation with FAS groups ===
16:26:00 <jflory7> Oh, excellent, will refresh!
16:26:05 <skamath> Oops. sorry.
16:26:14 <jflory7> All good!
16:26:21 <jflory7> Okay, so now for something a little different...
16:26:23 <jflory7> #topic Tickets
16:26:25 <dhanesh95> Haha.. :D
16:26:36 <skamath> *drum rolls*
16:26:36 <jflory7> Give me a minute while I get the new links...
16:26:44 <skamath> jflory7, check agenda
16:26:49 <skamath> Got 'em all there.
16:26:53 <jflory7> #link https://pagure.io/fedora-commops/issues?tags=meeting
16:26:56 <jflory7> skamath++ perfect.
16:27:23 <jflory7> I'm going to start with the obvious one, might do some jumping around in the order.
16:27:26 <jflory7> #info === Ticket #81 ===
16:27:28 <dhanesh95> skamath++
16:27:30 <jflory7> #info "Migrating to Pagure"
16:27:34 <jflory7> #link https://pagure.io/fedora-commops/issue/81
16:27:44 <jflory7> So, we are officially migrated from Trac to Pagure!
16:28:01 <jflory7> We will no longer be using Trac as an active part of our workflow - instead, we will be migrating to Pagure for tickets and tasks.
16:28:26 <skamath> pagure++
16:28:47 <jflory7> #info Successfully migrated to Pagure last night as scheduled; Trac will no longer be an active part of our workflow. Trac will be kept up for another month before a Fedora Infra ticket will be filed requesting it to be dropped off.
16:28:59 <jflory7> #action jflory7 Remove Ticket #81 from meeting agenda
16:29:26 <skamath> jflory7, should I mark it as fixed and remove tag now?
16:29:28 <dhanesh95> pagure++
16:29:35 <jflory7> No worries, just got it. :)
16:29:48 <skamath> Cool.
16:30:21 <jflory7> #info === Ticket #82 ===
16:30:26 <jflory7> #info "Move CommOps toolbox to Pagure"
16:30:31 <jflory7> #link https://pagure.io/fedora-commops/issue/82
16:30:51 <jflory7> So I think playing around with the Pagure importer tool will be good homework on this one for now. I also did some reorganizing on the wiki page of our tools.
16:31:01 <jflory7> #link https://pagure.io/pagure-importer
16:31:11 <jflory7> #link https://fedoraproject.org/wiki/CommOps#Toolbox
16:31:14 <decause> \o/ that's huge everyone! Trac has been the primary flow for *years*
16:31:28 <skamath> decause, Indeed :)
16:31:44 <jflory7> decause: Super excited about making the move!! Pagure is proving pretty effective too from my experience so far. :)
16:32:24 <jflory7> I think really once the last repos are ported to Pagure, this ticket should be all set.
16:33:34 <jflory7> I don't have a whole lot else to add to this one.
16:33:54 * jflory7 apologizes for being so disorganized this morning - feels like he is jumping around a lot
16:34:25 <jflory7> If nothing else here, I think we should move to the Python SIG ticket, which should be a little more discussion-oriented...
16:34:35 <skamath> jflory7, no worries.
16:35:04 <jflory7> #agreed Will work on migrating GitHub repos to Pagure to increase accessibility and visibility of useful metrics or data visualization tools for other community members
16:35:26 <jflory7> #info === Ticket #84 ===
16:35:32 <jflory7> #info "Python SIG Onboarding"
16:35:37 <jflory7> #link https://pagure.io/fedora-commops/issue/84
16:35:43 <jflory7> This issue is a stub for working out ideas, concepts, and other steps involved for contributors who would like to officially join the Python SIG.
16:36:15 <jflory7> A lot of the notes mentioned here were transcribed from last week's meeting, but I think we can try to form some action items out of this.
16:36:42 * jflory7 reads over ticket for a minute to brainstorm
16:37:02 <skamath> python-sig already has an Onboarding badge.
16:37:10 * jflory7 nods
16:37:22 <skamath> #link https://badges.fedoraproject.org/badge/python-sig-member
16:37:34 <jflory7> They do have the badge, but this issue looks more into how their onboarding process is communicated.
16:37:44 <dhanesh95> My first suggestion for this would be re-organizing the wiki..
16:37:51 <jflory7> I think it's a lot of wording, and maybe even psychology at play. ;)
16:38:00 <jflory7> dhanesh95: I think some wiki gardening is definitely high priority
16:38:12 <jflory7> I mention psychology for this reason:
16:38:54 <jflory7> When people participate something, they want to have some kind of acknowledgment or token to recognize their involvement. In this case, I think the FAS group is that thing. Getting sponsored in the FAS group is the acknowledgment / token. And that
16:39:03 <jflory7> * And that's how it works in a lot of the project already too.
16:39:30 <skamath> iirc, there are more python badges
16:39:58 <jflory7> So I think possibly making the current SIG group tied to a different name *could* be a solution and making it more open to sponsorship is one possible solution of a series
16:40:15 <jflory7> Along with more clear communication on the wiki page.
16:40:20 <jflory7> skamath: Actually, you know, you're right...
16:40:24 <jflory7> The Python 3 porting badges...
16:40:27 <dhanesh95> jflory7: I don't understand tying to a different name
16:40:51 <jflory7> Those could be good "starter" goals for incoming members to work on as part of the SIG. Try porting packages to Python 3 from 2.
16:41:13 <dhanesh95> I was gonna say ^ :P
16:41:35 <jflory7> dhanesh95: I think the name is misleading. The FAS group is python-sig, but that group can receive private, 0day security issues. So who has access is a very important question - it needs to be vetted, trustworthy members of the community for that reason.
16:41:47 <jflory7> But it can make someone who sees "python-sig" group apply and then wonder why they are rejected
16:41:58 <skamath> #link https://badges.fedoraproject.org/tags/python/any
16:42:09 <skamath> Parselmouth it is
16:42:28 <jflory7> So perhaps a different name could be one small solution to that problem, with either the addition of a second or just not at all. Or just clearly communicating that in the FAS group.
16:42:33 <jflory7> skamath++
16:42:40 <jflory7> Let me log some of these ideas
16:42:58 <jflory7> #idea Using the Parselmouth badge series as beginning steps for participation in Python SIG (porting packages from Python 2 to 3)
16:43:04 <skamath> jflory7, security things should go to #fedora-security-team right?
16:43:23 <jflory7> #idea Changing the name of the FAS group or more clearly communicating the security clearance required for sponsorship into the FAS group
16:43:48 <jflory7> skamath: Not necessarily - the Python SIG handles ones specific to Python, as far as I know. It would be helpful for clarification about what kind of data they have access to.
16:43:59 * skamath nods
16:44:01 <jflory7> #idea Wiki gardening to organize info about the SIG and how to participate
16:44:33 <jflory7> I actually think the Parselmouth series is a really good way to "vet" people getting involved with the SIG
16:44:54 <jflory7> That's one of the toughest things here is that this SIG has a very manual process for reviewing new applicants
16:45:00 <jflory7> It's a decision completely based on context
16:45:15 <jflory7> But using something like Parselmouth / porting Python 2 packages is a good way to show merit and ability
16:45:24 <skamath> jflory7, and membership is dependent on the number of packages ported?
16:46:13 <jflory7> skamath: It depends on the type of packages is what I remember churchyard telling me at Flock. The example being on one hand, someone maintaining / porting ten tiny Python libraries or small programs, while on the other hand, someone who is maintaining and porting Python Flask.
16:46:29 <skamath> nod nod
16:46:40 <jflory7> Flask just being an example of something I presume is large and notable Python package... but you get the idea.
16:46:41 <dhanesh95> How do we recognize that?
16:46:52 <skamath> jflory7, Yep. Got it, thanks.
16:47:36 <jflory7> dhanesh95: That's the tricky part, it's not really something you can automate or easily check off on a list. So I think an onboarding guide for this SIG should be more of a guide to participating, not strictly definite steps to become a member.
16:47:52 <jflory7> And it's also worth noting too that people can declare their interest / join the SIG just by writing their name on a wiki page.
16:48:48 <jflory7> So turning this ticket into a series of actions...
16:49:04 <jflory7> Step #1) Help reorganize / classify wiki page into more easily readable format
16:49:32 <dhanesh95> jflory7: So considering a newcomer, he'll be guided to participate.. So will he be promoted to "member" manually?
16:49:42 <jflory7> Step #2) Create guides / steps for becoming a member (e.g. Join page) using things like Parselmouth badge as goals (maybe other development badges too?)
16:50:00 <jflory7> dhanesh95: Correct. At least for FAS group sponsorship.
16:50:20 <dhanesh95> jflory7: Cool
16:50:25 <jflory7> Step #3) Look at FAS group and make sure info is clearly written in group description and look into whether a name change is a valid solution
16:50:40 <jflory7> Do these three steps seem fair?
16:50:43 <skamath> The re-write of wiki is going to be hectic.
16:50:43 <skamath> =1
16:50:46 <skamath> * +1
16:50:57 <jflory7> +1 from me, but I proposed it :P
16:51:09 <downey> +1
16:51:11 <dhanesh95> About the name change, can't we have two separate groups?
16:51:14 <jflory7> skamath: It will be a little hectic, but I think it will be doable.
16:51:20 <jflory7> dhanesh95: That could be a solution too.
16:51:29 <skamath> dhanesh95, like the apprentice group?
16:51:33 <jflory7> e.g. python-sig and python-security or something
16:51:34 * jflory7 shrugs
16:51:44 <jflory7> Apprentice program could potentially work if that's something they want to do.
16:51:47 <skamath> jflory7, that actually makes  sense.
16:52:04 <skamath> We will need to ask them first
16:52:17 <jflory7> Right.
16:52:28 <dhanesh95> jflory7: Yes
16:52:30 * skamath has something for the open floor
16:52:33 <dhanesh95> skamath: Yes
16:52:44 <jflory7> skamath: Will be sure to ping then. :)
16:52:53 <skamath> jflory7++
16:53:13 <dhanesh95> Do we have any contacts there?
16:53:16 <jflory7> So to wrap up this ticket... would the rest of you be free soon to discuss the wiki page rewrite? Or does someone want to try forking it to a personal page in their user space to try rewriting it?
16:53:30 <jflory7> This would be a great task for someone to tackle if they're looking for something :)
16:53:52 <dhanesh95> Free to discuss wiki page rewite +1
16:53:56 <dhanesh95> rewrite*
16:54:20 <downey> also happy to brainstorm the wiki page
16:54:30 <jflory7> Someone could do a fork like: https://fedoraproject.org/User:Myuser/SIGs/Python
16:55:06 <jflory7> And try putting their hand at it, or we can discuss it in channel tomorrow afternoon IST / morning US time.
16:55:47 <dhanesh95> I won't be available tomorrow afternoon IST
16:55:51 <jflory7> If no volunteers right now, we can aim to discuss it later on.
16:56:04 <jflory7> Or could do a mailing list thread, etc.
16:56:28 <jflory7> I think I'll leave this one up for discussion about wiki gardening
16:56:44 <jflory7> #action jflory7 Start IRC / mailing list discussion on wiki gardening for Python SIG
16:57:12 <dhanesh95> jflory7: I'll fork the CommOps wiki page in my personal page for Python SIG and interested people can chip in
16:57:18 <jflory7> dhanesh95: +1.
16:57:29 <jflory7> dhanesh95: This sound good? https://fedoraproject.org/User:Dhanesh95/SIGs/Python
16:57:29 <skamath> dhanesh95++
16:57:33 <dhanesh95> We'll send a mail on the mailing list
16:57:36 <jflory7> oh, lol
16:57:41 <jflory7> dhanesh95: This sound good? https://fedoraproject.org/wiki/User:Dhanesh95/SIGs/Python
16:57:57 <dhanesh95> jflory7: Yes
16:58:03 <jflory7> Then let's make it official!
16:58:04 <jflory7> #link https://fedoraproject.org/wiki/User:Dhanesh95/SIGs/Python
16:58:25 <jflory7> Feel free to copy+paste the whole page there and start making modifications.
16:58:38 <dhanesh95> jflory7: Sir, yes sir!
16:58:42 <jflory7> Anything else to cover for this ticket?
16:58:52 <skamath> We're good to go :)
16:59:00 * jflory7 can't think of anything either...
16:59:10 <jflory7> Python SIG ticket, going once...
16:59:20 <jflory7> Going twice...
16:59:25 <jflory7> Thrice...
16:59:28 <dhanesh95> Sold!
17:00:09 <jflory7> Hmmm... so looking at the rest of the tickets marked for today's meeting, I think it's still a little unsorted from the migration
17:00:16 <jflory7> I need some time to triage tickets and add updates to a few
17:00:21 * dhanesh95 leaving for dinner. Will be back in a while
17:00:33 <jflory7> I don't see any tickets that we can readily cover now, unless someone had one they wanted to touch on.
17:00:36 <jflory7> dhanesh95: Okay, sounds good!
17:00:40 <jflory7> Thanks for the heads-up.
17:00:57 <dhanesh95> jflory7 and skamath: Thanks for chairing!
17:01:04 <skamath> :)
17:01:10 <amitsin6h> amitsin6h
17:01:33 <skamath> amitsin6h, hi again
17:01:40 <jflory7> Tickets, going once...
17:01:50 <jflory7> Going twice...
17:01:55 <jflory7> Thrice...
17:02:04 <skamath> jflory7, shall we have newcomer topic now?
17:02:17 <jflory7> #action jflory7 Do some srs ticket triaging / updating this week
17:02:24 <jflory7> skamath: Actually, yeah, let's do so.
17:02:29 <jflory7> #topic Newcomer introduction
17:02:38 <skamath> amitsin6h, the floor is yours
17:02:48 <jflory7> amitsin6h: Care to do a quick introduction of yourself / what you're interested in with CommOps / anything else you want to share? :)
17:02:51 <amitsin6h> Amit Kumar Singh from Ranchi Jahrkhand
17:02:56 <jflory7> Hi Amit!
17:02:59 <downey> Welcome amitsin6h :)
17:03:05 <amitsin6h> Hello guys
17:03:29 <amitsin6h> I would to love to contribute to python projects
17:03:59 <jflory7> amitsin6h: Fortunately for you, Fedora is definitely a Python-heavy project. :)
17:04:19 <amitsin6h> cool
17:04:27 <jflory7> amitsin6h: Were there things specific to CommOps that you're interested in? Like maybe some of the Python tools with metrics? Or are you looking for something else to check out?
17:05:49 <skamath> amitsin6h, #python-fedora is a place you should idle in :)
17:06:06 <jflory7> s/#python-fedora/#fedora-python :)
17:06:17 <skamath> Ouch
17:06:19 <amitsin6h> badges, hubs, metrics, culture, voting, Misc
17:06:27 <skamath> python-fedora is the API
17:06:28 <skamath> damn
17:06:39 <skamath> jflory7++
17:06:48 <amitsin6h> but someone please approve my request to join CommOps group
17:06:55 <amitsin6h> need to create wiki page
17:07:03 <jflory7> amitsin6h: Okay, awesome! There's definitely some resources available for you to check out and learn more abut Hubs. There's some other members who might be able to help offer more info for the other parts.
17:07:12 <skamath> amitsin6h, approvals take time
17:07:26 <amitsin6h> ok
17:07:27 <jflory7> amitsin6h: The wiki page is no longer required because of the spam account issue. For now, you can work through the other steps and become a member. :)
17:07:34 <jflory7> amitsin6h: Are you subscribed to our mailing list currently?
17:07:40 <amitsin6h> yes
17:07:54 <jflory7> amitsin6h: Awesome! Have you sent an introduction already?
17:08:36 <jflory7> If not, it's no problem :)
17:08:44 <amitsin6h> yep sent introduction commops@lists.fedoraproject.org
17:09:08 <amitsin6h> already sent
17:09:12 <amitsin6h> to commops@lists.fedoraproject.org
17:09:25 <skamath> amitsin6h, Awesome
17:09:34 <jflory7> amitsin6h: Ah, okay, I see it is in the queue now. It doesn't seem like you're subscribed to the list though. Will you be free after the meeting to troubleshoot?
17:09:44 <jflory7> amitsin6h: If you're available, we can hop in #fedora-commops and get you set up. :)
17:09:55 <skamath> jflory7, we have 20 minutes.
17:09:58 <jflory7> For now, I'm going to action you with an item to follow up on.
17:10:19 <jflory7> #action amitsin6h Double-check subscription to the mailing list and make sure you are receiving mail from the list
17:10:19 <amitsin6h> yep Ill be free
17:10:28 <jflory7> amitsin6h: Perfect, we can figure out the details in a little bit!
17:10:33 <downey> amitsin6h++
17:10:33 <skamath> amitsin6h, Welcome onboard.
17:10:36 <jflory7> With that, let's go ahead and move on to finish out the agenda.
17:10:41 <jflory7> #topic Wiki Gardening
17:10:48 <jflory7> #nick commops
17:10:49 <jflory7> #action commops New members, make sure you add your timezone / interests on CommOps wiki [ https://fedoraproject.org/wiki/CommOps ]
17:10:57 <jflory7> So, surprise, I actually have two things to bring up here:
17:11:01 <skamath> jflory7, we should change that line
17:11:09 <jflory7> skamath: Hah, actually, you're right
17:11:12 <jflory7> #undo
17:11:12 <zodbot> Removing item from minutes: ACTION by jflory7 at 17:10:49 : commops New members, make sure you add your timezone / interests on CommOps wiki [ https://fedoraproject.org/wiki/CommOps ]
17:11:26 <jflory7> #action jflory7 Come up with a more fitting introductory item to place into the meeting
17:11:30 <skamath> lol
17:11:35 <skamath> jflory7++
17:11:37 <jflory7> #help CommOps wiki page needs to remove all mention of Trac and replace with Pagure
17:11:50 <jflory7> #action jflory7 Revisit Join page and edit / alter section about wiki page
17:12:07 * skamath will help jflory7
17:12:11 <jflory7> Would anyone be up for doing some wiki gardening on our home page to remove the Trac mention?
17:12:16 <jflory7> skamath: Cool, you want that action item?
17:12:31 <skamath> jflory7, I can do it
17:12:41 <skamath> I'll take that.
17:12:42 <jflory7> #action skamath Garden the CommOps wiki page to remove mention of Trac and replace with Pagure (and update hyperlinks)
17:12:45 <jflory7> skamath++
17:12:48 <jflory7> Perfect. :)
17:12:52 <skamath> \o/
17:13:03 <jflory7> That's all I had to bring up for wiki gardening.
17:13:09 <jflory7> Anyone else have anything they want to mention here?
17:13:15 <jflory7> Any pages needing some love or pages that are confusing?
17:13:18 <downey> !
17:13:25 <jflory7> downey: Go for it!
17:13:38 <downey> jflory7: Maybe skamath (or I can if not) may want to tweak that part on the join page about creating a wiki profile
17:13:45 <skamath> downey, already did
17:13:49 <downey> skamath: ok :D
17:13:56 <skamath> downey, https://fedoraproject.org/wiki/CommOps/Join#Add_yourself_to_the_wiki_page
17:14:15 <downey> awesome.
17:14:30 <downey> skamath++
17:14:45 <downey> jflory7: that is all :)
17:14:46 <jflory7> downey: As an off-hand idea, I was thinking of moving that table to its own page, though, e.g. CommOps#Interest Areas => CommOps/Members
17:14:52 <downey> jflory7: +1
17:14:54 <jflory7> downey: Think that might be something you want to do?
17:14:59 <downey> jflory7: sure
17:15:01 * jflory7 notes the list is getting a little long :)
17:15:08 <skamath> jflory7, Actually yes
17:15:09 <skamath> +1
17:15:10 <jflory7> downey: Okay, awesome. I think it would be tidier that way
17:15:55 <jflory7> #action downey Migrate the member table from https://fedoraproject.org/wiki/CommOps#Interest_Areas to https://fedoraproject.org/wiki/CommOps/Members
17:16:06 <skamath> downey++
17:16:11 <jflory7> downey: Drop a ping in channel whenever you get around to it. :)
17:16:13 <jflory7> downey++
17:16:27 <jflory7> Okay, that's all I can think of for wiki gardening now.
17:16:35 <jflory7> skamath, downey: Thanks for being proactive :)
17:16:52 <skamath> Just happy to help :)
17:16:59 <jflory7> #topic Community Blog
17:17:15 * skamath grabs popcorn as usual
17:17:15 <jflory7> #info How this is supposed to work: 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.
17:17:46 <jflory7> #info How it's happening today: jflory7 didn't have time to prep any of the data or go through numbers, so he is going to compensate at next week's meeting
17:17:48 <jflory7> jflory7--
17:18:14 <jflory7> If it were a small amount, I could probably do it on the fly, but there's been a lot of traffic on the CommBlog lately :)
17:18:17 <jflory7> Which is awesome!
17:18:51 <devyani7> :)
17:19:16 <jflory7> Anyways... but I'll be better next week. It's been a tough week for me getting caught up. So much traveling around for one month!!
17:19:17 <devyani7> CommBlog++ jflory7++
17:19:30 <jflory7> devyani7: Cheers, thanks :)
17:19:36 <skamath> zodbot : jflory7, no negative karma allowed
17:19:40 <skamath> :p
17:19:41 <jflory7> #topic Release Schedule
17:19:54 <jflory7> skamath: Heheh, probably for the better!
17:19:57 <jflory7> #link https://fedorapeople.org/groups/schedule/f-25/f-25-key-tasks.html
17:20:16 <jflory7> #info (1) Alpha Release Public Availability (Tue 2016-08-30)
17:20:31 <jflory7> #info (2) Software Translation Deadline (due: Tue 2016-09-13)
17:20:45 <jflory7> I believe pravins, noriko, and the rest of the G11N team are on track for this one ^
17:20:46 <jflory7> :)
17:21:06 <jflory7> #info (3) Change Checkpoint: 100% Code Complete Deadline (Tue 2016-09-27)
17:21:13 <pravins> jflory7: yes almost
17:21:20 <jflory7> #info (4) Beta Freeze (00:00 UTC) (Tue 2016-09-27)
17:21:32 <pravins> I think, we will able to cover major stuff during Translation sprint.
17:21:41 <jflory7> pravins: Awesome - if you need anything, you know where to find us. Keep up the awesome work in G11N :) pravins++ g11n++
17:21:48 <skamath> pravins++
17:21:49 <zodbot> skamath: Karma for pravins changed to 8 (for the f24 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
17:21:57 <pravins> i am hoping Jona and Sylvia will put an article in commblog soon.
17:22:04 <jflory7> Oh, excellent!
17:22:14 <jflory7> Sounds like a plan.
17:22:16 <pravins> Article is only remaining thing for Translation sprint.
17:22:22 <jflory7> \o/
17:22:25 <jflory7> #topic Open Floor
17:22:28 <pravins> #link https://fedoraproject.org/wiki/G11N/vFAD_Translation_F25
17:22:47 <skamath> !
17:22:52 <jflory7> And the fancy new badge for anyone on the hunt for a way to get one more in their collection. ;)
17:22:53 <jflory7> #link https://badges.fedoraproject.org/badge/fedora-25-translation-sprint
17:22:56 <jflory7> skamath: Go on ahead!
17:23:16 <downey> ?
17:23:17 <skamath> jflory7, If you had missed it, I had cc'd CommOps on a Fedora Join thread
17:23:19 <skamath> #link https://lists.fedoraproject.org/archives/list/commops@lists.fedoraproject.org/thread/7DZLGLJC5QBP4MSWUCRPGL6T5EUX7CHO/
17:23:28 <jflory7> skamath: I think I saw it along the way, but need to get caught up on it.
17:23:29 * jflory7 clicks
17:23:43 <skamath> Fedora Join needs help from CommOps to set their Onboarding right
17:24:06 * jflory7 nods
17:24:10 <jflory7> Yeah, we probably do :P
17:24:13 <skamath> FranciscoD, ping Join
17:24:22 <FranciscoD> heya :)
17:24:34 * FranciscoD was sitting quietely in a corner
17:24:37 <skamath> FranciscoD, over to you :)
17:24:44 <FranciscoD> ah, not much to say really
17:24:48 * jflory7 is a little behind, but can jump on this thread after the meeting too
17:24:56 <jflory7> Also, hi FranciscoD :)
17:24:56 <FranciscoD> trying to get join back to proper functioning
17:25:00 <FranciscoD> heya jflory7 :)
17:25:09 <jflory7> FranciscoD: We'll be happy to support in any way we can. :)
17:25:13 <FranciscoD> just hacked this up: all feedback welcome, of course: https://ankursinha.fedorapeople.org/charlie/index.html
17:25:42 <FranciscoD> jflory7: awesome, ta! We'll probably do this over the ML etc. Not in a position to start doing things yet :)
17:25:48 <jflory7> FranciscoD: Ohh! Ohh! If you are free after the meeting, this is actually something that reminds me of something that could be super useful!
17:26:01 <downey> FranciscoD++
17:26:01 <zodbot> downey: Karma for ankursinha changed to 4 (for the f24 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
17:26:04 <FranciscoD> jflory7: I'll be here :)
17:26:07 <skamath> FranciscoD, we can also have a shiny badge for fedora-join sponsorship ;)
17:26:16 <jflory7> FranciscoD: If you're not already, hop in #fedora-hubs and I will ping you there. :) There is ongoing discussion for something like this in Hubs... :)
17:26:21 <FranciscoD> skamath: yea! lots of ideas!
17:26:23 <skamath> We have been doing it for quite a while now
17:26:23 <jflory7> downey: Your turn!
17:26:37 <downey> jflory7: pagure newbie here, is there any equivalent of cc'ing an issue in pagure like was done in trac?
17:26:54 <skamath> downey, add a comment maybe?
17:27:02 <jflory7> downey: For now, it's the equivalent of a @username tag
17:27:04 <skamath> downey, or star the repo
17:27:17 <jflory7> You might have seen that I did a "CC" section at the bottom of the Python SIG ticket
17:27:29 <downey> skamath & jflory7 that is what i kind of assumed, but wanted to make sure i didn't miss any "hidden" feature. :) thanks!
17:27:29 <jflory7> I'm thinking I'll use that method for now :P
17:27:37 <jflory7> downey: Yup, no problem!
17:27:47 <jflory7> Okay, so before we wrap up, I want to say one thing and ask one question:
17:27:58 * skamath is all ears
17:28:13 * devyani7 is here, partially sleepy :P
17:28:15 <jflory7> #info jflory7 apologizes for being super late without any warning *and* dropping the ball on the agenda today - skamath is super awesome for picking up the slack and carrying the torch!
17:28:47 <skamath> Happy to help, as always :)
17:28:59 <jflory7> And my question is: is there anyone opposed to bumping the meeting 30 minutes later? The current start time doesn't work for me, but even another 20 minutes later would be fine :P
17:29:10 <jflory7> I'll ask on the mailing list too, but wanted to gather opinions.
17:29:14 <downey> +1
17:29:17 <skamath> +1 wfm
17:29:23 <jflory7> skamath, devyani7: Thanks both of you for sticking out this late :)
17:29:24 <bt0> +1
17:29:30 <jflory7> Ah, hey bt0 o/
17:29:35 <devyani7> +1 wfm
17:29:37 <devyani7> :)
17:29:47 <bt0> hi :)
17:30:06 <jflory7> #info Asked about bumping the meeting time ahead by 30 minutes for jflory7's new schedule - will ask on the mailing list and/or a ticket to finalize opinions ASAP
17:30:17 <dhanesh95> +1
17:30:18 <skamath> What fun is CommOps meeting without jflory7 :p
17:30:22 <jflory7> Good to know there's no immediate conflicts with bumping the time...
17:30:29 <devyani7> of course :)
17:30:31 <dhanesh95> CommOps without jflory7 is incomplete
17:30:31 <jflory7> I don't know if this has EVER happened before... :O
17:30:44 <jflory7> :)
17:31:01 <downey> jflory7: don't curse the outcome with optimism :)
17:31:02 * jflory7 is happy to have you all here part of the team :)
17:31:08 <jflory7> downey: Heh, touché!
17:31:15 <jflory7> Alrighty, we're a minute over time.
17:31:20 <jflory7> Thanks for coming out today, everyone!
17:31:26 <jflory7> Will do some following up in channels after I send the minutes!
17:31:28 <skamath> Thank you everyone :)
17:31:33 <jflory7> CommOps, out!
17:31:35 * jflory7 drops the mic
17:31:37 <jflory7> #endmeeting