*[Chinese]* 参会人：Linkis PPMCs，社区运营贡献者 时间：2021/01/05 19:00~20:30 纪要：见腾讯文档 https://docs.qq.com/sheet/DSFJyTld3Y0JGeU54?tab=uf5xax 指标描述 当前(12.15) 毕业目标 目标说明 上周进度 本周进度 备注 核心指标 产品版本 dev-1.1.1 release-1.0.2 +8版本发布 +8 Apache 版本 3% 8% 已确认6个版本的负责人和大致时间排期，另有4个版本确认中 参见： https://docs.qq.com/sheet/DWkVIV0VhdHhpUGRB?tab=BB08J2 Contributors 51 101 +50位 0% 30% 已+15个contributors Committers 15（webank 10+5外部） 25 10；能主持开发发布Linkis 1个版本，或有重要特性贡献，或持续性社区积极贡献，即可提名 注：取决于社区贡献者团队/个人能力、意愿和资源投入，不可控性强，风险高 PPMC 6团队 10团队 +4团队 Mail List（Topics） 760 2800 +2000，人肉250封/版本每个PMC团队+20QA邮件 以邮件来做各个团队工作沟通记录介质 以github project 来构建需求池，拉通各个团队在做的事情 +403 当前1163？ Issues 631(open+closed) 2300 正常增速：+100*8 毕业增速：+200*8 +20 当前651 Pull Requests 569(open+closed) 2200 当前：+130*8目标：+200*8 +56 当前625 版本project 管理 规范化，每个版本进入开发之前要把project 建好，主要feature和issue整理好； 每个版本的规划、发布两个环节，需要PMC 投票表决 需求issue 管理 规范化，参考contributing.md；已加github template； 及时性，日常发现问题/需求随时及时提交，不要攒到一起提； 需求issue 要拆分出一部分简单、易解决的“拉新issue”，保持不少于5个open的“拉新issue”，定期发到各社区群里寻找愿意参与贡献的新contributor 开发规范 基于github repo开发； Committer 公司内部版本与开源版本Gap 拉平控制 0% 43% 切换到基于Github repo 开发： 微众约3月底完成； 爱奇艺已完成； BOSS约1月底完成； 天翼云约1月底完成； 萨摩耶已完成； 仙翁科技已完成； 社区联合开发测试环境建设CI/CD 规范化&效率提升；CI/CD 基于Github Action 联合开发环境约2月底面向社区提供 联合开发环境优先部署下一个要发布的版本，供测试验证 CI/CD流程补充天翼云环节（如生成docker镜像和发布到hub） 多版本并行开发，最近一个拟发布版本，向master 分支每天挑选commit提pr 做merge 开发规范文档完善，代码扫描模板补充 https://linkis.apache.org/zh-CN/docs/latest/development/development_specification/overview 测试管理 规范化，建立基础冒烟测试用例集；做到最基本的TDD(Test-Driven Development)，每次新增/改动/删除代码，都要准备好基本的冒烟测试用例； 每次代码提交前，都必须先做BVT (Build Verification Test)，本地编译，基础冒烟测试用例集 跑通过后，再提PR；PR中须注明BVT是否通过。后继要做CI自动化 测试用例完善&自动化 规范化&效率提升；PR 提交需考虑附带测试用例 50% UT覆盖； 60% SIT覆盖； 微众整理需补充测试用例范围，发布请社区共建 需微众给单元测试样例 发布管理 参考 https://linkis.apache.org/zh-CN/community/how-to-release 基于Linkis 1.0.3，打造WDS 生态完整稳定版本 社区例会机制（双周例会&Report） 轮值主持；做成开发者社区例会 下一次尹强主持 社群运营 附属指标 活动运营（形式，次数，主办/协办/参与） 内容运营 奖项 Stars 2318 Forks 760 用户案例（行业数量、案例个数）
*[English]* Participants: Linkis PPMCs, Community Operations contributor Time: 2021/01/05 19:00~20:30 Summary: Tencent document at https://docs.qq.com/sheet/DSFJyTld3Y0JGeU54?tab=uf5xax Indicator description Current (12.15) Graduation goal Goal description Last week's progress Progress this week Remark core indicators product version dev-1.1.1 release-1.0.2 +8 version released +8 Apache version 3% 8% The person in charge and approximate time schedule of 6 versions have been confirmed, and the other 4 versions are confirmed in : https://docs.qq.com/sheet/DWkVIV0VhdHhpUGRB?tab=BB08J2 Contributors 51 101 +50 people 0% 30% +15 contributors Committers 15 (external to webank 10+5) 25 10; Can preside over the development and release of Linkis 1 version, or have important feature contributions, or continuous community active contributions, you can nominate Note: It depends on the team/personal ability, willingness and resource input of community contributors, strong uncontrollability and high risk PPMC 6 teams 10 teams +4 team Mail List (Topics) 760 2800 +2000, 250 human flesh/versions for each PMC team +20QA emails to do the work of each team with emails to communicate the recording medium to build the demand pool with github project to pull together what each team is doing 403 Current 1163? Issues 631(open+closed) 2300 Normal growth rate: +100*8 Graduation growth rate: +200*8 20 Current 651 Pull Requests 569(open+closed) 2200 Current: +130*8 Target: +200*8 56 Current 625 Version project management Standardization, the project must be built before each version enters development, and the main features and issues must be organized; the planning and release of each version requires PMC voting Demand issue management Standardization, refer to contributing.md; github template has been added; timeliness, daily problems/requirements are submitted at any time, do not collect them together; demand issues should be split into some simple and easy-to-solve "pull new issues" Less than 5 open "pull new issues" are regularly sent to various community groups to find new contributors who are willing to contribute development specification Developed based on github repo; Gap leveling control between Committer's internal version and open source version 0% 43% Switch to development based on Github repo: Weizhong will be completed by the end of March; iqiyi has been completed; BOSS will be completed by the end of January; Tianyiyun will be completed by the end of January; Samoyed has been completed; Xianweng Technology has been completed; Community joint development and testing environment construction CI/CD standardization & efficiency improvement; CI/CD based on Github Action The joint development environment will provide the community with a joint development environment at about the end of February to prioritize the deployment of the next version to be released for testing and verifying the CI/CD process to supplement the Tianyi Cloud link (such as generating docker images and publishing to the hub). Multi-version parallel development. Release the version, select commit and pr every day to merge from the master branch The development specification document is complete, and the code scanning template is supplemented https://linkis.apache.org/zh-CN/docs/latest/development/development_specification/overview Test management Standardize, establish a basic smoke test case set; achieve the most basic TDD (Test-Driven Development), every time you add/change/delete code, you must prepare basic smoke test cases; before each code submission, You must do BVT (Build Verification Test) first, compile locally, and pass the basic smoke test case set before submitting a PR; the PR must indicate whether the BVT has passed. Follow-up to do CI automation test case improvement & automation standardization & efficiency improvement; PR submission needs to consider incidental test cases 50% UT coverage; 60% SIT coverage; Weizhong needs to supplement the scope of test cases for finishing, and the community is required to jointly build the unit test samples. Release management Refer to https://linkis.apache.org/zh-CN/community/how-to-release Create a complete and stable version of the WDS ecosystem based on Linkis 1.0.3 Community Regular Meeting Mechanism (Bi-weekly Regular Meeting & Report) Rotate to host; make a regular meeting of the developer community Next time Yin Qiang will host Community operation Subsidiary indicators Event operation (form, frequency, hosting/co-organization/participation) Content operation Awards Stars 2318 Forks 760 User cases (number of industries, number of cases) Shuai Di Best Regards.
