Page History

Add meeting frequency and timing e.g. Meeting Thursday (biweekly) at 7:00 PM IST.

Mar 16th, 2022

Time:  10:00 PM Beijing Time

Meeting link：https://meeting.tencent.com/dm/xsyfqLSvQbVt

Host : 尹强

Next Host : 刘振东

Attendees :  

姜宁，Eason，Ted，肖宇，刘振东，goson，薛炜明，尹强，邸帅

Agenda：

      1. How to improve the quality of code submitted by the community?

a. code style, CICD can guarantee most of the code quality problems;

b. at the beginning, it is necessary to communicate clearly with the community, and split the functions into finer details, so that it is easier to merge.

c. For core modules, the requirements are stricter, and for non-core modules, the merging conditions can be appropriately relaxed.

d. If the contribution is a large module, the contributing company needs to sign the SGA, and the relevant contributor signs the ICLA.

e. Contributors who contribute for the first time can be appropriately relaxed and do not need to sign the CCLA.

f. Be careful with large PRs (over 500 lines) submitted by the community. When collaborating, it is best for everyone to develop based on the upstream, and to communicate with the leaders of the relevant participants.

https://incubator.apache.org/ip-clearance/

      2. Different apache project code license issues (the code is submitted by the same person)

Try not to copy the code of other projects, even if they are all Apache projects, written by the same person.

      3. How to release a version quickly, and do you have to go through a strict release voting process every time?

Voting is a must, unless there is a security breach to take the fast track.

https://www.apache.org/legal/release-policy.html#release-approval

      4. The github code is synchronized to gitee development, and then synchronized back to facilitate submission in the domestic network environment. Is it possible to do this? 

Apache has Gitbox, which is not blocked. It can submit PR, but it does not support code review. Officials do not recommend developing in non-GitHub repositories, and issues, PRs, etc. cannot be synchronized in both directions. First confirm whether the above two-way synchronization problem of Gitee can be solved.

      5. The evolution relationship problem of version bug feature

Release-1.1, a feature1 was issued; release-1.2, a feature2 (including feature1) was added. If a bug in feature1 is found, do both release-1.1 and release1.2 need to fix the bug? The core lies in the need to confirm the life cycle of the relevant version and disclose the maintenance cycle.

      6. Can the snapshot version be used as the version to fix the problem urgently? Does it still need to go through the voting process?

Snapshots can be sent without voting. They are for development and a small number of users for testing and verification.
SNAPSHOT version release can refer to:

http://github.com/apache/servicecomb-pack

https://github.com/apache/servicecomb-pack/blob/master/.github/asf-deploy-settings.xml

https://github.com/apache/servicecomb-pack/blob/master/.github/workflows/asf-snapshots-deploy.yml

The deployed username and password are set by Infra through

Feb 23th, 2022

Time:  10:00 PM Beijing Time

...