Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. review of the conclusions of 4rd meeting
    1. Call for community mentors
      1. all committers can be mentors
      2. Q & A docs, FAQ docs, start up docs.
      3. waiting
    2. About IoTDB publicity
      1. WeChat officialaccount, Bilibili, Tiktok, aliyun(private account)
      2. video is uploaded in Bilibili
      3. self ask, self answer in StackOverFlow - ask jincheng
    3. compares to influx in terms of performance
      1. https://iotdb.apache.org/UserGuide/Master/Comparison/TSDB-Comparison.html
      2. upgrade version 0.8.0→0.11.1 - xiangdong
      3. tsbs benchmark: timescaledb、influxdb
    4. preproduction site
      1. chinese ppt
      2. ApacheCon - use cases
      3. https://iotdb.apache.org/Community/Materials.html upgrade 2020 - xiangdong
    5. New committer introduction - qiaojialin
      1. Houliang Qi
      2. Xinyu Tan
    6. the label coverage of PR - xiangdong
    7. announce of 0.11.1 (haonan)
      1. WeChat officialaccount 
      2. or just announce 0.11.2 (qiaojialin)
        1. flush
    8. github robot - next meeting to be discussed
      1. https://github.com/marketplace
      2. waiting
    9. contributor weekly (qiaojialin) - need discuss
      1. all important contribution
      2. for all new contributor
    10. best contributor monthly (zhouyurun) - need discuss and proposal
      1. PR
      2. review
      3. mailing list
      4. WeChat officialaccount 
      5. doc
      6. event(activity)
    11. to be a committer - need discuss
      1. code
        1. PRs(xinyu)
        2. modules - fix significant bug(xinyu)
        3. can maintain a module(xiangdong)
          1. a clear impression of someone
      2. doc or others 
      3. pingcap:https://pingcap.com/blog-cn/tidb-community-upgrade/
  2. code management by git flow:
    1. avoid pushing to the repository directly
    2. provide relatively detailed commit message.
    3. Do not force-push a commit if someone has reviewed your code
    4. use squash merge(whether need to disable directly-merge?)
    5. list the reproduction procedure when reporting bugs
    6. detailed pr/issue title(is Chinese needed?)
  3. next host:

...