Hi folks,
Loop Lv bo in. It seems that Lv bo isn't aware of this discussion because he doesn't subscribe to the TSC mailinglist. BR, Huabing 原始邮件 发件人：CatherineLEFEVRE <catherine.lefe...@intl.att.com> 收件人：onap-tsc@lists.onap.org <onap-tsc@lists.onap.org>; 抄送人：FORSYTH, JAMES <jf2...@att.com>; 日 期 ：2018年10月18日 05:28 主 题 ：Re: [onap-tsc] TSC Escalation - AAI/ESR Committer issue. Thank you Kenny for bringing this issue to our attention. Thank you Alexis for your feedback. Speaking to Jimmy, AAI PTL, I understand that no new code was released related to AAI/ESR as part of the Casablanca release. The current challenge is to progress on the Security issues (even if the code did not change, the security criteria has increased including Severe). Therefore the immediate request is not the promotion of any AAI committer but the allocation of AA/ESR SME to fix these issues. As stated by Kenny, Lv Bo did not make any contribution yet but it will be a great opportunity for him to demonstrate his engagement on AAI/ESR before being eligible for committer election. Lv Bo – can you please confirm urgently your engagement, helping AAI team on Security issues, CII badging? Thank you. AAI/ESR Security issues – mainly Tomcat, jquery, bootstrap, dropwizard.jaws and our famous fasterxml.jackson, etc. Additional information can be provided as soon as an AAI/ESR SME starts to be engaged. I would also recommend to review the existing committers list in case of some of them have not been active during this release. In addition, what will be the future of AAI/ESR sub-project if the engagement is not confirmed? Many thanks & regards Catherine From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of Alexis de Talhouet Sent: Wednesday, October 17, 2018 2:06 PM To: onap-tsc@lists.onap.org Cc: FORSYTH, JAMES <jf2...@att.com> Subject: Re: [onap-tsc] TSC Escalation - AAI/ESR Committer issue. Hi, When it comes to define new committers for a given project, what I’ve seen happening before, and it worked fairly well, is to have the PTL of the project start a committer election of a week or two.. Contributors to the project can self-nominate themselves, and once nomination period is over, committers vote whether each nominee can become committer by assessing their involvement in the project (e.g. meritocracy). It is generally good to perform such committer election at the beginning of each release, as it allows to make sure we don’t have an un-healthy project with not enough committers, and also to recognize work that has been done during previous release. It is also good practice to refresh project’s committer list by making sure all committers are *active*. In this case, I would suggest to run a committer election within the project. That way, who ever feels then can take on the committer role can candidate. In the case no one show up, then it’s a different discussion. In the case ppl showing up don’t have any contribution to that specific project is up to the actual committers to decide what to do. Once new committers have been elected within the project, PTL sends a mail to TSC asking to vote on whether new committers can be approved or not. Knowing the background / history of the project, TSC should be able to judge the candidate accordingly, making sure the project can be in a healthy state. I don’t know who is aai/esr-* PTL, but committer election should be held. Lv Bo should step up (maybe some other will), the aai/esr-* committers vote, e.g. Li Zi and Sun QI vote, then PTL present to TSC with new potential committer(s), being, among other, Lv Bo. And we can have that as an TSC agenda item to discuss briefly whether we agree to have Lv Bo committer knowing the history. Regards, Alexis On Oct 16, 2018, at 10:03 PM, Kenny Paul <kp...@linuxfoundation.org> wrote: Jimmy tried to pursue the correct channels to resolve the following issue but he is stuck, so I'm formally escalating it to the TSC. Li Zi, (li.z...@zte.com.cn) has been the primary code contributor and Committer to the ESR sub project of AAI. She is no longer participating in the ONAP project and security fixes are required for the Casablanca Release. · Li Zi requested that Lv Bo (lv.bo...@zte.com.cn) be assigned as her replacement. This is not allowed as it violates sections 3.1.1 Contributor & 3.1.2 Committer of the ONAP Technical Community document: Committers cannot be appointed, they must be meritocracy elected from the pool of active Contributors to that project's repositories There is no record of Lv Bo ever making a contribution to the aai/esr-* repositories. ( There have been numerous code contributions to a different ONAP project: msb/service-mesh ) The only Committers on the aai/esr-* repos are Li Zi, (li.z...@zte.com.cn) and Sun Qi (sun.qi...@zte.com.cn). Both were the only individuals listed on the original project submission form https://wiki.onap.org/pages/viewpage.action?pageId=5734948 In terms of Committer responsibilities, Sun Qi has made +2 all of Li Zi's contributions to aai/esr-*. Exclusively. There are no records of code reviews being performed for any contributor other than Li Zi. There is no record of any code contributions being made by Sun Qi. Based upon the fact that self merges are not permitted, nothing can be done. The guidance the TSC needs to provide here is: Recommend that Jimmy work with Sun Qi to nominate one of the individuals below to Committer status Recommend that Jimmy pursue an exception to section 3.2.2.1 Adding Committers by filling out a Committer Promotion Request for Lv Bo, backed by contributions made outside of the AAI project Decide to take action based upon section 3.2.2.2 Adding Committers to moribund projects to appoint a Committer from the list below. Contributors to the aai/esr-* repos over the past 6 months: Submitter Repository Status created Summary Bin Yang aai/esr-server NEW 2018-09-03 Refactor cloud region registration logic Gary Wu aai/esr-server NEW 2018-08-24 Use managed guava version Gary Wu aai/esr-gui NEW 2018-08-24 Use managed guava version Li Zi aai/esr-server MERGED 2018-08-21 Fix the nullpointer error when register PNF Li Zi aai/esr-server MERGED 2018-08-21 Add unit test for PNF registration function. Li Zi aai/esr-server MERGED 2018-08-20 Realize the update PNF API. Li Zi aai/esr-server MERGED 2018-08-20 Realize the query PNF list API. Li Zi aai/esr-server MERGED 2018-08-20 Realize the delete PNF list API. Li Zi aai/esr-server MERGED 2018-08-20 Realize the PNF registration API Li Zi aai/esr-server MERGED 2018-08-20 Define attributes about PNF Li Zi aai/esr-server MERGED 2018-08-20 Add the API of query PNF. Li Zi aai/esr-server MERGED 2018-08-17 Add the framework for PNF registration function Li Zi aai/esr-server MERGED 2018-08-14 Fix the security issue about jetty Abhay Narayan Katare aai/esr-gui NEW 2018-07-26 Change Jira links updated Li Zi aai/esr-server MERGED 2018-07-26 set the ENV in shell instead of Dockerfile Li Zi aai/esr-server MERGED 2018-07-26 Fix the grammer issue in Dockerfile Venkata Harish Kajur aai/esr-server MERGED 2018-07-18 Upversion the esr server to 1.2.0 Gildas Lanilis aai/esr-server MERGED 2018-06-12 Update architecture diagram James Forsyth aai/esr-server MERGED 2018-06-06 Update architecture diagram Catherine Lefevre aai/esr-gui ABANDONED 2018-06-04 Update RL to Beijing (data to be added) Sudhakar Reddy aai/esr-gui MERGED 2018-04-24 Change field length to 50 for password Li Zi aai/esr-gui MERGED 2018-04-24 Fix the docker tag. Li Zi aai/esr-server MERGED 2018-04-24 Security: dropwizard in esr-server Li Zi aai/esr-server MERGED 2018-04-24 Fix the docker tag. Dénes Németh aai/esr-server MERGED 2018-04-21 Fix HTTP protocol used over HTTPS port Best Regards, -kenny Kenny Paul, Technical Program Manager, The Linux Foundation kp...@linuxfoundation.org, 510.766.5945 San Francisco Bay Area, Pacific Time Zone -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#3937): https://lists.onap.org/g/onap-tsc/message/3937 Mute This Topic: https://lists.onap.org/mt/27376142/21656 Group Owner: onap-tsc+ow...@lists.onap.org Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
