17:00:06 <FranciscoD> #startmeeting Fedora Join 2018-10-09
17:00:06 <zodbot> Meeting started Tue Oct  9 17:00:06 2018 UTC.
17:00:06 <zodbot> This meeting is logged and archived in a public location.
17:00:06 <zodbot> The chair is FranciscoD. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:00:06 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
17:00:06 <zodbot> The meeting name has been set to 'fedora_join_2018-10-09'
17:00:14 <FranciscoD> #meetingname fedora-join
17:00:14 <zodbot> The meeting name has been set to 'fedora-join'
17:00:33 <FranciscoD> #chair bt0 hellbanger dhanesh95 x3mboy
17:00:33 <zodbot> Current chairs: FranciscoD bt0 dhanesh95 hellbanger x3mboy
17:00:45 <FranciscoD> If I've missed anyone, please let me know.
17:00:55 <FranciscoD> #info We will follow this meeting guide: https://fedoraproject.org/wiki/Meeting:Guide
17:01:05 <FranciscoD> #info The agenda is here: https://fedoraproject.org/wiki/SIGs/Join/Next_Meeting
17:01:12 <FranciscoD> #topic Roll call
17:01:51 <FranciscoD> #info FAS: ankursinha; IRC: FranciscoD; GMT+1; Classrooms, Join, Packaging, NeuroFedora
17:01:54 <bt0> .fas bt0dotninja
17:01:55 <zodbot> bt0: bt0dotninja 'Alberto Rodriguez Sanchez' <hotgalan@gmail.com>
17:01:58 <bt0> #info Alberto Rodriguez S; UTC-5;CommOps (Metrics, Community engagement), DotNet (Testing), Infrastructure(Apprentice), Marketing (Member), Ambassadors (Member),Fedora-Join(Member) ,Cats (lover)
17:02:50 <FranciscoD> Let's wait 5 minutes for others to join in.
17:02:53 <hellbanger> .fas hellbangerkarna
17:02:54 <zodbot> hellbanger: hellbangerkarna '' <akarshan.biswas@hotmail.com>
17:03:07 <hellbanger> .fasinfo hellbangerkarna
17:03:07 <zodbot> hellbanger: User: hellbangerkarna, Name: Akarshan Biswas, email: akarshan.biswas@hotmail.com, Creation: 2018-02-18, IRC Nick: hellbanger, Timezone: Asia/Kolkata, Locale: en, GPG key ID: 4C400AC7, Status: active
17:03:10 <zodbot> hellbanger: Approved Groups: cla_done cla_fpca
17:05:56 <FranciscoD> I've pinged folks on telegram, let's wait another 2 minutes and then proceed
17:05:57 <bt0> awesome the modularity classroom
17:06:32 <FranciscoD> +1, it was really good. Lots of people turned up too
17:06:46 <hellbanger> bt0: Yes. I was late though. I will rewatch once I gets uploaded on Youtube.
17:06:52 <FranciscoD> OK, Let's proceed then
17:06:54 <bt0> yeah, sure
17:07:08 <FranciscoD> #topic New member introductions
17:07:36 <FranciscoD> #info If anyone here is new to Fedora or the team, please introduce yourselves :)
17:07:45 * FranciscoD doesn't think so
17:07:58 <FranciscoD> Note that avigne did get sponsored to the packager group. Filing a ticket did it.
17:08:17 <FranciscoD> So we were able to help in some way at least.
17:08:40 <hellbanger> FranciscoD: That is the best way to get sponsored imo.
17:08:49 <bt0> +1
17:09:21 <FranciscoD> hellbanger: maybe. I'd still leave ticket filing as last resort. I'd prefer it if a packager sponsor looked at someone's work and gave them tips etc to help them learn the trade first
17:09:32 <FranciscoD> Not really sure why it didn't happen in this specific case. Usually does.
17:09:40 <FranciscoD> #topic Community announcements
17:10:16 <FranciscoD> #info Fedora 29 final freeze: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/thread/PTB74FXL7EEBUSMZ3D7XQV6ZPP5VHENN/
17:10:53 <dhanesh95> .fas dhanesh95
17:10:54 <zodbot> dhanesh95: dhanesh95 'Dhanesh Bhalchandra Sabane' <dhanesh95@disroot.org>
17:10:55 <FranciscoD> #info Fedora Modularity test day on 2018-10-12: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/thread/NX4RQ3XEKZ6PAIBEXXW5TZSAQ5BJMIO7/
17:11:46 <FranciscoD> #info FPgM's report: https://communityblog.fedoraproject.org/fpgm-report-2018-40/
17:12:05 <FranciscoD> I can't find anything else---you folks have anything?
17:12:17 <FranciscoD> #chair dhanesh95
17:12:17 <zodbot> Current chairs: FranciscoD bt0 dhanesh95 hellbanger x3mboy
17:12:35 * dhanesh95 got nothing
17:12:35 <bt0> o/ dhanesh95
17:12:40 <dhanesh95> bt0: o/
17:12:50 <bt0> not from me
17:12:59 <FranciscoD> Neither do I. Let's quickly go over tasks from last week so that we can get to tickets
17:13:03 * hellbanger can't think of anything either.
17:13:03 <FranciscoD> #topic Tasks from last week
17:13:12 <FranciscoD> #info Logs from last week's meeting: https://meetbot-raw.fedoraproject.org/fedora-meeting-3/2018-10-02/fedora-join.2018-10-02-17.07.txt
17:14:05 <FranciscoD> #info bt0 update https://pagure.io/fedora-join/Fedora-Join/issue/72 with more information (Script to get last activity of a user): DONE
17:14:44 <FranciscoD> bt0: what does "last_seen" really mean? Last time logged into FAS, or last time seen by fedmsg?
17:14:59 <FranciscoD> https://pagure.io/fedora-join/Fedora-Join/issue/72#comment-535664 -> comment in question
17:15:25 <bt0> last activitie registred in  fedmsg
17:15:32 <FranciscoD> bt0: if it means "last time seen by fedmsg", then that works. If it means "last time logged into FAS", that's not entirely accurate as a measure of activity.
17:15:36 <FranciscoD> Ah, then that works for me
17:15:43 <FranciscoD> hellbanger: dhanesh95 : what do you think?
17:15:52 <FranciscoD> Should we vote to agree?
17:15:56 <FranciscoD> (or disagree)?
17:16:25 * dhanesh95 votes to agree
17:16:29 <bt0> we need latex support for pagure.io
17:16:35 * bt0 +1
17:16:43 <hellbanger> #agree
17:17:02 <FranciscoD> haha, LaTeX support would be nice
17:17:05 <FranciscoD> +1 too
17:17:34 <FranciscoD> #agreed Use "last seen" and "active" fields of FAS with some date constraint to measure activity of contributors in script (+4/-0)
17:17:47 <FranciscoD> #action FranciscoD comment on ticket noting agreement
17:18:01 <bt0> the format output will csv, easy to export to another scripts or visualize in calc
17:18:13 <FranciscoD> Yeh, that'll be ideal
17:18:29 <FranciscoD> #info dhanesh95 FranciscoD finish post and aim to publish in 2 weeks: PENDING
17:18:47 <FranciscoD> dhanesh95: you told us you are busy, so we won't discuss this until next meeting or the one after that. Is that OK?
17:19:25 <FranciscoD> We have a ticket for it too, so we needn't keep it in the task list each week
17:19:30 <dhanesh95> FranciscoD: I think the meeting after the next one will be a good time to discuss this. I think I can definitely work on the improvements till then
17:19:42 <FranciscoD> Awesome
17:20:00 <FranciscoD> Is there a way to mention timelines in Pagure tickets? No, right? Unless we use milestones and all that?
17:20:31 * dhanesh95 doesn't know about that
17:20:48 <bt0> i don't know
17:20:48 <FranciscoD> I don't think so. That's fine. I'll just put it in the logs
17:21:07 <FranciscoD> #info dhanesh95 FranciscoD finish post and aim to publish: to be discussed in meeting on 23rd October.
17:21:10 <FranciscoD> there
17:21:24 <dhanesh95> +1
17:21:42 <FranciscoD> #info FranciscoD e-mail devel list to clarify the function of "Trivial" key word on review tickets: PENDING, reassigning
17:22:02 <FranciscoD> This is somewhat low priority at the moment, so I haven't bothered to start this discussion yet
17:22:34 <FranciscoD> #action FranciscoD e-mail devel list to clarify the function of "Trivial" key word on review tickets
17:23:27 <FranciscoD> #info s14ck FranciscoD discuss newcomers + classroom after meeting: DONE: a separate set of sessions for LATAM will be run. More information at https://pagure.io/fedora-join/Fedora-Join/issue/74
17:23:47 <FranciscoD> #info FranciscoD send e-mails to ML about tickets that need discussing one by one: PENDING, needs discussion, reassigning
17:24:08 <FranciscoD> If we manage to get to these tickets, we need to decide which ones need the ML. Relegating to before "open floor".
17:24:16 <bt0> ok
17:24:44 <dhanesh95> hellbanger: See #74. Probably something like this for localised sessions?
17:24:54 <hellbanger> dhanesh95: yes
17:25:04 <FranciscoD> #info FranciscoD work on https://pagure.io/fedora-join/Fedora-Join/issue/6: (Introduction template for contributors): PENDING, reassigning
17:25:13 <FranciscoD> Not high priority at the moment either.
17:25:24 <FranciscoD> Leaving it as a ticket
17:25:54 <FranciscoD> #info FranciscoD file ticket proposing zsh classroom session and assign it to x3mboy : DONE:  https://pagure.io/fedora-join/Fedora-Join/issue/76
17:26:13 <FranciscoD> #info FranciscoD file ticket for Vim 102 classroom session: DONE: https://pagure.io/fedora-join/Fedora-Join/issue/77
17:26:13 <dhanesh95> ZSH \o/
17:26:22 <dhanesh95> x3mboy++
17:26:36 <dhanesh95> VIM \o/
17:26:39 <FranciscoD> #info FranciscoD file ticket for Silverblue classroom session: DONE: https://pagure.io/fedora-join/Fedora-Join/issue/78
17:26:45 <dhanesh95> Just my everyday tools. :)
17:26:52 <bt0> Silverblue
17:26:54 <hellbanger> Mine too
17:26:57 <bt0> \0/
17:27:01 <FranciscoD> #info FranciscoD send out logs and updates next_meeting page etc: DONE
17:27:03 <hellbanger> Well I see silverblue as well
17:27:21 <hellbanger> rpm-ostree \o/
17:27:33 <FranciscoD> #info FranciscoD close https://pagure.io/fedora-join/Fedora-Join/issue/28: DONE (Video platform overview)
17:28:08 <FranciscoD> #info hellbanger file ticket about l10n classroom sessions: DONE: https://pagure.io/fedora-join/Fedora-Join/issue/73 and https://pagure.io/fedora-join/Fedora-Join/issue/80
17:28:30 <FranciscoD> #info #73 is about holding more sessions for non English speakers
17:28:39 <FranciscoD> #info #80 is about a session on l10N 101
17:28:56 <FranciscoD> Phew, that's all the tasks. Moving on to tickets.
17:29:00 <FranciscoD> #topic Pagure tickets
17:29:21 <FranciscoD> #info https://pagure.io/fedora-join/Fedora-Join/issue/87: Release related Fedora classroom schedule
17:29:50 <FranciscoD> This one is high priority. Here's what I came up with as an example:  https://fedoraproject.org/wiki/Classroom/Release_schedule
17:29:57 * FranciscoD mentioned a wrong link on the ticket
17:30:35 <FranciscoD> Please go through it and see what you think. If that looks OK, I can make a proper one that we can try to use for the F29 release cycle (although we're a little behind already)
17:30:52 <FranciscoD> AND, I can speak to the FPgM to make us a proper one as he does for all teams
17:31:19 <dhanesh95> FranciscoD: How about we review the draft off meeting?
17:31:36 <dhanesh95> Add comments to the tickets later?
17:31:40 <FranciscoD> Could do, but I was hoping we can do it today so that we can agree on whether or not we want to follow it for F29
17:31:57 <FranciscoD> if we push it to next week, we lose another week from the "preparation phase"
17:32:00 <FranciscoD> :(
17:32:14 <FranciscoD> Maybe it's too ambitious to try and use it for F29, given how close we are to release?
17:32:15 * dhanesh95 thinks we shouldn't hurry this for the F29 release.
17:32:51 * hellbanger is reading the Release_schedule
17:33:13 <dhanesh95> FranciscoD: We could scramble and get it working somehow but it won't really help us a lot, IMO. I'd suggest targetting this for F30.
17:33:13 <FranciscoD> But then, the preparation period for F30 cycle will only start on 2019-09-11
17:33:15 <bt0> +1
17:33:37 <FranciscoD> 2019-09-11  is in a year. Have I messed something up?
17:33:42 * FranciscoD double checks
17:34:13 <dhanesh95> FranciscoD: That date doesn't seem correct.
17:34:18 <FranciscoD> Yeh, I have. Typo.
17:34:25 <FranciscoD> Should be 2019-03-11
17:34:28 <FranciscoD> phew
17:35:03 <dhanesh95> So March next year which gives us ample time to review and revise the plan.
17:35:41 <FranciscoD> OK. So everyone needs to go through this, and drop comments on the ticket
17:36:01 <dhanesh95> What are everyone's thoughts? Shall we go ahead with this for F29 or F30?
17:36:11 <FranciscoD> #action dhanesh95 bt0 x3mboy alciregi hellbanger FranciscoD : review https://pagure.io/fedora-join/Fedora-Join/issue/87 and provide comments
17:36:18 <FranciscoD> dhanesh95: We can implement it partially
17:36:43 <FranciscoD> For example, we can choose 6 sessions from the ideas we have and work on having them ready for the "semester" period
17:36:57 <FranciscoD> we won't have the proposed readiness meetings etc---keep it fluid this time
17:37:06 <dhanesh95> FranciscoD: That sounds fair. But let's keep it flexible? I mean no hard limits.
17:37:08 <FranciscoD> sort of a prototyping run?
17:37:14 <dhanesh95> +1
17:37:15 <dhanesh95> +1
17:37:21 <hellbanger> +1
17:38:04 <FranciscoD> Yeh. The idea is that we have one 8week period where we have classrooms every week---this would be the period in between two releases so it won't compete with release related work, and it'll keep the community ticking
17:38:26 <bt0> +1
17:38:27 <FranciscoD> since we'll know in advance what dates these are on etc., we can plan better---schedule all the posts etc. better
17:38:34 <FranciscoD> no last minute running etc etc
17:38:55 <FranciscoD> it'll also give us some downtime where we can rest and re-charge our batteries
17:39:47 <FranciscoD> So, should we vote on what 6 classroom sessions we do in the F29 cycle this week, and decide on them at next week's meeting?
17:40:03 <FranciscoD> (8 doable weeks, I thought 6 sessions is good--gives us 2 weeks buffer)
17:40:39 <FranciscoD> We can order them in a thematic way etc., decide on the dates now, and get to work on setting them up
17:42:33 <dhanesh95> +1
17:42:33 <FranciscoD> How does that sound? +1s?
17:42:39 <bt0> +1
17:42:50 <hellbanger> +1
17:43:01 <FranciscoD> +1
17:43:17 <FranciscoD> #agreed We decide 6 classroom sessions for F29 at next week's meeting
17:43:59 <FranciscoD> #info https://pagure.io/fedora-join/Fedora-Join/issue/61: Fedora modularity classroom sessions
17:44:17 <FranciscoD> bt0: should we leave this open until the recording links have been uploaded? Nothing else is required, no?
17:44:45 <FranciscoD> related ticket: https://pagure.io/fedora-join/Fedora-Join/issue/65
17:44:57 <bt0> yeah
17:45:28 <FranciscoD> Weird. The last comment says "depends on 65", but the metadata doesn't say so
17:46:01 <FranciscoD> bt0: I'll close 61, and you can close 65 when the recoring link is up. Does that sound OK?
17:46:24 <bt0> perfect
17:46:34 <FranciscoD> #action FranciscoD close #61
17:46:44 <FranciscoD> #action bt0 close #65 when recording link has been provided
17:47:04 <FranciscoD> #info https://pagure.io/fedora-join/Fedora-Join/issue/86: Keeping an eye on contributors looking for sponsorship to various groups
17:47:39 <FranciscoD> as bt0 has commented, keeping an eye on all SIGs is hard, since our team isn't present on them all
17:47:46 <FranciscoD> So what can we do? :/
17:47:48 <dhanesh95> This was a hot topic on the packaging mailing list
17:48:12 <FranciscoD> dhanesh95: Oh, as a result of avigne's e-mail?
17:48:19 <FranciscoD> Can you find us a link?
17:48:26 <dhanesh95> FranciscoD: I think we should first compile a list of groups that need attention for newbies.
17:48:28 <dhanesh95> FranciscoD: Yes.
17:48:29 <bt0> please dhanesh95
17:49:12 <FranciscoD> +1, I was thinking we need to collect some data first. A script that gives us the list of accounts that have applied for membership to a FAS group but have not been approved maybe?
17:49:47 <FranciscoD> If we see an account's request has not been sponsored in 2/3 weeks, we can e-mail the account to ask "what is up?" and see how we can help move things along?
17:50:33 <FranciscoD> QA is now doing something similar I think. They send periodic e-mails to people who have applied to join the FAS group, but who have not introduced themselves to the mailing list etc.
17:50:45 <dhanesh95> That sounds good.
17:51:27 <dhanesh95> avigne's mail - https://lists.fedoraproject.org/archives/list/fedora-join@lists.fedoraproject.org/thread/5FPGDMAMUHKBFG54VOBWKHESRC4U2XXQ/
17:51:34 <dhanesh95> It started on the Join mailing list
17:51:52 <FranciscoD> Yeh, but I thikn bex sent his reply to the packaging ML too, and then I lost the thread since I'm not on that ML
17:53:08 <dhanesh95> Join SIG was in the CC list. I can see all the emails I read on the thread I linked above.
17:53:27 <FranciscoD> Ah, then I'm up to date with it.
17:53:28 <hellbanger> FranciscoD: It's better to keep a check on those people who has applied for sponsorship. Being a packager myself. I will talk about this with you later since I'm tired now.
17:53:33 * dhanesh95 is drowning in emails related to Fedora
17:53:44 <FranciscoD> hellbanger: yeh, that is what I was proposing
17:53:58 <FranciscoD> if nothing else, we can make this info available to different teams so they can take necessary steps
17:54:28 <FranciscoD> #action FranciscoD write script to extract information from FAS on applications to FAS groups
17:54:37 <dhanesh95> FranciscoD: Let's file a ticket to write a script?
17:55:01 <FranciscoD> dhanesh95: I was thinking I'll comment on the already open ticket and assign it to myself?
17:55:23 <bt0> don't worry about that script it's very similar to the get the groups membership than i'm writing
17:55:31 <FranciscoD> wait, no, I'll open a new ticket for the script and block the current ticket
17:55:50 <dhanesh95> There will be multiple layers to this. I think it'd be best to use the current ticket as the tracker ticket
17:56:01 <dhanesh95> FranciscoD: Ohh.. You got there first. :P
17:56:28 <FranciscoD> bt0: yes, but I think we need to use a db somewhere to keep some info so that we can track each application over time
17:56:32 <dhanesh95> FranciscoD: Give others a chance! :P
17:56:46 <FranciscoD> ie. abc applied on this date, and 4 weeks later, the application is still pending
17:56:59 <FranciscoD> dhanesh95: this is me being active. As soon as the meeting finishes, I'll crash XD
17:57:24 <FranciscoD> #action FranciscoD open new ticket for script and make it block #86
17:57:30 <bt0> ok
17:57:48 <FranciscoD> We're at 57 past. Should we leave it at this and close right on time?
17:57:49 * dhanesh95 needs to wake up!
17:58:01 * FranciscoD is tired and still needs to do more work
17:58:05 <bt0> maybe without db, just looking for the age of the message in fedmsg
17:58:29 * hellbanger yawns
17:58:36 <FranciscoD> bt0: hrm, yeh, that should work too
17:58:39 <bt0> more processing yes, but don't require any infra
17:58:49 <dhanesh95> FranciscoD: I think let's wrap it up.
17:59:04 <FranciscoD> +1
17:59:08 <dhanesh95> And let's try to cover more tickets in the next meeting.
17:59:17 <hellbanger> Okay, I am leaving. Good night.
17:59:23 <dhanesh95> I think we have less action items to cover from this meeting.
17:59:25 <hellbanger> o/
17:59:29 <dhanesh95> hellbanger: Good night!
17:59:31 <FranciscoD> +1---they're all discussion based tickets too
17:59:45 <FranciscoD> #action FranciscoD send out logs and update next_meeting page
17:59:45 <bt0> +1 too
18:00:01 <FranciscoD> #endmeeting