Hi Min Ji,

This is a conference theme and send it before out meeting, but I wrote the
wrong title.

I'm rewriting a new meeting minutes and send it later

Min Ji <[email protected]> 于2023年12月11日周一 10:31写道:

> Hi Jiawei,
>
> I feel that this is not a meeting minutes document. Meeting minutes should
> contain key conclusions and a review of the progress on past matters.
>
>
> Warm regards,
>
> Ji Min
>
>
> zhangjiawei_apache <[email protected]> 于2023年12月9日周六 11:53写道:
>
> > Hi Seata Community,
> >
> > I am writing to provide you with the minutes from our community meeting
> > held on December 9, 2023. The meeting was productive, and we covered
> > several important topics as outlined below:
> >
> > Moderator: Jiawei Zhang
> >
> > *Attendees* (PPMC only, others refer to the appendix): @Wang Te @Liu
> Yuecai
> > @Zhong Zhengtao @Zhuang Jinlei @Xuan Yi @Zhang Jiawei @Wang Liang @Wu
> > Jiangke @Wang Xin, etc., totaling 37 people.
> >
> > *Minutes of the Meeting in Chinese:*
> > https://github.com/seata/seata/wiki/20231209
> >
> >
> > *Discussion items:*
> >
> >    - Collect the information of contributor whos contribute more than 100
> > line.
> >
> >    - The public of email template.
> >
> >    - Talking about the committer of seata.
> >
> >    - Talking about the flow of search engine.
> >
> >    - The compliance of seata.io website.
> >
> >    - The Document of history, use guide, configuration, upgrade, deploy.
> >
> >    - Document move the wiki.
> >
> >    - Upgrade the document of 1.8.x, 2.x, release note, seata simple.
> >
> >    - The plan of branch of maintain.
> >
> >    - The compatibility of seata.
> >
> >    - The coverage of unit test.
> >
> >    - The integration of test.
> >
> >    - The compatibility of test.
> >
> >    - The benchmark of test.
> >
> >    - The mock of test.
> >
> >    - The reconstruction of the code.
> >
> >    - The historical of pull request.
> >
> >    - Support spring boot actuator.
> >
> >    - The unique identifier of tcc.
> >
> >
> > Best regards,
> >
> >  Jiawei Zhang
> >
>

Reply via email to