16:00:16 #startmeeting NeuroFedora 2020-02-25 16:00:16 Meeting started Tue Feb 25 16:00:16 2020 UTC. 16:00:16 This meeting is logged and archived in a public location. 16:00:16 The chair is MeWjOr. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:16 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:00:16 The meeting name has been set to 'neurofedora_2020-02-25' 16:00:29 #meetingname neurofedora 16:00:29 The meeting name has been set to 'neurofedora' 16:01:09 #chair MeWjOr FranciscoD gicmo bt0 dan1mal alciregi 16:01:09 Current chairs: FranciscoD MeWjOr alciregi bt0 dan1mal gicmo 16:01:25 .fasinfo 16:01:28 dan1mal: (fasinfo ) -- Return information on a Fedora Account System username. 16:01:34 .fasinfo dan1mal 16:01:35 dan1mal: User: dan1mal, Name: Danny Lee, email: dreamer@panix.com, Creation: 2019-07-29, IRC Nick: dan1mal, Timezone: UTC, Locale: en, GPG key ID: B2D41DBDBC0206EA, Status: active 16:01:37 Please feel free to add yourselves to the chair (in case I missed someone) 16:01:38 dan1mal: Approved Groups: neuro-sig packager fedorabugs qa cla_done cla_fpca 16:01:45 #topic Agenda Summary 16:02:06 o/ 16:03:07 #info https://lists.fedoraproject.org/archives/list/neurofedora@lists.fedoraproject.org/thread/S3P27DFONJTKADIPJNNOVEQSYRQHOR35/ 16:03:17 #info Introductions and roll call 16:03:21 #info Tasks from last meeting 16:03:28 #info Pagure tickets 16:03:34 #info Bugs 16:03:43 #info Neuroscience query of the week https://pagure.io/neuro-sig/NeuroFedora/issue/318 16:03:47 #info Open floor 16:03:59 #topic Introductions and roll call 16:04:15 A quick roll-call, and let's move forward 16:04:23 .fasinfo major 16:04:25 MeWjOr: User: major, Name: Aniket Pradhan, email: aniketpradhan1999@gmail.com, Creation: 2019-02-09, IRC Nick: MeWjOr, Timezone: Asia/Kolkata, Locale: en, GPG key ID: None, Status: active 16:04:28 MeWjOr: Approved Groups: qa neuro-sig fedorabugs packager wikiedit cla_done cla_fpca 16:04:33 .fasinfo dan1mal 16:04:49 dan1mal: User: dan1mal, Name: Danny Lee, email: dreamer@panix.com, Creation: 2019-07-29, IRC Nick: dan1mal, Timezone: UTC, Locale: en, GPG key ID: B2D41DBDBC0206EA, Status: active 16:04:52 dan1mal: Approved Groups: neuro-sig packager fedorabugs qa cla_done cla_fpca 16:05:37 .fasinfo ankursinha 16:05:55 @ping 16:06:02 hrm, oh well 16:06:04 FranciscoD: User: ankursinha, Name: Ankur Sinha, email: sanjay.ankur@gmail.com, Creation: 2008-05-28, IRC Nick: FranciscoD, Timezone: Europe/London, Locale: en_GB, GPG key ID: E629112D, Status: active 16:06:07 FranciscoD: Approved Groups: @scitech_sig @wikiedit provenpackager +packager robotics-sig @ask-fedora scitech @neuro-sig @fedora-join cla_fedora cla_done fedorabugs @freemedia @gitfedora-tour cla_fpca @gitfpaste +qa 16:06:13 ah 16:07:04 Next topic? 16:07:12 #topic Tasks from last meeting on 2020-02-11 16:07:29 #info Minutes: https://meetbot.fedoraproject.org/fedora-neuro/2020-02-11/neurofedora.2020-02-11-16.04.html 16:08:37 #info MeWjOr write event report, send to ML, submit to Mindshare --- Written a draft so far... Will review and add more stuff soon 16:08:47 #info MeWjOr e-mail ML with other discussion points that came up during FOSDEM --- Done 16:09:05 please re-assign tasks that we haven't completed 16:09:13 * FranciscoD has lots of incomplete tasks this time :/ 16:09:46 #info LoKoMurdoK file ticket with Mindshare requesting some NeuroFedora swag --- waiting for a reply from mindshare 16:10:08 #info FranciscoD ask bt0 alciregi if they know how badges are to be given out manually --- In progress? 16:10:33 no, we know now 16:10:54 Ahh... 16:10:57 #undo 16:10:57 Removing item from minutes: INFO by MeWjOr at 16:10:08 : FranciscoD ask bt0 alciregi if they know how badges are to be given out manually --- In progress? 16:11:06 #info Once the badge has been imported to badges, I'll be able to award them: https://pagure.io/fedora-badges/issue/678#comment-628475 16:11:12 #info FranciscoD ask bt0 alciregi if they know how badges are to be given out manually --- Done. 16:11:19 #info LoKoMurdoK comment on the ticket thanking riecatnor and asking what needs to be next: how do we give the badges out, manually to start with. --- done. Waiting for the badges team to push the badge online 16:11:55 #info Everyone look for nice brain images with a CC license for the banner image --- let's do this over this week? 16:12:00 also, we have a few +1s on the swag ticket. Needs a ping 16:12:08 yep... 16:12:12 MeWjOr: yes, that one is still pending, please -reassing 16:12:16 I'll ping there.. 16:12:22 er s/reassing/reassign/ XD 16:12:35 #action MeWjOr ping on the mindshare ticket for swag 16:12:43 MeWjOr: probably better to action lbazan to do it, since it's his request? 16:12:55 #action Everyone look for nice brain images with a CC license for the banner image 16:13:26 umm... how do I undo that action? 16:13:33 #undo 2 16:13:33 Removing item from minutes: ACTION by MeWjOr at 16:12:55 : Everyone look for nice brain images with a CC license for the banner image 16:13:38 #undo 16:13:38 Removing item from minutes: ACTION by MeWjOr at 16:12:35 : MeWjOr ping on the mindshare ticket for swag 16:13:44 ah, a stack 16:13:47 * FranciscoD didn't know that 16:13:48 #action lbazan ping on the mindshare ticket for swag 16:13:52 #action Everyone look for nice brain images with a CC license for the banner image 16:14:01 Lol 16:14:17 #info FranciscoD take care of all the other tickets this week --- I'll help you with this.... 16:14:25 heh 16:14:52 #action FranciscoD, MeWjOr take care of all the other tickets this week 16:15:15 yeh, suitably vague task XD 16:15:16 #info FranciscoD write abstract for CNS*2020 this week also --- did you write it? 16:15:28 have a draft, but not ready to send out yet 16:15:34 suitable for me... :P 16:15:43 had to prioritise the gsoc proposal etc 16:15:53 please re-assign, hopefully will get it done this week 16:16:00 #action FranciscoD finalize the draft of the abstract for CNS*2020 this week also 16:16:30 #info FranciscoD add some packaging tickets to kanban for folks to test out --- You added the FTBFS bugs, so great 16:16:45 #info FranciscoD send a list of FTBFS bugs to ML --- done. ^.^ 16:16:51 Oo, abstract submission closes on 4th Jan, This is high priority now, yikes 16:17:02 4th jan? 16:17:10 March, you mean? 16:17:31 #info FranciscoD send out logs, update tickets --- done. 16:17:43 yeh, march 16:17:56 my brain's gone for a walk, sorry 16:18:13 :P 16:18:17 moving on... 16:18:55 I posted some links with brain images, maybe ill pull some and make mock banners? 16:19:39 I was thinking that we will use a single image - as it is - for the banner? 16:19:51 dan1mal: I think if we give the image we choose to the websites team, they'll be able to "bannerify" 16:20:17 since they'll crop it etc and add css and all that 16:21:04 #Topic Pagure tickets 16:21:14 #info https://pagure.io/neuro-sig/NeuroFedora/issues?status=Open&tags=S%3A+Next+meeting 16:21:29 The first issue is... 16:21:39 LinkedIn Group Research 16:21:53 #info LinkedIn Group Research https://pagure.io/neuro-sig/NeuroFedora/issue/338 16:21:57 dan1mal: it'll come in issues, let's discuss it then :) 16:22:03 * FranciscoD looks at the images in the meantime 16:22:23 Its real easy to make a group, if we get a few ppl to join up and start inviting people in the field i think it might gain traction 16:22:43 also it could be useful to add a link to our SIG page, if thats something we wanted to do. 16:22:57 dan1mal: sure, can you please create the group and we'll all join it 16:23:02 I think this is a great idea... It would definitely help in the promotion of the group 16:23:06 +1 16:23:22 adding to docs is easy, and we can also add it to the blog header with the other social links 16:23:28 when I search for neurofedora on linked in only one person came up morgan hugh 16:23:30 hough 16:23:43 yeh, that's from the previous iteration XD 16:23:51 I too was wondering of a Twitter account for the same... but that's for some other time, I believe... 16:23:57 but neuro science comes up with a lot of people/schools/organizations and articles 16:24:16 Its not actually a group, its a hit on his personal linked in - because he mentions it 16:24:28 MeWjOr: let's wait a bit for twitter: a passive twitter account isn't good, and we don't have enough domain folks to tweet constantly 16:24:35 I can make a group and perhaps post the link on the pagure post and we can start joining 16:24:43 so, dan1mal do I assign/action it to you? 16:24:51 labs and organisations hire people to manage their social media, so marketing requires resources to be put aside for it :/ 16:24:55 dan1mal: +1 16:25:07 create group, post group link. 16:25:29 #action dan1mal create the LinkedIn group and post it on the ticket. 16:25:31 I can populate the info page from our SIG info page and add links to our important resources (pagure, irc/telegram/meeting times) 16:26:05 also our lab once its up 16:26:19 dan1mal: +1: neuro.fp.o and neuroblog.fp.o would be sufficient 16:26:27 that way, we don't have to keep multiple pages up to date 16:26:42 ok, will do! 16:26:45 keep docs + blog up to date as primary sources of info, and link everything to them 16:27:12 👏 16:27:15 great 16:27:41 #info Once the group is active, we will have to add it to neuro.fp.o as well 16:28:04 neuro{,blog}.fp.o 16:28:36 #undo 16:28:36 Removing item from minutes: INFO by MeWjOr at 16:27:41 : Once the group is active, we will have to add it to neuro.fp.o as well 16:28:45 #info Once the group is active, we will have to add it to neuro{,blog}.fp.o as well 16:28:58 next issue then? 16:29:04 issue++ 16:29:13 Next issue is: 16:29:27 #info Estimating team resources: https://pagure.io/neuro-sig/NeuroFedora/issue/337 16:29:55 That totals up to about 12--16 hours per week 16:30:07 for the whole team, at the moment. Which isn't a lot tbh 16:30:22 So, our tasks and plans must be made so that they can be done in this time 16:30:45 ++ 16:30:47 Matching people to their skills is also something we'll have to do. For instance, at the moment only MeWjOr and I are doing a majority of the packging 16:31:02 but that'll improve as we get more folks involved, and more of them learn packaging and other skills 16:31:05 Are there any estimate of how many activities we have that need to be done all the time, and those that are optional? 16:31:28 dan1mal: unfortunately, no. A lot of our tasks are "on-demand" 16:31:40 I guess writing a blog post per fortnight could be a "periodic" task, for example 16:32:04 but most of the software tasks come in spurts: as you've seen from the compose issues 16:32:07 Yeah, I'm sure its a lot of keeping up with new stuff coming down the pipeline 16:32:12 +1 16:32:32 Are there any other tasks than "write the blog update" that can be periodic? 16:32:43 +1 16:33:38 I cannot think of anything else that can be periodic 16:33:58 I agree that most work done by us is usually on-demand, or packaging related 16:34:02 hrm, yeh, neither can I 16:34:24 Do we have a way to ensure that a blog post goes out every 2 weeks at least? 16:34:49 Something like the CPE team's updates: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/JLIEHF3TTIAY6PY3MVHCMZBNVCN7FTZK/ 16:35:08 only, on our blog instead of the ML (or both if that's doable) 16:36:01 We could advertise for a "project update wrangler" 16:36:13 Someone that pokes the team to provide updates that will go into the post every two weeks? 16:36:37 keep us on our toes, ensure that we at least put out a blog post every 2 weeks as part of outreach/marketing? 16:37:21 I am not sure where would we advertise for the position, though? 16:37:42 oh, the blog and the MLs 16:38:10 https://neuroblog.fedoraproject.org/2019/08/07/open-position-neurofedora-is-looking-for-a-spin-lab-master.html 16:38:13 like that 16:38:20 ohh... 16:38:29 isn't that what got you interested dan1mal ? 16:38:43 Actually yes 16:38:58 yay, 100% return on that post XD 16:39:01 very rare 16:39:04 dan1mal++ 16:39:05 FranciscoD: Karma for dan1mal changed to 1 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 16:39:06 .thank dan1mal 16:39:11 FranciscoD thinks dan1mal is awesome and is happy they are helping! (Please also type dan1mal++ since that is what gives them a cookie) 16:39:21 ohh... lol 16:39:25 Definitely draws people who might not be involved yet in. We need more ppl that arent necessary CS or neuroscience majors 16:39:31 +1 16:39:41 thank you! thankyoU! :) 16:39:47 and we definitely need folks who know some marketing :) 16:40:24 It would be interesting to see if after the spin page comes out, maybe we could get some coverage in a neuroscience/science magazine. 16:40:42 I guess we can discuss this topic in the open floor, as well... Let's move on further with the rest of the issues? 16:40:48 MeWjOr++ 16:40:58 Mewj0r++ 16:41:09 all right... moving on 16:41:10 dan1mal: as soon as I submit my PhD dissertation, I intend to write a paper on NeuroFedora 16:41:10 Keep us on track! :) 16:41:36 #info Use teams.fedoraproject.org (Taiga) kanban board for better planning --- https://pagure.io/neuro-sig/NeuroFedora/issue/336 16:41:39 How far along are you? Those are years long projects arent they? For phDs 16:42:12 we had been using it, and it definitely has a better interface as compared to bugzilla (for monitoring the status of tickets) 16:42:30 yeh, but let's close it and leave folks free to organise their tasks as they wish for the time being. 16:42:46 yep... I too was going to say that.. :P 16:43:01 dan1mal: I'm writing up, will submit next month. Been > 5 years now 🤯 16:43:37 #info The next issues are for the comp-neuro lab... Featured apps, banner images, screenshots, summary and content 16:43:37 MeWjOr: +1 to close then 16:43:57 MeWjOr: let's look at the banner first? 16:44:15 I really like this one: https://www.piqsels.com/en/public-domain-photo-ffpsl 16:44:39 and this gets my second vote: https://www.piqsels.com/en/public-domain-photo-fblot 16:45:27 along with https://www.piqsels.com/en/public-domain-photo-ffbsb but I'm not sure how this will look as a rectangular banner 🤔 16:45:31 Wow! Coming to fruition! Congratulations! 🙌🏼 16:46:01 ach,,, piqsels is loading slowly for me... 16:46:10 they're quite huge images :) 16:46:21 yeah, its quite slow. 16:46:24 dan1mal: thanks! :D 16:46:53 anyways, can you comment these images on the ticket? It would be great to evaluate the available options on a single screen 16:48:36 doing so now 16:48:45 pagure.issue.edit -- major edited the close_status and status fields of ticket neuro-sig/NeuroFedora#336 https://pagure.io/neuro-sig/NeuroFedora/issue/336 16:48:46 pagure.issue.comment.added -- major commented on ticket neuro-sig/NeuroFedora#336: "Use teams.fedoraproject.org (Taiga) kanban board for better planning" https://pagure.io/neuro-sig/NeuroFedora/issue/336#comment-628706 16:48:50 ahh... great 16:48:58 I'll try to look some more as well 16:49:22 The next ticket is about FOSDEM 16:49:24 #info https://pagure.io/neuro-sig/NeuroFedora/issue/307 16:50:41 I'll try to make some amends to the report and notify people here too... I am also moving to a platform which supports RSS... My current site would require a bit more work for that 16:51:06 Next ticket: 16:51:18 #info Figure out badges rule to award badge automatically to pagure group members: https://pagure.io/neuro-sig/NeuroFedora/issue/250 16:51:19 pagure.issue.comment.added -- ankursinha commented on ticket neuro-sig/NeuroFedora#330: "Banner Image for the lab webpage." https://pagure.io/neuro-sig/NeuroFedora/issue/330#comment-628709 16:51:44 MeWjOr: let's put this one off for a few weeks. Once I can give the badges manually, we'll work on automation 16:51:55 I suggest we tag it as "future meeting" and come back to it later 16:52:11 All right... let's look it up later then 16:52:19 pagure.issue.tag.added -- major tagged ticket neuro-sig/NeuroFedora#250: S: Future meeting https://pagure.io/neuro-sig/NeuroFedora/issue/250 16:52:20 pagure.issue.tag.removed -- major removed the S: Next meeting tags from ticket neuro-sig/NeuroFedora#250 https://pagure.io/neuro-sig/NeuroFedora/issue/250 16:52:28 great, next topic then... 16:52:39 #topic Open bugs 16:52:50 #info Open bugs: https://tinyurl.com/neurofedora-bugs 16:53:14 The one that is holding up neuro fedora in the f32?33? rawhide build 16:53:44 FTBFS? 16:53:50 paraview iirc 16:53:52 let me look 16:54:22 A bug has been filed: https://bugzilla.redhat.com/show_bug.cgi?id=1799847 16:54:26 not fixed yet 16:54:34 https://koji.fedoraproject.org/koji/packageinfo?packageID=2729 16:54:52 Since paraview is an extra analysis tool, I was wondering if we should drop it from the ISO for the time being? 16:54:59 it isn't a featured app either 16:55:07 and folks can install it from the repositories if they need to anyway 16:55:35 If it fails to build for rawhide, wont that mean it wont build when people try to install later? (on f32) 16:55:50 dan1mal: well, the maintainers will have time to fix it 16:55:58 the compose on the other hand needs to pass much before release 16:56:12 I think that dropping would be a reasonable course of action. 16:56:20 +1 16:56:27 +1 16:56:32 it isn't one of our packages either, so we've got to wait for the maintainer 16:56:40 we can look into it, but we have quite a lot on our plates already 16:56:46 +1 to drop also 16:57:15 great then 16:57:17 oo, we get to use the zodbot agreed command? 16:57:25 #agree? 16:57:30 #agree 16:57:33 #agreed 16:57:35 ach 16:57:38 followed by what we agreed on 16:57:49 I think 16:57:51 #agreed Drop paraview from the image 16:57:55 #agree Drop paraview from the image 16:58:08 https://fedoraproject.org/wiki/Meeting:Guide#MeetBot_Commands -> agreed 16:58:10 nice 16:58:16 #info We agree on drop[ing paraview from the image 16:58:21 #undo 16:58:21 Removing item from minutes: INFO by MeWjOr at 16:58:16 : We agree on drop[ing paraview from the image 16:58:24 XD 16:58:38 #info We agree on dropping paraview from the image 16:58:43 better 16:59:03 dan1mal: would you make a PR on this repo to remove it? https://pagure.io/fedora-kickstarts 16:59:17 chance to practice some git, and I'll be online to help if you need it? 16:59:37 we* 16:59:37 Ok sounds good 16:59:48 great 17:00:12 #action dan1mal Make a PR on fedora-kickstarts to remove paraview from the image 17:00:29 Any other important bugs? 17:00:44 nothing urgent iirc 17:00:51 we're doing OK with the FTBFS bugs mostly 17:00:57 https://teams.fedoraproject.org/project/neurofedora-ftbfs-bugs-f32/kanban 17:01:02 got only a few left 17:01:03 I only see a few Py3.9 failures... I can pick them up in the future 17:01:14 Yep 17:01:21 +1, we'll move on to them once the FTBFS ones are sort of done 17:01:30 great 17:01:37 moving on... 17:01:44 #info FTBFS bugs are in control: https://teams.fedoraproject.org/project/neurofedora-ftbfs-bugs-f32/kanban 17:02:12 Do we have time for the neuroscience query of the week (NQoW)? 17:02:29 Not really, we've over time, let's skip it this time 17:02:32 yep 17:02:42 NQoW++ 17:02:50 #topic Next meeting --- Time and Chair 17:02:53 :P 17:02:56 in 2 weeks? 17:02:58 same time 17:03:00 ? 17:03:00 +1 17:03:03 +1 17:03:13 dan1mal, would you like to chair this time? 17:03:32 🙂 ok 17:03:36 yay! 17:03:44 Lol, its like pressure, like a job interview 17:03:47 great 17:03:50 :P 17:03:52 haha, no, no pressure at all :) 17:04:03 do whatever you're comfortable with 17:04:12 #action dan1mal will chair the next meeting 17:04:13 we'll just keep poking to see if you want to do something new ;) 17:04:14 Hehe, thats what they say about job interviews, just be yourself...guess I need the practice! 17:04:35 #info next meeting will take place on 10th March 2020, same time (1600 UTC) 17:04:53 I guess this concludes this meeting 17:05:00 #endmeeting