05:30:05 #startmeeting i18n 05:30:05 Meeting started Tue Apr 23 05:30:05 2019 UTC. 05:30:05 This meeting is logged and archived in a public location. 05:30:05 The chair is paragan. Information about MeetBot at http://wiki.debian.org/MeetBot. 05:30:05 Useful Commands: #action #agreed #halp #info #idea #link #topic. 05:30:05 The meeting name has been set to 'i18n' 05:30:05 #meetingname i18n 05:30:05 The meeting name has been set to 'i18n' 05:30:05 #topic agenda and roll call 05:30:05 #link https://fedoraproject.org/wiki/I18N/Meetings/2019-04-23 05:30:23 hi .. 05:30:29 hi 05:31:35 hi 05:31:56 hi 05:32:03 .hello2 05:32:04 petersen: petersen 'Jens Petersen' 05:32:24 Hi 05:32:31 #chair suanand fujiwarat epico petersen mfabian 05:32:31 Current chairs: epico fujiwarat mfabian paragan petersen suanand 05:32:37 Hi all 05:33:20 hi 05:33:40 #chair pravins 05:33:40 Current chairs: epico fujiwarat mfabian paragan petersen pravins suanand 05:33:43 let's start 05:33:53 #topic Upcoming schedule 05:34:00 #info 2019-04-16 Final Freeze (*) 05:34:09 so we are in final freeze already 05:34:53 Have anyone found any important issues in Fedora 30? 05:35:32 #info the current blocker bug status is at https://qa.fedoraproject.org/blockerbugs/milestone/30/final/buglist 05:36:57 the latest F30 tree available for testing is 20190422.n.1 05:38:35 Hopefully we will get Fedora 30 released on 30th April :) 05:38:42 Fedora 30 Release Readiness meeting is on 25th April 05:39:15 if there is nothing to discuss here related to F30 release then let's move to tickets 05:40:21 #topic Outstanding issue 05:40:21 #info #107: Docs Beats for Fedora 30 (pnemade) 05:40:21 #link https://pagure.io/i18n/issue/107 05:40:40 This has been worked on last week 05:41:28 #info https://pagure.io/fedora-docs/release-notes/pull-request/316 05:41:59 Thanks! 05:42:09 paragan++ 05:42:10 epico: Karma for pnemade changed to 2 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 05:42:15 Has there anyone still want to add some release notes? 05:42:24 epico++ thanks for your notes 05:42:27 paragan: Karma for pwu changed to 1 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 05:45:00 Let's close this when we will have F30 released 05:45:07 moving to next ticket 05:45:38 #topic No assignee issues 05:45:38 #info #108: add Fedora CI tests to our important packages (petersen) 05:45:38 #link https://pagure.io/i18n/issue/108 05:46:20 anyone worked on adding CI tests? 05:46:49 how to trigger CI event? 05:47:13 I import some tests for opencc, but not enable gating yet. 05:47:37 How to run the ansible script? 05:48:22 you don't have to run anything 05:48:45 just try scratch-build of that package and it will run CI tests 05:49:05 Thanks again! :) 05:52:38 how about other members? 05:53:43 paragan, yes tried for liberation-fonts 05:54:09 epico, in test dir just create test.yml(ansible playbook). whenever you try to build you package your CI test will get triggered 05:54:10 vishal_vvr, nice. So are the tests running fine? 05:54:51 paragan, failing due to bug in source font package :P 05:54:56 vishal_vvr: thanks! :) 05:55:08 that means my CI works 05:55:18 its failing due to error in font file 05:55:24 oh 05:55:46 thanks paragan for pointer of scratch build. 05:56:02 So what is wrong? 05:57:29 Who is planning to work on CI next? 05:58:22 petersen, CI will only pass when my source file bugs will get fixed. already fixed it will push into release then CI will pass 05:59:03 cool 05:59:31 Was just curious 05:59:51 :) 06:00:56 if there is nothing more to discuss, let's move to last ticket 06:02:33 #info #105: Fedora 28 Bug triaging (pnemade) 06:02:33 #link https://pagure.io/i18n/issue/105 06:05:45 14 bugs as of now 06:07:05 Keep triaging and if needed moving to rawhide/f30 06:07:57 vishal_vvr: can the liberation-fonts bugs be moved? 06:08:50 petersen, yes doing the same 06:14:39 ok moving on 06:14:50 #topic Open Floor 06:14:57 anything to discuss here? 06:15:02 * petersen will test the gnome-initial-setup bug 06:15:34 Thanks! 06:17:34 Was just curious if we can create any local CI testing setup, because fedoraCI is like a black box we don't get to know what is running inside 06:18:00 almost push new test code 10 time and debugged the issue :P 06:18:28 Hard to debug eh? 06:18:59 vishal_vvr: any way to get more detailed output? 06:19:10 did you try ansible-playbook tests.yml? 06:19:43 yes we do get output, but don't know in which environment they are running test 06:20:55 like container image or qcow image 06:21:16 or dependencies already installed and etc 06:21:17 I think it is a VM? bicbw 06:21:37 Probably quite minimal by default 06:21:46 yes i feel so 06:25:03 I think let's close the meeting 06:25:11 thanks to all who joined this meeting 06:25:15 oh 06:25:54 I wanted to ask about this i18n meeting 06:26:06 Anything we should do to increase engagement and participation in this meeting? 8-) 06:29:06 maybe others can think on that and comeup with some suggestions by next meeting? 06:29:59 petersen, can we try rotating chair person for every meeting 06:33:24 #endmeeting