18:01:54 #startmeeting "NeuroFedora - 20200518" 18:01:54 Meeting started Mon May 18 18:01:54 2020 UTC. 18:01:54 This meeting is logged and archived in a public location. 18:01:54 The chair is FranciscoD. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:01:54 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:01:54 The meeting name has been set to '"neurofedora_-_20200518"' 18:02:21 #meetingname neurofedora 18:02:21 The meeting name has been set to 'neurofedora' 18:02:40 #chair mhough zbyszek mhough lbazan gicmo bt0 alciregi 18:02:40 Current chairs: FranciscoD alciregi bt0 gicmo lbazan mhough zbyszek 18:02:53 If anyone else is here for the meeting, please let me know too so I can add you to the list of chairs 18:03:09 #topic Agenda 18:03:24 #info New introductions and roll call 18:03:33 #info Tasks from last week's meeting 18:03:39 #info Open Pagure tickets 18:03:45 #info Comp Neuro Lab compose check 18:03:58 #info Bug review 18:04:07 #info Neuroscience query of the fortnight 18:04:16 #info Next meeting day and chair 18:04:19 #info Open floor 18:04:26 #topic New introductions and roll call 18:04:47 #info ankursinha: packaging and stuff 18:04:49 XD 18:04:51 I'm here 18:04:58 #chair MeWjOr 18:05:06 #chair MeWjOr 18:05:06 Current chairs: FranciscoD MeWjOr alciregi bt0 gicmo lbazan mhough zbyszek 18:05:37 #info major/MeWjOr: currently nothing... Legacy support maybe? :P 18:05:46 haha 18:06:13 let's wait a minute or two 18:06:19 Here 18:07:18 hello @bt0dotninja! 18:07:53 ok, next topic 18:07:58 #topic Tasks from last week 18:08:02 #info https://meetbot.fedoraproject.org/teams/neurofedora/neurofedora.2020-04-27-18.01.html 18:08:16 #info FranciscoD update docs to remove info about the iso image we generated : DONE 18:08:34 #info FranciscoD e-mail devel list asking for volunteers: pending 18:08:38 I don't think I've done that yet 18:08:58 not sure if it's worth doing at the moment, what do you folks think? 18:09:47 We have a heap-load of packages left.. and plenty other work... 18:10:12 maybe you can point me to some easy ones 18:10:17 yeh, but the devel list does not seem to be the set of people with the free time to take this on IMO 18:10:23 #chair bt0 18:10:23 Current chairs: FranciscoD MeWjOr alciregi bt0 gicmo lbazan mhough zbyszek 18:10:45 bt0: there are quite a few ones tagged with "easy" or "good first issue": perhaps start with them? 18:10:52 That too as well... :/ 18:10:53 Cool 18:11:01 I can find ones for you after the meeting if you wish 18:11:14 Yeah I will take some 18:11:19 MeWjOr: that's sort of why I wrote the post as "we're looking for trainees" 18:11:28 hoping that'll attract folks who are looking to learn 18:11:36 but it isn't that easy either tbg 18:11:40 s/tbg/tbh/ 18:12:03 Should we discuss ideas on increasing the team in open floor perhaps? 18:12:11 yep... 18:12:24 #info Discuss ideas on increasing the team in Open Floor 18:12:41 #info FranciscoD add spin-master to list of open positions in blog post: DONE 18:12:58 I didn't explicitly say "spin master" because people outside the community wouldn't know what that meant 18:13:22 +1 18:13:25 i just said "software development" 18:13:35 umm... that's very generic 18:13:37 XD 18:13:58 Yeh, but how do you we envelop packaging/testing/spin generation and so on? :( 18:14:20 agreed 18:14:41 I gave some more info in there, but for a non Fedora audience writing the details isn't ideal 18:15:09 #info FranciscoD e-mail neuroscience mailing lists about the CompNeuro release: DONE 18:15:20 this went well, we got some retweets etc also 18:15:52 that's all the action items 18:16:40 #topic Open pagure tickets 18:16:57 #info https://pagure.io/neuro-sig/NeuroFedora/issues?status=Open&tags=S%3A+Next+meeting 18:17:02 Nothing here this week :D 18:17:11 #info No tickets to discuss: YAY 18:17:24 #topic Bugs 18:17:28 #info https://tinyurl.com/neurofedora-bugs 18:18:23 #info Not too many urgent bugs: a few updates, a few remaining slightly complex FTBFS bugs 18:18:31 Any particular ones that merit a discussion? 18:18:34 Well... I was wondering if I should start with any open tickets this week... maybe take some time off my work and get started here 18:18:57 MeWjOr: sure, 18:18:58 I'll go through the "catalogue" and see which one's I can work on 18:19:02 +1 18:19:09 catalogue -> the bug list 18:19:10 but don't let it affect work :) 18:19:38 yeah, working from home has other constraints... one of which is using Windows! 18:20:03 LOL 18:20:21 #topic Compose check 18:20:59 #info Latest was incomplete: https://pagure.io/releng/failed-composes/issue/1447 18:21:18 let's see if it's one of our packages or just a generic failure 18:21:32 #info koji task: https://koji.fedoraproject.org/koji/taskinfo?taskID=44632603 18:21:57 It was LibreOffice that was not building correctly last time right? 18:22:03 #info root.log: https://kojipkgs.fedoraproject.org//work/tasks/2606/44632606/root.log 18:22:08 yes, that got fixed iirc 18:22:31 Now it's the tex stack, but I'm sure this is known and is being worked on, if not already fixed. 18:22:43 tex live? 18:22:52 I saw a mail on devel recently about it 18:22:58 texlive 2020 maybe 18:23:10 Yeh 18:23:33 #info https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/2JPVOJLK7NPTBI7IZPMB3L6MUHT3JMFW/ -> TeXLive 2020 is causing it, will be fixed soon 18:23:36 spot++ 18:23:36 FranciscoD: Karma for spot changed to 1 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 18:23:44 only he knows how he manages the stack 18:23:52 lol 18:24:14 the spec file is generated using a C program, that's how complex it is! 18:25:00 #info Compose: nothing we need to do at the moment 18:25:18 #topic Query of the fortnight 18:25:29 spec using C... O>O 18:25:32 #info Some new stuff here that's worth looking at: https://pagure.io/neuro-sig/NeuroFedora/issue/318 18:26:16 Here's a nature paper on COVID and an antibody that neurtralizes it: https://www.nature.com/articles/s41586-020-2349-y 18:26:59 pagure.issue.comment.added -- ankursinha commented on ticket neuro-sig/NeuroFedora#318: "NeuroFedora reading/listening list" https://pagure.io/neuro-sig/NeuroFedora/issue/318#comment-652884 18:27:13 https://www.sciencenews.org/article/blind-vision-brain-stimulation-trace-letters -> was quite intersting 18:27:25 "Blind people can ‘see’ letters traced directly onto their brains | Science News" 18:28:42 Okay... how do people even conduct studies like this? 18:28:48 XD 18:29:01 I'll have to read the methods section of the paper to answer that 18:29:21 lol... I'll go through as well 18:29:42 OK, so open floor then :D 18:29:45 #topic Open floor 18:30:20 #info The Java SIG has been re-launched, and quite a few folks joined to help out: https://lists.fedoraproject.org/archives/list/stewardship-sig@lists.fedoraproject.org/message/NGE3RS4U2LZ2DTLSSAURVDSKDKZM2PV4/ 18:30:22 decathorpe++ 18:30:42 * FranciscoD joined because of the java packages in NeuroFedora 18:30:52 let's hope we can get java sorted :D 18:31:04 that's good news 18:31:13 anything else before we move on to brainstorming on how to attract more folks? 18:31:49 Java guys literally deserve an applause... I couldn't even get the how to package native java code 18:32:02 if it's maven, I now understand it 18:32:07 spot++ 18:32:07 MeWjOr: Karma for spot changed to 2 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 18:32:14 let's hope they come back :P 18:32:23 but the whole gradle system is just not something I understand yet 18:32:55 MeWjOr: a lot of the java bits were managed by RH folks initially, and i think they moved off it and dropped their packages 18:33:06 gradle was a mess when I was starting out with mobile app development :P 18:33:13 whoa 18:33:26 not entirely sure of the history there, but let's hope the new SIG lives long and well 18:33:36 yep 18:34:11 Should we move on to brainstorming for ideas? 18:34:42 Hey there, sorry 18:35:10 mhough: hello, no worries :) 18:35:21 #topic Attracting more contributors 18:35:39 Happy to talk later too about neuroimaging 18:35:43 So, let's start with a 5 minute brainstorm: put down whatever comes into our heads as infos. 18:35:56 (the idea is not to overthink and just put everything down, and then filter later) 18:36:00 #info More outreach 18:36:16 #info Make meetings even more open: advertise on social media also 18:36:22 #info packaging classroom sessions? 18:36:47 #info invited talks from folks in the field? 18:36:58 #info university collaborations 18:37:30 #info move to more accessible meeting format: jitsi/zoom and all that? 18:37:52 #info speak to tool devs to ask what it would take for them to make neurofedora their default usage platform? 18:38:21 #info poke new folks in the join sig channels towards packaging (I already do this :P) 18:38:40 MeWjOr mhough : any ideas? please just throw them out 18:38:44 bt0: ^ 18:38:48 will do 18:39:11 I was just looking at your ideas... I can't think of anything better 18:39:43 #info regular packaging classroom sessions 18:39:49 #info vFADs 18:40:13 #info blog posts on using NeuroFedora for actual work 18:40:31 #info replicating bits and publishing in rescience using NeuroFedora (https://rescience.github.io/) 18:40:47 #info calls for volunteers on academic mailing lists (may not get through moderation) 18:41:23 #info get funding/grants/sponsorshipts: MONEY (dunno how: don't think it can be done in an academic capacity, but perhaps in a FOSS capacity) 18:41:45 #info Use contacts in academia to encourage students 18:42:09 zbyszek mhough : you folks have any contacts who may supervise students etc and may be open to encouraging participation on FOSS/NeuroFedora? 18:42:46 #info "hire" volunteers: not even sure how or what this would be tbh 18:43:23 #info tweet to scicomm etc folks 18:43:42 #info link up with INCF somehow 18:44:14 #info student internships (can we give actual letters/certificates that universities require??) 18:45:12 well.. I am out of ideas... 18:45:37 I think my neurons have spiked all they would too 18:45:53 But I particularly like the idea of inviting people for some talk and university collaborations 18:45:54 OK, out of this pile of random text, which ones can we try for a start? 18:46:18 MeWjOr: I do too, but now we've got to do a "cost analysis" 18:46:28 inviting academics to such talks is *hard* 18:46:49 university collaborations are even harder: Fedora had a campus something initiative that broke down iirc 18:47:06 https://fedoraproject.org/wiki/Campus_Ambassadors 18:47:34 What ideas have a higher return/effort ratio? 18:47:42 ie., more return on less effort? 18:47:57 we can advertise the meetings on social media, that's easy 18:48:10 #info have a neurofedora twitter handle and tweet from it daily 18:48:18 another relatively less effort requiring idea 18:48:19 yep... and can move from the IRC 18:48:34 OK, let's try that 18:48:43 that was a lot of good ideas 18:48:46 to some other easy platform, like gitter, or jitsi/zoom 18:48:46 #agreed we'll advertise meetings on social media 18:49:26 MeWjOr: should we try zoom and irc in parallel, is that doable do you think? 18:49:32 We are using Jitsi 18:49:38 mhough: working well? 18:49:50 how many folks, it had performance issues last time we tried it for Fedora classrooms 18:50:14 It was until today 18:50:33 I'm not really certain of zoom, but we can try other video conferencing solutions like Google Meet alongside IRC/Telegram 18:50:44 hangouts you mean? 18:50:47 We got zoom bombed in jitsi too 18:50:51 google meets is a paid account iirc 18:51:00 Google meet is free for all now 18:51:04 uh, yeh, the trolling is an issue 18:51:06 I think zoom has better features with a waiting room 18:51:22 MeWjOr: aha? should we try meet next time for a start 18:51:34 and the chair can keep logs using meetbot here also? 18:51:47 zoom had some vulnerabilities... leading to data loss... That's why many/I avoid it 18:51:52 +1 18:51:54 s/had/has 18:52:01 meet should be OK for a start 18:52:13 even jitsi really: works well if there aren't too many people 18:52:19 Yep... I'm always in for a video call... Better than staring at a text-editor 18:52:32 we could start with jitsi, and if that gives issues, use meet instead 18:52:51 jitsi is foss, and doesnt require a google account: many folks I know are quite anti-google :D 18:52:51 agreed 18:53:06 #agreed Have meetings on jitsi to make them more accessible 18:53:19 will have to be wary of the trolling bits, but that can be managed 18:53:31 yep 18:53:36 how about a dedicated twitter account with regular tweets? 18:53:44 ++ 18:54:13 #agreed finally create a dedicated twitter account for NeuroFedora and tweet every day 18:54:29 #action FranciscoD set up twitter account using neuro-sig private ML address 18:54:34 like I did for the github account 18:54:36 do we create a new FAS mail for neurofedora twitter? 18:54:40 oohhh 18:54:47 no, I just use the neuro-sig private ml XD 18:55:28 what other low hanging fruits are there? 18:55:29 gotta make sure to unsubscribe from twitter notifications then... I get plenty of twitter feeds on my mail 18:55:40 yeh, and they'll get stuck in moderation anyway 18:56:20 that's better than using neuro-sig-members@fp.o or another account that doesn't have moderation 18:56:30 (using the private ML) 18:56:37 > speak to tool devs to ask what it would take for them to make neurofedora their default usage platform? 18:56:50 we can start with one tool dev? 18:56:58 hrm, well I can probably speak to the nest folks 18:57:03 so that they would also "recommend" us 18:57:06 yeh 18:57:16 and we can also say, "as used by ____ devs" 18:57:22 +1 18:57:48 #agreed reach out to tool devs to ask what it would take for them to make neurofedora their suggested usage platform 18:58:01 gicmo, you're in G-Node, right? 18:58:07 #action FranciscoD reach out to NEST folks when possible 18:58:16 MeWjOr: used to, now I am Red Hat 18:58:35 oohh... I remember now... 18:58:53 anyways, could you also reach out to some folks at G-Node for the same? 18:58:53 mhough: any idea how hard it would be to get INCF endorsement? 18:59:22 I think regular packaging workshops may be doable, I'll think about how that can be done 18:59:51 Yeah definiteyl 18:59:55 #action FranciscoD speak to -devel and -classroom to see if regular packaging workshops/classrooms can be held to increase package maintainers 19:00:15 mhough: what does one have to do for INCF endorsement? IIRC there's a whole process, right? 19:00:28 MeWjOr: do you want to look into this? 19:00:41 #info https://www.incf.org/activities/endorse 19:00:56 if nothing else, we'll get some good feedback from the scientific community 19:01:06 okay... I'll see and report the details about the same 19:01:11 we have some neuroscience researchers here in the team, so we can use our affiliations etc 19:01:31 great, it's not super important, but if we do get INCF endorsed, that'll help a lot with outreach 19:01:39 #action MeWjOr look at INCF endorsement 19:02:11 OK, some good ideas there. We can see at the next meeting how it affected things 19:02:36 #action FranciscoD MeWjOr gicmo mhough bt0 : discuss effects of our measures at the next meeting 19:02:51 MeWjOr: I can reach out yeah 19:03:00 gicmo: that'd be awesome, thanks :D 19:03:20 even if they can tell us what improvements they want to use Fedora/NeuroFedora, we will have something to work on 19:03:28 gicmo++ 19:03:28 FranciscoD: Karma for gicmo changed to 2 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 19:03:29 Thanks a lot gicmo ... you're awesome 19:03:38 gicmo++ 19:03:38 MeWjOr: Karma for gicmo changed to 3 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 19:03:43 #action gicmo reach out to folks at g-node for feedback/comments on NeuroFedora 19:04:00 #topic Next meeting: date, time, chair 19:04:07 two weeks? same time? 19:04:12 ++ 19:04:28 Sounds good 19:04:29 MeWjOr: will you chair? 19:05:07 yep... I'll do it 19:05:07 I am talking to INCF about membership for NeuroTechX 19:05:34 mhough: nice, if NeuroFedora can fit in anywhere, do let us knwo 19:05:40 we're not neuro-imaging ready yet, though 19:05:46 #action MeWjOr chair next meeting 19:05:48 Yeah will do 19:05:53 #info Next meeting in 2 weeks, same time 19:06:03 OK, let's close, we're 5 minutes over! 19:06:09 If there's nothing else, I'll close in a minute 19:06:22 #action FranciscoD send out logs etc 19:06:26 FranciscoD: let me know if you want to chat neuroimaging 19:06:39 mhough: yeh, let me e-mail you and we can perhaps fix a time? 19:06:52 MeWjOr: how's your week looking, would you have time for a video call too? 19:06:56 maybe this or next week 19:06:56 Ok np 19:06:57 ? 19:07:06 Sure 19:07:07 I already seem to have plenty of meetings this week XD 19:07:19 nilearn dev days this week BTW 19:07:23 #action FranciscoD e-mail folks for a neuro-imaging focussed meeting setup 19:07:26 video call + IRC? 19:07:29 Yeh, saw that, forwarded it to some folks 19:07:32 I could try.. 19:07:42 MeWjOr: if it's only 2-3 of us, just an informal video chat would be OK 19:07:58 OK, I'll send you folks a whenisgood 19:08:02 OK 19:08:05 yep... sounds great for me 19:08:13 OK, closing now then. 19:08:16 #endmeeting