Re: [DISCUSSION] Incubating Proposal of Firestorm

2022-05-18 Thread Yu Li
Thanks Willem for the coordination, and thanks Jerry and the Firestorm team
for the open discussion!

+1 for the proposal. Good luck and hope our paths could cross in the future
(smile).

Best Regards,
Yu


On Thu, 19 May 2022 at 11:28, Willem Jiang  wrote:

> Hi,
>
> We just had a quick meeting to talk about the possibility of the joint
> effort today.
>
> Jerry ,Yu and I expressed the pros and cons about merging the project
> together,  we also discussed the challenges (legal affairs, design and
> codebase decision making) of merging these two projects together. As
> there are a lot of things that need to be done before two teams can
> work together, both sides agree to enter the ASF incubator first then
> we can seek the possibility of joint efforts in the future.
>
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Wed, May 18, 2022 at 6:40 PM Yu Li  wrote:
> >
> > Thanks all for the considerate comments and thanks Jerry (and Firestorm
> > team) for the open mind.
> >
> > I totally agree that working as one project/community is a good wish
> > instead of a prerequisite (and I believe no one meant this actually),
> and I
> > don't have any intention to block the incubating process of Firestorm.
> >
> > I believe that even if we cannot make it a joint force, the two projects
> > could be good frenemy with competitive friendship (smile).
> >
> > Let's discuss more offline. :-)
> >
> > Best Regards,
> > Yu
> >
> >
> > On Wed, 18 May 2022 at 17:41, Jerry Shao  wrote:
> >
> > > Yes, I think we could discuss the possibilities offline.
> > >
> > > But I would like to clarify that "merging these projects together" is
> > > neither a "problem" (a "wish" indeed), nor a prerequisite for
> incubating.
> > > In the heyday of Hadoop, there were so many similar or even same
> purpose
> > > projects in ASF, the choice is made by user, not by ASF.
> > >
> > > Best
> > > Jerry
> > >
> > > Willem Jiang  于2022年5月18日周三 17:17写道:
> > >
> > > > On Wed, May 18, 2022 at 2:50 PM Sheng Wu 
> > > > wrote:
> > > > >
> > > > > Hi Firestorm community
> > > > >
> > > > > Considering what Yu Li is proposing, I would recommend you could do
> > > > > some discussions directly, maybe off the list if you want.
> > > > > Both of the projects are young and very new to the community, it
> may
> > > > > be not a concern from my perspective(may be concerned by some
> IPMC),
> > > > > as one/both could fail in the incubating. But with you are going to
> > > > > work on the similar things, the challenge would be for both of your
> > > > > projects to establish the incubating process. Also, when we talk
> about
> > > > > graduation in the future, it would be my concern of causing
> confusion
> > > > > to users.
> > > > >
> > > > > Two TLPs are nearly the same is really not a good practice from the
> > > > > foundation level.
> > > > >
> > > > > > We heartfully welcome you to join Firestorm project and
> community.
> > > > >
> > > > > So, I suggest not just saying joining Firestorm, this may be a
> simple
> > > > > reaction, I hope you could do more.
> > > > > This is an opportunity to do a bigger and more powerful project
> > > > > supported by Tencent and Alibaba's initial teams.
> > > > >
> > > >
> > > > After talking with LiYu and Jerry Shao,  I realized there could be
> > > > some challenges we may face.
> > > > But it would be great if we can work together to tackle the same
> problem.
> > > > I'd like to help two teams to start a meeting to discuss the
> > > > possibility of merging these projects together.
> > > >
> > > > Willem Jiang
> > > >
> > > > Twitter: willemjiang
> > > > Weibo: 姜宁willem
> > > >
> > > > > I know it is not easy to do a joint project, but it is actually
> much
> > > > > better to see you two competing with each other in the next 1-2
> years.
> > > > > In the ASF, we hope to create a better project for the whole
> industry.
> > > > >
> > > > >
> > > > > Sheng Wu 吴晟
> > > > > Twitter, wusheng1108
> > > > >
> > > > > Jerry Shao  于2022年5月18日周三 14:38写道:
> > > > > >
> > > > > > Hi Yu,
> > > > > >
> > > > > > IMO, I think we're open and welcome all the contributions. We
> > > > heartfully
> > > > > > welcome you to join Firestorm project and community.
> > > > > >
> > > > > > Best regards,
> > > > > > Jerry
> > > > > >
> > > > > > Yu Li  于2022年5月18日周三 13:36写道:
> > > > > >
> > > > > > > Hi Jerry,
> > > > > > >
> > > > > > > Good to see the proposal for incubating a uniform remote
> shuffle
> > > > service.
> > > > > > > Coincidently, we are preparing an incubating proposal for the
> same
> > > > > > > direction based on two open source projects Alibaba is driving
> [1]
> > > > [2], and
> > > > > > > I'm the champion for that. Our proposal is still not fully
> prepared
> > > > because
> > > > > > > the merge of the two projects is still in progress, and I'm
> writing
> > > > this
> > > > > > > email to check whether it's possible that we have a joint
> force to
> > > > achieve
> > > > > > > the same goal. I 

Re: [DISCUSSION] Incubating Proposal of Firestorm

2022-05-18 Thread Saisai Shao
Thanks Willem for organizing, thanks Yu to join and have this open
discussion.

We have made a consensus that both projects developing separately, and seek
the opportunity to collaborate in future. So +1 from my side.

Back to the merging or separation discussion, I think both ways have pros
and cons, and currently we cannot clearly see which way is more good than
harm. So I think we could leave the user, community and time to decide. If
someday in the future, we think that the two projects should be merged for
any reason, and we can clearly see the advantages, we will definitely do
this.

Regard to the current challenges, I think it is existed and cannot be
neglected from many areas (legal, architecture, codebase, time efforts),
and will potentially make the cost too high to afford. So without seeing
the clear advantages, I would incline to be conservative.

Thanks all for your kind suggestions and open discussion.

Best regards,
Jerry


Willem Jiang  于2022年5月19日周四 11:28写道:

> Hi,
>
> We just had a quick meeting to talk about the possibility of the joint
> effort today.
>
> Jerry ,Yu and I expressed the pros and cons about merging the project
> together,  we also discussed the challenges (legal affairs, design and
> codebase decision making) of merging these two projects together. As
> there are a lot of things that need to be done before two teams can
> work together, both sides agree to enter the ASF incubator first then
> we can seek the possibility of joint efforts in the future.
>
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Wed, May 18, 2022 at 6:40 PM Yu Li  wrote:
> >
> > Thanks all for the considerate comments and thanks Jerry (and Firestorm
> > team) for the open mind.
> >
> > I totally agree that working as one project/community is a good wish
> > instead of a prerequisite (and I believe no one meant this actually),
> and I
> > don't have any intention to block the incubating process of Firestorm.
> >
> > I believe that even if we cannot make it a joint force, the two projects
> > could be good frenemy with competitive friendship (smile).
> >
> > Let's discuss more offline. :-)
> >
> > Best Regards,
> > Yu
> >
> >
> > On Wed, 18 May 2022 at 17:41, Jerry Shao  wrote:
> >
> > > Yes, I think we could discuss the possibilities offline.
> > >
> > > But I would like to clarify that "merging these projects together" is
> > > neither a "problem" (a "wish" indeed), nor a prerequisite for
> incubating.
> > > In the heyday of Hadoop, there were so many similar or even same
> purpose
> > > projects in ASF, the choice is made by user, not by ASF.
> > >
> > > Best
> > > Jerry
> > >
> > > Willem Jiang  于2022年5月18日周三 17:17写道:
> > >
> > > > On Wed, May 18, 2022 at 2:50 PM Sheng Wu 
> > > > wrote:
> > > > >
> > > > > Hi Firestorm community
> > > > >
> > > > > Considering what Yu Li is proposing, I would recommend you could do
> > > > > some discussions directly, maybe off the list if you want.
> > > > > Both of the projects are young and very new to the community, it
> may
> > > > > be not a concern from my perspective(may be concerned by some
> IPMC),
> > > > > as one/both could fail in the incubating. But with you are going to
> > > > > work on the similar things, the challenge would be for both of your
> > > > > projects to establish the incubating process. Also, when we talk
> about
> > > > > graduation in the future, it would be my concern of causing
> confusion
> > > > > to users.
> > > > >
> > > > > Two TLPs are nearly the same is really not a good practice from the
> > > > > foundation level.
> > > > >
> > > > > > We heartfully welcome you to join Firestorm project and
> community.
> > > > >
> > > > > So, I suggest not just saying joining Firestorm, this may be a
> simple
> > > > > reaction, I hope you could do more.
> > > > > This is an opportunity to do a bigger and more powerful project
> > > > > supported by Tencent and Alibaba's initial teams.
> > > > >
> > > >
> > > > After talking with LiYu and Jerry Shao,  I realized there could be
> > > > some challenges we may face.
> > > > But it would be great if we can work together to tackle the same
> problem.
> > > > I'd like to help two teams to start a meeting to discuss the
> > > > possibility of merging these projects together.
> > > >
> > > > Willem Jiang
> > > >
> > > > Twitter: willemjiang
> > > > Weibo: 姜宁willem
> > > >
> > > > > I know it is not easy to do a joint project, but it is actually
> much
> > > > > better to see you two competing with each other in the next 1-2
> years.
> > > > > In the ASF, we hope to create a better project for the whole
> industry.
> > > > >
> > > > >
> > > > > Sheng Wu 吴晟
> > > > > Twitter, wusheng1108
> > > > >
> > > > > Jerry Shao  于2022年5月18日周三 14:38写道:
> > > > > >
> > > > > > Hi Yu,
> > > > > >
> > > > > > IMO, I think we're open and welcome all the contributions. We
> > > > heartfully
> > > > > > welcome you to join Firestorm project and community.
> > > > > >
> > > > > > Best regards,
> 

Re: [DISCUSSION] Incubating Proposal of Firestorm

2022-05-18 Thread Willem Jiang
Hi,

We just had a quick meeting to talk about the possibility of the joint
effort today.

Jerry ,Yu and I expressed the pros and cons about merging the project
together,  we also discussed the challenges (legal affairs, design and
codebase decision making) of merging these two projects together. As
there are a lot of things that need to be done before two teams can
work together, both sides agree to enter the ASF incubator first then
we can seek the possibility of joint efforts in the future.


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Wed, May 18, 2022 at 6:40 PM Yu Li  wrote:
>
> Thanks all for the considerate comments and thanks Jerry (and Firestorm
> team) for the open mind.
>
> I totally agree that working as one project/community is a good wish
> instead of a prerequisite (and I believe no one meant this actually), and I
> don't have any intention to block the incubating process of Firestorm.
>
> I believe that even if we cannot make it a joint force, the two projects
> could be good frenemy with competitive friendship (smile).
>
> Let's discuss more offline. :-)
>
> Best Regards,
> Yu
>
>
> On Wed, 18 May 2022 at 17:41, Jerry Shao  wrote:
>
> > Yes, I think we could discuss the possibilities offline.
> >
> > But I would like to clarify that "merging these projects together" is
> > neither a "problem" (a "wish" indeed), nor a prerequisite for incubating.
> > In the heyday of Hadoop, there were so many similar or even same purpose
> > projects in ASF, the choice is made by user, not by ASF.
> >
> > Best
> > Jerry
> >
> > Willem Jiang  于2022年5月18日周三 17:17写道:
> >
> > > On Wed, May 18, 2022 at 2:50 PM Sheng Wu 
> > > wrote:
> > > >
> > > > Hi Firestorm community
> > > >
> > > > Considering what Yu Li is proposing, I would recommend you could do
> > > > some discussions directly, maybe off the list if you want.
> > > > Both of the projects are young and very new to the community, it may
> > > > be not a concern from my perspective(may be concerned by some IPMC),
> > > > as one/both could fail in the incubating. But with you are going to
> > > > work on the similar things, the challenge would be for both of your
> > > > projects to establish the incubating process. Also, when we talk about
> > > > graduation in the future, it would be my concern of causing confusion
> > > > to users.
> > > >
> > > > Two TLPs are nearly the same is really not a good practice from the
> > > > foundation level.
> > > >
> > > > > We heartfully welcome you to join Firestorm project and community.
> > > >
> > > > So, I suggest not just saying joining Firestorm, this may be a simple
> > > > reaction, I hope you could do more.
> > > > This is an opportunity to do a bigger and more powerful project
> > > > supported by Tencent and Alibaba's initial teams.
> > > >
> > >
> > > After talking with LiYu and Jerry Shao,  I realized there could be
> > > some challenges we may face.
> > > But it would be great if we can work together to tackle the same problem.
> > > I'd like to help two teams to start a meeting to discuss the
> > > possibility of merging these projects together.
> > >
> > > Willem Jiang
> > >
> > > Twitter: willemjiang
> > > Weibo: 姜宁willem
> > >
> > > > I know it is not easy to do a joint project, but it is actually much
> > > > better to see you two competing with each other in the next 1-2 years.
> > > > In the ASF, we hope to create a better project for the whole industry.
> > > >
> > > >
> > > > Sheng Wu 吴晟
> > > > Twitter, wusheng1108
> > > >
> > > > Jerry Shao  于2022年5月18日周三 14:38写道:
> > > > >
> > > > > Hi Yu,
> > > > >
> > > > > IMO, I think we're open and welcome all the contributions. We
> > > heartfully
> > > > > welcome you to join Firestorm project and community.
> > > > >
> > > > > Best regards,
> > > > > Jerry
> > > > >
> > > > > Yu Li  于2022年5月18日周三 13:36写道:
> > > > >
> > > > > > Hi Jerry,
> > > > > >
> > > > > > Good to see the proposal for incubating a uniform remote shuffle
> > > service.
> > > > > > Coincidently, we are preparing an incubating proposal for the same
> > > > > > direction based on two open source projects Alibaba is driving [1]
> > > [2], and
> > > > > > I'm the champion for that. Our proposal is still not fully prepared
> > > because
> > > > > > the merge of the two projects is still in progress, and I'm writing
> > > this
> > > > > > email to check whether it's possible that we have a joint force to
> > > achieve
> > > > > > the same goal. I believe it will be cool if we could do this
> > > together,
> > > > > > although there will be a lot (more) work to do to make this happen.
> > > > > >
> > > > > > Please let me know your thoughts and let's have more discussions if
> > > you're
> > > > > > also interested. Thanks.
> > > > > >
> > > > > > Best Regards,
> > > > > > Yu
> > > > > >
> > > > > > [1] https://github.com/flink-extended/flink-remote-shuffle
> > > > > > [2] https://github.com/alibaba/RemoteShuffleService
> > > > > >
> > > > > >
> > >
> > > 

Re: Setting up project website

2022-05-18 Thread hulk
Thanks to Jhon and kezhenxu94.

We will fix those issues accordingly to the suggestions.

On Thu, 19 May 2022 at 00:34, John D. Ament  wrote:

> On Wed, May 18, 2022 at 12:06 PM kezhenxu94  wrote:
>
> > > Perhaps what
> > you were referring to is the first time the podling is mentioned, the
> > podling should be referred to as Apache  (incubating)
> >
> > This is exactly what I meant. And I believe the very first time the
> > podling is mentioned is the headline of the website and the README of the
> > GitHub repo.
> >
>
> For github specifically, the About section is the first thing read, so it
> must say Apache  (incubating) or similar reference.  The README is
> not the first thing on the page.  Usually that sort of reference gets
> sorted after the repository is moved from another org to GitHub, or done
> prior to migrating it when the podling still has admin rights on the repo.
> The README *must* say Apache Kvrocks, it would be nice if it said Apache
> Kvrocks (incubating) but it's not a requirement.
>
> Usually the issue with headlines is that they get very long.  So Apache
> Kvrocks (incubating) can cause alignment issues, hence it's OK to ask for
> IPMC to look at it a different way.
>
>
> >
> > The headline is at a position that attracts users‘ attention at first
> > glance (also first mentioned) and “incubating” is what we want the users
> to
> > be aware of when they visit the project for the first time.
>
>
> > > It’s a little harder with hero text the way Kvrocks has it
> >
> > I check the website of kvrocks but failed to understand why it is hard to
> > add “incubating” in the headline, though I’m also ok if they add it in
> the
> > first paragraph.
>
>
> On a 1080p monitor, the text Apache Kvrocks (incubating) gets very close to
> the navigation area.  It may be confusing to a visitor with the layout, so
> putting it in another place that's a little lower but more direct line of
> site may be just as good.
>
>
> >
> >
> >
> > > On May 18, 2022, at 23:44, John D. Ament 
> wrote:
> > >
> > > On Wed, May 18, 2022 at 11:33 AM kezhenxu94 
> > wrote:
> > >
> > >> Hi John, can you explain what does this line mean in the link you
> > pasted?
> > >> I’m not a native English speaker so might misunderstand it.
> > >>
> > >> “Each page has a navigation bar and a project standard header that
> > >> includes the Incubator graphic.”
> > >>
> > >
> > > If you look at an established podling like Pony Mail's page as an
> example
> > > [2].  The bottom footer has the incubator logo and disclaimer, the
> > standard
> > > links are with the disclaimer text which passes our needs.  Perhaps
> what
> > > you were referring to is the first time the podling is mentioned, the
> > > podling should be referred to as Apache  (incubating).  It's a
> > > little harder with hero text the way Kvrocks has it, so I would
> recommend
> > > the first time it's mentioned in the paragraph text (in each header is
> > not
> > > necessary, but because an easy way to deal with it).
> > >
> > > [2]: https://ponymail.apache.org/
> > >
> > >
> > >>
> >  On May 18, 2022, at 23:15, John D. Ament 
> > wrote:
> > >>>
> > >>> On Wed, May 18, 2022 at 10:14 AM kezhenxu94 
> > >> wrote:
> > >>>
> >  Congrats but please remember to add “incubating” in the headline and
> >  GitHub index page (README), I know the podling is in progress but
> just
> > >> in
> >  case.
> > 
> > >>>
> > >>> Neither is required per [1].  Please don't recommend undue burden.
> > >>>
> > >>>
> > >>> [1]: https://incubator.apache.org/guides/sites.html
> > >>>
> > >>>
> > 
> > >> On May 15, 2022, at 21:30, tison  wrote:
> > >
> > > Thank you. It seems that the website is online and the problem is
> > that
> > > initializing the website takes some time.
> > >
> > > Best,
> > > tison.
> > >
> > >
> > > Calvin Kirs  于2022年5月15日周日 21:20写道:
> > >
> > >> HI,
> > >>
> > >> FYI [1]: Website deployment service for Git repositories.
> > >>
> > >> btw. I recommend that the mentor guide PPMC do such a thing,
> rather
> > >> than the mentor doing it himself.
> > >>
> > >> [1]
> > >>
> > 
> > >>
> >
> https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features#Git.asf.yamlfeatures-WebsitedeploymentserviceforGitrepositories
> > >>
> > >> tison  于2022年5月15日周日 21:07写道:
> > >>>
> > >>>
> > 
> > https://github.com/apache/incubator-kvrocks-website/blob/main/.asf.yaml
> > >>>
> > >>> .asf.yaml is also present on main branch.
> > >>>
> > >>> Best,
> > >>> tison.
> > >>>
> > >>>
> > >>> Sheng Wu  于2022年5月15日周日 20:58写道:
> > >>>
> >  I remember you need this
> > 
> > 
> > https://github.com/apache/skywalking-website/blob/master/.asf.yaml
> > 
> >  Sheng Wu 吴晟
> >  Twitter, wusheng1108
> > 
> >  tison  于2022年5月15日周日 20:50写道:
> > >
> > > Hi,

Re: Proposal

2022-05-18 Thread Daniel Widdis
Speaking only for myself, I’ll say I am interested in the open source software 
model and am not interested in participating in any private group.

 

Additionally, GPT3 is a closed source model with the only “free” part being a 
public-facing API, with usage primarily benefiting one company.

 

I would expect you might get more interest in building a product around GPT-J 
[1], which is an Apache License 2.0 product.  But I also expect most people on 
this list would like to see what is proposed and discussed in the open.  

 

[1] https://github.com/kingoflolz/mesh-transformer-jax/

 

 

 

From: m sacks 
Date: Wednesday, May 18, 2022 at 5:58 PM
To: Daniel Widdis , 
Subject: Re: Proposal

 

So I’m not sure if this made it either: is there at least one person interested 
in collaborating on this project it involves GPT three?

 

On Mon, May 16, 2022 at 10:47 PM m sacks  wrote:

Not sure if this made it:

Just a term of endearment, mot taken to be meant literally. 

 

Sure. 

 

Initially the community would be a private group put together by me. 

 

Then we can discuss building it once others have decided if it’s even a useful 
application first?

 

On Mon, May 16, 2022 at 10:20 PM Daniel Widdis  wrote:

I'm not an ASF warlord or general.  In fact, I don't think such things exist. 
It's about community.  Decisions are made by communities.  Warlords, generals, 
and benevolent dictators don't fit well.

Related, I don't see anything "community" in your post. You state "I" have got 
code, not "we".

You can have the best code in the universe, but if you don't have a community 
developing it, it's not really a good fit here.

So tell us less about your code and more about your community developing it.


On 5/16/22, 10:05 PM, "m sacks"  wrote:

I have some gpt3 based python code to simulate leonardo da vinci as a
chatbot proof of concept. I think it could be useful, but i am not sure, so
i leave it to the council of ASF warlords and generals to decide if the
code should be incubated?


I have not shared sources as of yet.





Re: [VOTE] Release Apache Flagon UserALE.js 2.3.0

2022-05-18 Thread Furkan KAMACI
Hi,

+1 from me (binding, carrying over my vote).

I checked:

- Incubating in name
- DISCLAIMER exists
- LICENSE and NOTICE are fine
- No unexpected binary files
- Checked PGP signatures
- Checked checksums
- Code compiles and tests successfully run

Kind Regards,
Furkan KAMACI

On Thu, May 19, 2022 at 4:06 AM Joshua Poore  wrote:

> IPMC,
>
> Please VOTE on our Release Candidate for Apache Flagon (Incubating)
> UserALE.js 2.3.0
>
> > On May 10, 2022, at 5:18 PM, Joshua Poore  wrote:
> >
> > Hello IPMC—
> >
> > Please VOTE on the Apache Flagon (Incubating) UserALE.js 2.3.0 Release
> Candidate # 01.
> >
> > Flagon Community VOTE can be found here:
> https://lists.apache.org/thread/7d4g4ftgs4mjckqmk6y45vs64g5fllmv <
> https://lists.apache.org/thread/7d4g4ftgs4mjckqmk6y45vs64g5fllmv>
> >
> > Summary of Community VOTE:
> >
> > +1 : 4 (1 IPMC Binding - Furkan Kamaci, 2 PPMC Non-Binding)
> > +0: 0
> > -1: 0
> >
> > About Flagon: http://flagon.incubator.apache.org/ <
> http://flagon.incubator.apache.org/>
> >
> > This Minor release includes:
> >
> > Fixes issue in autostart configurations and start(), stop() export usage
> > Adds additional unit tests for autostart configurations
> > Adds React App.js example/test utility
> > Adds additional examples (non-user log examples)
> > Minor updates to update deprecated downstream dev dependencies
> > Minor changes to documentation, updated examples
> >
> > Resolved issues:
> https://github.com/apache/incubator-flagon-useralejs/projects/9 <
> https://github.com/apache/incubator-flagon-useralejs/projects/9>
> >
> > Git source tag (566b279;
> https://github.com/apache/incubator-flagon-useralejs/releases/tag/2.3.0-RC-01
> <
> https://github.com/apache/incubator-flagon-useralejs/releases/tag/2.3.0-RC-01
> >)
> >
> > Staging repo: https://dist.apache.org/repos/dist/dev/incubator/flagon/ <
> https://dist.apache.org/repos/dist/dev/incubator/flagon/>
> >
> > Source Release Artifacts:
> https://dist.apache.org/repos/dist/dev/incubator/flagon/apache-flagon-useralejs-incubating-2.3.0-RC-01/
> <
> https://dist.apache.org/repos/dist/dev/incubator/flagon/apache-flagon-useralejs-incubating-2.3.0-RC-01/
> >
> >
> > PGP release keys (signed using F9374FAE3FCADF6E):
> https://dist.apache.org/repos/dist/release/incubator/flagon/KEYS <
> https://dist.apache.org/repos/dist/release/incubator/flagon/KEYS>
> >
> > Link to Successful CI Build:
> https://github.com/apache/incubator-flagon-useralejs/runs/5958813955 <
> https://github.com/apache/incubator-flagon-useralejs/runs/5958813955>
> >
> > Reference to the UserALE.js testing framework to assist in your unit and
> integration tests:
> https://cwiki.apache.org/confluence/display/FLAGON/UserALE.js+Release+Management+Procedure
> <
> https://cwiki.apache.org/confluence/display/FLAGON/UserALE.js+Release+Management+Procedure
> >
> >
> > I checked:
> >
> > [ x ] Build and Unit Tests Pass
> > [ x ] Integration Tests Pass (Example Page, Webpack (NPM), React (NPM)
> > [ x ] "Incubating" in References to Project and Distribution File Names
> > [ x ] Signatures and Hashes Match Keys
> > [ x ] DISCLAIMER, LICENSE, and NOTICE Files in Source and Binary Release
> Packages
> > [ x ] DISCLAIMER, LICENSE, and NOTICE are consistent with ASF and
> Incubator Policy
> > [ x ] CHANGELOG included with release distribution
> > [ x ] New source code (React app, OpenTelemetry Ex) have compatible
> licenses (ALv2, MIT)
> > [ x ] All Source Files Have Correct ASF Headers (ran RAT tool: only json
> / .png files exclude headers)
> > [ x ] No Binary Files in Source Release Packages (except for supporting
> .png files)
> >
> > Vote will be open for 72 hours. Please VOTE as follows:
> >
> > [ ] +1, let's get it released!!!
> > [ ] +/-0, fine, but consider to fix few issues before...
> > [ ] -1, nope, because... (and please explain why)
> >
> > Along with your VOTE, please indicate testing and checks you've made
> against build artifacts, src, and documentation:
> >
> > [ ] Build and Unit Tests Pass
> > [ ] Integration Tests Pass
> > [ ] "Incubating" in References to Project and Distribution File Names
> > [ ] Signatures and Hashes Match Keys
> > [ ] DISCLAIMER, LICENSE, and NOTICE Files in Source and Binary Release
> Packages
> > [ ] DISCLAIMER, LICENSE, and NOTICE are consistent with ASF and
> Incubator Policy
> > [ ] CHANGELOG included with release distribution
> > [ ] All Source Files Have Correct ASF Headers
> > [ ] No Binary Files in Source Release Packages
> >
> > Thank you to everyone that is able to VOTE as well as everyone that
> contributed to Apache Flagon UserALE.js 2.3.0!
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


Re: [VOTE] Release Apache Flagon UserALE.js 2.3.0

2022-05-18 Thread Joshua Poore
IPMC,

Please VOTE on our Release Candidate for Apache Flagon (Incubating) UserALE.js 
2.3.0

> On May 10, 2022, at 5:18 PM, Joshua Poore  wrote:
> 
> Hello IPMC— 
> 
> Please VOTE on the Apache Flagon (Incubating) UserALE.js 2.3.0 Release 
> Candidate # 01.
> 
> Flagon Community VOTE can be found here: 
> https://lists.apache.org/thread/7d4g4ftgs4mjckqmk6y45vs64g5fllmv 
>  
> 
> Summary of Community VOTE:
> 
> +1 : 4 (1 IPMC Binding - Furkan Kamaci, 2 PPMC Non-Binding)
> +0: 0
> -1: 0
> 
> About Flagon: http://flagon.incubator.apache.org/ 
> 
> 
> This Minor release includes:
> 
> Fixes issue in autostart configurations and start(), stop() export usage
> Adds additional unit tests for autostart configurations
> Adds React App.js example/test utility
> Adds additional examples (non-user log examples)
> Minor updates to update deprecated downstream dev dependencies
> Minor changes to documentation, updated examples
> 
> Resolved issues: 
> https://github.com/apache/incubator-flagon-useralejs/projects/9 
> 
> 
> Git source tag (566b279; 
> https://github.com/apache/incubator-flagon-useralejs/releases/tag/2.3.0-RC-01 
> )
> 
> Staging repo: https://dist.apache.org/repos/dist/dev/incubator/flagon/ 
> 
> 
> Source Release Artifacts: 
> https://dist.apache.org/repos/dist/dev/incubator/flagon/apache-flagon-useralejs-incubating-2.3.0-RC-01/
>  
> 
> 
> PGP release keys (signed using F9374FAE3FCADF6E): 
> https://dist.apache.org/repos/dist/release/incubator/flagon/KEYS 
> 
> 
> Link to Successful CI Build: 
> https://github.com/apache/incubator-flagon-useralejs/runs/5958813955 
> 
> 
> Reference to the UserALE.js testing framework to assist in your unit and 
> integration tests: 
> https://cwiki.apache.org/confluence/display/FLAGON/UserALE.js+Release+Management+Procedure
>  
> 
> 
> I checked:
> 
> [ x ] Build and Unit Tests Pass
> [ x ] Integration Tests Pass (Example Page, Webpack (NPM), React (NPM)
> [ x ] "Incubating" in References to Project and Distribution File Names
> [ x ] Signatures and Hashes Match Keys
> [ x ] DISCLAIMER, LICENSE, and NOTICE Files in Source and Binary Release 
> Packages
> [ x ] DISCLAIMER, LICENSE, and NOTICE are consistent with ASF and Incubator 
> Policy
> [ x ] CHANGELOG included with release distribution
> [ x ] New source code (React app, OpenTelemetry Ex) have compatible licenses 
> (ALv2, MIT)
> [ x ] All Source Files Have Correct ASF Headers (ran RAT tool: only json / 
> .png files exclude headers)
> [ x ] No Binary Files in Source Release Packages (except for supporting .png 
> files)
> 
> Vote will be open for 72 hours. Please VOTE as follows:
> 
> [ ] +1, let's get it released!!!
> [ ] +/-0, fine, but consider to fix few issues before...
> [ ] -1, nope, because... (and please explain why)
> 
> Along with your VOTE, please indicate testing and checks you've made against 
> build artifacts, src, and documentation:
> 
> [ ] Build and Unit Tests Pass
> [ ] Integration Tests Pass
> [ ] "Incubating" in References to Project and Distribution File Names
> [ ] Signatures and Hashes Match Keys
> [ ] DISCLAIMER, LICENSE, and NOTICE Files in Source and Binary Release 
> Packages
> [ ] DISCLAIMER, LICENSE, and NOTICE are consistent with ASF and Incubator 
> Policy
> [ ] CHANGELOG included with release distribution
> [ ] All Source Files Have Correct ASF Headers
> [ ] No Binary Files in Source Release Packages
> 
> Thank you to everyone that is able to VOTE as well as everyone that 
> contributed to Apache Flagon UserALE.js 2.3.0!


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



Re: Proposal

2022-05-18 Thread m sacks
So I’m not sure if this made it either: is there at least one person
interested in collaborating on this project it involves GPT three?

On Mon, May 16, 2022 at 10:47 PM m sacks  wrote:

> Not sure if this made it:
> Just a term of endearment, mot taken to be meant literally.
>
> Sure.
>
> Initially the community would be a private group put together by me.
>
> Then we can discuss building it once others have decided if it’s even a
> useful application first?
>
> On Mon, May 16, 2022 at 10:20 PM Daniel Widdis  wrote:
>
>> I'm not an ASF warlord or general.  In fact, I don't think such things
>> exist. It's about community.  Decisions are made by communities.  Warlords,
>> generals, and benevolent dictators don't fit well.
>>
>> Related, I don't see anything "community" in your post. You state "I"
>> have got code, not "we".
>>
>> You can have the best code in the universe, but if you don't have a
>> community developing it, it's not really a good fit here.
>>
>> So tell us less about your code and more about your community developing
>> it.
>>
>>
>> On 5/16/22, 10:05 PM, "m sacks"  wrote:
>>
>> I have some gpt3 based python code to simulate leonardo da vinci as a
>> chatbot proof of concept. I think it could be useful, but i am not
>> sure, so
>> i leave it to the council of ASF warlords and generals to decide if
>> the
>> code should be incubated?
>>
>>
>> I have not shared sources as of yet.
>>
>>
>>
>>


Re: Setting up project website

2022-05-18 Thread John D. Ament
On Wed, May 18, 2022 at 12:06 PM kezhenxu94  wrote:

> > Perhaps what
> you were referring to is the first time the podling is mentioned, the
> podling should be referred to as Apache  (incubating)
>
> This is exactly what I meant. And I believe the very first time the
> podling is mentioned is the headline of the website and the README of the
> GitHub repo.
>

For github specifically, the About section is the first thing read, so it
must say Apache  (incubating) or similar reference.  The README is
not the first thing on the page.  Usually that sort of reference gets
sorted after the repository is moved from another org to GitHub, or done
prior to migrating it when the podling still has admin rights on the repo.
The README *must* say Apache Kvrocks, it would be nice if it said Apache
Kvrocks (incubating) but it's not a requirement.

Usually the issue with headlines is that they get very long.  So Apache
Kvrocks (incubating) can cause alignment issues, hence it's OK to ask for
IPMC to look at it a different way.


>
> The headline is at a position that attracts users‘ attention at first
> glance (also first mentioned) and “incubating” is what we want the users to
> be aware of when they visit the project for the first time.


> > It’s a little harder with hero text the way Kvrocks has it
>
> I check the website of kvrocks but failed to understand why it is hard to
> add “incubating” in the headline, though I’m also ok if they add it in the
> first paragraph.


On a 1080p monitor, the text Apache Kvrocks (incubating) gets very close to
the navigation area.  It may be confusing to a visitor with the layout, so
putting it in another place that's a little lower but more direct line of
site may be just as good.


>
>
>
> > On May 18, 2022, at 23:44, John D. Ament  wrote:
> >
> > On Wed, May 18, 2022 at 11:33 AM kezhenxu94 
> wrote:
> >
> >> Hi John, can you explain what does this line mean in the link you
> pasted?
> >> I’m not a native English speaker so might misunderstand it.
> >>
> >> “Each page has a navigation bar and a project standard header that
> >> includes the Incubator graphic.”
> >>
> >
> > If you look at an established podling like Pony Mail's page as an example
> > [2].  The bottom footer has the incubator logo and disclaimer, the
> standard
> > links are with the disclaimer text which passes our needs.  Perhaps what
> > you were referring to is the first time the podling is mentioned, the
> > podling should be referred to as Apache  (incubating).  It's a
> > little harder with hero text the way Kvrocks has it, so I would recommend
> > the first time it's mentioned in the paragraph text (in each header is
> not
> > necessary, but because an easy way to deal with it).
> >
> > [2]: https://ponymail.apache.org/
> >
> >
> >>
>  On May 18, 2022, at 23:15, John D. Ament 
> wrote:
> >>>
> >>> On Wed, May 18, 2022 at 10:14 AM kezhenxu94 
> >> wrote:
> >>>
>  Congrats but please remember to add “incubating” in the headline and
>  GitHub index page (README), I know the podling is in progress but just
> >> in
>  case.
> 
> >>>
> >>> Neither is required per [1].  Please don't recommend undue burden.
> >>>
> >>>
> >>> [1]: https://incubator.apache.org/guides/sites.html
> >>>
> >>>
> 
> >> On May 15, 2022, at 21:30, tison  wrote:
> >
> > Thank you. It seems that the website is online and the problem is
> that
> > initializing the website takes some time.
> >
> > Best,
> > tison.
> >
> >
> > Calvin Kirs  于2022年5月15日周日 21:20写道:
> >
> >> HI,
> >>
> >> FYI [1]: Website deployment service for Git repositories.
> >>
> >> btw. I recommend that the mentor guide PPMC do such a thing, rather
> >> than the mentor doing it himself.
> >>
> >> [1]
> >>
> 
> >>
> https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features#Git.asf.yamlfeatures-WebsitedeploymentserviceforGitrepositories
> >>
> >> tison  于2022年5月15日周日 21:07写道:
> >>>
> >>>
> 
> https://github.com/apache/incubator-kvrocks-website/blob/main/.asf.yaml
> >>>
> >>> .asf.yaml is also present on main branch.
> >>>
> >>> Best,
> >>> tison.
> >>>
> >>>
> >>> Sheng Wu  于2022年5月15日周日 20:58写道:
> >>>
>  I remember you need this
> 
> 
> https://github.com/apache/skywalking-website/blob/master/.asf.yaml
> 
>  Sheng Wu 吴晟
>  Twitter, wusheng1108
> 
>  tison  于2022年5月15日周日 20:50写道:
> >
> > Hi,
> >
> > On Apache Kvrocks (Incubating) project, I just set up the website
> >> repo
> > (main and asf-site branch)[1] and it seems the asf-site branch is
>  properly
> > configured and static site staff published.
> >
> > However, the homepage https://kvrocks.apache.org/ still returns
> >> 404
> >> NOT
> > FOUND. I don't know whether it takes some time to 

Re: Setting up project website

2022-05-18 Thread kezhenxu94
> Perhaps what
you were referring to is the first time the podling is mentioned, the
podling should be referred to as Apache  (incubating)

This is exactly what I meant. And I believe the very first time the podling is 
mentioned is the headline of the website and the README of the GitHub repo.

The headline is at a position that attracts users‘ attention at first glance 
(also first mentioned) and “incubating” is what we want the users to be aware 
of when they visit the project for the first time.

> It’s a little harder with hero text the way Kvrocks has it

I check the website of kvrocks but failed to understand why it is hard to add 
“incubating” in the headline, though I’m also ok if they add it in the first 
paragraph. 


> On May 18, 2022, at 23:44, John D. Ament  wrote:
> 
> On Wed, May 18, 2022 at 11:33 AM kezhenxu94  wrote:
> 
>> Hi John, can you explain what does this line mean in the link you pasted?
>> I’m not a native English speaker so might misunderstand it.
>> 
>> “Each page has a navigation bar and a project standard header that
>> includes the Incubator graphic.”
>> 
> 
> If you look at an established podling like Pony Mail's page as an example
> [2].  The bottom footer has the incubator logo and disclaimer, the standard
> links are with the disclaimer text which passes our needs.  Perhaps what
> you were referring to is the first time the podling is mentioned, the
> podling should be referred to as Apache  (incubating).  It's a
> little harder with hero text the way Kvrocks has it, so I would recommend
> the first time it's mentioned in the paragraph text (in each header is not
> necessary, but because an easy way to deal with it).
> 
> [2]: https://ponymail.apache.org/
> 
> 
>> 
 On May 18, 2022, at 23:15, John D. Ament  wrote:
>>> 
>>> On Wed, May 18, 2022 at 10:14 AM kezhenxu94 
>> wrote:
>>> 
 Congrats but please remember to add “incubating” in the headline and
 GitHub index page (README), I know the podling is in progress but just
>> in
 case.
 
>>> 
>>> Neither is required per [1].  Please don't recommend undue burden.
>>> 
>>> 
>>> [1]: https://incubator.apache.org/guides/sites.html
>>> 
>>> 
 
>> On May 15, 2022, at 21:30, tison  wrote:
> 
> Thank you. It seems that the website is online and the problem is that
> initializing the website takes some time.
> 
> Best,
> tison.
> 
> 
> Calvin Kirs  于2022年5月15日周日 21:20写道:
> 
>> HI,
>> 
>> FYI [1]: Website deployment service for Git repositories.
>> 
>> btw. I recommend that the mentor guide PPMC do such a thing, rather
>> than the mentor doing it himself.
>> 
>> [1]
>> 
 
>> https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features#Git.asf.yamlfeatures-WebsitedeploymentserviceforGitrepositories
>> 
>> tison  于2022年5月15日周日 21:07写道:
>>> 
>>> 
 https://github.com/apache/incubator-kvrocks-website/blob/main/.asf.yaml
>>> 
>>> .asf.yaml is also present on main branch.
>>> 
>>> Best,
>>> tison.
>>> 
>>> 
>>> Sheng Wu  于2022年5月15日周日 20:58写道:
>>> 
 I remember you need this
 
 https://github.com/apache/skywalking-website/blob/master/.asf.yaml
 
 Sheng Wu 吴晟
 Twitter, wusheng1108
 
 tison  于2022年5月15日周日 20:50写道:
> 
> Hi,
> 
> On Apache Kvrocks (Incubating) project, I just set up the website
>> repo
> (main and asf-site branch)[1] and it seems the asf-site branch is
 properly
> configured and static site staff published.
> 
> However, the homepage https://kvrocks.apache.org/ still returns
>> 404
>> NOT
> FOUND. I don't know whether it takes some time to deploy or the
>> setting
 is
> wrong which needs more polishing.
> 
> Best,
> tison.
> 
> [1]
>> https://github.com/apache/incubator-kvrocks-website/tree/asf-site
 
>> 
>> 
>> 
>> --
>> Best wishes!
>> CalvinKirs
>> 
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
>> 
 
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 
 
>> 


Re: Setting up project website

2022-05-18 Thread John D. Ament
On Wed, May 18, 2022 at 11:33 AM kezhenxu94  wrote:

> Hi John, can you explain what does this line mean in the link you pasted?
> I’m not a native English speaker so might misunderstand it.
>
> “Each page has a navigation bar and a project standard header that
> includes the Incubator graphic.”
>

If you look at an established podling like Pony Mail's page as an example
[2].  The bottom footer has the incubator logo and disclaimer, the standard
links are with the disclaimer text which passes our needs.  Perhaps what
you were referring to is the first time the podling is mentioned, the
podling should be referred to as Apache  (incubating).  It's a
little harder with hero text the way Kvrocks has it, so I would recommend
the first time it's mentioned in the paragraph text (in each header is not
necessary, but because an easy way to deal with it).

[2]: https://ponymail.apache.org/


>
> > On May 18, 2022, at 23:15, John D. Ament  wrote:
> >
> > On Wed, May 18, 2022 at 10:14 AM kezhenxu94 
> wrote:
> >
> >> Congrats but please remember to add “incubating” in the headline and
> >> GitHub index page (README), I know the podling is in progress but just
> in
> >> case.
> >>
> >
> > Neither is required per [1].  Please don't recommend undue burden.
> >
> >
> > [1]: https://incubator.apache.org/guides/sites.html
> >
> >
> >>
>  On May 15, 2022, at 21:30, tison  wrote:
> >>>
> >>> Thank you. It seems that the website is online and the problem is that
> >>> initializing the website takes some time.
> >>>
> >>> Best,
> >>> tison.
> >>>
> >>>
> >>> Calvin Kirs  于2022年5月15日周日 21:20写道:
> >>>
>  HI,
> 
>  FYI [1]: Website deployment service for Git repositories.
> 
>  btw. I recommend that the mentor guide PPMC do such a thing, rather
>  than the mentor doing it himself.
> 
>  [1]
> 
> >>
> https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features#Git.asf.yamlfeatures-WebsitedeploymentserviceforGitrepositories
> 
>  tison  于2022年5月15日周日 21:07写道:
> >
> >
> >> https://github.com/apache/incubator-kvrocks-website/blob/main/.asf.yaml
> >
> > .asf.yaml is also present on main branch.
> >
> > Best,
> > tison.
> >
> >
> > Sheng Wu  于2022年5月15日周日 20:58写道:
> >
> >> I remember you need this
> >>
> >> https://github.com/apache/skywalking-website/blob/master/.asf.yaml
> >>
> >> Sheng Wu 吴晟
> >> Twitter, wusheng1108
> >>
> >> tison  于2022年5月15日周日 20:50写道:
> >>>
> >>> Hi,
> >>>
> >>> On Apache Kvrocks (Incubating) project, I just set up the website
>  repo
> >>> (main and asf-site branch)[1] and it seems the asf-site branch is
> >> properly
> >>> configured and static site staff published.
> >>>
> >>> However, the homepage https://kvrocks.apache.org/ still returns
> 404
>  NOT
> >>> FOUND. I don't know whether it takes some time to deploy or the
>  setting
> >> is
> >>> wrong which needs more polishing.
> >>>
> >>> Best,
> >>> tison.
> >>>
> >>> [1]
>  https://github.com/apache/incubator-kvrocks-website/tree/asf-site
> >>
> 
> 
> 
>  --
>  Best wishes!
>  CalvinKirs
> 
>  -
>  To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>  For additional commands, e-mail: general-h...@incubator.apache.org
> 
> 
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> For additional commands, e-mail: general-h...@incubator.apache.org
> >>
> >>
>


Resigning as Datalab mentor

2022-05-18 Thread Konstantin Boudnik
Please consider this as my official resignation from the role of 
Datalab's mentor as I don't have any cycles for the project anymore.


--
With regards,
  Konstantin Boudnik

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



Re: Setting up project website

2022-05-18 Thread kezhenxu94
Hi John, can you explain what does this line mean in the link you pasted? I’m 
not a native English speaker so might misunderstand it. 

“Each page has a navigation bar and a project standard header that includes the 
Incubator graphic.”

> On May 18, 2022, at 23:15, John D. Ament  wrote:
> 
> On Wed, May 18, 2022 at 10:14 AM kezhenxu94  wrote:
> 
>> Congrats but please remember to add “incubating” in the headline and
>> GitHub index page (README), I know the podling is in progress but just in
>> case.
>> 
> 
> Neither is required per [1].  Please don't recommend undue burden.
> 
> 
> [1]: https://incubator.apache.org/guides/sites.html
> 
> 
>> 
 On May 15, 2022, at 21:30, tison  wrote:
>>> 
>>> Thank you. It seems that the website is online and the problem is that
>>> initializing the website takes some time.
>>> 
>>> Best,
>>> tison.
>>> 
>>> 
>>> Calvin Kirs  于2022年5月15日周日 21:20写道:
>>> 
 HI,
 
 FYI [1]: Website deployment service for Git repositories.
 
 btw. I recommend that the mentor guide PPMC do such a thing, rather
 than the mentor doing it himself.
 
 [1]
 
>> https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features#Git.asf.yamlfeatures-WebsitedeploymentserviceforGitrepositories
 
 tison  于2022年5月15日周日 21:07写道:
> 
> 
>> https://github.com/apache/incubator-kvrocks-website/blob/main/.asf.yaml
> 
> .asf.yaml is also present on main branch.
> 
> Best,
> tison.
> 
> 
> Sheng Wu  于2022年5月15日周日 20:58写道:
> 
>> I remember you need this
>> 
>> https://github.com/apache/skywalking-website/blob/master/.asf.yaml
>> 
>> Sheng Wu 吴晟
>> Twitter, wusheng1108
>> 
>> tison  于2022年5月15日周日 20:50写道:
>>> 
>>> Hi,
>>> 
>>> On Apache Kvrocks (Incubating) project, I just set up the website
 repo
>>> (main and asf-site branch)[1] and it seems the asf-site branch is
>> properly
>>> configured and static site staff published.
>>> 
>>> However, the homepage https://kvrocks.apache.org/ still returns 404
 NOT
>>> FOUND. I don't know whether it takes some time to deploy or the
 setting
>> is
>>> wrong which needs more polishing.
>>> 
>>> Best,
>>> tison.
>>> 
>>> [1]
 https://github.com/apache/incubator-kvrocks-website/tree/asf-site
>> 
 
 
 
 --
 Best wishes!
 CalvinKirs
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 
 
>> 
>> 
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
>> 


Re: Setting up project website

2022-05-18 Thread John D. Ament
On Wed, May 18, 2022 at 10:14 AM kezhenxu94  wrote:

> Congrats but please remember to add “incubating” in the headline and
> GitHub index page (README), I know the podling is in progress but just in
> case.
>

Neither is required per [1].  Please don't recommend undue burden.


[1]: https://incubator.apache.org/guides/sites.html


>
> > On May 15, 2022, at 21:30, tison  wrote:
> >
> > Thank you. It seems that the website is online and the problem is that
> > initializing the website takes some time.
> >
> > Best,
> > tison.
> >
> >
> > Calvin Kirs  于2022年5月15日周日 21:20写道:
> >
> >> HI,
> >>
> >> FYI [1]: Website deployment service for Git repositories.
> >>
> >> btw. I recommend that the mentor guide PPMC do such a thing, rather
> >> than the mentor doing it himself.
> >>
> >> [1]
> >>
> https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features#Git.asf.yamlfeatures-WebsitedeploymentserviceforGitrepositories
> >>
> >> tison  于2022年5月15日周日 21:07写道:
> >>>
> >>>
> https://github.com/apache/incubator-kvrocks-website/blob/main/.asf.yaml
> >>>
> >>> .asf.yaml is also present on main branch.
> >>>
> >>> Best,
> >>> tison.
> >>>
> >>>
> >>> Sheng Wu  于2022年5月15日周日 20:58写道:
> >>>
>  I remember you need this
> 
>  https://github.com/apache/skywalking-website/blob/master/.asf.yaml
> 
>  Sheng Wu 吴晟
>  Twitter, wusheng1108
> 
>  tison  于2022年5月15日周日 20:50写道:
> >
> > Hi,
> >
> > On Apache Kvrocks (Incubating) project, I just set up the website
> >> repo
> > (main and asf-site branch)[1] and it seems the asf-site branch is
>  properly
> > configured and static site staff published.
> >
> > However, the homepage https://kvrocks.apache.org/ still returns 404
> >> NOT
> > FOUND. I don't know whether it takes some time to deploy or the
> >> setting
>  is
> > wrong which needs more polishing.
> >
> > Best,
> > tison.
> >
> > [1]
> >> https://github.com/apache/incubator-kvrocks-website/tree/asf-site
> 
> >>
> >>
> >>
> >> --
> >> Best wishes!
> >> CalvinKirs
> >>
> >> -
> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> For additional commands, e-mail: general-h...@incubator.apache.org
> >>
> >>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


Re: Setting up project website

2022-05-18 Thread kezhenxu94
Congrats but please remember to add “incubating” in the headline and GitHub 
index page (README), I know the podling is in progress but just in case.

> On May 15, 2022, at 21:30, tison  wrote:
> 
> Thank you. It seems that the website is online and the problem is that
> initializing the website takes some time.
> 
> Best,
> tison.
> 
> 
> Calvin Kirs  于2022年5月15日周日 21:20写道:
> 
>> HI,
>> 
>> FYI [1]: Website deployment service for Git repositories.
>> 
>> btw. I recommend that the mentor guide PPMC do such a thing, rather
>> than the mentor doing it himself.
>> 
>> [1]
>> https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features#Git.asf.yamlfeatures-WebsitedeploymentserviceforGitrepositories
>> 
>> tison  于2022年5月15日周日 21:07写道:
>>> 
>>> https://github.com/apache/incubator-kvrocks-website/blob/main/.asf.yaml
>>> 
>>> .asf.yaml is also present on main branch.
>>> 
>>> Best,
>>> tison.
>>> 
>>> 
>>> Sheng Wu  于2022年5月15日周日 20:58写道:
>>> 
 I remember you need this
 
 https://github.com/apache/skywalking-website/blob/master/.asf.yaml
 
 Sheng Wu 吴晟
 Twitter, wusheng1108
 
 tison  于2022年5月15日周日 20:50写道:
> 
> Hi,
> 
> On Apache Kvrocks (Incubating) project, I just set up the website
>> repo
> (main and asf-site branch)[1] and it seems the asf-site branch is
 properly
> configured and static site staff published.
> 
> However, the homepage https://kvrocks.apache.org/ still returns 404
>> NOT
> FOUND. I don't know whether it takes some time to deploy or the
>> setting
 is
> wrong which needs more polishing.
> 
> Best,
> tison.
> 
> [1]
>> https://github.com/apache/incubator-kvrocks-website/tree/asf-site
 
>> 
>> 
>> 
>> --
>> Best wishes!
>> CalvinKirs
>> 
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
>> 


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



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

2022-05-18 Thread 陈明雨
Hi Justin,
The website[1] has been modified, such as adding asf disclaimer at the footer.
And this artical[2] is a machine-translated article by a third-party website. 
We have contacted the author to delete the corresponding Chinese article.(This 
article is just a personal blog and does not come from starrocks company or 
PPMC members)


[1] https://www.starrocks.com/en-US/index
[2] https://chowdera.com/2022/135/202205150625040654.html



--

此致!Best Regards
陈明雨 Mingyu Chen

Email:
chenmin...@apache.org





在 2022-05-16 21:21:24,"陈明雨"  写道:
>[1] and [2] has been renamed. And [3] has been removed.
>The website[4] still has some issues waiting to be modified. I will keep touch 
>with starrocks.
>
>
>[1] https://github.com/StarRocks/flink-connector-starrocks
>[2] https://github.com/StarRocks/spark-starrocks-connector
>[3] https://github.com/StarRocks/apache-orc
>[4] https://www.starrocks.com/
>
>
>
>
>--
>
>此致!Best Regards
>陈明雨 Mingyu Chen
>
>Email:
>chenmin...@apache.org
>
>
>
>
>
>At 2022-05-16 16:31:07, "Justin Mclean"  wrote:
>>HI,
>>
>>There is also an issue with the naming and use of ASF trademark of this 
>>product:
>>https://github.com/StarRocks/flink-connector-starrocks
>>
>>And this:
>>https://github.com/StarRocks/apache-orc
>>
>>And this:
>>https://github.com/StarRocks/spark-starrocks-connector
>>
>>Kind Regards,
>>Justin
>>-
>>To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>For additional commands, e-mail: general-h...@incubator.apache.org


Re: [DISCUSSION] Incubating Proposal of Firestorm

2022-05-18 Thread Yu Li
Thanks all for the considerate comments and thanks Jerry (and Firestorm
team) for the open mind.

I totally agree that working as one project/community is a good wish
instead of a prerequisite (and I believe no one meant this actually), and I
don't have any intention to block the incubating process of Firestorm.

I believe that even if we cannot make it a joint force, the two projects
could be good frenemy with competitive friendship (smile).

Let's discuss more offline. :-)

Best Regards,
Yu


On Wed, 18 May 2022 at 17:41, Jerry Shao  wrote:

> Yes, I think we could discuss the possibilities offline.
>
> But I would like to clarify that "merging these projects together" is
> neither a "problem" (a "wish" indeed), nor a prerequisite for incubating.
> In the heyday of Hadoop, there were so many similar or even same purpose
> projects in ASF, the choice is made by user, not by ASF.
>
> Best
> Jerry
>
> Willem Jiang  于2022年5月18日周三 17:17写道:
>
> > On Wed, May 18, 2022 at 2:50 PM Sheng Wu 
> > wrote:
> > >
> > > Hi Firestorm community
> > >
> > > Considering what Yu Li is proposing, I would recommend you could do
> > > some discussions directly, maybe off the list if you want.
> > > Both of the projects are young and very new to the community, it may
> > > be not a concern from my perspective(may be concerned by some IPMC),
> > > as one/both could fail in the incubating. But with you are going to
> > > work on the similar things, the challenge would be for both of your
> > > projects to establish the incubating process. Also, when we talk about
> > > graduation in the future, it would be my concern of causing confusion
> > > to users.
> > >
> > > Two TLPs are nearly the same is really not a good practice from the
> > > foundation level.
> > >
> > > > We heartfully welcome you to join Firestorm project and community.
> > >
> > > So, I suggest not just saying joining Firestorm, this may be a simple
> > > reaction, I hope you could do more.
> > > This is an opportunity to do a bigger and more powerful project
> > > supported by Tencent and Alibaba's initial teams.
> > >
> >
> > After talking with LiYu and Jerry Shao,  I realized there could be
> > some challenges we may face.
> > But it would be great if we can work together to tackle the same problem.
> > I'd like to help two teams to start a meeting to discuss the
> > possibility of merging these projects together.
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > > I know it is not easy to do a joint project, but it is actually much
> > > better to see you two competing with each other in the next 1-2 years.
> > > In the ASF, we hope to create a better project for the whole industry.
> > >
> > >
> > > Sheng Wu 吴晟
> > > Twitter, wusheng1108
> > >
> > > Jerry Shao  于2022年5月18日周三 14:38写道:
> > > >
> > > > Hi Yu,
> > > >
> > > > IMO, I think we're open and welcome all the contributions. We
> > heartfully
> > > > welcome you to join Firestorm project and community.
> > > >
> > > > Best regards,
> > > > Jerry
> > > >
> > > > Yu Li  于2022年5月18日周三 13:36写道:
> > > >
> > > > > Hi Jerry,
> > > > >
> > > > > Good to see the proposal for incubating a uniform remote shuffle
> > service.
> > > > > Coincidently, we are preparing an incubating proposal for the same
> > > > > direction based on two open source projects Alibaba is driving [1]
> > [2], and
> > > > > I'm the champion for that. Our proposal is still not fully prepared
> > because
> > > > > the merge of the two projects is still in progress, and I'm writing
> > this
> > > > > email to check whether it's possible that we have a joint force to
> > achieve
> > > > > the same goal. I believe it will be cool if we could do this
> > together,
> > > > > although there will be a lot (more) work to do to make this happen.
> > > > >
> > > > > Please let me know your thoughts and let's have more discussions if
> > you're
> > > > > also interested. Thanks.
> > > > >
> > > > > Best Regards,
> > > > > Yu
> > > > >
> > > > > [1] https://github.com/flink-extended/flink-remote-shuffle
> > > > > [2] https://github.com/alibaba/RemoteShuffleService
> > > > >
> > > > >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>


Re: [DISCUSSION] Incubating Proposal of Firestorm

2022-05-18 Thread Jerry Shao
Yes, I think we could discuss the possibilities offline.

But I would like to clarify that "merging these projects together" is
neither a "problem" (a "wish" indeed), nor a prerequisite for incubating.
In the heyday of Hadoop, there were so many similar or even same purpose
projects in ASF, the choice is made by user, not by ASF.

Best
Jerry

Willem Jiang  于2022年5月18日周三 17:17写道:

> On Wed, May 18, 2022 at 2:50 PM Sheng Wu 
> wrote:
> >
> > Hi Firestorm community
> >
> > Considering what Yu Li is proposing, I would recommend you could do
> > some discussions directly, maybe off the list if you want.
> > Both of the projects are young and very new to the community, it may
> > be not a concern from my perspective(may be concerned by some IPMC),
> > as one/both could fail in the incubating. But with you are going to
> > work on the similar things, the challenge would be for both of your
> > projects to establish the incubating process. Also, when we talk about
> > graduation in the future, it would be my concern of causing confusion
> > to users.
> >
> > Two TLPs are nearly the same is really not a good practice from the
> > foundation level.
> >
> > > We heartfully welcome you to join Firestorm project and community.
> >
> > So, I suggest not just saying joining Firestorm, this may be a simple
> > reaction, I hope you could do more.
> > This is an opportunity to do a bigger and more powerful project
> > supported by Tencent and Alibaba's initial teams.
> >
>
> After talking with LiYu and Jerry Shao,  I realized there could be
> some challenges we may face.
> But it would be great if we can work together to tackle the same problem.
> I'd like to help two teams to start a meeting to discuss the
> possibility of merging these projects together.
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> > I know it is not easy to do a joint project, but it is actually much
> > better to see you two competing with each other in the next 1-2 years.
> > In the ASF, we hope to create a better project for the whole industry.
> >
> >
> > Sheng Wu 吴晟
> > Twitter, wusheng1108
> >
> > Jerry Shao  于2022年5月18日周三 14:38写道:
> > >
> > > Hi Yu,
> > >
> > > IMO, I think we're open and welcome all the contributions. We
> heartfully
> > > welcome you to join Firestorm project and community.
> > >
> > > Best regards,
> > > Jerry
> > >
> > > Yu Li  于2022年5月18日周三 13:36写道:
> > >
> > > > Hi Jerry,
> > > >
> > > > Good to see the proposal for incubating a uniform remote shuffle
> service.
> > > > Coincidently, we are preparing an incubating proposal for the same
> > > > direction based on two open source projects Alibaba is driving [1]
> [2], and
> > > > I'm the champion for that. Our proposal is still not fully prepared
> because
> > > > the merge of the two projects is still in progress, and I'm writing
> this
> > > > email to check whether it's possible that we have a joint force to
> achieve
> > > > the same goal. I believe it will be cool if we could do this
> together,
> > > > although there will be a lot (more) work to do to make this happen.
> > > >
> > > > Please let me know your thoughts and let's have more discussions if
> you're
> > > > also interested. Thanks.
> > > >
> > > > Best Regards,
> > > > Yu
> > > >
> > > > [1] https://github.com/flink-extended/flink-remote-shuffle
> > > > [2] https://github.com/alibaba/RemoteShuffleService
> > > >
> > > >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


Re: [DISCUSSION] Incubating Proposal of Firestorm

2022-05-18 Thread Willem Jiang
On Wed, May 18, 2022 at 2:50 PM Sheng Wu  wrote:
>
> Hi Firestorm community
>
> Considering what Yu Li is proposing, I would recommend you could do
> some discussions directly, maybe off the list if you want.
> Both of the projects are young and very new to the community, it may
> be not a concern from my perspective(may be concerned by some IPMC),
> as one/both could fail in the incubating. But with you are going to
> work on the similar things, the challenge would be for both of your
> projects to establish the incubating process. Also, when we talk about
> graduation in the future, it would be my concern of causing confusion
> to users.
>
> Two TLPs are nearly the same is really not a good practice from the
> foundation level.
>
> > We heartfully welcome you to join Firestorm project and community.
>
> So, I suggest not just saying joining Firestorm, this may be a simple
> reaction, I hope you could do more.
> This is an opportunity to do a bigger and more powerful project
> supported by Tencent and Alibaba's initial teams.
>

After talking with LiYu and Jerry Shao,  I realized there could be
some challenges we may face.
But it would be great if we can work together to tackle the same problem.
I'd like to help two teams to start a meeting to discuss the
possibility of merging these projects together.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

> I know it is not easy to do a joint project, but it is actually much
> better to see you two competing with each other in the next 1-2 years.
> In the ASF, we hope to create a better project for the whole industry.
>
>
> Sheng Wu 吴晟
> Twitter, wusheng1108
>
> Jerry Shao  于2022年5月18日周三 14:38写道:
> >
> > Hi Yu,
> >
> > IMO, I think we're open and welcome all the contributions. We heartfully
> > welcome you to join Firestorm project and community.
> >
> > Best regards,
> > Jerry
> >
> > Yu Li  于2022年5月18日周三 13:36写道:
> >
> > > Hi Jerry,
> > >
> > > Good to see the proposal for incubating a uniform remote shuffle service.
> > > Coincidently, we are preparing an incubating proposal for the same
> > > direction based on two open source projects Alibaba is driving [1] [2], 
> > > and
> > > I'm the champion for that. Our proposal is still not fully prepared 
> > > because
> > > the merge of the two projects is still in progress, and I'm writing this
> > > email to check whether it's possible that we have a joint force to achieve
> > > the same goal. I believe it will be cool if we could do this together,
> > > although there will be a lot (more) work to do to make this happen.
> > >
> > > Please let me know your thoughts and let's have more discussions if you're
> > > also interested. Thanks.
> > >
> > > Best Regards,
> > > Yu
> > >
> > > [1] https://github.com/flink-extended/flink-remote-shuffle
> > > [2] https://github.com/alibaba/RemoteShuffleService
> > >
> > >

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



Re: [DISCUSSION] Incubating Proposal of Firestorm

2022-05-18 Thread Justin Mclean
Hi,

> It’s a bit different from my impression, could I know it’s fine to have many 
> projects sharing much similar functions or aiming in parallel here?

It's 100% fine and we have many TLP that do similar things as each other.

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



Re: [DISCUSSION] Incubating Proposal of Firestorm

2022-05-18 Thread BLAST
Hi ShengWu
 Is there a successful precedent for this open source in the 
community?



---

在 2022/5/18 下午2:50,“Sheng Wu”https://github.com/flink-extended/flink-remote-shuffle

   [2] https://github.com/alibaba/RemoteShuffleService

  

  

   On Wed, 18 May 2022 at 12:15, Jerry Shao 


Re: [DISCUSSION] Incubating Proposal of Firestorm

2022-05-18 Thread Jerry Shao
Thanks guys for your opinions, we will discuss the things off the list.

But AFAIK, this should not be the blocking issue here for incubating.

Best,
Jerry

Juan Pan  于2022年5月18日周三 15:31写道:

> Hello Justin,
>
>
> > 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.
>
>
> It’s a bit different from my impression, could I know it’s fine to have
> many projects sharing much similar functions or aiming in parallel here?
>
>
> Thanks,
> Trista
>
> --
> Trista Pan
> Twitter & Github: tristaZero
>
>
>
>
> On 05/18/2022 15:12,Justin Mclean wrote:
> 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: [DISCUSSION] Incubating Proposal of Firestorm

2022-05-18 Thread Juan Pan
Hello Justin,


> 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.


It’s a bit different from my impression, could I know it’s fine to have many 
projects sharing much similar functions or aiming in parallel here?


Thanks,
Trista
--
Trista Pan
Twitter & Github: tristaZero




On 05/18/2022 15:12,Justin Mclean wrote:
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: [DISCUSSION] Incubating Proposal of Firestorm

2022-05-18 Thread Justin Mclean
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: [DISCUSSION] Incubating Proposal of Firestorm

2022-05-18 Thread Daniel Widdis
+1 to this.  Would love to see both groups come together.

On 5/17/22, 11:50 PM, "Sheng Wu"  wrote:

Hi Firestorm community

Considering what Yu Li is proposing, I would recommend you could do
some discussions directly, maybe off the list if you want.
Both of the projects are young and very new to the community, it may
be not a concern from my perspective(may be concerned by some IPMC),
as one/both could fail in the incubating. But with you are going to
work on the similar things, the challenge would be for both of your
projects to establish the incubating process. Also, when we talk about
graduation in the future, it would be my concern of causing confusion
to users.

Two TLPs are nearly the same is really not a good practice from the
foundation level.

> We heartfully welcome you to join Firestorm project and community.

So, I suggest not just saying joining Firestorm, this may be a simple
reaction, I hope you could do more.
This is an opportunity to do a bigger and more powerful project
supported by Tencent and Alibaba's initial teams.

I know it is not easy to do a joint project, but it is actually much
better to see you two competing with each other in the next 1-2 years.
In the ASF, we hope to create a better project for the whole industry.


Sheng Wu 吴晟
Twitter, wusheng1108

Jerry Shao  于2022年5月18日周三 14:38写道:
>
> Hi Yu,
>
> IMO, I think we're open and welcome all the contributions. We heartfully
> welcome you to join Firestorm project and community.
>
> Best regards,
> Jerry
>
> Yu Li  于2022年5月18日周三 13:36写道:
>
> > Hi Jerry,
> >
> > Good to see the proposal for incubating a uniform remote shuffle 
service.
> > Coincidently, we are preparing an incubating proposal for the same
> > direction based on two open source projects Alibaba is driving [1] [2], 
and
> > I'm the champion for that. Our proposal is still not fully prepared 
because
> > the merge of the two projects is still in progress, and I'm writing this
> > email to check whether it's possible that we have a joint force to 
achieve
> > the same goal. I believe it will be cool if we could do this together,
> > although there will be a lot (more) work to do to make this happen.
> >
> > Please let me know your thoughts and let's have more discussions if 
you're
> > also interested. Thanks.
> >
> > Best Regards,
> > Yu
> >
> > [1] https://github.com/flink-extended/flink-remote-shuffle
> > [2] https://github.com/alibaba/RemoteShuffleService
> >
> >
> > On Wed, 18 May 2022 at 12:15, Jerry Shao  wrote:
> >
> > > Sure Felix, let me add you to the list.
> > >
> > > Best,
> > > Jerry
> > >
> > > Felix Cheung  于2022年5月18日周三 11:59写道:
> > >
> > > > Same here, would love to see if I can help, Jerry.
> > > >
> > > >
> > > > On Mon, May 16, 2022 at 10:31 PM Saisai Shao 

> > > > wrote:
> > > >
> > > > > Thanks Weiwei, let me add you to the mentor list.
> > > > >
> > > > > Best regards,
> > > > > Jerry
> > > > >
> > > > > Weiwei Yang  于2022年5月17日周二 12:18写道:
> > > > >
> > > > > > +1
> > > > > > This is an interesting project, I'd be happy to help the 
project's
> > > > > > incubation process.
> > > > > > Let me know if you need my help, Thanks
> > > > > >
> > > > > > On Mon, May 16, 2022 at 8:09 PM Saisai Shao <
> > sai.sai.s...@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > > > Got it, thanks a lot Justin.
> > > > > > >
> > > > > > > Best regards,
> > > > > > > Jerry
> > > > > > >
> > > > > > > Justin Mclean  于2022年5月17日周二 
10:59写道:
> > > > > > >
> > > > > > > > Hi,
> > > > > > > >
> > > > > > > > The new project name doesn’t need to be a registered 
trademark,
> > > but
> > > > > you
> > > > > > > > would still need to pick a name that is now likely to have 
any
> > > > > > trademark
> > > > > > > > issues.
> > > > > > > >
> > > > > > > > The project may want to get the ASF to register the mark at 
a
> > > later
> > > > > > date,
> > > > > > > > but it wold be best to talk abut that on the trademarks@ 
list.
> > > > > > > >
> > > > > > > > Kind Regards,
> > > > > > > > Justin
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > 
-
> > > > > > > > To unsubscribe, e-mail:
> > general-unsubscr...@incubator.apache.org
> > > > > > > > For additional commands, e-mail:
> > > general-h...@incubator.apache.org
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >

-
To unsubscribe, e-mail: 

Re: [DISCUSSION] Incubating Proposal of Firestorm

2022-05-18 Thread Sheng Wu
Hi Firestorm community

Considering what Yu Li is proposing, I would recommend you could do
some discussions directly, maybe off the list if you want.
Both of the projects are young and very new to the community, it may
be not a concern from my perspective(may be concerned by some IPMC),
as one/both could fail in the incubating. But with you are going to
work on the similar things, the challenge would be for both of your
projects to establish the incubating process. Also, when we talk about
graduation in the future, it would be my concern of causing confusion
to users.

Two TLPs are nearly the same is really not a good practice from the
foundation level.

> We heartfully welcome you to join Firestorm project and community.

So, I suggest not just saying joining Firestorm, this may be a simple
reaction, I hope you could do more.
This is an opportunity to do a bigger and more powerful project
supported by Tencent and Alibaba's initial teams.

I know it is not easy to do a joint project, but it is actually much
better to see you two competing with each other in the next 1-2 years.
In the ASF, we hope to create a better project for the whole industry.


Sheng Wu 吴晟
Twitter, wusheng1108

Jerry Shao  于2022年5月18日周三 14:38写道:
>
> Hi Yu,
>
> IMO, I think we're open and welcome all the contributions. We heartfully
> welcome you to join Firestorm project and community.
>
> Best regards,
> Jerry
>
> Yu Li  于2022年5月18日周三 13:36写道:
>
> > Hi Jerry,
> >
> > Good to see the proposal for incubating a uniform remote shuffle service.
> > Coincidently, we are preparing an incubating proposal for the same
> > direction based on two open source projects Alibaba is driving [1] [2], and
> > I'm the champion for that. Our proposal is still not fully prepared because
> > the merge of the two projects is still in progress, and I'm writing this
> > email to check whether it's possible that we have a joint force to achieve
> > the same goal. I believe it will be cool if we could do this together,
> > although there will be a lot (more) work to do to make this happen.
> >
> > Please let me know your thoughts and let's have more discussions if you're
> > also interested. Thanks.
> >
> > Best Regards,
> > Yu
> >
> > [1] https://github.com/flink-extended/flink-remote-shuffle
> > [2] https://github.com/alibaba/RemoteShuffleService
> >
> >
> > On Wed, 18 May 2022 at 12:15, Jerry Shao  wrote:
> >
> > > Sure Felix, let me add you to the list.
> > >
> > > Best,
> > > Jerry
> > >
> > > Felix Cheung  于2022年5月18日周三 11:59写道:
> > >
> > > > Same here, would love to see if I can help, Jerry.
> > > >
> > > >
> > > > On Mon, May 16, 2022 at 10:31 PM Saisai Shao 
> > > > wrote:
> > > >
> > > > > Thanks Weiwei, let me add you to the mentor list.
> > > > >
> > > > > Best regards,
> > > > > Jerry
> > > > >
> > > > > Weiwei Yang  于2022年5月17日周二 12:18写道:
> > > > >
> > > > > > +1
> > > > > > This is an interesting project, I'd be happy to help the project's
> > > > > > incubation process.
> > > > > > Let me know if you need my help, Thanks
> > > > > >
> > > > > > On Mon, May 16, 2022 at 8:09 PM Saisai Shao <
> > sai.sai.s...@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > > > Got it, thanks a lot Justin.
> > > > > > >
> > > > > > > Best regards,
> > > > > > > Jerry
> > > > > > >
> > > > > > > Justin Mclean  于2022年5月17日周二 10:59写道:
> > > > > > >
> > > > > > > > Hi,
> > > > > > > >
> > > > > > > > The new project name doesn’t need to be a registered trademark,
> > > but
> > > > > you
> > > > > > > > would still need to pick a name that is now likely to have any
> > > > > > trademark
> > > > > > > > issues.
> > > > > > > >
> > > > > > > > The project may want to get the ASF to register the mark at a
> > > later
> > > > > > date,
> > > > > > > > but it wold be best to talk abut that on the trademarks@ list.
> > > > > > > >
> > > > > > > > Kind Regards,
> > > > > > > > Justin
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > -
> > > > > > > > To unsubscribe, e-mail:
> > general-unsubscr...@incubator.apache.org
> > > > > > > > For additional commands, e-mail:
> > > general-h...@incubator.apache.org
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >

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



Re: [DISCUSSION] Incubating Proposal of Firestorm

2022-05-18 Thread Jerry Shao
Hi Yu,

IMO, I think we're open and welcome all the contributions. We heartfully
welcome you to join Firestorm project and community.

Best regards,
Jerry

Yu Li  于2022年5月18日周三 13:36写道:

> Hi Jerry,
>
> Good to see the proposal for incubating a uniform remote shuffle service.
> Coincidently, we are preparing an incubating proposal for the same
> direction based on two open source projects Alibaba is driving [1] [2], and
> I'm the champion for that. Our proposal is still not fully prepared because
> the merge of the two projects is still in progress, and I'm writing this
> email to check whether it's possible that we have a joint force to achieve
> the same goal. I believe it will be cool if we could do this together,
> although there will be a lot (more) work to do to make this happen.
>
> Please let me know your thoughts and let's have more discussions if you're
> also interested. Thanks.
>
> Best Regards,
> Yu
>
> [1] https://github.com/flink-extended/flink-remote-shuffle
> [2] https://github.com/alibaba/RemoteShuffleService
>
>
> On Wed, 18 May 2022 at 12:15, Jerry Shao  wrote:
>
> > Sure Felix, let me add you to the list.
> >
> > Best,
> > Jerry
> >
> > Felix Cheung  于2022年5月18日周三 11:59写道:
> >
> > > Same here, would love to see if I can help, Jerry.
> > >
> > >
> > > On Mon, May 16, 2022 at 10:31 PM Saisai Shao 
> > > wrote:
> > >
> > > > Thanks Weiwei, let me add you to the mentor list.
> > > >
> > > > Best regards,
> > > > Jerry
> > > >
> > > > Weiwei Yang  于2022年5月17日周二 12:18写道:
> > > >
> > > > > +1
> > > > > This is an interesting project, I'd be happy to help the project's
> > > > > incubation process.
> > > > > Let me know if you need my help, Thanks
> > > > >
> > > > > On Mon, May 16, 2022 at 8:09 PM Saisai Shao <
> sai.sai.s...@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > Got it, thanks a lot Justin.
> > > > > >
> > > > > > Best regards,
> > > > > > Jerry
> > > > > >
> > > > > > Justin Mclean  于2022年5月17日周二 10:59写道:
> > > > > >
> > > > > > > Hi,
> > > > > > >
> > > > > > > The new project name doesn’t need to be a registered trademark,
> > but
> > > > you
> > > > > > > would still need to pick a name that is now likely to have any
> > > > > trademark
> > > > > > > issues.
> > > > > > >
> > > > > > > The project may want to get the ASF to register the mark at a
> > later
> > > > > date,
> > > > > > > but it wold be best to talk abut that on the trademarks@ list.
> > > > > > >
> > > > > > > Kind Regards,
> > > > > > > Justin
> > > > > > >
> > > > > > >
> > > > > > >
> > > -
> > > > > > > To unsubscribe, e-mail:
> general-unsubscr...@incubator.apache.org
> > > > > > > For additional commands, e-mail:
> > general-h...@incubator.apache.org
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>