Looks good to me :) Best Regards, Yongjun Hong (YongGoose)
On 2025/08/03 07:16:45 Min Ji wrote: > I have updated the maturity assessment on the official website. > https://seata.apache.org/docs/next/developers/maturity > > Warm regards, > > Min Ji > > Min Ji <ji...@apache.org> 于2025年7月13日周日 22:50写道： > > > > Hi YongJun, > > > > The binary package includes a DISCLAIMER file. I consulted the mentor, > > Sheng, about this issue, and he confirmed that this is indeed a > > convenience binary, for which the ASF typically disclaims > > responsibility. My confusion lies in why we still need to validate the > > LICENSE and NOTICE files within the binary package if it is > > disclaimed. Sheng explained that this serves as supplemental > > validation to ensure no non-compliant dependencies are inadvertently > > introduced into the source code. > > > > > > Warm regards, > > > > Min Ji > > > > YongJun Hong <yongj...@apache.org> 于2025年7月13日周日 10:03写道： > > > > > > Hello Jimin :) > > > > > > IMO, the -bin suffix typically indicates a binary distribution. Since > > > it’s a convenience binary rather than source code, I believe a disclaimer > > > should be included. > > > > > > For example, the Apache HTTP project includes the following disclaimer: > > > “Please note that ability to exploit this issue is dependent on running > > > untrusted 3rd party modules or untrusted server-side code.” > > > > > > It might be good for us to include a similar statement clarifying that no > > > guarantees are provided. > > > > > > Also, just a personal suggestion — I think having an English version of > > > the recorded discussion would be helpful. > > > > > > Aside from the number of committers, everything else looks good to me. 🚀 > > > > > > Best Regards, > > > Yongjun Hong (YongGoose) > > > > > > > > > On 2025/07/13 00:16:45 Jiangke Wu wrote: > > > > Hi Min, > > > > > > > > I have reviewed the checklist[1] and Apache Project Maturity Model[2], > > > > and > > > > it looks good overall. However, in item CO40, "XX" should be replaced > > > > with > > > > the actual number of new committers, although this number may change > > > > later. I believe it’s time to initiate the graduation vote – please go > > > > ahead. Good luck to Seata! > > > > > > > > > > > > [1 ] > > > > https://github.com/apache/incubator-seata/wiki/maturity-model-assessment > > > > [2] > > > > https://community.apache.org/apache-way/apache-project-maturity-model.html > > > > > > > > Best Regards, > > > > Jiangke Wu(xingfudeshi) > > > > > > > > > > > > On Sat, Jul 12, 2025 at 7:36 PM Min Ji <ji...@apache.org> wrote: > > > > > > > > > As mentioned above, if you have time, please help Review it. After > > > > > confirming that there are no issues, I will update it to the official > > > > > website and launch a graduation vote. > > > > > > > > > > Warm regards, > > > > > > > > > > Min Ji > > > > > > > > > > Min Ji <ji...@apache.org> 于2025年7月7日周一 15:10写道： > > > > > > > > > > > > Hi All, > > > > > > > > > > > > I have compiled a checklist aligned with the Apache Project Maturity > > > > > > Model to evaluate our graduation readiness. During this process, I > > > > > > identified gaps in certain documentation requirements, which I’ve > > > > > > addressed by submitting updates to the Seata website. > > > > > > > > > > > > Current Status: > > > > > > - Checklist Draft: Hosted on the project wiki for collaborative > > > > > > review. > > > > > > - Community Alignment: Based on my preliminary assessment, we > > > > > > largely meet PMM criteria. However, this is my personal evaluation > > > > > > and > > > > > > requires broader validation. > > > > > > - Next Steps: Once consensus is reached on each checklist item, I > > > > > > will migrate the finalized version to the official website. > > > > > > > > > > > > Invitation for Feedback: > > > > > > Please review the checklist and share your insights. Focused > > > > > > discussions on specific criteria are particularly welcomed. > > > > > > > > > > > > During my review of the checklist, I encountered ambiguity regarding > > > > > > Release Requirement RE40 in the Apache Maturity Model. The original > > > > > > text states: > > > > > > > The project can distribute convenience binaries alongside source > > > > > > > code, > > > > > but they are not Apache Releases, they are provided with no guarantee. > > > > > > > > > > > > Does this mean our release artifacts (e.g., > > > > > > apache-seata-2.4.0-incubating-bin.tar.gz) qualify as convenience > > > > > > binaries rather than official ASF releases? If so, should we > > > > > > explicitly disclaim warranties for these binaries per ASF release > > > > > > policy? > > > > > > > > > > > > Seata Maturity model checklist: > > > > > > https://github.com/apache/incubator-seata/wiki/maturity-model-assessment > > > > > > Apache Project Maturity Model: > > > > > > > > > > > https://community.apache.org/apache-way/apache-project-maturity-model.html > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Warm regards, > > > > > > > > > > > > Min Ji > > > > > > > > > > > > Min Ji <ji...@apache.org> 于2025年7月7日周一 14:43写道： > > > > > > > > > > > > > > Hi YongJun, > > > > > > > > > > > > > > Thank you very much for your reply. Before graduation, we have > > > > > > > many > > > > > > > things to deal with and improve. > > > > > > > > > > > > > > > > > > > > > Warm regards, > > > > > > > > > > > > > > Min Ji > > > > > > > > > > > > > > YongJun Hong <yongj...@apache.org> 于2025年7月6日周日 19:48写道： > > > > > > > > > > > > > > > > Hi all, > > > > > > > > > > > > > > > > I'm glad to see that Seata is getting closer to graduating from > > > > > > > > the > > > > > Incubator! > > > > > > > > > > > > > > > > I agree with Jiangke Wu’s suggestion to assign owners and target > > > > > completion dates for each item — it’s a great way to ensure steady > > > > > progress. > > > > > > > > > > > > > > > > If there’s anything I can help with, please feel free to let me > > > > > > > > know. > > > > > > > > I’ll do my best to support the effort. > > > > > > > > > > > > > > > > Best regards, > > > > > > > > Yongjun Hong (YongGoose) > > > > > > > > > > > > > > > > > > > > > > > > On 2025/07/04 08:39:40 Jiangke Wu wrote: > > > > > > > > > Hi all, > > > > > > > > > > > > > > > > > > It's great to see Min Ji initiating the discussion about > > > > > > > > > Seata's > > > > > > > > > graduation. After 608 days in the incubator, it's truly > > > > > > > > > exciting > > > > > that we > > > > > > > > > are getting close to this significant milestone. > > > > > > > > > > > > > > > > > > I completely agree with Min Ji's points. As he emphasized, > > > > > graduation is > > > > > > > > > not the responsibility of a single committer but a shared > > > > > > > > > duty for > > > > > every > > > > > > > > > one of us in the PPMC and the broader community. We need to > > > > > collaborate > > > > > > > > > closely to complete this final stretch. > > > > > > > > > > > > > > > > > > The proposal to create a public checklist on the official > > > > > > > > > website > > > > > is > > > > > > > > > excellent. It will allow us to systematically track our > > > > > > > > > progress > > > > > against > > > > > > > > > the Apache Maturity Model and keep the entire community > > > > > > > > > informed. > > > > > > > > > > > > > > > > > > To make this plan even more effective, I suggest that as we > > > > > > > > > build > > > > > the > > > > > > > > > checklist, we also assign a specific owner to each action > > > > > > > > > item and > > > > > perhaps > > > > > > > > > a target date for completion. This will ensure clear > > > > > accountability and > > > > > > > > > help us move forward efficiently. > > > > > > > > > > > > > > > > > > Let's work together to complete this checklist and > > > > > > > > > successfully > > > > > guide Seata > > > > > > > > > through graduation. > > > > > > > > > > > > > > > > > > Looking forward to collaborating with all of you on this. > > > > > > > > > > > > > > > > > > Best Regards, > > > > > > > > > Jiangke Wu(xingfudeshi) > > > > > > > > > > > > > > > > > > > > > > > > > > > On Sat, Jun 28, 2025 at 10:58 PM Min Ji <ji...@apache.org> > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > Dear All, > > > > > > > > > > > > > > > > > > > > As we approach 608 days since entering the Apache > > > > > > > > > > Incubator, I > > > > > propose > > > > > > > > > > we initiate a formal discussion to assess our project's > > > > > > > > > > maturity > > > > > > > > > > against the Apache Maturity Model [1]. This evaluation is > > > > > crucial to > > > > > > > > > > determine whether Seata meets all requirements outlined in > > > > > > > > > > the > > > > > model > > > > > > > > > > and is ready to graduate from incubation. > > > > > > > > > > > > > > > > > > > > Key Discussion Points: > > > > > > > > > > > > > > > > > > > > Review current status against the 37-point Apache Maturity > > > > > Checklist > > > > > > > > > > Establish consensus on graduation readiness > > > > > > > > > > Define action items for remaining requirements > > > > > > > > > > > > > > > > > > > > I suggest we set up a public document and put it on the > > > > > > > > > > official > > > > > > > > > > website to check and record the contents item by item and > > > > > > > > > > Invite > > > > > IPMC > > > > > > > > > > mentors to provide guidance > > > > > > > > > > > > > > > > > > > > [1]. > > > > > > > > > > > > > > > https://community.apache.org/apache-way/apache-project-maturity-model.html > > > > > > > > > > > > > > > > > > > > Let's collaborate to ensure Seata successfully completes > > > > > > > > > > this > > > > > critical > > > > > > > > > > milestone. Please share your availability and thoughts on > > > > > > > > > > the > > > > > proposed > > > > > > > > > > approach. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Warm regards, > > > > > > > > > > > > > > > > > > > > Min Ji > > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > > > > > To unsubscribe, e-mail: private-unsubscr...@seata.apache.org > > > > > > > > > > For additional commands, e-mail: > > > > > > > > > > private-h...@seata.apache.org > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > > > To unsubscribe, e-mail: dev-unsubscr...@seata.apache.org > > > > > > > > For additional commands, e-mail: dev-h...@seata.apache.org > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > To unsubscribe, e-mail: dev-unsubscr...@seata.apache.org > > > > > For additional commands, e-mail: dev-h...@seata.apache.org > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: dev-unsubscr...@seata.apache.org > > > For additional commands, e-mail: dev-h...@seata.apache.org > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@seata.apache.org > For additional commands, e-mail: dev-h...@seata.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@seata.apache.org For additional commands, e-mail: dev-h...@seata.apache.org
