Re: [DISCUSS] Graduate Apache InLong(Incubating) as a TLP

[Jean-Baptiste Onofré]

+1 (binding)

The project is ready to graduate. The community is healthy and active.

Thanks !
Regards
JB

On Thu, May 19, 2022 at 11:09 AM Charles Zhang  wrote:
>
> Dear Apache Incubator Community,
>
>
> The InLong Project has been incubating since 2019-11-03. In the past two
> and a half years, the project has been renamed from TubeMQ to InLong, and
> expanded its scope from a message queue service to a one-stop integration
> framework for massive data.
>
>
> The InLong community has a discussion thread [1], passed the community vote
> [2], and the vote result is published [3]. Our assessment is that Apache
> InLong(Incubating) is ready to graduate as a TLP. We would like to raise
> the discussion to IPMC and collect more feedback towards graduation.
>
>
> Since incubating in ASF, the project itself has become more mature and
> stable. The following is a brief summary of the project and community
> during the incubation:
>
>
> - 11 versions were released by 6 different release managers, of which 5
> versions are the original TubeMQ, and 6 versions are after the name was
> changed to InLong. The release cadence is about 2 months [4].
>
>
> - 10 new Committers and 3 PPMCs were added during incubating, they are from
> 4 different organizations. All PPMCs and Committers are spread across 8
> different organizations [5].
>
>
> - 101 unique code developers [6].
>
>
> - Closed more than 2200 issues, with an average of 200 issues per version
> [7].
>
>
> - All the dependencies were reviewed and ensured they do not bring any
> license issues [8].
>
>
> - Evaluated the InLong project and self-checked the InLong maturity model
> [9] and the pre-graduation Check [10].
>
>
> - Well and Complete documentation for contributors and users [11].
>
>
> - Created channels like Email, Slack, Twitter, WeChat, and GitHub
> Discussions to communicate, with more than 650 subscribers.
>
>
> - Actively participated in or held more than 15 meetups to increase
> community influence.
>
>
> Please see the proposed board resolution below and let us know what you
> think. The initial PMC members were passed by the discussion and invitation
> [12].
>
>
> The discussion will remain open for at least 72 hours, looking forward to
> your feedback.
>
>
> [1] https://lists.apache.org/thread/pzqk3z4pbbh3qx0cl1hmpzo1305p2lro
>
> [2] https://lists.apache.org/thread/03topv74zgp4j22cg805l50sqzcr3y20
>
> [3] https://lists.apache.org/thread/n1mkcplz53ytlmhk7r506toxgsv6rfw9
>
> [4] https://inlong.apache.org/download/main/
>
> [5] https://whimsy.apache.org/roster/ppmc/inlong
>
> [6] https://github.com/apache/incubator-inlong/graphs/contributors
>
> [7]
> https://github.com/apache/incubator-inlong/issues?q=is%3Aissue+is%3Aclosed
>
> [8] https://github.com/apache/incubator-inlong/tree/master/licenses
>
> [9]
> https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=INLONG=Maturity+Assessment+for+InLong
>
> [10]
> https://cwiki.apache.org/confluence/display/INLONG/Graduation+Check+List
>
> [11] https://inlong.apache.org/docs/next/introduction
>
> [12] https://lists.apache.org/thread/mgl2jgpdojb6dzdhnhoq7dfqs26hj2xc
>
>
> --
>
> Establish the Apache InLong Project
>
>
> WHEREAS, the Board of Directors deems it to be in the best interests of
>
> the Foundation and consistent with the Foundation's purpose to establish
>
> a Project Management Committee charged with the creation and maintenance
>
> of open-source software, for distribution at no charge to the public,
>
> related to a one-stop data integration framework that provides
>
> automatic, secure, and reliable data transmission capabilities. InLong
>
> supports both batch and stream data processing at the same time, which
>
> offers great power to build data analysis, modeling, and other real-time
>
> applications based on streaming data.
>
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
>
> (PMC), to be known as the "Apache InLong Project", be and hereby is
>
> established pursuant to Bylaws of the Foundation; and be it further
>
>
> RESOLVED, that the Apache InLong Project be and hereby is responsible
>
> for the creation and maintenance of software related to a one-stop data
>
> integration framework that provides automatic, secure, and reliable data
>
> transmission capabilities. InLong supports both batch and stream data
>
> processing at the same time, which offers great power to build data
>
> analysis, modeling, and other real-time applications based on streaming
>
> data; and be it further
>
>
> RESOLVED, that the office of "Vice President, Apache InLong" be and
>
> hereby is created, the person holding such office to serve at the
>
> direction of the Board of Directors as the chair of the Apache InLong
>
> Project, and to have primary responsibility for management of the
>
> projects within the scope of responsibility of the Apache 

Re: [DISCUSS] Graduate Apache InLong(Incubating) as a TLP

[Aloys Zhang]

+1, good luck

Liang Chen  于2022年5月21日周六 00:04写道：

> +1, good luck.
>
> Regards
> Liang
>
> tison  于2022年5月20日周五 18:13写道：
>
> > +1 good luck
> >
> > Young Seung Andrew Ko 于2022年5月20日
> 周五17:36写道：
> >
> > > +1  (non-binding)
> > >
> > > Well done :)
> > >
> > > On Fri, May 20, 2022 at 6:32 PM wangxiaogang 
> > > wrote:
> > >
> > > > +1, good luck；
> > > >
> > > >
> > > > Eason Chen  于2022年5月20日周五 16:34写道：
> > > >
> > > > > + 1  （non-binding）
> > > > >
> > > > > Good luck!
> > > > >
> > > > > On Fri, May 20, 2022 at 3:43 PM XiaoYu  wrote:
> > > > > >
> > > > > > + 1  （non-binding）
> > > > > >
> > > > > > Good luck!
> > > > > >
> > > > > > Heal Chow  于2022年5月20日周五 15:16写道：
> > > > > > >
> > > > > > > +1.
> > > > > > >
> > > > > > > I've learned a lot about community collaboration and
> maintaining
> > > open
> > > > > source projects in the InLong project. Looking forward to InLong
> > doing
> > > > > better in data integration.
> > > > > > >
> > > > > > > Good luck!
> > > > > > > HealChow
> > > > > > >
> > > > > > > On 2022/05/19 10:47:52 Goson zhang wrote:
> > > > > > > > +1
> > > > > > > >
> > > > > > > > Since the InLong project entered the incubation pool, the
> team
> > > has
> > > > > > > > continued to grow, with the help of community contributors,
> the
> > > > > project has
> > > > > > > > developed from a single module to a mature data integration
> > > > > framework, and
> > > > > > > > has implemented the application of the project in multiple
> > > > > environments.
> > > > > > > >
> > > > > > > > Looking forward to the continuous improvement of the InLong
> > > project
> > > > > to
> > > > > > > > become a global community of contributors to better serve the
> > big
> > > > > data
> > > > > > > > business.
> > > > > > > >
> > > > > > > > Thanks!
> > > > > > > >
> > > > > > > > Kent Yao  于2022年5月19日周四 17:25写道：
> > > > > > > >
> > > > > > > > > +1, good luck to InLong community
> > > > > > > > >
> > > > > > > > > Charles Zhang  于2022年5月19日周四
> > 17:09写道：
> > > > > > > > > >
> > > > > > > > > > Dear Apache Incubator Community,
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > The InLong Project has been incubating since 2019-11-03.
> In
> > > the
> > > > > past two
> > > > > > > > > > and a half years, the project has been renamed from
> TubeMQ
> > to
> > > > > InLong, and
> > > > > > > > > > expanded its scope from a message queue service to a
> > one-stop
> > > > > integration
> > > > > > > > > > framework for massive data.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > The InLong community has a discussion thread [1], passed
> > the
> > > > > community
> > > > > > > > > vote
> > > > > > > > > > [2], and the vote result is published [3]. Our assessment
> > is
> > > > > that Apache
> > > > > > > > > > InLong(Incubating) is ready to graduate as a TLP. We
> would
> > > like
> > > > > to raise
> > > > > > > > > > the discussion to IPMC and collect more feedback towards
> > > > > graduation.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Since incubating in ASF, the project itself has become
> more
> > > > > mature and
> > > > > > > > > > stable. The following is a brief summary of the project
> and
> > > > > community
> > > > > > > > > > during the incubation:
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > - 11 versions were released by 6 different release
> > managers,
> > > of
> > > > > which 5
> > > > > > > > > > versions are the original TubeMQ, and 6 versions are
> after
> > > the
> > > > > name was
> > > > > > > > > > changed to InLong. The release cadence is about 2 months
> > [4].
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > - 10 new Committers and 3 PPMCs were added during
> > incubating,
> > > > > they are
> > > > > > > > > from
> > > > > > > > > > 4 different organizations. All PPMCs and Committers are
> > > spread
> > > > > across 8
> > > > > > > > > > different organizations [5].
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > - 101 unique code developers [6].
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > - Closed more than 2200 issues, with an average of 200
> > issues
> > > > > per version
> > > > > > > > > > [7].
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > - All the dependencies were reviewed and ensured they do
> > not
> > > > > bring any
> > > > > > > > > > license issues [8].
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > - Evaluated the InLong project and self-checked the
> InLong
> > > > > maturity model
> > > > > > > > > > [9] and the pre-graduation Check [10].
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > - Well and Complete documentation for contributors and
> > users
> > > > > [11].
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > - Created channels like Email, Slack, Twitter, WeChat,
> and
> > > > GitHub
> > > > > > > > > > Discussions to communicate, with more than 650
> subscribers.
> > > > > > > > > >
> > > > > > > > > >
> > > > 

Re: [DISCUSSION] Incubating Proposal of Firestorm

[俊平堵]

I cannot agree more.
In ASF, we have many SQLs, MQs, streamings, etc, and some projects among
them are really awesome. We (in ASF) should not be in the position to ask
projects to merge but leave it to community (users and developers) of
projects to decide if they want to.
Appreciate Jerry and Yu who spend time to discuss the possibilities of
working together in some way.
+1 on the proposal and good luck to Firestorm!

Justin Mclean  于2022年5月18日周三 15:12写道：

> Hi,
>
> It would be good if the project could work together, but there isn’t
> anything wrong with having two similar incubating projects. If the projects
> decide not to join forces, we would welcome an incubating proposal from the
> other project. The ASF doesn't pick projects to use, we let the wider user
> community decide what they want to use.
>
> Kind Regards,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Graduate Apache MXNet (incubating) to a Top Level Project

[Joe Evans]

> > We have reached out to a few companies that were in violation, but have
> not
> > yet received any indication that they will fix them.
>
> Despite having PPMC members who work for those companies?
>

Sorry, I should have been more clear in the original email about who we
contacted. We contacted Alibaba and Jetware, which we do not have any PPMC
who work for these companies. We are currently working through issues from
AWS and Gluon, which we expect to be fixed very soon (in the next week.)


> > In this case, what are your suggestions on how to deal with these? Do we
> have legal resources at
> > Apache that could assist?
>
> I would try contacting them again. If they don’t respond then you should
> bring it up on trademarks@ to discuss the next steps.


Thanks. If we do not get the issues resolved soon, we will bring it up on
the trademarks@ list.

Joe

Re: [VOTE] Graduate Apache MXNet (incubating) to a Top Level Project

[Justin Mclean]

Hi,

> We have reached out to a few companies that were in violation, but have not
> yet received any indication that they will fix them.

Despite having PPMC members who work for those companies?

> In this case, what are your suggestions on how to deal with these? Do we have 
> legal resources at
> Apache that could assist?

I would try contacting them again. If they don’t respond then you should bring 
it up on trademarks@ to discuss the next steps.

Kind Regards,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Graduate Apache MXNet (incubating) to a Top Level Project

[Joe Evans]

Hi Justin,

Thanks for bringing this up. I have created a Github issue
 to track these
changes and work on a solution to proactively deal with these violations.
We have reached out to a few companies that were in violation, but have not
yet received any indication that they will fix them. In this case, what are
your suggestions on how to deal with these? Do we have legal resources at
Apache that could assist?

Thanks for your help.
Joe

On Tue, May 10, 2022 at 11:11 PM Justin Mclean 
wrote:

> Hi,
>
> A while back when I looked at the MxNet project there seemed to be a lot
> of trademark and branding issues. Have theses been addressed by the project?
>
> A quick google search seems to show they may not have been and some more
> work is needed here?
>
> https://hub.docker.com/u/mxnet
> https://hub.docker.com/r/mxnet/python
> https://anaconda.org/anaconda/mxnet
> https://cv.gluon.ai/tutorials/index.html
>
> https://www.alibabacloud.com/help/en/machine-learning-platform-for-ai/latest/download-mxnet-resources
> https://rocmdocs.amd.com/en/latest/Deep_learning/MXNet.html
> https://aws.amazon.com/marketplace/pp/prodview-wktuc2vochjwe
>
> Kind Regards,
> Justin
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] Graduate Apache InLong(Incubating) as a TLP

[Liang Chen]

+1, good luck.

Regards
Liang

tison  于2022年5月20日周五 18:13写道：

> +1 good luck
>
> Young Seung Andrew Ko 于2022年5月20日 周五17:36写道：
>
> > +1  (non-binding)
> >
> > Well done :)
> >
> > On Fri, May 20, 2022 at 6:32 PM wangxiaogang 
> > wrote:
> >
> > > +1, good luck；
> > >
> > >
> > > Eason Chen  于2022年5月20日周五 16:34写道：
> > >
> > > > + 1  （non-binding）
> > > >
> > > > Good luck!
> > > >
> > > > On Fri, May 20, 2022 at 3:43 PM XiaoYu  wrote:
> > > > >
> > > > > + 1  （non-binding）
> > > > >
> > > > > Good luck!
> > > > >
> > > > > Heal Chow  于2022年5月20日周五 15:16写道：
> > > > > >
> > > > > > +1.
> > > > > >
> > > > > > I've learned a lot about community collaboration and maintaining
> > open
> > > > source projects in the InLong project. Looking forward to InLong
> doing
> > > > better in data integration.
> > > > > >
> > > > > > Good luck!
> > > > > > HealChow
> > > > > >
> > > > > > On 2022/05/19 10:47:52 Goson zhang wrote:
> > > > > > > +1
> > > > > > >
> > > > > > > Since the InLong project entered the incubation pool, the team
> > has
> > > > > > > continued to grow, with the help of community contributors, the
> > > > project has
> > > > > > > developed from a single module to a mature data integration
> > > > framework, and
> > > > > > > has implemented the application of the project in multiple
> > > > environments.
> > > > > > >
> > > > > > > Looking forward to the continuous improvement of the InLong
> > project
> > > > to
> > > > > > > become a global community of contributors to better serve the
> big
> > > > data
> > > > > > > business.
> > > > > > >
> > > > > > > Thanks!
> > > > > > >
> > > > > > > Kent Yao  于2022年5月19日周四 17:25写道：
> > > > > > >
> > > > > > > > +1, good luck to InLong community
> > > > > > > >
> > > > > > > > Charles Zhang  于2022年5月19日周四
> 17:09写道：
> > > > > > > > >
> > > > > > > > > Dear Apache Incubator Community,
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > The InLong Project has been incubating since 2019-11-03. In
> > the
> > > > past two
> > > > > > > > > and a half years, the project has been renamed from TubeMQ
> to
> > > > InLong, and
> > > > > > > > > expanded its scope from a message queue service to a
> one-stop
> > > > integration
> > > > > > > > > framework for massive data.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > The InLong community has a discussion thread [1], passed
> the
> > > > community
> > > > > > > > vote
> > > > > > > > > [2], and the vote result is published [3]. Our assessment
> is
> > > > that Apache
> > > > > > > > > InLong(Incubating) is ready to graduate as a TLP. We would
> > like
> > > > to raise
> > > > > > > > > the discussion to IPMC and collect more feedback towards
> > > > graduation.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Since incubating in ASF, the project itself has become more
> > > > mature and
> > > > > > > > > stable. The following is a brief summary of the project and
> > > > community
> > > > > > > > > during the incubation:
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > - 11 versions were released by 6 different release
> managers,
> > of
> > > > which 5
> > > > > > > > > versions are the original TubeMQ, and 6 versions are after
> > the
> > > > name was
> > > > > > > > > changed to InLong. The release cadence is about 2 months
> [4].
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > - 10 new Committers and 3 PPMCs were added during
> incubating,
> > > > they are
> > > > > > > > from
> > > > > > > > > 4 different organizations. All PPMCs and Committers are
> > spread
> > > > across 8
> > > > > > > > > different organizations [5].
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > - 101 unique code developers [6].
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > - Closed more than 2200 issues, with an average of 200
> issues
> > > > per version
> > > > > > > > > [7].
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > - All the dependencies were reviewed and ensured they do
> not
> > > > bring any
> > > > > > > > > license issues [8].
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > - Evaluated the InLong project and self-checked the InLong
> > > > maturity model
> > > > > > > > > [9] and the pre-graduation Check [10].
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > - Well and Complete documentation for contributors and
> users
> > > > [11].
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > - Created channels like Email, Slack, Twitter, WeChat, and
> > > GitHub
> > > > > > > > > Discussions to communicate, with more than 650 subscribers.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > - Actively participated in or held more than 15 meetups to
> > > > increase
> > > > > > > > > community influence.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Please see the proposed board resolution below and let us
> > know
> > > > what you
> > > > > > > > > think. The initial PMC members were passed by the
> discussion
> > > and
> > > > > > > > invitation
> > > > > > > > 

Re: [DISCUSS] Graduate Apache Doris (Incubating) as TLP

[Justin Mclean]

Hi,

The project was aware of these issues before the graduation proposal was 
submitted, and some issues had been outstanding for more than a year. I 
understand it can be complex and take time dealing with 3rd parties about these 
issues, but I do have to ask if there are people from StarRocks on the PPMC, 
why was this not resolved earlier? Also why should those people, that have 
relicensed Apache Doris under Elastic License 2.0, be on the proposed PMC?

Also, this seems very reactive. Projects need to proactively manage their 
trademarks and brand and not just fix things when asked to.

Not a project problem, but I’ll also note that the StarRock changes mentioned 
are not enough to comply with the Apache license requirements. Small changes do 
not allow StarRocks to change the license of a file without the copyright 
holder's permission.

Kind Regards,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] Graduate Apache Doris (Incubating) as TLP

[Zhao Chun]

Yes, StarRocks is my employer now.
After I learned that there is a license issue in StarRocks codebase, I
informed this to the company.
When we realized the oversight, we changed the license headers ASAP.

Thanks,
Zhao Chun


John D. Ament  于2022年5月20日周五 20:27写道：

> On Fri, May 20, 2022 at 08:09 Zhao Chun  wrote:
>
> > Justin, thanks for your note.
> >
> > I'm one of Apache Doris PPMC members, and now working for StarRocks.
> >
> > We have our web developers update our web site to fix the
> > trademark/branding issues.
> >
> > We have also modified our codebase to ensure that unchanged files in our
> > repo bear the Apache license notice only.
> > This was an oversight on our part and we appreciate you bringing it to
> our
> > attention.
>
>
> StarRocks is your employer? These people are doing it because they were
> told to?
>
>
> >
> > Thanks,
> > Chun Zhao
> >
> >
> > Justin Mclean  于2022年5月15日周日 10:42写道：
> >
> > > Hi,
> > >
> > > In short:
> > > - There are still some trademark and branding issues, including some
> that
> > > the PPMC have been made aware of and have been outstanding for more
> than
> > a
> > > year.
> > > - Have the Doris trademark(s) been transferred to the ASF? AFAIK they
> > have
> > > not. [1][2] This issue has also been brought up wth the PPMC several
> > times.
> > > - What is the relationship between the proposed PPMC and chair to the
> > > StarRocks project?
> > > - StarRocks trademark and branding issues.
> > > - StarRocks licensing issues.
> > >
> > > Kind Regards,
> > > Justin
> > >
> > > 1. https://www.apache.org/foundation/marks/faq/#incubator
> > > 2. https://www.apache.org/foundation/marks/list/
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> >
>

Re: [DISCUSS] Graduate Apache Doris (Incubating) as TLP

[John D. Ament]

On Fri, May 20, 2022 at 08:09 Zhao Chun  wrote:

> Justin, thanks for your note.
>
> I'm one of Apache Doris PPMC members, and now working for StarRocks.
>
> We have our web developers update our web site to fix the
> trademark/branding issues.
>
> We have also modified our codebase to ensure that unchanged files in our
> repo bear the Apache license notice only.
> This was an oversight on our part and we appreciate you bringing it to our
> attention.


StarRocks is your employer? These people are doing it because they were
told to?


>
> Thanks,
> Chun Zhao
>
>
> Justin Mclean  于2022年5月15日周日 10:42写道：
>
> > Hi,
> >
> > In short:
> > - There are still some trademark and branding issues, including some that
> > the PPMC have been made aware of and have been outstanding for more than
> a
> > year.
> > - Have the Doris trademark(s) been transferred to the ASF? AFAIK they
> have
> > not. [1][2] This issue has also been brought up wth the PPMC several
> times.
> > - What is the relationship between the proposed PPMC and chair to the
> > StarRocks project?
> > - StarRocks trademark and branding issues.
> > - StarRocks licensing issues.
> >
> > Kind Regards,
> > Justin
> >
> > 1. https://www.apache.org/foundation/marks/faq/#incubator
> > 2. https://www.apache.org/foundation/marks/list/
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [DISCUSS] Graduate Apache Doris (Incubating) as TLP

[Zhao Chun]

Justin, thanks for your note.

I'm one of Apache Doris PPMC members, and now working for StarRocks.

We have our web developers update our web site to fix the
trademark/branding issues.

We have also modified our codebase to ensure that unchanged files in our
repo bear the Apache license notice only.
This was an oversight on our part and we appreciate you bringing it to our
attention.

Thanks,
Chun Zhao


Justin Mclean  于2022年5月15日周日 10:42写道：

> Hi,
>
> In short:
> - There are still some trademark and branding issues, including some that
> the PPMC have been made aware of and have been outstanding for more than a
> year.
> - Have the Doris trademark(s) been transferred to the ASF? AFAIK they have
> not. [1][2] This issue has also been brought up wth the PPMC several times.
> - What is the relationship between the proposed PPMC and chair to the
> StarRocks project?
> - StarRocks trademark and branding issues.
> - StarRocks licensing issues.
>
> Kind Regards,
> Justin
>
> 1. https://www.apache.org/foundation/marks/faq/#incubator
> 2. https://www.apache.org/foundation/marks/list/
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] Graduate Apache InLong(Incubating) as a TLP

[tison]

+1 good luck

Young Seung Andrew Ko 于2022年5月20日 周五17:36写道：

> +1  (non-binding)
>
> Well done :)
>
> On Fri, May 20, 2022 at 6:32 PM wangxiaogang 
> wrote:
>
> > +1, good luck；
> >
> >
> > Eason Chen  于2022年5月20日周五 16:34写道：
> >
> > > + 1  （non-binding）
> > >
> > > Good luck!
> > >
> > > On Fri, May 20, 2022 at 3:43 PM XiaoYu  wrote:
> > > >
> > > > + 1  （non-binding）
> > > >
> > > > Good luck!
> > > >
> > > > Heal Chow  于2022年5月20日周五 15:16写道：
> > > > >
> > > > > +1.
> > > > >
> > > > > I've learned a lot about community collaboration and maintaining
> open
> > > source projects in the InLong project. Looking forward to InLong doing
> > > better in data integration.
> > > > >
> > > > > Good luck!
> > > > > HealChow
> > > > >
> > > > > On 2022/05/19 10:47:52 Goson zhang wrote:
> > > > > > +1
> > > > > >
> > > > > > Since the InLong project entered the incubation pool, the team
> has
> > > > > > continued to grow, with the help of community contributors, the
> > > project has
> > > > > > developed from a single module to a mature data integration
> > > framework, and
> > > > > > has implemented the application of the project in multiple
> > > environments.
> > > > > >
> > > > > > Looking forward to the continuous improvement of the InLong
> project
> > > to
> > > > > > become a global community of contributors to better serve the big
> > > data
> > > > > > business.
> > > > > >
> > > > > > Thanks!
> > > > > >
> > > > > > Kent Yao  于2022年5月19日周四 17:25写道：
> > > > > >
> > > > > > > +1, good luck to InLong community
> > > > > > >
> > > > > > > Charles Zhang  于2022年5月19日周四 17:09写道：
> > > > > > > >
> > > > > > > > Dear Apache Incubator Community,
> > > > > > > >
> > > > > > > >
> > > > > > > > The InLong Project has been incubating since 2019-11-03. In
> the
> > > past two
> > > > > > > > and a half years, the project has been renamed from TubeMQ to
> > > InLong, and
> > > > > > > > expanded its scope from a message queue service to a one-stop
> > > integration
> > > > > > > > framework for massive data.
> > > > > > > >
> > > > > > > >
> > > > > > > > The InLong community has a discussion thread [1], passed the
> > > community
> > > > > > > vote
> > > > > > > > [2], and the vote result is published [3]. Our assessment is
> > > that Apache
> > > > > > > > InLong(Incubating) is ready to graduate as a TLP. We would
> like
> > > to raise
> > > > > > > > the discussion to IPMC and collect more feedback towards
> > > graduation.
> > > > > > > >
> > > > > > > >
> > > > > > > > Since incubating in ASF, the project itself has become more
> > > mature and
> > > > > > > > stable. The following is a brief summary of the project and
> > > community
> > > > > > > > during the incubation:
> > > > > > > >
> > > > > > > >
> > > > > > > > - 11 versions were released by 6 different release managers,
> of
> > > which 5
> > > > > > > > versions are the original TubeMQ, and 6 versions are after
> the
> > > name was
> > > > > > > > changed to InLong. The release cadence is about 2 months [4].
> > > > > > > >
> > > > > > > >
> > > > > > > > - 10 new Committers and 3 PPMCs were added during incubating,
> > > they are
> > > > > > > from
> > > > > > > > 4 different organizations. All PPMCs and Committers are
> spread
> > > across 8
> > > > > > > > different organizations [5].
> > > > > > > >
> > > > > > > >
> > > > > > > > - 101 unique code developers [6].
> > > > > > > >
> > > > > > > >
> > > > > > > > - Closed more than 2200 issues, with an average of 200 issues
> > > per version
> > > > > > > > [7].
> > > > > > > >
> > > > > > > >
> > > > > > > > - All the dependencies were reviewed and ensured they do not
> > > bring any
> > > > > > > > license issues [8].
> > > > > > > >
> > > > > > > >
> > > > > > > > - Evaluated the InLong project and self-checked the InLong
> > > maturity model
> > > > > > > > [9] and the pre-graduation Check [10].
> > > > > > > >
> > > > > > > >
> > > > > > > > - Well and Complete documentation for contributors and users
> > > [11].
> > > > > > > >
> > > > > > > >
> > > > > > > > - Created channels like Email, Slack, Twitter, WeChat, and
> > GitHub
> > > > > > > > Discussions to communicate, with more than 650 subscribers.
> > > > > > > >
> > > > > > > >
> > > > > > > > - Actively participated in or held more than 15 meetups to
> > > increase
> > > > > > > > community influence.
> > > > > > > >
> > > > > > > >
> > > > > > > > Please see the proposed board resolution below and let us
> know
> > > what you
> > > > > > > > think. The initial PMC members were passed by the discussion
> > and
> > > > > > > invitation
> > > > > > > > [12].
> > > > > > > >
> > > > > > > >
> > > > > > > > The discussion will remain open for at least 72 hours,
> looking
> > > forward to
> > > > > > > > your feedback.
> > > > > > > >
> > > > > > > >
> > > > > > > > [1]
> > > https://lists.apache.org/thread/pzqk3z4pbbh3qx0cl1hmpzo1305p2lro
> > > > > > > >
> > > > > > > > [2]
> > > 

[VOTE] Release Apache Linkis (Incubating) 1.1.1-RC2

[peacewong]

Hello Incubator Community,

This is a call for a vote to release Apache Linkis(Incubating) version
1.1.1-RC2

The Apache Linkis community has voted on and approved a proposal to release
Apache Linkis(Incubating) version  1.1.1-RC2

We now kindly request the Incubator PMC members review and vote on this
incubator release.

The RC2 version mainly optimizes the problems reported by Justin in RC1
1. Removed maven-wrapper.jar from source release and fix mvnw the
wrong line endings
2. Upgrade py4j version to py4j-0.10.9.5 solve the license issue.
3. In addition, the current compilation instructions in the readme
are to jump to the linkis official website 'Compile Guide', and the Linkis
community will pay attention to the validity of the link. And in the
future, it will be optimized to give compilation instructions directly in
  the readme.

Linkis community vote thread:
•

https://lists.apache.org/thread/fokdzv8q8yq6r0kyodjgzcvsfl2t44r7

Vote result thread:
• https://lists.apache.org/thread/g2jkwxck8scl584vk39glwbkhokszhxl

The release candidate:
• https://dist.apache.org/repos/dist/dev/incubator/linkis/1.1.1-RC2/

Git tag for the release:
•
https://github.com/apache/incubator-linkis/releases/tag/release-1.1.1-rc2

Release notes:
•  https://linkis.apache.org/docs/1.1.1/release-notes-1.1.1/

The artifacts signed with PGP key [ 38C76105 ], corresponding to [
peacew...@apache.com], that can be found in keys file:
• https://downloads.apache.org/incubator/linkis/KEYS



This is the first non DISCLAIMER-WIP version after joining the ASF incubator


The vote will be open for at least 72 hours or until necessary
number of votes are reached.

Please vote accordingly:

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove with the reason

More detail checklist  please refer:
•
https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist

Steps to validate the release，Please refer to:
• https://linkis.apache.org/community/how-to-verify

Thanks,
On behalf of Apache Linkis(Incubating) community

Re: [DISCUSS] Graduate Apache InLong(Incubating) as a TLP

[Young Seung Andrew Ko]

+1  (non-binding)

Well done :)

On Fri, May 20, 2022 at 6:32 PM wangxiaogang 
wrote:

> +1, good luck；
>
>
> Eason Chen  于2022年5月20日周五 16:34写道：
>
> > + 1  （non-binding）
> >
> > Good luck!
> >
> > On Fri, May 20, 2022 at 3:43 PM XiaoYu  wrote:
> > >
> > > + 1  （non-binding）
> > >
> > > Good luck!
> > >
> > > Heal Chow  于2022年5月20日周五 15:16写道：
> > > >
> > > > +1.
> > > >
> > > > I've learned a lot about community collaboration and maintaining open
> > source projects in the InLong project. Looking forward to InLong doing
> > better in data integration.
> > > >
> > > > Good luck!
> > > > HealChow
> > > >
> > > > On 2022/05/19 10:47:52 Goson zhang wrote:
> > > > > +1
> > > > >
> > > > > Since the InLong project entered the incubation pool, the team has
> > > > > continued to grow, with the help of community contributors, the
> > project has
> > > > > developed from a single module to a mature data integration
> > framework, and
> > > > > has implemented the application of the project in multiple
> > environments.
> > > > >
> > > > > Looking forward to the continuous improvement of the InLong project
> > to
> > > > > become a global community of contributors to better serve the big
> > data
> > > > > business.
> > > > >
> > > > > Thanks!
> > > > >
> > > > > Kent Yao  于2022年5月19日周四 17:25写道：
> > > > >
> > > > > > +1, good luck to InLong community
> > > > > >
> > > > > > Charles Zhang  于2022年5月19日周四 17:09写道：
> > > > > > >
> > > > > > > Dear Apache Incubator Community,
> > > > > > >
> > > > > > >
> > > > > > > The InLong Project has been incubating since 2019-11-03. In the
> > past two
> > > > > > > and a half years, the project has been renamed from TubeMQ to
> > InLong, and
> > > > > > > expanded its scope from a message queue service to a one-stop
> > integration
> > > > > > > framework for massive data.
> > > > > > >
> > > > > > >
> > > > > > > The InLong community has a discussion thread [1], passed the
> > community
> > > > > > vote
> > > > > > > [2], and the vote result is published [3]. Our assessment is
> > that Apache
> > > > > > > InLong(Incubating) is ready to graduate as a TLP. We would like
> > to raise
> > > > > > > the discussion to IPMC and collect more feedback towards
> > graduation.
> > > > > > >
> > > > > > >
> > > > > > > Since incubating in ASF, the project itself has become more
> > mature and
> > > > > > > stable. The following is a brief summary of the project and
> > community
> > > > > > > during the incubation:
> > > > > > >
> > > > > > >
> > > > > > > - 11 versions were released by 6 different release managers, of
> > which 5
> > > > > > > versions are the original TubeMQ, and 6 versions are after the
> > name was
> > > > > > > changed to InLong. The release cadence is about 2 months [4].
> > > > > > >
> > > > > > >
> > > > > > > - 10 new Committers and 3 PPMCs were added during incubating,
> > they are
> > > > > > from
> > > > > > > 4 different organizations. All PPMCs and Committers are spread
> > across 8
> > > > > > > different organizations [5].
> > > > > > >
> > > > > > >
> > > > > > > - 101 unique code developers [6].
> > > > > > >
> > > > > > >
> > > > > > > - Closed more than 2200 issues, with an average of 200 issues
> > per version
> > > > > > > [7].
> > > > > > >
> > > > > > >
> > > > > > > - All the dependencies were reviewed and ensured they do not
> > bring any
> > > > > > > license issues [8].
> > > > > > >
> > > > > > >
> > > > > > > - Evaluated the InLong project and self-checked the InLong
> > maturity model
> > > > > > > [9] and the pre-graduation Check [10].
> > > > > > >
> > > > > > >
> > > > > > > - Well and Complete documentation for contributors and users
> > [11].
> > > > > > >
> > > > > > >
> > > > > > > - Created channels like Email, Slack, Twitter, WeChat, and
> GitHub
> > > > > > > Discussions to communicate, with more than 650 subscribers.
> > > > > > >
> > > > > > >
> > > > > > > - Actively participated in or held more than 15 meetups to
> > increase
> > > > > > > community influence.
> > > > > > >
> > > > > > >
> > > > > > > Please see the proposed board resolution below and let us know
> > what you
> > > > > > > think. The initial PMC members were passed by the discussion
> and
> > > > > > invitation
> > > > > > > [12].
> > > > > > >
> > > > > > >
> > > > > > > The discussion will remain open for at least 72 hours, looking
> > forward to
> > > > > > > your feedback.
> > > > > > >
> > > > > > >
> > > > > > > [1]
> > https://lists.apache.org/thread/pzqk3z4pbbh3qx0cl1hmpzo1305p2lro
> > > > > > >
> > > > > > > [2]
> > https://lists.apache.org/thread/03topv74zgp4j22cg805l50sqzcr3y20
> > > > > > >
> > > > > > > [3]
> > https://lists.apache.org/thread/n1mkcplz53ytlmhk7r506toxgsv6rfw9
> > > > > > >
> > > > > > > [4] https://inlong.apache.org/download/main/
> > > > > > >
> > > > > > > [5] https://whimsy.apache.org/roster/ppmc/inlong
> > > > > > >
> > > > > > > [6]
> > https://github.com/apache/incubator-inlong/graphs/contributors
> > > > > > >
> > > > > > > 

Re: [DISCUSS] Graduate Apache InLong(Incubating) as a TLP

[wangxiaogang]

+1, good luck；


Eason Chen  于2022年5月20日周五 16:34写道：

> + 1  （non-binding）
>
> Good luck!
>
> On Fri, May 20, 2022 at 3:43 PM XiaoYu  wrote:
> >
> > + 1  （non-binding）
> >
> > Good luck!
> >
> > Heal Chow  于2022年5月20日周五 15:16写道：
> > >
> > > +1.
> > >
> > > I've learned a lot about community collaboration and maintaining open
> source projects in the InLong project. Looking forward to InLong doing
> better in data integration.
> > >
> > > Good luck!
> > > HealChow
> > >
> > > On 2022/05/19 10:47:52 Goson zhang wrote:
> > > > +1
> > > >
> > > > Since the InLong project entered the incubation pool, the team has
> > > > continued to grow, with the help of community contributors, the
> project has
> > > > developed from a single module to a mature data integration
> framework, and
> > > > has implemented the application of the project in multiple
> environments.
> > > >
> > > > Looking forward to the continuous improvement of the InLong project
> to
> > > > become a global community of contributors to better serve the big
> data
> > > > business.
> > > >
> > > > Thanks!
> > > >
> > > > Kent Yao  于2022年5月19日周四 17:25写道：
> > > >
> > > > > +1, good luck to InLong community
> > > > >
> > > > > Charles Zhang  于2022年5月19日周四 17:09写道：
> > > > > >
> > > > > > Dear Apache Incubator Community,
> > > > > >
> > > > > >
> > > > > > The InLong Project has been incubating since 2019-11-03. In the
> past two
> > > > > > and a half years, the project has been renamed from TubeMQ to
> InLong, and
> > > > > > expanded its scope from a message queue service to a one-stop
> integration
> > > > > > framework for massive data.
> > > > > >
> > > > > >
> > > > > > The InLong community has a discussion thread [1], passed the
> community
> > > > > vote
> > > > > > [2], and the vote result is published [3]. Our assessment is
> that Apache
> > > > > > InLong(Incubating) is ready to graduate as a TLP. We would like
> to raise
> > > > > > the discussion to IPMC and collect more feedback towards
> graduation.
> > > > > >
> > > > > >
> > > > > > Since incubating in ASF, the project itself has become more
> mature and
> > > > > > stable. The following is a brief summary of the project and
> community
> > > > > > during the incubation:
> > > > > >
> > > > > >
> > > > > > - 11 versions were released by 6 different release managers, of
> which 5
> > > > > > versions are the original TubeMQ, and 6 versions are after the
> name was
> > > > > > changed to InLong. The release cadence is about 2 months [4].
> > > > > >
> > > > > >
> > > > > > - 10 new Committers and 3 PPMCs were added during incubating,
> they are
> > > > > from
> > > > > > 4 different organizations. All PPMCs and Committers are spread
> across 8
> > > > > > different organizations [5].
> > > > > >
> > > > > >
> > > > > > - 101 unique code developers [6].
> > > > > >
> > > > > >
> > > > > > - Closed more than 2200 issues, with an average of 200 issues
> per version
> > > > > > [7].
> > > > > >
> > > > > >
> > > > > > - All the dependencies were reviewed and ensured they do not
> bring any
> > > > > > license issues [8].
> > > > > >
> > > > > >
> > > > > > - Evaluated the InLong project and self-checked the InLong
> maturity model
> > > > > > [9] and the pre-graduation Check [10].
> > > > > >
> > > > > >
> > > > > > - Well and Complete documentation for contributors and users
> [11].
> > > > > >
> > > > > >
> > > > > > - Created channels like Email, Slack, Twitter, WeChat, and GitHub
> > > > > > Discussions to communicate, with more than 650 subscribers.
> > > > > >
> > > > > >
> > > > > > - Actively participated in or held more than 15 meetups to
> increase
> > > > > > community influence.
> > > > > >
> > > > > >
> > > > > > Please see the proposed board resolution below and let us know
> what you
> > > > > > think. The initial PMC members were passed by the discussion and
> > > > > invitation
> > > > > > [12].
> > > > > >
> > > > > >
> > > > > > The discussion will remain open for at least 72 hours, looking
> forward to
> > > > > > your feedback.
> > > > > >
> > > > > >
> > > > > > [1]
> https://lists.apache.org/thread/pzqk3z4pbbh3qx0cl1hmpzo1305p2lro
> > > > > >
> > > > > > [2]
> https://lists.apache.org/thread/03topv74zgp4j22cg805l50sqzcr3y20
> > > > > >
> > > > > > [3]
> https://lists.apache.org/thread/n1mkcplz53ytlmhk7r506toxgsv6rfw9
> > > > > >
> > > > > > [4] https://inlong.apache.org/download/main/
> > > > > >
> > > > > > [5] https://whimsy.apache.org/roster/ppmc/inlong
> > > > > >
> > > > > > [6]
> https://github.com/apache/incubator-inlong/graphs/contributors
> > > > > >
> > > > > > [7]
> > > > > >
> > > > >
> https://github.com/apache/incubator-inlong/issues?q=is%3Aissue+is%3Aclosed
> > > > > >
> > > > > > [8]
> https://github.com/apache/incubator-inlong/tree/master/licenses
> > > > > >
> > > > > > [9]
> > > > > >
> > > > >
> https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=INLONG=Maturity+Assessment+for+InLong
> > > > > >
> > > > > > [10]
> > > > > >
> 

Re: Proposal

[Bertrand Delacretaz]

Hi,

Le ven. 20 mai 2022 à 00:33, m sacks  a écrit :
>
> And if i want to publish it without building community just publish to
> github if i understand correctly?...

You can do that, and if you have plans to join the ASF later it's
useful to take a look at [1] and ideally shape your emerging community
along these lines.

And also look at [2] as mentioned earlier, which is more specifically
about the ASF Incubator.

-Bertrand

[1] https://community.apache.org/apache-way/apache-project-maturity-model.html
[2] https://incubator.apache.org/cookbook/

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] Graduate Apache InLong(Incubating) as a TLP

[Eason Chen]

+ 1  （non-binding）

Good luck!

On Fri, May 20, 2022 at 3:43 PM XiaoYu  wrote:
>
> + 1  （non-binding）
>
> Good luck!
>
> Heal Chow  于2022年5月20日周五 15:16写道：
> >
> > +1.
> >
> > I've learned a lot about community collaboration and maintaining open 
> > source projects in the InLong project. Looking forward to InLong doing 
> > better in data integration.
> >
> > Good luck!
> > HealChow
> >
> > On 2022/05/19 10:47:52 Goson zhang wrote:
> > > +1
> > >
> > > Since the InLong project entered the incubation pool, the team has
> > > continued to grow, with the help of community contributors, the project 
> > > has
> > > developed from a single module to a mature data integration framework, and
> > > has implemented the application of the project in multiple environments.
> > >
> > > Looking forward to the continuous improvement of the InLong project to
> > > become a global community of contributors to better serve the big data
> > > business.
> > >
> > > Thanks!
> > >
> > > Kent Yao  于2022年5月19日周四 17:25写道：
> > >
> > > > +1, good luck to InLong community
> > > >
> > > > Charles Zhang  于2022年5月19日周四 17:09写道：
> > > > >
> > > > > Dear Apache Incubator Community,
> > > > >
> > > > >
> > > > > The InLong Project has been incubating since 2019-11-03. In the past 
> > > > > two
> > > > > and a half years, the project has been renamed from TubeMQ to InLong, 
> > > > > and
> > > > > expanded its scope from a message queue service to a one-stop 
> > > > > integration
> > > > > framework for massive data.
> > > > >
> > > > >
> > > > > The InLong community has a discussion thread [1], passed the community
> > > > vote
> > > > > [2], and the vote result is published [3]. Our assessment is that 
> > > > > Apache
> > > > > InLong(Incubating) is ready to graduate as a TLP. We would like to 
> > > > > raise
> > > > > the discussion to IPMC and collect more feedback towards graduation.
> > > > >
> > > > >
> > > > > Since incubating in ASF, the project itself has become more mature and
> > > > > stable. The following is a brief summary of the project and community
> > > > > during the incubation:
> > > > >
> > > > >
> > > > > - 11 versions were released by 6 different release managers, of which 
> > > > > 5
> > > > > versions are the original TubeMQ, and 6 versions are after the name 
> > > > > was
> > > > > changed to InLong. The release cadence is about 2 months [4].
> > > > >
> > > > >
> > > > > - 10 new Committers and 3 PPMCs were added during incubating, they are
> > > > from
> > > > > 4 different organizations. All PPMCs and Committers are spread across 
> > > > > 8
> > > > > different organizations [5].
> > > > >
> > > > >
> > > > > - 101 unique code developers [6].
> > > > >
> > > > >
> > > > > - Closed more than 2200 issues, with an average of 200 issues per 
> > > > > version
> > > > > [7].
> > > > >
> > > > >
> > > > > - All the dependencies were reviewed and ensured they do not bring any
> > > > > license issues [8].
> > > > >
> > > > >
> > > > > - Evaluated the InLong project and self-checked the InLong maturity 
> > > > > model
> > > > > [9] and the pre-graduation Check [10].
> > > > >
> > > > >
> > > > > - Well and Complete documentation for contributors and users [11].
> > > > >
> > > > >
> > > > > - Created channels like Email, Slack, Twitter, WeChat, and GitHub
> > > > > Discussions to communicate, with more than 650 subscribers.
> > > > >
> > > > >
> > > > > - Actively participated in or held more than 15 meetups to increase
> > > > > community influence.
> > > > >
> > > > >
> > > > > Please see the proposed board resolution below and let us know what 
> > > > > you
> > > > > think. The initial PMC members were passed by the discussion and
> > > > invitation
> > > > > [12].
> > > > >
> > > > >
> > > > > The discussion will remain open for at least 72 hours, looking 
> > > > > forward to
> > > > > your feedback.
> > > > >
> > > > >
> > > > > [1] https://lists.apache.org/thread/pzqk3z4pbbh3qx0cl1hmpzo1305p2lro
> > > > >
> > > > > [2] https://lists.apache.org/thread/03topv74zgp4j22cg805l50sqzcr3y20
> > > > >
> > > > > [3] https://lists.apache.org/thread/n1mkcplz53ytlmhk7r506toxgsv6rfw9
> > > > >
> > > > > [4] https://inlong.apache.org/download/main/
> > > > >
> > > > > [5] https://whimsy.apache.org/roster/ppmc/inlong
> > > > >
> > > > > [6] https://github.com/apache/incubator-inlong/graphs/contributors
> > > > >
> > > > > [7]
> > > > >
> > > > https://github.com/apache/incubator-inlong/issues?q=is%3Aissue+is%3Aclosed
> > > > >
> > > > > [8] https://github.com/apache/incubator-inlong/tree/master/licenses
> > > > >
> > > > > [9]
> > > > >
> > > > https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=INLONG=Maturity+Assessment+for+InLong
> > > > >
> > > > > [10]
> > > > > https://cwiki.apache.org/confluence/display/INLONG/Graduation+Check+List
> > > > >
> > > > > [11] https://inlong.apache.org/docs/next/introduction
> > > > >
> > > > > [12] https://lists.apache.org/thread/mgl2jgpdojb6dzdhnhoq7dfqs26hj2xc
> 

Re: [DISCUSS] Graduate Apache InLong(Incubating) as a TLP

[XiaoYu]

+ 1  （non-binding）

Good luck!

Heal Chow  于2022年5月20日周五 15:16写道：
>
> +1.
>
> I've learned a lot about community collaboration and maintaining open source 
> projects in the InLong project. Looking forward to InLong doing better in 
> data integration.
>
> Good luck!
> HealChow
>
> On 2022/05/19 10:47:52 Goson zhang wrote:
> > +1
> >
> > Since the InLong project entered the incubation pool, the team has
> > continued to grow, with the help of community contributors, the project has
> > developed from a single module to a mature data integration framework, and
> > has implemented the application of the project in multiple environments.
> >
> > Looking forward to the continuous improvement of the InLong project to
> > become a global community of contributors to better serve the big data
> > business.
> >
> > Thanks!
> >
> > Kent Yao  于2022年5月19日周四 17:25写道：
> >
> > > +1, good luck to InLong community
> > >
> > > Charles Zhang  于2022年5月19日周四 17:09写道：
> > > >
> > > > Dear Apache Incubator Community,
> > > >
> > > >
> > > > The InLong Project has been incubating since 2019-11-03. In the past two
> > > > and a half years, the project has been renamed from TubeMQ to InLong, 
> > > > and
> > > > expanded its scope from a message queue service to a one-stop 
> > > > integration
> > > > framework for massive data.
> > > >
> > > >
> > > > The InLong community has a discussion thread [1], passed the community
> > > vote
> > > > [2], and the vote result is published [3]. Our assessment is that Apache
> > > > InLong(Incubating) is ready to graduate as a TLP. We would like to raise
> > > > the discussion to IPMC and collect more feedback towards graduation.
> > > >
> > > >
> > > > Since incubating in ASF, the project itself has become more mature and
> > > > stable. The following is a brief summary of the project and community
> > > > during the incubation:
> > > >
> > > >
> > > > - 11 versions were released by 6 different release managers, of which 5
> > > > versions are the original TubeMQ, and 6 versions are after the name was
> > > > changed to InLong. The release cadence is about 2 months [4].
> > > >
> > > >
> > > > - 10 new Committers and 3 PPMCs were added during incubating, they are
> > > from
> > > > 4 different organizations. All PPMCs and Committers are spread across 8
> > > > different organizations [5].
> > > >
> > > >
> > > > - 101 unique code developers [6].
> > > >
> > > >
> > > > - Closed more than 2200 issues, with an average of 200 issues per 
> > > > version
> > > > [7].
> > > >
> > > >
> > > > - All the dependencies were reviewed and ensured they do not bring any
> > > > license issues [8].
> > > >
> > > >
> > > > - Evaluated the InLong project and self-checked the InLong maturity 
> > > > model
> > > > [9] and the pre-graduation Check [10].
> > > >
> > > >
> > > > - Well and Complete documentation for contributors and users [11].
> > > >
> > > >
> > > > - Created channels like Email, Slack, Twitter, WeChat, and GitHub
> > > > Discussions to communicate, with more than 650 subscribers.
> > > >
> > > >
> > > > - Actively participated in or held more than 15 meetups to increase
> > > > community influence.
> > > >
> > > >
> > > > Please see the proposed board resolution below and let us know what you
> > > > think. The initial PMC members were passed by the discussion and
> > > invitation
> > > > [12].
> > > >
> > > >
> > > > The discussion will remain open for at least 72 hours, looking forward 
> > > > to
> > > > your feedback.
> > > >
> > > >
> > > > [1] https://lists.apache.org/thread/pzqk3z4pbbh3qx0cl1hmpzo1305p2lro
> > > >
> > > > [2] https://lists.apache.org/thread/03topv74zgp4j22cg805l50sqzcr3y20
> > > >
> > > > [3] https://lists.apache.org/thread/n1mkcplz53ytlmhk7r506toxgsv6rfw9
> > > >
> > > > [4] https://inlong.apache.org/download/main/
> > > >
> > > > [5] https://whimsy.apache.org/roster/ppmc/inlong
> > > >
> > > > [6] https://github.com/apache/incubator-inlong/graphs/contributors
> > > >
> > > > [7]
> > > >
> > > https://github.com/apache/incubator-inlong/issues?q=is%3Aissue+is%3Aclosed
> > > >
> > > > [8] https://github.com/apache/incubator-inlong/tree/master/licenses
> > > >
> > > > [9]
> > > >
> > > https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=INLONG=Maturity+Assessment+for+InLong
> > > >
> > > > [10]
> > > > https://cwiki.apache.org/confluence/display/INLONG/Graduation+Check+List
> > > >
> > > > [11] https://inlong.apache.org/docs/next/introduction
> > > >
> > > > [12] https://lists.apache.org/thread/mgl2jgpdojb6dzdhnhoq7dfqs26hj2xc
> > > >
> > > >
> > > >
> > > --
> > > >
> > > > Establish the Apache InLong Project
> > > >
> > > >
> > > > WHEREAS, the Board of Directors deems it to be in the best interests of
> > > >
> > > > the Foundation and consistent with the Foundation's purpose to establish
> > > >
> > > > a Project Management 

Re: [DISCUSS] Graduate Apache InLong(Incubating) as a TLP

[Heal Chow]

+1.

I've learned a lot about community collaboration and maintaining open source 
projects in the InLong project. Looking forward to InLong doing better in data 
integration.

Good luck!
HealChow

On 2022/05/19 10:47:52 Goson zhang wrote:
> +1
> 
> Since the InLong project entered the incubation pool, the team has
> continued to grow, with the help of community contributors, the project has
> developed from a single module to a mature data integration framework, and
> has implemented the application of the project in multiple environments.
> 
> Looking forward to the continuous improvement of the InLong project to
> become a global community of contributors to better serve the big data
> business.
> 
> Thanks!
> 
> Kent Yao  于2022年5月19日周四 17:25写道：
> 
> > +1, good luck to InLong community
> >
> > Charles Zhang  于2022年5月19日周四 17:09写道：
> > >
> > > Dear Apache Incubator Community,
> > >
> > >
> > > The InLong Project has been incubating since 2019-11-03. In the past two
> > > and a half years, the project has been renamed from TubeMQ to InLong, and
> > > expanded its scope from a message queue service to a one-stop integration
> > > framework for massive data.
> > >
> > >
> > > The InLong community has a discussion thread [1], passed the community
> > vote
> > > [2], and the vote result is published [3]. Our assessment is that Apache
> > > InLong(Incubating) is ready to graduate as a TLP. We would like to raise
> > > the discussion to IPMC and collect more feedback towards graduation.
> > >
> > >
> > > Since incubating in ASF, the project itself has become more mature and
> > > stable. The following is a brief summary of the project and community
> > > during the incubation:
> > >
> > >
> > > - 11 versions were released by 6 different release managers, of which 5
> > > versions are the original TubeMQ, and 6 versions are after the name was
> > > changed to InLong. The release cadence is about 2 months [4].
> > >
> > >
> > > - 10 new Committers and 3 PPMCs were added during incubating, they are
> > from
> > > 4 different organizations. All PPMCs and Committers are spread across 8
> > > different organizations [5].
> > >
> > >
> > > - 101 unique code developers [6].
> > >
> > >
> > > - Closed more than 2200 issues, with an average of 200 issues per version
> > > [7].
> > >
> > >
> > > - All the dependencies were reviewed and ensured they do not bring any
> > > license issues [8].
> > >
> > >
> > > - Evaluated the InLong project and self-checked the InLong maturity model
> > > [9] and the pre-graduation Check [10].
> > >
> > >
> > > - Well and Complete documentation for contributors and users [11].
> > >
> > >
> > > - Created channels like Email, Slack, Twitter, WeChat, and GitHub
> > > Discussions to communicate, with more than 650 subscribers.
> > >
> > >
> > > - Actively participated in or held more than 15 meetups to increase
> > > community influence.
> > >
> > >
> > > Please see the proposed board resolution below and let us know what you
> > > think. The initial PMC members were passed by the discussion and
> > invitation
> > > [12].
> > >
> > >
> > > The discussion will remain open for at least 72 hours, looking forward to
> > > your feedback.
> > >
> > >
> > > [1] https://lists.apache.org/thread/pzqk3z4pbbh3qx0cl1hmpzo1305p2lro
> > >
> > > [2] https://lists.apache.org/thread/03topv74zgp4j22cg805l50sqzcr3y20
> > >
> > > [3] https://lists.apache.org/thread/n1mkcplz53ytlmhk7r506toxgsv6rfw9
> > >
> > > [4] https://inlong.apache.org/download/main/
> > >
> > > [5] https://whimsy.apache.org/roster/ppmc/inlong
> > >
> > > [6] https://github.com/apache/incubator-inlong/graphs/contributors
> > >
> > > [7]
> > >
> > https://github.com/apache/incubator-inlong/issues?q=is%3Aissue+is%3Aclosed
> > >
> > > [8] https://github.com/apache/incubator-inlong/tree/master/licenses
> > >
> > > [9]
> > >
> > https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=INLONG=Maturity+Assessment+for+InLong
> > >
> > > [10]
> > > https://cwiki.apache.org/confluence/display/INLONG/Graduation+Check+List
> > >
> > > [11] https://inlong.apache.org/docs/next/introduction
> > >
> > > [12] https://lists.apache.org/thread/mgl2jgpdojb6dzdhnhoq7dfqs26hj2xc
> > >
> > >
> > >
> > --
> > >
> > > Establish the Apache InLong Project
> > >
> > >
> > > WHEREAS, the Board of Directors deems it to be in the best interests of
> > >
> > > the Foundation and consistent with the Foundation's purpose to establish
> > >
> > > a Project Management Committee charged with the creation and maintenance
> > >
> > > of open-source software, for distribution at no charge to the public,
> > >
> > > related to a one-stop data integration framework that provides
> > >
> > > automatic, secure, and reliable data transmission capabilities. InLong
> > >
> > > supports both batch and stream data processing at the same time, which
> > >
> > >