09:00:37 #startmeeting infrastructure 09:00:37 Meeting started Tue Feb 18 09:00:37 2020 UTC and is due to finish in 60 minutes. The chair is freesky-edward. Information about MeetBot at https://openeuler.org/en/meetings.html. 09:00:37 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 09:00:37 The meeting name has been set to 'infrastructure' 09:00:43 hi 09:00:52 freesky-edward: Hi 09:01:02 imjoey, hi, how are you? 09:01:24 all is good. how about you? 09:01:38 all is fine 09:02:03 are you at office or at home? 09:02:13 It seems only us in . 09:02:17 at home 09:02:29 it seems 09:02:55 let us wait for one moment 09:03:09 ok 09:03:33 tommylikehu_: hi, good to see you. 09:03:33 hi tommylikehu_ 09:03:39 hi 09:04:25 ok, there is not many things except one topic. please refer to https://gitee.com/openeuler/infrastructure/wikis/Meeting%20Schedule?sort_id=1610120 09:04:47 of course, if you have any topic, we can add it now 09:05:17 #topic Add zhongjun2 to maintainer group 09:05:49 this is exactly to say a proposal from tommylikehu_ 09:06:01 yeah. 09:06:34 https://gitee.com/openeuler/community/pulls/135 09:06:55 I think she did a great job on setting up our promethus system 09:07:46 that's really awesome work, imo. 09:07:57 yeah, I sent an email for this proposal, and got three +1 now 09:08:36 that's more than a half 09:08:48 let's vote again here 09:09:17 sure 09:09:26 #startvote do agree to add zhongjun2 as maintainers of infra? (+1,0, -1) 09:09:26 Begin voting on: do agree to add zhongjun2 as maintainers of infra? Valid vote options are , +1, 0, -1, . 09:09:26 Vote using '#vote OPTION'. Only your last vote counts. 09:09:41 #vote +1 09:09:46 #vote +1 09:09:56 #vote +1 09:09:59 hey zhongjun2_ 09:10:03 zhongjun2_: Hi, welcome. 09:10:09 hello all 09:10:10 hi, zhongjun2_ 09:11:28 let's hold on for a moment, please throw it out if you have any question for this topic. thanks 09:11:39 hi freesky-edward tommylikehu_ imjoey 09:12:06 #endvote 09:12:06 Voted on "do agree to add zhongjun2 as maintainers of infra?" Results are 09:12:06 +1 (3): freesky-edward, tommylikehu_, imjoey 09:12:16 okay, passed 09:12:31 let's celebrate 09:12:34 Thanks It's my pleasure 09:12:43 yep. congrats to zhongjun2_ 09:13:16 imjoey, tommylikehu_ could you please give your review comment for this PR https://gitee.com/openeuler/community/pulls/135 09:13:23 congrats zhongjun2_ 09:14:08 #topic open discussion 09:14:16 imjoey: sure 09:15:08 freesky-edward: maybe tommylikehu_ needs rebase that pr before merged. 09:15:25 yeah working on 09:15:38 tommylikehu_: thanks. 09:16:27 BTW, our published the blog system, please test and you are welcome to submit any post. 09:16:33 http://blog.openeuler.org/ 09:16:44 this is the link 09:16:50 hi, sorry for being late 09:17:00 please continue and I will catch up 09:17:01 fred_li, hi 09:17:07 fred_li: Hi 09:17:48 The blog is still in trial phase and feel free to try, review and submit your suggestion or proposal. thanks 09:17:55 fred_li, we voted for adding zhongjun2 as the maintainers, though the process is end, you can also give your comments. thanks 09:18:41 I have +1. 09:18:54 fred_li, thanks 09:18:57 thanks :) 09:19:20 ok, let move to next 09:19:24 The commit has conflicts and I asked @tommylikehu_ who submitted the PR to handle. Hopefully he will have time. 09:19:51 tommylikehu_ do you have anything to sync for the OBS open? 09:19:57 @zhongjun2_ We all appreciated your work 09:20:05 fred_li: done 09:20:35 hmm, I was going to setting up another backend for our home project as we discussed before 09:20:51 fred_li: Thank you!! became the core member again haha , supprise 09:20:51 but now I am working on the x86 performance issue now 09:21:40 tommylikehu_, could you give a little more detailed introduction for your design? so that everyone can understand more, thanks 09:22:18 Or you can share your design/idea document if you have. 09:22:33 especially, why to set up another backend, and how is working. 09:22:40 ok, the background is we are going to open OBS to public 09:23:12 but we also need guarantee the resource that will be used for our main projects 09:23:50 so we need to setting up another backend(including all of the backend services) for main projects, that's copied from opensuse's deployment 09:24:52 and the tech detail can be found: https://openbuildservice.org/help/manuals/obs-admin-guide/obs.cha.installation_and_configuration.html#_distributed_setup 09:25:19 that's is to say, we would setting another new backend for any logined user 09:25:20 fred_li, +1, that would be a good practice if there being a design docs for this update in infrastructure project 09:25:43 will do 09:25:54 #link https://build.opensuse.org/monitor 09:26:12 This is another link to understand how openSUSE OBS works now. 09:26:13 tommylikehu_ great jobs, thanks 09:30:00 https://gitee.com/openeuler/community/pulls/135 this path needs another lgtm label 09:30:32 ping 09:30:50 okay 09:30:53 I did 5 days ago :-) 09:31:25 fred_li syncing issue :) 09:32:17 let's continue 09:32:28 any other thing are you going to discuss? except blog and OBS 09:32:53 imjoey: 09:33:18 I've one about renaming repo via ci-bot. 09:33:22 do you have anything to sync regarding testing developing process on gitee? 09:33:47 I am thinking of sending weekly report to all the community members about what infrastructure team is working on and what is still pending. 09:34:09 If anyone wants to join un for help, he needs to understand the current situation. 09:34:25 fred_li: great! 09:34:58 fred_li: yep, that would be great. 09:36:04 #link: #link: https://gitee.com/oschina/git-osc/issues/I18R3F gitee has officially supported renaming both the path and name of a repo today. But there still some issues about the gitee OpenAPI. 09:37:34 I found an issue that the new API to change a repository always return 400 with a error message 'path is missing' . 09:38:09 I was curious that if it would affect our ci-bot currently. 09:38:15 fred_li fine, I would like to send the email if you agree. 09:39:31 +1 and big thanks @freesky-edward 09:39:32 imjoey it indeed affect the bot now, we are still researching in how to fix it. 09:39:54 good news. liwen from gitee official left a new comment about the issue and will resolve it tonight. 09:39:56 now, the bot cannot create the repo via API 09:40:04 Just a minute ago. 09:40:16 cool Liwen 09:40:38 nice 09:40:57 unfortunately, he did a breaking change for the OpenAPI. 09:42:42 I'll follow that issue and to ensure everything will be fine again. 09:43:30 freesky-edward: Could you please provide the error message about repo creation failure? 09:43:48 imjoey, do you know waht kind changes it had? 09:44:19 error message i got is '400 bad request' 09:45:23 Honestly, the changes are to enable updating both the name and path of a repository. IMO, it should never affect other APIs, such as repo creation. 09:45:53 ok, looks fine 09:45:58 thanks imjoey 09:47:31 while, the release of the updated API seems not well tested. :) 09:47:56 it may be 09:49:15 #link: https://gitee.com/oschina/git-osc/issues/I19N86?from=project-issue I also request an issue to Gitee-Feedback for asking support for disabling comment to a repo. 09:49:37 I will add that functionality once OpenAPI is ready. 09:50:07 imjoey thanks so much 09:50:30 my pleasure. 09:52:16 do you have other topics? 09:52:56 not any more. 09:53:08 I don't have now 09:53:37 ok, that's all, thanks you all, see you next time 09:53:47 see you all 09:53:49 See you guys. 09:53:50 bye 09:53:55 bye 09:54:15 #endmeeting