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

June 22th, 2022

Time:  10:00 PM Beijing Time

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

Host : Yu Xiao

Next Host : Heng Du

Attendees :  

Agenda:

       1.  ApacheCon Asia

          1.1  The presentation PPT needs to be in English and use a uniform template.

          1.2  Recorded videos can be in Chinese.

          1.3 Topics: Apache ShenYu (2) , Apache Inlong (2), Apache eventmesh(2), Apache RocketMQ(15), Apache linkis(2)

          1.4 forwarded apacheCon asia articles by ALC shenzhen, Apache ShenYu etc.

      2.  Apache ShenYu graduation review.

        2.1  About resolution template If you are not good at English, we recommend using Grammarly.
        2.2   Translation https://incubator.apache.org/guides/graduation.html by Ted Liu.

      3. Apache eventmesh same repository contains releases in different languages (Java, Go).

           * Apache has no rules, only process specifications that conform to Apache releases.

         3.1 Benefits of splitting molecule projects based on different languages.
             a. developers with different technology stacks, easier to contribute.
             b. CI checks are easy and more manageable.

       3.2 Problems associated with splitting projects based on different languages.
            a. Version consistency issues (suggested to organize version compatibility tables).
            b. Project statistics, we recommend using https://cauldron.io/.

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

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

Host : 肖宇

Next Host : 尹强

Attendees :  

Agenda:

       1. Apache RocketMQ Summit(https://mp.weixin.qq.com/s/NVaqUOT-BBaFX6V78kXwdw).

         a. Event date: April (to be confirmed).

         b.Apache ShenYu Topic  (topic to be decided).

         c. Eason will be the producer (topic to be confirmed).

      2. Participate in the ApacheCon Asia session.

        a. Currently in the conference budget stage.
        b. Call for Topics (CFP) in April.
        c. Call for sponsors (sponsorship package not yet decided) Jingdong sponsorship matchmaking enquiries w. Ted / Cao Peng - Xiao Yu.

      3. ALC Shenzhen governance in each community.

        a. Linkis developing some metrics for graduation (releases, etc.), 6 external contributors PPMC, other data teams are working closely on integration.
       b. EventMesh is preparing to release a third Apache version, and is working with other communities to hold a meetup, and with external developers to update the more important features. How to tap into company-level users to share or PR, and later               conduct enterprise walk events.
      c. ShenYu is preparing to release the fourth Apache version, adding 2 Committers . The students of ShenYu are participating in open source and contributing big PRs.
      d. RocketMQ added SIG bi-weekly meeting, purpose (community autonomy): 1. collector issues 2. community promotion 3. attract more developers.

      4. Participate in an open source sharing session with the JD.com Group(https://shimo.im/docs/Ee32M5EDpYhDMJA2)

      5. GSoC 2022

         a. Difficulty of the topic.

        c. Help more Chinese students attend.

Feb 2th, 2022

Time:  10:00 PM Beijing Time

Meeting link:

https://meeting.tencent.com/dm/wOQVESKQqfj2

#Tencent meeting ID:

   147-643-448

Attendee:

Recorder: 

    peacewong@Apache Linkis(incubating)

Agenda& Notes:

1. Unit testing How to unit test the interface that needs to operate the database, such as the interface needs to call mysql? peacewong


a. If sql is more general, you can use H2 DB.
b. Otherwise, if you must use MySql, you can use the testContainer framework (closer to the real data).
b. Or use mock data.
c. It is recommended to use junit5.
d. It is recommended to assign an Easy Task for unit testing to community development users for participation.


2. Is the community official website independently developed or generated by tools? Are there any good recommended build tools? dongeforever


a. Many projects use Docusaurus, many themes are optional, and versions of supported documents.


3. Would you like to share some evangelistic experiences of promotion projects? qqeasonchen


a. Projects can help users solve their company’s problems and let them share documentation of their experience.
b. case case documentation is more efficient.
c. Title party articles are not good practice.
d. The advertised data should be true, and provide relevant methods for verification.
e. The skywalking license event of the volcano engine is a good case. Open source projects are good projects, and community users will support them.
f. Good articles in the project field, can be translated, and put your own project in the head as a reference or tail conclusion for organic publicity.
g. Pay attention to popular events, dynamic event marketing.


4. Recommended github action plugin for security vulnerability scanning Zhang Chao


a. Trivy can scan CVE of docker image, tool address: https://github.com/aquasecurity/trivy
b. You can add github Dependabot, you can find INFRA application
c. findBugs plugin can also scan parts
d. codeql-action: https://github.com/github/codeql-action



Jan 26th, 2022

Time:  10:00 PM Beijing Time

Meeting link:

https://meeting.tencent.com/dm/1ooadKOco22L

#Tencent meeting ID:918-632-572

Attendees: 陈广胜,杜恒,肖宇,邸帅,王和平,薛炜明,尹强,刘振东,张国成,柯振旭

Recorder:Mike Xue

Agenda& Notes:

1. Is there a good tool to sort out the licenses of third-party dependent components?-Goson Zhang

2. Is it better to develop code in master or develop? Non-default branch cannot count contributors?-Chen Guangsheng

3. Suggestions for voting on the release version

The rc version voted for is a release candidate. It is uncertain whether it can pass the vote. After passing the vote, the non-rc official version can be released. The official version must be consistent with the rc version code that has passed the vote.
The suggestion is to find the mentor in the dev to do the verification first, and the mentor will vote, and the vote can be brought into the IPMC voting.

4. Digging to find contributors

Organize Q&A documents, and related low-cost issues, and then deliver them to more active users

5. How to guide users to mention English issue to discuss design plan, etc.

The design scheme can be expressed in both Chinese and English.

6. When the code contributed by community contributors is inconsistent with the current main goals and concerns of the community, whether to consider merging code

If there are indeed community contributors who have a certain demand for this feature, and the code quality meets their standards, and does not have much impact on the main core parts of the project, you can consider merging it.


Jan 12th, 2022

Time:  10:00 PM Beijing Time

Meeting link:

https://meeting.tencent.com/dm/sfKresi4L4rF

#Tencent meeting ID:816-8425-8350

Attendees: 陈广胜,杜恒,姜宁,陈亮,邸帅,王和平,薛炜明,尹强,张超,张国成,柯振旭,单致豪

Recorder: Shuai Di

Agenda& Notes:

1. Happy Hiking. Choose a good weather and organize an outing on the weekend. - Heng Du
-- The vote will be held after the outbreak in Shenzhen.  

2. Can the efficiency of answering questions in Apache be optimized?  - Guangsheng Chen  
-- For technical and operational questions, go to the general@incubator.apache.org mailing list. Infra related best submit an JIRA issue, easier to track. Slack's Incubator channel is a more immediate option.  

3. What are the nomination and withdrawal mechanisms for Mentors /PPMC/Committer?  - Guangsheng Chen  
The detailed process guidance can be found in the Apache guidance document.  
https://infra.apache.org/new-committers-guide.html#becoming-a-committer
https://apache.org/foundation/how-it-works.html#meritocracy
https://www.apache.org/foundation/voting.html
Nomination standards are generally agreed within each project according to the different status at different stages of project development.  "Apache is a meritocracy. Once someone has shown sufficient sustained commitment to a project by helping out and contributing work to it (and the ASF), the project may vote to invite that person to become a committer."
"Get involved and contribute via the user and developer email lists, Wiki and forums (if any); extend or improve the documentation; work on bugs listed in the issue tracker or submit code patches. Answering other users' questions is a great way to get started, as is suggesting patches or improvements to Apache project websites."
Follow the meritocracy, consider multiple contribution dimensions such as code and community operations.  Consider positive incentives to contributions to the community, not just for the sake of ADD one, but to ensure enough credits, to be recognized and trusted by the community.  Features/requirements are discussed in mailing lists, issues, and PR.  Note the addition of documentation and test cases, preferably written by the PR person, as a sign of project maturity and professionalism.  
Committer voting is done on the Private mailing list within the community, with existing Committers nominating to vote. Then follow the becoming-a-committer to Apache to finish the set-up.  
PPMC needs to go to the general@incubator.apache.org mailing list.  
Mentor also needs to go to the general@incubator.apache.org mailing list.  
Exit/withdrawal mechanism, mostly by oneself to put forward the initiative to quit. There is no quantitative activity requirements. For Apache members, there will be strong activity related requirements.  

4. Can github issue be equivalent to Maillist Issue discussion?  - GuangSheng Chen  
-- It has the same effect in the discussion process. As long as the discussion process is transparent and open, and the track record is complete, retrievable and archived, it can be basically equivalent.  But the email is read-only and the issue can be edited.  Things like voting should based on email.  

5. What is the standard practice for scanning and labeling licenses of non-text files (such as pictures and fonts) in Apache Releases?  - Shuai Di
-- Firstly, make sure the file is free to use and not infringing, then you need to show the source and license. Note this in the LICENSE/NOTICE file. It is best not to use without authorization, and a DISCLAIMER may not serve as a protection. Do not use the file without a license statement.  
If you want to issue the version in the form of WIP with files without explicit authorization/license, suggest to confirm with Justin again.  

6. "Not listed as an incubator committer" Roster in the new committer shows this (project privileges didn't work), and there is no committer privileges either.  There are PPMC members showing this, why?  - Guangsheng Chen  
-- If not, ask the INCUBATOR secretary.  The LDAP permission problem is involved.  You can ask IPMC members in your project mentors to try add them into the Incubator project.  

7. Does the project have regular meetings for the whole community?  
-- Depending on the purpose of the meeting, some directional, decision-making, and targeted items may be more efficient to a limited attendee scope, such as committers, SIG. Something want to promote to the whole community, such as version release publicity, should consider a meeting to the whole community. Asynchronous, email-based communication is also a good way.  

8. Apache Conn ASIA 2022, set around 7/20.  ALC Beijing preparing for the launch. More likely online form, welcome to join. 


Dec 29th, 2021

Time:  10:00 PM Beijing Time

Meeting link:

https://meeting.tencent.com/dm/yn87VOIkxpck

#Tencent meeting ID:865-842-911

Attendees: 陈广胜,杜恒,冯嘉,姜宁,刘天栋,陈亮,院生,邸帅,薛炜明,尹强,肖宇,刘振东,张超,张国成


Agenda:

  1. Happy hiking  discuss
  2. How can the community partner team, especially their's private repo better track with the community version to collaborate and contribute more effectively? 
  3. Establish ApacheCon Asia 2022 Preparatory Working Group in cooperation with ALC Beijing
  4. Encourage members of ALC Shenzhen to participate in ASF Incubator PMC and Community Development (ComDev) PMC

Notes:

  1. Call for a vote on the specific time and place of the hiking
  2. ApacheCon Asia 2022 will start preparations in February, hope that some companies can sponsor online meeting facilities, such as Tencent Conference. In addition, hope more members can take the initiative to help follow up on specific matters of each track
  3. Recommend everyone to subscribe to the general(general@incubator.apache.org ) and comdev(dev@community.apache.org)mailing list, we all try and help one another.


Dec 15th, 2021

Time:  10:00 PM Beijing Time

Meeting link:

https://meeting.tencent.com/dm/sfKresi4L4rF
#Tencent meeting ID:816-8425-8350


Attendees: 陈广胜,杜恒,冯嘉,姜宁,刘天栋,谭中意,薛炜明,邸帅,尹强,王和平,刘振东,柯振旭,cherryucao

Agenda:

  1. Introduce yourself to the team.
  2. Plan about the coming up bi-weekly meeting.
  3. Discuss the standard of graduate of an incubating project, especially how to evaluate the activity of a community.
  4. How is ALC Shenzhen can better help the local incubating projects in a efficient way.

Notes:

  1. Take turns to preside the bi-weekly meeting, discuss the agenda in advance, make meeting minutes after meeting.
  2. Prepare the announcement of ALC Shenzhen.
  3. Find potential cooperation opportunities between the incubating projects.
  4. Get some help and good practices from ALC Beijing.