05:30:54 #startmeeting i18n 05:30:54 Meeting started Mon Oct 17 05:30:54 2022 UTC. 05:30:54 This meeting is logged and archived in a public location. 05:30:54 The chair is paragan. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 05:30:54 Useful Commands: #action #agreed #halp #info #idea #link #topic. 05:30:54 The meeting name has been set to 'i18n' 05:30:54 #meetingname i18n 05:30:54 #topic agenda and roll call 05:30:54 The meeting name has been set to 'i18n' 05:30:55 #link https://fedoraproject.org/wiki/I18N/Meetings/2022-10-17 05:31:08 Hi 05:31:14 hello 05:31:36 hi 05:31:46 #chair tagoh[m] JensPetersen[m] SudipShil[m] 05:31:46 Current chairs: JensPetersen[m] SudipShil[m] paragan tagoh[m] 05:31:53 hi 05:31:56 hello 05:32:02 #chair pwu suanand 05:32:02 Current chairs: JensPetersen[m] SudipShil[m] paragan pwu suanand tagoh[m] 05:32:13 Hi all 05:32:27 hmm my client is still on EU time... 05:32:45 #topic Upcoming schedule 05:33:10 #info Tue 2022-10-25 Current Final Target date 05:33:33 As you know we are still in Fedora 37 Final Freeze 05:33:58 Release of F37 delayed by 1 week 05:34:21 current date of release scheduled is 2022-10-25 05:34:56 You can check the current status of bugs blocking F37 release 05:34:57 https://qa.fedoraproject.org/blockerbugs/milestone/37/final/buglist 05:36:33 anything to discuss here in this topic? 05:37:34 Looks under control? 05:38:09 for us no important issues there 05:38:49 Anyone have any concerns for f37 currently? 05:39:19 I should really rebase soon now 05:40:34 I guess not 05:40:53 not particularly. that looks woring fine so far. 05:41:00 s/woring/working/ 05:41:33 at least for me 05:41:39 okay 05:42:48 moving to next topic 05:42:58 #topic Issues 05:42:58 #info #168: Fedora 35 Bug triaging (pnemade) 05:42:58 #link https://pagure.io/i18n/issue/168 05:43:56 Still 31 bugs 05:44:13 we got one more month to triage them 05:44:23 22nd Nov is F35 EOL 05:44:46 Hope to see soon bug assignee helping to triage these bugs 05:46:55 anything to discuss here if not lets move to next issue 05:48:20 #info #170: F37 Change: Gettext Runtime Subpackage (suanand) 05:48:20 #link https://pagure.io/i18n/issue/170 05:49:00 anything to discuss for this Change implementation? 05:49:29 Has release notes submitted for this Change? 05:50:38 Yes, release notes are submitted.. 05:50:51 thanks for confirming 05:51:44 moving to next issue 05:52:00 #info #171: F37 Change: Firefox Langpacks Subpackage (petersen) 05:52:01 #link https://pagure.io/i18n/issue/171 05:52:06 anything to discuss for this Change implementation? 05:52:53 I think next time we should submit a single collective PR for i18n change 05:53:02 for relnotes 05:53:26 well individual should also work 05:53:28 We currently have 3+ conflicts PRs adding the I18N section... 05:53:39 its just that Fedora documentation team is not much active 05:54:08 Individual contribute text or a commit 05:54:09 Ugh 05:54:15 commit 05:54:17 Individuals can contribute content or a commit I htink 05:54:24 In one PR 05:54:37 we have been doing individual PR since some releases 05:54:49 I know 05:55:02 this release I have seen very much less response from Fedora Documentation team 05:55:14 So I am suggesting we change this for F38 05:55:28 Sure we can do that way also 05:55:31 Dunno - it always seems to happen quite late in the cycle anyway 05:55:58 Fedora Documentation team never care to branch on time for submitting release notes 05:56:19 hence delay always occurs 05:56:23 Right - that's why this time I feel a unified PR makes more sense 05:56:55 I assume they are "unresourced" 05:57:13 So a single PR may also make their life easier 05:57:30 Okay 05:57:37 can someone volunteer for this? 05:58:04 I can help from next release 05:58:30 I meant from F38 yes 05:58:51 Ok 05:58:53 Though we could also do it for this round if we want 05:58:54 maybe we can coordinate in pagure ticket first and then create PR? 05:58:59 Exactly 06:00:20 https://pagure.io/fesco/issue/2868 06:00:39 I think it is pretty much impossible to do the i18n relnotes individually separately without causing merge conflicts 06:00:43 if someone want to do it for this time, please help 06:01:14 Okay 06:01:20 anything more to discuss? 06:02:12 moving to next issue 06:02:20 #info #172: F37 Change: IBus 1.5.27 (fujiwara) 06:02:20 #link https://pagure.io/i18n/issue/172 06:02:28 anything to discuss for this Change implementation? 06:02:50 is the release notes text ready for this Change? 06:03:14 I would welcome that relnotes automation though - though not sure how it will conclude... 06:04:24 I think IBus release notes need to be written 06:04:41 hopefully Change owner will find some time soon 06:05:14 anything to discuss here for this Change? 06:06:33 probably not so moving to next issue 06:06:41 #info #173: F37 Change: ibus-libpinyin 1.13 (pwu) 06:06:42 #link https://pagure.io/i18n/issue/173 06:06:55 is the release notes text ready for this Change? 06:07:31 https://pagure.io/fedora-docs/release-notes/pull-request/885 06:07:51 pwu, Thank you 06:08:11 welcome 06:09:26 anything to discuss here? 06:10:47 moving to next topic 06:10:49 #topic Open Floor 06:12:04 Also I think good to link the PRs into the relnotes Change tickets 06:13:10 I guess there is a chance that F37 may be released before our next meeting 06:15:20 anyone got any topic to discuss here? 06:16:39 I assume nothing to discuss here. 06:16:47 Thank you for joining this meeting 06:16:53 #endmeeting