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
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
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.
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
> >
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.
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,
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
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.
>
>
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
> 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.
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.”
>
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:
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
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]:
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
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
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
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
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
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
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
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
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
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
+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
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
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
27 matches
Mail list logo
