Re: [VOTE] Drop the incubator- prefix for podling's GitHub repo name

[Alexander Alten]

As a polling member, my vote is -1 (unbinding) for dropping incubator-* 

We need a clear difference between projects who are in consideration to get a 
full supported TLP and the ones who undergo the process. Just my 2 cents

—Alex 

> On 8. May 2024, at 10:20, Sheng Wu  wrote:
> 
> sebb mailto:seb...@gmail.com>> 于2024年5月8日周三 16:12写道：
>> 
>> Remember that the purpose of the incubator prefix is to clearly signal
>> that the code is under Incubation.
>> 
>> It is essential that this change does not result in losing this indication.
>> 
>> AFAICT, for most podlings, dropping the incubator prefix will require
>> additional work to ensure that the Incubation status is clear to
>> users,
>> and will require additional work by the IPMC to ensure that podlings
>> adequately display the Incubation status for each repository.
> 
> Can't agree more on this.
> In this vote proposal, we implicitly add many more checks for IPMC,
> and lead more potential arguments about whether the incubating status
> indicator is clear enough.
> We are making IPMC pay the price in the future by removing a simple
> GitHub supported operation.
> 
> On second thought, I am changing my vote to -1 binding.
> 
>> 
>> 
>> On Wed, 8 May 2024 at 08:30, alin.jerpe...@sony.com
>>  wrote:
>>> 
>>> +1 (non binding)
>>> 
>>> from my experience will make the documentation and releases easy to migrate 
>>> after graduation
>>> 
>>> Best regards
>>> Alin
>>> 
>>> Från: hulk 
>>> Skickat: den 8 maj 2024 09:06
>>> Till: general@incubator.apache.org 
>>> Ämne: Re: [VOTE] Drop the incubator- prefix for podling's GitHub repo name
>>> 
>>> -0 (binding) On Wed, 8 May 2024 at 13: 58, Richard Zowalla >> zowalla. com> wrote: > -0 (binding) > > (I like the prefix) > > Am 8. Mai 
>>> 2024 07: 41: 16 MESZ schrieb Sheng Wu : > >-0
>>> ZjQcmQRYFpfptBannerStart
>>> Caution : This email originated from outside of Sony.
>>> Do not click links or open any attachments unless you recognize the sender 
>>> and know the content is safe. Please report phishing if unsure.
>>> 
>>> ZjQcmQRYFpfptBannerEnd
>>> 
>>> -0 (binding)
>>> 
>>> On Wed, 8 May 2024 at 13:58, Richard Zowalla  wrote:
>>> 
 -0 (binding)
 
 (I like the prefix)
 
 Am 8. Mai 2024 07:41:16 MESZ schrieb Sheng Wu :
> -0 binding
> 
> Sheng Wu 吴晟
> Twitter, wusheng1108
> 
> Dave Fisher  于2024年5月8日周三 12:16写道：
>> 
>> +0 (binding) wave
>> 
>>> On May 7, 2024, at 5:34 PM, Francis Chuang 
 wrote:
>>> 
>>> +1 (binding)
>>> 
>>> I think this is a pragmatic and well-thought out approach.
>>> 
>>> Francis
>>> 
>>> On 8/05/2024 10:31 am, tison wrote:
 Hi,
 Following the discussion thread [1], I'd start a vote on the
 following
 proposals:
 1. Establish a consensus to allow and finally converge podling's
 GitHub repo to
 have a name without the incubator- prefix.
 2. Allow existing ongoing podlings to ask the INFRA to drop their
 incubator- prefix by now, not MUST during the graduation.
 3. Update the docs on incubator.apache.org everywhere if the
 description
 can conflict with this consensus.
 4. Update the docs on incubator.apache.org to guide how to describe
 podling's incubating status on the GitHub repo (namely, including
 "incubating" in the repo description and README, point to the
 DISCLAIMER
 content).
 [1] 
 https://www.google.com/url?q=https://lists.apache.org/thread/kxvdkrf8g8yr6hww1n08r21xdy67y4ok=gmail-imap=171576124300=AOvVaw1uJQyA9Cowa2NFPkD5nOTS
 +1 allow podling's GitHub repo to have a name without the incubator-
 prefix, and other items above
 +0 do not care strongly
 -1 disagree the proposals above, because ...
 Please vote with your ASF ID followed by (binding) if you are a
 member of
 the Incubator PMC or (not binding) if not.
 Vote will be open for at least 72 hours.
 Best,
 tison.
>>> 
>>> -
>>> 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
>> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 
 
>>> 
>>> 
>>> --
>>> Best Regards,
>>> - *Hulk Lin*
>>> 
>> 
>> -
>> To unsubscribe, e-mail: 

Re: Publishing pywayang for pip

[Alexander Alten-Lorenz]

Awesome Xuanwo, thank you!

—Alex 

> On 24. Apr 2024, at 16:07, Xuanwo  wrote:
> 
> Hi,
> 
> Pypi supports OIDC so that we don't need to configure static tokens at all.
> 
> Welcome to take a look over opendal's python release workflow[1]. You can 
> find more at pypa/gh-action-pypi-publish[2]
> 
> [1]: 
> https://www.google.com/url?q=https://github.com/apache/opendal/blob/main/.github/workflows/release_python.yml%23L114-L139=gmail-imap=171457247300=AOvVaw1AtT04WP0yql-SPIqi967O
> [2]: 
> https://www.google.com/url?q=https://github.com/pypa/gh-action-pypi-publish=gmail-imap=171457247300=AOvVaw1AL9hxgRb6Y0gCC9Kpc0TB
> 
> On Wed, Apr 24, 2024, at 21:42, Alexander Alten wrote:
>> Hi Juri et all,
>> 
>> I extend to the incubator community, since that is quite a great question. 
>> 
>> Does any project have a python module released and how does the process 
>> looks like?
>> 
>> Thank you,
>> —Alex 
>> 
>>> On 24. Apr 2024, at 14:23, Juri Petersen  wrote:
>>> 
>>> Hello,
>>> we plan to publish our Python API pywayang as a package to make it 
>>> installable via pip.
>>> In order to do this, we need to generate Python API tokens and store them.
>>> Is there any knowledge on how storing secrets like the token is to be done 
>>> in Apache projects?
>>> Is the infrastructure team responsible for publications like this?
>>> 
>>> Best,
>>> Juri
>> 
>> 
>> -- 
>> *Why Scalytics:* 
>> Break data silos. Put your data to work. All without ever 
>> sharing your data. That's the Scalytics difference.
>> 
>> 
>> --
>> 3401 N. MIAMI AVE. 
>> STE 230
>> 33127 Miami, Florida 
>> United States
>> www.scalytics.io 
>> <https://www.google.com/url?q=http://www.scalytics.io=gmail-imap=171457247300=AOvVaw1zbwEdBS0qzk_kLqRKe50k>
>> 
>> --  Please consider the environment before 
>> printing this email --
>> 
>> Disclaimer:
>> The content of this message is 
>> confidential. If you have received it by mistake, please inform us by an 
>> email reply and then delete the message. It is forbidden to copy, forward, 
>> or in any way reveal the contents of this message to anyone. The integrity 
>> and security of this email cannot be guaranteed over the Internet. 
>> Therefore, the sender will not be held liable for any damage caused by the 
>> message.
>> 
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org 
>> <mailto:general-unsubscr...@incubator.apache.org>
>> For additional commands, e-mail: general-h...@incubator.apache.org 
>> <mailto:general-h...@incubator.apache.org>
> 
> -- 
> Xuanwo

Re: Publishing pywayang for pip

[Alexander Alten]

Hi Juri et all,

I extend to the incubator community, since that is quite a great question. 

Does any project have a python module released and how does the process looks 
like?

Thank you,
 —Alex 

> On 24. Apr 2024, at 14:23, Juri Petersen  wrote:
> 
> Hello,
> we plan to publish our Python API pywayang as a package to make it 
> installable via pip.
> In order to do this, we need to generate Python API tokens and store them.
> Is there any knowledge on how storing secrets like the token is to be done in 
> Apache projects?
> Is the infrastructure team responsible for publications like this?
> 
> Best,
> Juri


-- 
*Why Scalytics:* 
Break data silos. Put your data to work. All without ever 
sharing your data. That's the Scalytics difference.


--
3401 N. MIAMI AVE. 
STE 230
33127 Miami, Florida 
United States
www.scalytics.io 


--  Please consider the environment before 
printing this email --

Disclaimer:
The content of this message is 
confidential. If you have received it by mistake, please inform us by an 
email reply and then delete the message. It is forbidden to copy, forward, 
or in any way reveal the contents of this message to anyone. The integrity 
and security of this email cannot be guaranteed over the Internet. 
Therefore, the sender will not be held liable for any damage caused by the 
message.

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

Re: Update Website Template (WAS: Help to get the Wayang project website in shape)

[Alexander Alten-Lorenz]

+1 (non-binding), quite important to make the onboarding for podlings much 
easier 

> On Feb 14, 2024, at 13:50, Alex Porcelli  wrote:
> 
> +1 (non-binding)
> 
> Awesome initiative!
> 
> 
> On Wed, Feb 14, 2024 at 7:48 AM Twice  wrote:
> 
>> +1.
>> 
>> Docusaurus is super suitable for building open-source project
>> websites, and currently being used by lots of ASF projects.
>> 
>> Replacing the original website template makes sense to me.
>> 
>> Best,
>> Twice
>> 
>> On Wed, Feb 14, 2024 at 3:54 PM Suyan  wrote:
>>> 
>>> +1, that's great!
>>> 
>>> Sincerely,
>>> Suyan
>>> 
>>> tison  于2024年2月4日周日 23:17写道：
>>>> 
>>>> Hi,
>>>> 
>>>> I finally find some time to prepare a demo for the new website
>> template [1].
>>>> 
>>>> It may still open to be improved including a download page template
>>>> and a community page template, as well as some guides as its docs. But
>>>> I'd like to first collecting feedback and finding which PMC is
>>>> responsible for this repository [2].
>>>> 
>>>> The background is that our current template is quite old and not
>>>> updated for the past six years. Few people understand those techniques
>>>> and have a hard time to build their own site. Also, new policy
>>>> compliance and new techniques benefits can be included in the template
>>>> to help new projects (podlings) build a wonderful site.
>>>> 
>>>> I'm glad to maintain this repo but I find myself has no permission
>>>> over this repo. So again, which PMC is responsible for this
>>>> repository?
>>>> 
>>>> Best,
>>>> tison.
>>>> 
>>>> [1]
>> https://github.com/tisonkun/apache-website-template/tree/docusaurus
>>>> [2] https://github.com/apache/apache-website-template/
>>>> 
>>>> Alex Porcelli  于2024年1月30日周二 04:53写道：
>>>>> 
>>>>> Another shout-out for tison and the Apache Fury to provide such a
>> nice
>>>>> starting point for new websites.
>>>>> 
>>>>> I managed to put, for now, a simple placeholder website for Apache
>> KIE
>>>>> (incubation).
>>>>> 
>>>>> Thank you tison and the Apache Fury community!
>>>>> 
>>>>> On Fri, Jan 26, 2024 at 4:10 AM Xuanwo  wrote:
>>>>>> 
>>>>>>> I managed to move our old website to Docusaurus in one day -
>> using the template
>>>>>>> structure from Fury, if you don’t mind.
>>>>>> 
>>>>>> Congrats!
>>>>>> 
>>>>>> On Fri, Jan 26, 2024, at 17:07, Alexander Alten-Lorenz wrote:
>>>>>>> Hey tison,
>>>>>>> 
>>>>>>> Thank you for the head-up. I managed to move our old website to
>>>>>>> Docusaurus in one day - using the template structure from Fury,
>> if you
>>>>>>> don’t mind. Awesome stuff, would love when we’d had a template
>> for the
>>>>>>> podlings to setup a good looking, SEO friendly project page.
>> That’s
>>>>>>> needed to grow the community!
>>>>>>> 
>>>>>>> Cheers, thanks again,
>>>>>>> —Alex
>>>>>>> 
>>>>>>>> On Jan 25, 2024, at 12:01, tison  wrote:
>>>>>>>> 
>>>>>>>> Hi Alexander,
>>>>>>>> 
>>>>>>>> I use Docusaurus for Kvrocks and Fury. Their configuration
>> should be
>>>>>>>> straightforward to follow already. The most simple one now is
>>>>>>>> https://github.com/apache/incubator-fury-site.
>>>>>>>> 
>>>>>>>> Also, Docu is well-documented https://docusaurus.io/docs.
>>>>>>>> 
>>>>>>>> I'm thinking of updating the website template [1] with Docu but
>> have
>>>>>>>> not yet had time and understand which PMC manages this project.
>>>>>>>> 
>>>>>>>> Best,
>>>>>>>> tison.
>>>>>>>> 
>>>>>>>> [1] https://github.com/apache/apache-website-template
>>>>>>>> 
>>>>>>>> Alexander Alten-Lorenz 
>> 于2024年1月

Re: Help to get the Wayang project website in shape

[Alexander Alten-Lorenz]

Hey tison,

Thank you for the head-up. I managed to move our old website to Docusaurus in 
one day - using the template structure from Fury, if you don’t mind. Awesome 
stuff, would love when we’d had a template for the podlings to setup a good 
looking, SEO friendly project page. That’s needed to grow the community!

Cheers, thanks again,
 —Alex 

> On Jan 25, 2024, at 12:01, tison  wrote:
> 
> Hi Alexander,
> 
> I use Docusaurus for Kvrocks and Fury. Their configuration should be
> straightforward to follow already. The most simple one now is
> https://github.com/apache/incubator-fury-site.
> 
> Also, Docu is well-documented https://docusaurus.io/docs.
> 
> I'm thinking of updating the website template [1] with Docu but have
> not yet had time and understand which PMC manages this project.
> 
> Best,
> tison.
> 
> [1] https://github.com/apache/apache-website-template
> 
> Alexander Alten-Lorenz  于2024年1月25日周四 18:20写道：
>> 
>> Hi Xuanwo,
>> 
>> Thank you, highly appreciated! Do you have any how-to for setting Docusaurus 
>> up?
>> 
>> —Alex
>> 
>>> On Jan 25, 2024, at 11:01, Xuanwo  wrote:
>>> 
>>> Hi, alexander
>>> 
>>>> We aren't web designers and we would love to find helping hands to get
>>>> the page in order, including re-organizing and rewriting.
>>> 
>>> I'm with the OpenDAL Community, and we also lack web designers. Our 
>>> community
>>> opted for Docusaurus[1], which we found easy to start with and set up. It
>>> offers a decent theme suitable for open-source projects. For reference, you
>>> can check out OpenDAL's homepage[2]. We hope our experience proves useful.
>>> 
>>> [1] https://docusaurus.io/
>>> [2] https://opendal.apache.org/
>>> 
>>> On Thu, Jan 25, 2024, at 16:26, Alexander Alten wrote:
>>>> Hi incubator community,
>>>> 
>>>> Would anyone be willing to help the Wayang project with our website?
>>>> We aren't web designers and we would love to find helping hands to get
>>>> the page in order, including re-organizing and rewriting.
>>>> 
>>>> thank you, cheers,
>>>> --alexander
>>>> 
>>>> -
>>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>> 
>>> --
>>> Xuanwo
>>> 
>>> -
>>> 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
>> 
> 
> -
> 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: Help to get the Wayang project website in shape

[Alexander Alten-Lorenz]

Hi Xuanwo,

Thank you, highly appreciated! Do you have any how-to for setting Docusaurus up?

—Alex 

> On Jan 25, 2024, at 11:01, Xuanwo  wrote:
> 
> Hi, alexander
> 
>> We aren't web designers and we would love to find helping hands to get
>> the page in order, including re-organizing and rewriting.
> 
> I'm with the OpenDAL Community, and we also lack web designers. Our community
> opted for Docusaurus[1], which we found easy to start with and set up. It 
> offers a decent theme suitable for open-source projects. For reference, you 
> can check out OpenDAL's homepage[2]. We hope our experience proves useful.
> 
> [1] https://docusaurus.io/
> [2] https://opendal.apache.org/
> 
> On Thu, Jan 25, 2024, at 16:26, Alexander Alten wrote:
>> Hi incubator community,
>> 
>> Would anyone be willing to help the Wayang project with our website?
>> We aren't web designers and we would love to find helping hands to get
>> the page in order, including re-organizing and rewriting.
>> 
>> thank you, cheers,
>> --alexander
>> 
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
> 
> -- 
> Xuanwo
> 
> -
> 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

Help to get the Wayang project website in shape

[Alexander Alten]

Hi incubator community,

Would anyone be willing to help the Wayang project with our website?
We aren't web designers and we would love to find helping hands to get
the page in order, including re-organizing and rewriting.

thank you, cheers,
 --alexander

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

Re: [VOTE] Release Apache Wayang (Incubating) v0.7.1 RC3

[Alexander Alten-Lorenz]

Hi Paul,

Good point, added the mention in NOTICE. 

Thank you,
 —Alex 

> On 12. Sep 2023, at 14:34, Paul King  wrote:
> 
> +1 (binding)
> 
> I checked LICENSE, NOTICE, DISCLAIMER, checksum and signature.
> I see Chris has given you useful input on other aspects in the podling
> vote, so I won't duplicate.
> "mvn clean install" worked fine on Ubuntu but failed for me on Windows
> (could be my setup).
> 
> For the vote email, you normally wouldn't have the "or" part of your
> clause "at least 72 hours or until the necessary number
> of votes are reached". -1 votes might come in during the 72 hours but
> after 3 +1 votes.
> 
> For the NOTICE file, I suggest adding a line above the "Copyright 2016
> Sebastian Kruse" entry, something like:
> Some of the files under
> wayang-commons/wayang-utils-profile-db/src/main/java/org/apache/wayang/commons/util/profiledb
> have the following copyright:
> 
> I also checked the 0.7.1 artifacts with my Whiskey Wayang clustering
> example here:
> https://github.com/paulk-asert/groovy-data-science/tree/master/subprojects/WhiskeyWayang
> I used Groovy 5 (alpha-1), JDK11, Wayang 0.7.1, Scala 2.12. All worked
> with no issues.
> 
> Cheers, Paul.
> 
> 
> 
> 
> On Sun, Sep 10, 2023 at 3:19 AM Gláucia Esppenchutz
>  wrote:
>> 
>> Hello everyone,
>> 
>> This calls for a vote to release Release Apache Wayang (Incubating) v0.7.1
>> RC3.
>> The Apache Wayang voted on and approved a proposal to release Apache Wayang
>> (Incubating) version v0.7.1 RC3.
>> 
>> We now kindly request the Incubator PMC members review and vote on this
>> incubator release.
>> 
>> Community vote thread:
>> 
>> https://lists.apache.org/thread/c6d59nfmjq4gs2sfhh1n5gf4c6hxy5vb
>> 
>> Community vote result thread:
>> 
>> https://lists.apache.org/thread/hlc0dh2mwbpwmd9oc1s1oh7l7lj7od36
>> 
>> The release candidates:
>> 
>> https://dist.apache.org/repos/dist/dev/incubator/wayang/0.7.1/rc3/
>> 
>> Git tag for the release:
>> 
>> https://github.com/apache/incubator-wayang/tree/wayang-0.7.1
>> 
>> Keys to verify the Release Candidate:
>> 
>> https://downloads.apache.org/incubator/wayang/KEYS
>> 
>> How to build:
>> 
>> https://github.com/apache/incubator-wayang/tree/wayang-0.7.1#building
>> 
>> The vote will be open for at least 72 hours or until the necessary number
>> of votes are reached.
>> 
>> Please vote accordingly:
>> [ ] +1 approve
>> [ ] +0 no opinion
>> [ ] -1 disapprove with the reason
>> 
>> --
>> Gláucia Esppenchutz
> 
> -
> 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: [VOTE] Release Apache Wayang (Incubating) v0.7.1 RC3

[Alexander Alten-Lorenz]

Hi,

Carry my vote over.

+1 (non-binding)

—Alexander 

> On 9. Sep 2023, at 19:18, Gláucia Esppenchutz  wrote:
> 
> Hello everyone,
> 
> This calls for a vote to release Release Apache Wayang (Incubating) v0.7.1
> RC3.
> The Apache Wayang voted on and approved a proposal to release Apache Wayang
> (Incubating) version v0.7.1 RC3.
> 
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
> 
> Community vote thread:
> 
> https://lists.apache.org/thread/c6d59nfmjq4gs2sfhh1n5gf4c6hxy5vb
> 
> Community vote result thread:
> 
> https://lists.apache.org/thread/hlc0dh2mwbpwmd9oc1s1oh7l7lj7od36
> 
> The release candidates:
> 
> https://dist.apache.org/repos/dist/dev/incubator/wayang/0.7.1/rc3/
> 
> Git tag for the release:
> 
> https://github.com/apache/incubator-wayang/tree/wayang-0.7.1
> 
> Keys to verify the Release Candidate:
> 
> https://downloads.apache.org/incubator/wayang/KEYS
> 
> How to build:
> 
> https://github.com/apache/incubator-wayang/tree/wayang-0.7.1#building
> 
> The vote will be open for at least 72 hours or until the necessary number
> of votes are reached.
> 
> Please vote accordingly:
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
> 
> -- 
> Gláucia Esppenchutz


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

Re: Write Access to submit Podling Report

[Alexander Alten-Lorenz]

Hey Mirko,

We use 

https://cwiki.apache.org/confluence/display/INCUBATOR/June2023#wayang => edit 
page

As example. You need to login with your ASF ID (..@apache.org)

Best,
 —Alex 

> On 2. Aug 2023, at 11:27, Mirko Kämpf  wrote:
> 
> Hello ASF Admins,
> 
> I try another attempt to submit a podling report for the ASF Training 
> Incubator project.
> 
> Unfortunately, I am still not able to edit the report submission page:
> 
> https://cwiki.apache.org/confluence/display/incubator/August2023#training
> 
> I am using this account:
> 
> 
> 
> 
> 
> 
> 
> 
> Dear Admin, please give me the write permission to add the podling reports 
> for the ASF Training project.
> 
> In order to speed up the process I have attached the report to this email.
> 
> Many thanks and best regards,
> Mirko
> 
> 
> -- 
> 
> Dr. rer. nat. Mirko Kämpf
> Müchelner Str. 23
> 06259 Frankleben
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org

Re: License question when including other ASF projects

[Alexander Alten-Lorenz]

Hey Chris,

Thank you, solved that. Wasn’t sure about the licenses, but as they come from 
Calcite we just whitelisted Eclipse.

Cheers,
 —Alex 

> On 3. May 2023, at 14:24, Christofer Dutz  wrote:
> 
> Hi Alex,
> 
> sorry for the late response ... I also checked and the Eclipse Distribution 
> Licence 1.0 seems to be Category A and EPL 2.0 cat B, so it should be ok as 
> long as you only have dependencies to it.
> 
> However I don’t know the plugin that you are using, so I can’t really help 
> about how to resolve false-positives ... might have a look at it thoug.
> 
> Chris
> 
> 
> Von: Alexander Alten-Lorenz 
> Datum: Dienstag, 2. Mai 2023 um 16:05
> An: general@incubator.apache.org 
> Betreff: Re: License question when including other ASF projects
> Can anyone give us a tip regarding this one?
> 
> Thanks,
> —alex
> 
>> On 30. Apr 2023, at 18:13, Alexander Alten-Lorenz  
>> wrote:
>> 
>> Hey Dominik,
>> 
>> Sry for bugging, any chance you know how to tune the license check that the 
>> Eclipse License passes?
>> https://github.com/apache/incubator-wayang/actions/runs/4845087374/jobs/8633774880#step:6:1151
>> 
>> It’s merged, but we’d love to have a green build :)
>> 
>> Cheers,
>> —Alex
>> 
>> 
>>> On 29. Apr 2023, at 11:40, Alexander Alten-Lorenz 
>>>  wrote:
>>> 
>>> Hey Dominik,
>>> 
>>> Thank you for confirming. I try to merge now, let’s hope :)
>>> 
>>> Cheers,
>>> —Alex
>>> 
>>>> On 29. Apr 2023, at 11:36, Dominik Riemer  wrote:
>>>> 
>>>> Hi Alex,
>>>> 
>>>> EPL 2.0 should be fine in case it is included in binary-only form (see 
>>>> Category B under [1]).
>>>> 
>>>> Cheers
>>>> Dominik
>>>> 
>>>> 
>>>> [1] https://www.apache.org/legal/resolved.html
>>>> 
>>>> 
>>>> -Original Message-
>>>> From: Alexander Alten-Lorenz 
>>>> Sent: Saturday, April 29, 2023 11:29 AM
>>>> To: general@incubator.apache.org
>>>> Subject: License question when including other ASF projects
>>>> 
>>>> Hi,
>>>> 
>>>> We use Apache Calcite, dependabot suggests a bump, but the automation 
>>>> failed since Calcite uses a non-compatible license (if I’m right)
>>>> 
>>>> https://github.com/apache/incubator-wayang/actions/runs/4751917613/jobs/8441627979?pr=302#step:6:1117
>>>> 
>>>> How can we solve this, except not to update ;) Or is this just a false 
>>>> alarm?
>>>> 
>>>> Thanks for the help,
>>>> —Alex
>>>> 
>>>> 
>>>> 
>>>> -
>>>> 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: License question when including other ASF projects

[Alexander Alten-Lorenz]

Can anyone give us a tip regarding this one?

Thanks,
 —alex

> On 30. Apr 2023, at 18:13, Alexander Alten-Lorenz  
> wrote:
> 
> Hey Dominik,
> 
> Sry for bugging, any chance you know how to tune the license check that the 
> Eclipse License passes?
> https://github.com/apache/incubator-wayang/actions/runs/4845087374/jobs/8633774880#step:6:1151
> 
> It’s merged, but we’d love to have a green build :)
> 
> Cheers,
>  —Alex 
> 
> 
>> On 29. Apr 2023, at 11:40, Alexander Alten-Lorenz  
>> wrote:
>> 
>> Hey Dominik,
>> 
>> Thank you for confirming. I try to merge now, let’s hope :)
>> 
>> Cheers,
>> —Alex 
>> 
>>> On 29. Apr 2023, at 11:36, Dominik Riemer  wrote:
>>> 
>>> Hi Alex,
>>> 
>>> EPL 2.0 should be fine in case it is included in binary-only form (see 
>>> Category B under [1]).
>>> 
>>> Cheers
>>> Dominik
>>> 
>>> 
>>> [1] https://www.apache.org/legal/resolved.html
>>> 
>>> 
>>> -Original Message-
>>> From: Alexander Alten-Lorenz  
>>> Sent: Saturday, April 29, 2023 11:29 AM
>>> To: general@incubator.apache.org
>>> Subject: License question when including other ASF projects
>>> 
>>> Hi,
>>> 
>>> We use Apache Calcite, dependabot suggests a bump, but the automation 
>>> failed since Calcite uses a non-compatible license (if I’m right) 
>>> 
>>> https://github.com/apache/incubator-wayang/actions/runs/4751917613/jobs/8441627979?pr=302#step:6:1117
>>> 
>>> How can we solve this, except not to update ;) Or is this just a false 
>>> alarm?
>>> 
>>> Thanks for the help,
>>> —Alex 
>>> 
>>> 
>>> 
>>> -
>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
> 

Re: License question when including other ASF projects

[Alexander Alten-Lorenz]

Hey Dominik,

Sry for bugging, any chance you know how to tune the license check that the 
Eclipse License passes?
https://github.com/apache/incubator-wayang/actions/runs/4845087374/jobs/8633774880#step:6:1151

It’s merged, but we’d love to have a green build :)

Cheers,
 —Alex 


> On 29. Apr 2023, at 11:40, Alexander Alten-Lorenz  
> wrote:
> 
> Hey Dominik,
> 
> Thank you for confirming. I try to merge now, let’s hope :)
> 
> Cheers,
> —Alex 
> 
>> On 29. Apr 2023, at 11:36, Dominik Riemer  wrote:
>> 
>> Hi Alex,
>> 
>> EPL 2.0 should be fine in case it is included in binary-only form (see 
>> Category B under [1]).
>> 
>> Cheers
>> Dominik
>> 
>> 
>> [1] https://www.apache.org/legal/resolved.html
>> 
>> 
>> -Original Message-
>> From: Alexander Alten-Lorenz  
>> Sent: Saturday, April 29, 2023 11:29 AM
>> To: general@incubator.apache.org
>> Subject: License question when including other ASF projects
>> 
>> Hi,
>> 
>> We use Apache Calcite, dependabot suggests a bump, but the automation failed 
>> since Calcite uses a non-compatible license (if I’m right) 
>> 
>> https://github.com/apache/incubator-wayang/actions/runs/4751917613/jobs/8441627979?pr=302#step:6:1117
>> 
>> How can we solve this, except not to update ;) Or is this just a false alarm?
>> 
>> Thanks for the help,
>> —Alex 
>> 
>> 
>> 
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
> 

Re: License question when including other ASF projects

[Alexander Alten-Lorenz]

Hey Dominik,

Thank you for confirming. I try to merge now, let’s hope :)

Cheers,
 —Alex 

> On 29. Apr 2023, at 11:36, Dominik Riemer  wrote:
> 
> Hi Alex,
> 
> EPL 2.0 should be fine in case it is included in binary-only form (see 
> Category B under [1]).
> 
> Cheers
> Dominik
> 
> 
> [1] https://www.apache.org/legal/resolved.html
> 
> 
> -Original Message-
> From: Alexander Alten-Lorenz  
> Sent: Saturday, April 29, 2023 11:29 AM
> To: general@incubator.apache.org
> Subject: License question when including other ASF projects
> 
> Hi,
> 
> We use Apache Calcite, dependabot suggests a bump, but the automation failed 
> since Calcite uses a non-compatible license (if I’m right) 
> 
> https://github.com/apache/incubator-wayang/actions/runs/4751917613/jobs/8441627979?pr=302#step:6:1117
> 
> How can we solve this, except not to update ;) Or is this just a false alarm?
> 
> Thanks for the help,
> —Alex 
> 
> 
> 
> -
> 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

License question when including other ASF projects

[Alexander Alten-Lorenz]

Hi,

We use Apache Calcite, dependabot suggests a bump, but the automation failed 
since Calcite uses a non-compatible license (if I’m right) 

https://github.com/apache/incubator-wayang/actions/runs/4751917613/jobs/8441627979?pr=302#step:6:1117

How can we solve this, except not to update ;) Or is this just a false alarm?

Thanks for the help,
 —Alex 

Re: [VOTE] Accept Uniffle into the Apache Incubator

[Alexander Alten-Lorenz]

Hi,  +1 (non-binding), good luck :)

Sent from my iPhone

> On 31. May 2022, at 08:20, Justin Mclean  wrote:
> 
> Hi,
> 
> +1 (binding) if you need help with anything please ask on the 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: [DISCUSS] Graduate Apache InLong(Incubating) as a TLP

[Alexander Alten]

+1 (non-binding)

Well done! Good luck :) 

> On 20. May 2022, at 11:36, Young Seung Andrew Ko 
>  wrote:
> 
> +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
 
 [7]
 
>>> 
>>> 
>> https://github.com/apache/incubator-inlong/issues?q=is%3Aissue+is%3Aclosed
 
 [8]
>>> https://github.com/apache/incubator-inlong/tree/master/licenses
 
 [9]
 
>>> 
>>> 
>> 

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

[Alexander Alten-Lorenz]

+1 (non-binding). Good luck :)

—alex 

Sent from my iPhone

> On 11. May 2022, at 07:58, Jialin Qiao  wrote:
> 
> +1 (non-binding)
> —
> Jialin Qiao
> Apache IoTDB PMC
> 
> 
>  于2022年5月11日周三 12:22写道：
> 
>> +1(non-binding)
>> 
>> We had multiple success releases in Apache MXNet and have seen many
>> contributions.
>> In the past 5 years, we grow our members from a diverse backgrounds. It's
>> great to see the project finally move to the graduation.
>> 
>> Thanks,
>> Qing
>> 
>> 
>> From: Joe Evans 
>> Sent: Tuesday, April 26, 2022 14:06
>> To: general@incubator.apache.org 
>> Subject: [FWD] [VOTE] Graduate Apache MXNet (incubating) to a Top Level
>> Project
>> 
>> Hello Incubator Community,
>> 
>> After community discussions[1][2], the Apache MXNet (incubating) project is
>> currently having a community vote[3] to graduate to a top level project. We
>> welcome any feedback.
>> 
>> References:
>> 
>> [1]
>> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fincubator-mxnet%2Fissues%2F20984data=05%7C01%7C%7Cfe48413cd9f94667d47e08da27c8a117%7C84df9e7fe9f640afb435%7C1%7C0%7C637866039903742079%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=RjJWTNqk8Cga%2BSxjcm5dTh8%2BNP%2FqpBCr13UqX1rGysk%3Dreserved=0
>> 
>> [2]
>> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fl9h2qgb2vqs2y0cm46wh83sgomr9w190data=05%7C01%7C%7Cfe48413cd9f94667d47e08da27c8a117%7C84df9e7fe9f640afb435%7C1%7C0%7C637866039903742079%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=J3HDiyKq9rl53%2BmkCgDUH%2FJbJvP4arJY%2BmYS7KDv9NI%3Dreserved=0
>> 
>> [3]
>> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fpy1nw6whov78sch5kkm1gcg7cv3zb2svdata=05%7C01%7C%7Cfe48413cd9f94667d47e08da27c8a117%7C84df9e7fe9f640afb435%7C1%7C0%7C637866039903742079%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=0bu7rLw8xYC7jSWu8TEJd0C4MTFHvgfS4Y1FhaCQWFA%3Dreserved=0
>> 
>> 
>> -- Forwarded message -
>> From: Joe Evans 
>> Date: Tue, Apr 26, 2022 at 1:56 PM
>> Subject: [VOTE] Graduate Apache MXNet (incubating) to a Top Level Project
>> To: 
>> 
>> 
>> Hi MXNet Community,
>> 
>> Apache MXNet (incubating) has been an incubating project since January,
>> 2017. Since then, the project has matured and adopted the Apache Software
>> Foundation’s principles and philosophy around building and maintaining open
>> source software. There is a thriving community of developers and users from
>> all over the world that regularly contribute to the project.
>> 
>> Based on the positive responses in the graduation RFC[1] and discussion
>> thread[2], we would like to have a community vote on graduating MXNet to an
>> Apache Top Level project.
>> 
>> Here is a brief overview of the progress of the Apache MXNet (incubating)
>> project and community since entering the incubator:
>> 
>> Community
>> 
>>   -
>> 
>>   37 new PPMC members were added, bringing the total number of PPMC
>>   members to 50
>>   -
>> 
>>   56 new committers were added (which include new PPMC members), bringing
>>   the total number of committers to 87
>>   -
>> 
>>   The total number of contributors is now 870 and growing.
>> 
>> Project
>> 
>>   -
>> 
>>   18 releases[3] by 13 different release managers. All compliance issues
>>   have been resolved with the 1.9.0 and 2.0.beta releases.
>>   -
>> 
>>   MXNet website[4] is now compliant with Apache Project Website
>>   requirements[5]
>>   -
>> 
>>   MXNet has completed the project maturity self assessment[6]
>> 
>> 
>> Here is the proposed resolution:
>> 
>> —--
>> 
>> Establish the Apache MXNet 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 flexible and efficient library for Deep Learning.
>> 
>> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
>> 
>> (PMC), to be known as the "Apache MXNet Project", be and hereby is
>> 
>> established pursuant to Bylaws of the Foundation; and be it further
>> 
>> RESOLVED, that the Apache MXNet Project be and hereby is responsible for
>> 
>> the creation and maintenance of software related to a flexible and
>> 
>> efficient library for Deep Learning; and be it further
>> 
>> RESOLVED, that the office of "Vice President, Apache MXNet" be and
>> 
>> hereby is created, the person holding such office to serve at the
>> 
>> direction of the Board of Directors as the 

Re: [VOTE] Release Apache Wayang (Incubating) 0.6.0-RC9

[Alexander Alten]

Hi,

I carry my vote over, as non-binding

Cheers,
 —Alex 

> On 10. Dec 2021, at 15:49, Lars George  wrote:
> 
> Hi,
> 
> +1 (binding)
> 
> I checked:
> - Incubating in name
> - Hash matches archive
> - DISCLAIMER present
> - LICENSE and NOTICE content
> - License check with RAT
> - Build on Windows WSL 2 successfully
> 
> Lars
> 
> On Fri, Dec 10, 2021 at 2:52 PM Christofer Dutz 
> wrote:
> 
>> Common' folks ...
>> 
>> please could some more people vote on this release ... the team worked so
>> hard to resolve all of the issues pointed out, now let's help them get
>> their first release out the door :-)
>> 
>> Chris
>> 
>> -Original Message-
>> From: Zhang Yonglun 
>> Sent: Dienstag, 7. Dezember 2021 12:51
>> To: general@incubator.apache.org
>> Subject: Re: [VOTE] Release Apache Wayang (Incubating) 0.6.0-RC9
>> 
>> Hi,
>> 
>> +1 (non binding)
>> 
>> I checked:
>> - incubating in name
>> - signatures and hashes are fine
>> - Disclaimer exists
>> - LICENSE and NOTICE are fine
>> - All source have ASF headers
>> - No unexpected binary files
>> 
>> Hope this helps.
>> Maybe you would like to use this command to generate the hashes:
>> shasum -a 512
>> apache-wayang-${RELEASE.VERSION}-incubating-source-release.zip >
>> apache-wayang-${RELEASE.VERSION}-incubating-source-release.zip.sha512
>> After done that, one can check the hashes more simply by:
>> shasum -c
>> apache-wayang-${RELEASE.VERSION}-incubating-source-release.zip.sha512
>> 
>> --
>> 
>> Zhang Yonglun
>> Apache ShenYu (Incubating)
>> Apache ShardingSphere
>> 
>> 
>> Bertty Contreras  于2021年12月6日周一 19:02写道：
>> 
>>> Hello Incubator Community,
>>> 
>>> The Apache Wayang community has voted on and approved a proposal to
>>> release Apache Wayang(Incubating) version v0.6.0-RC9.
>>> 
>>> We now kindly request the Incubator PMC members review and vote on
>>> this incubator release.
>>> 
>>> Wayang community vote thread:
>>> *https://www.mail-archive.com/dev@wayang.apache.org/msg00594.html
>>> *
>>> 
>>> Vote result thread:
>>> *https://www.mail-archive.com/dev@wayang.apache.org/msg00608.html
>>> *
>>> 
>>> [ ] +1 Release this package as Apache Wayang v0.6.0 [ ] +0 [ ] -1 Do
>>> not release this package because ...
>>> 
>>> To learn more about Apache Wayang (Incubating), please see
>>> https://wayang.apache.org/
>>> 
>>> Release notes:
>>> https://github.com/apache/incubator-wayang/blob/rel/0.6.0/RELEASE_NOTE
>>> S
>>> 
>>> The tag to be voted on is wayang-0.6.0 (commit cb464b6):
>>> https://github.com/apache/incubator-wayang/tree/rel/0.6.0
>>> 
>>> The release files, including signatures, digests, etc. can be found at:
>>> https://dist.apache.org/repos/dist/dev/incubator/wayang/0.6.0/rc9
>>> 
>>> Signatures used for Wayang RC's can be found in this file:
>>> *https://downloads.apache.org/incubator/wayang/KEYS
>>> *
>>> 
>>> The staging repository for this release can be found at:
>>> 
>>> https://repository.apache.org/content/repositories/orgapachewayang-101
>>> 0/org/apache/wayang/
>>> 
>>> Build instructions:
>>> 
>>> https://github.com/apache/incubator-wayang/blob/rel/0.6.0/README.md#ho
>>> w-to-use-wayang
>>> 
>>> Thanks,
>>> Bertty Contreras Rojas
>>> 
>> 


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

Re: [VOTE] Accept SeaTunnel into the Apache Incubator

[Alexander Alten]

Hi,

I know SeaTunnel quite a while, and it would extend perfectly Wayang. Here my 
+1 (non binding)

Cheers,
 —Alex 

> On 3. Dec 2021, at 17:18, Daniel B. Widdis  wrote:
> 
> +1 (non binding)
> 
> On Fri, Dec 3, 2021 at 5:57 AM Willem Jiang  wrote:
> 
>> Hi all,
>> 
>> Following up the [DISCUSS] thread on SeaTunnel [1] I would like to call a
>> VOTE to accept into the Apache Incubator.
>> 
>> Please cast your vote:
>> 
>>  [ ] +1, bring  into the Incubator
>>  [ ] +0, I don't care either way
>>  [ ] -1, do not bring SeaTunnel into the Incubator, because...
>> 
>> The vote will open at least for 72 hours and only votes from the
>> Incubator PMC are binding, but votes from everyone are welcome.
>> 
>> Please check out the SeaTunnel Proposal from the incubator wiki[2].
>> 
>> [1]https://lists.apache.org/thread/nvp0sxnl0b69wgylxsvmdshfd70om1gk
>> [2]https://cwiki.apache.org/confluence/display/INCUBATOR/SeaTunnelProposal
>> 
>> Regards,
>> 
>> Willem Jiang
>> 
>> Twitter: willemjiang
>> Weibo: 姜宁willem
>> 
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
>> 
> 
> -- 
> Dan Widdis


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

Re: [VOTE] Release Apache Wayang (Incubating) 0.6.0-RC7

[Alexander Alten]

Thanks, fixed with PR #42 and #43. We look into the sha512 issue, was correct 
some days ago ..

cheers,
 —Alex 


> On 24. Nov 2021, at 15:29, Calvin Kirs  wrote:
> 
> The DISCLAIMER and NOTICE text is Incorrect：
>should be added "(Incubating)"  after Apache wayang.

Re: [VOTE] Release Apache Wayang (Incubating) 0.6.0-RC6

[Alexander Alten]

Hi,

Thanks for finding this, Justin. We fix and prepare the new RC. 

Stay safe, cheers,
—Alex 

> On 21. Nov 2021, at 09:29, Justin Mclean  wrote:
> 
> Hi,
> 
> Sorry but it -1 (binding) from me due to LICENSE and NOTICE issues and 3rd 
> party code having an ASF header.
> 
> I checked:
> - incubating in name
> - signatures and hashes are fine.
> - DISCLAIMER exists
> - NOTICE and LICENSE are not correct. Licenses need to be mentioned in 
> LICENSE. If the code has a NOTICE file then it’s content need to be in 
> NOTICE. 
> - ASF headers have been incorrectly added to 3rd party files e.g. [1]
> - Other ASF files headers seem fine
> - Can compile from source
> 
> Also please do not use the words "Copyright 2020 and onwards” as copyright 
> has an expiry date.
> 
> Kind Regards,
> Justin
> 
> 1. 
> ./wayang-commons/wayang-utils-profile-db/src/main/java/org/apache/wayang/commons/util/profiledb/instrumentation/StopWatch.java
> -
> 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: [VOTE] Release Apache Wayang (Incubating) 0.6.0-RC6

[Alexander Alten]

Hi,

I carry my +1 from the project, here as non-binding.

Stay safe,
 —Alex 

> On 19. Nov 2021, at 18:01, Lars George  wrote:
> 
> Hi,
> 
> +1
> 
> - Compiled on Windows (WSL Ubuntu)
> - Licenses checked (Ran rat plugin via Maven)
> - Checksum checked (SHA512)
> - Checked incubation in name
> 
> Lars
> 
> On Thu, Nov 18, 2021 at 4:16 AM Bertty Contreras 
> wrote:
> 
>> Hello Incubator Community,
>> 
>> Chris carei a his vote, +1 (binding)[1]
>> 
>> Best regards,
>> Bertty Contreras Rojas
>> 
>> [1] https://www.mail-archive.com/dev@wayang.apache.org/msg00534.html
>> 
>> 
>> On Thu, Nov 18, 2021 at 1:14 PM Bertty Contreras 
>> wrote:
>> 
>>> Hello Incubator Community,
>>> 
>>> The Apache Wayang community has voted on and approved a proposal to
>> release
>>> Apache Wayang(Incubating) version v0.6.0-RC6.
>>> 
>>> We now kindly request the Incubator PMC members review and vote on this
>>> incubator release.
>>> 
>>> Wayang community vote thread:
>>> *https://www.mail-archive.com/dev@wayang.apache.org/msg00525.html
>>> *
>>> 
>>> Vote result thread:
>>> *https://www.mail-archive.com/dev@wayang.apache.org/msg00536.html
>>> *
>>> 
>>> [ ] +1 Release this package as Apache Wayang v0.6.0
>>> [ ] +0
>>> [ ] -1 Do not release this package because ...
>>> 
>>> To learn more about Apache Wayang (Incubating), please see
>>> https://wayang.apache.org/
>>> 
>>> Release notes:
>>> https://github.com/apache/incubator-wayang/blob/rel/0.6.0/RELEASE_NOTES
>>> 
>>> The tag to be voted on is wayang-0.6.0 (commit 9fe19a1):
>>> https://github.com/apache/incubator-wayang/tree/rel/0.6.0
>>> 
>>> The release files, including signatures, digests, etc. can be found at:
>>> https://dist.apache.org/repos/dist/dev/incubator/wayang/0.6.0/rc6
>>> 
>>> Signatures used for Wayang RC's can be found in this file:
>>> *https://downloads.apache.org/incubator/wayang/KEYS
>>> *
>>> 
>>> The staging repository for this release can be found at:
>>> 
>>> 
>> https://repository.apache.org/content/repositories/orgapachewayang-1007/org/apache/wayang
>>> 
>>> Build instructions:
>>> 
>>> 
>> https://github.com/apache/incubator-wayang/blob/rel/0.6.0/README.md#how-to-use-wayang
>>> 
>>> Thanks,
>>> Bertty Contreras Rojas
>>> 
>> 


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

Re: [VOTE] Release Apache Wayang (Incubating) 0.6.0-RC5

[Alexander Alten]

Hi,

Ya, you’re right :) 

+1 (non-binding)

Compiled on Arm M1
Compiled on Windows
Licenses checked (rat)
Checksum checked
Incubation in name
ASF headers


> On 7. Nov 2021, at 12:34, Justin Mclean  wrote:
> 
> Hi,
> 
> I’ll also note that Alexander’s vote is non binding, best practice to 
> indicate it as such like so “+1 (non-binding)”. It also a good idea to list 
> what was checked in the release rather than just voting “+1". Only IPMC 
> members votes are binding on ASF incubator releases.
> 
> Kind Regards,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 

Re: [VOTE] Release Apache Wayang (Incubating) 0.6.0-RC5

[Alexander Alten]

Hi,

Honestly I don’t get it. Same techniques are used in Apache Spark and Apache 
Flink, as example. How’s that working? 
We referenced the Wikipedia article as a documentation how page rank works. Why 
should this violate the ASF policy? The algorithm looks exactly as is it is 
[1], means the only fix would be _not_to use it? 

1 - 
https://towardsdatascience.com/pagerank-algorithm-fully-explained-dc794184b4af

Best,
 —Alex 

> On 7. Nov 2021, at 11:24, Justin Mclean  wrote:
> 
> Hi,
> 
>> Agree with Daniel, the node creation is a common technique in the data 
>> science community and does not represent code, it is representing a 
>> procedure to create nodes. Therefore the use of this procedure seems 
>> compliant.
> 
> IMO it is not compliant with ASF policy, no matter how common this practice 
> may be in the data science community. ASF policy covers more than just code.
> 
> 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: [VOTE] Release Apache Wayang (Incubating) 0.6.0-RC5

[Alexander Alten]

+1 

PR for the NOTICE [1] includes the changes Justin suggested, will be fixed in 
the next release. Agree with Daniel, the node creation is a common technique in 
the data science community and does not represent code, it is representing a 
procedure to create nodes. Therefore the use of this procedure seems compliant.

1 - https://github.com/apache/incubator-wayang/pull/37

> On 7. Nov 2021, at 08:58, Daniel Widdis  wrote:
> 
> Generally in agreement, but:
> 
>> given there may be a license issue and it's very easy to fix, why not fix it?
> 
> Any "fix" will look like the old code and thus be "modified".  
> 
> The new graph in this case happens to have the same number of nodes and arcs 
> as the original copyrighted artwork, but arranged in a completely different 
> way.  Your position seems to be this might not "fix" the problem.
> 
> I think we are all in agreement that a randomly generated set of nodes and 
> arcs would be compliant, even if the code still looks similar.
> 
> 
> On 11/6/21, 11:40 PM, "Justin Mclean"  wrote:
> 
>Hi,
> 
>> And sure, the image labeled with B and C is based on the non-labeled image 
>> with smiley faces, so I'll concede that image, and even the exact network it 
>> represents, may fall under CC-BY-SA, and thus it was correct to remove the 
>> old code.
> 
>This main issue I think as the old code wasn’t replaced but modified. 
> Modified stuff in general keeps the same license the original. That may apply 
> here, but I’m not 100% sure, but I don’t think it a serious issue. But given 
> there may be a license issue and it's very easy to fix, why not fix it? Also 
> other IPMC members can still vote +1 and this become a release, but I suggest 
> the project fixes it in a future release. If you had used teh WIP progress 
> disclaimer I would have votes +1 and suggested that.
> 
>> Are you asserting that any directed graph is CC-BY-SA licensed?  If not, 
>> what is the threshold for difference that you would accept?
> 
>I would assume not, but you'd need to get actually legal advice to regards 
> what the threshold would be. As is every user of this software may need to 
> seek that advice in order to use it without that risk. The risk could be 
> minimal or nonexistent, but IANAL it's best IMO to err on the side of caution 
> with stuff like this.
> 
>> Would it be acceptable to generate a completely random graph using [1] and 
>> represent that in the code?
> 
>Sure, but so would one that the project came up with itself that wasn’t 
> based on another one, or one that was under compatible license.
> 
>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
> 


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

Re: [VOTE] Release Apache Wayang (Incubating) 0.6.0

[Alexander Alten]

+1 (binding)

--alex

On Sat, Oct 23, 2021, 13:52 Bertty Contreras  wrote:

> Hello Incubator Community,
>
> The Apache Wayang community has voted on and approved a proposal to release
> Apache Wayang(Incubating) version v0.6.0-RC4.
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Wayang community vote thread:
> https://www.mail-archive.com/dev@wayang.apache.org/msg00446.html
>
> Vote result thread:
> https://www.mail-archive.com/dev@wayang.apache.org/msg00458.html
>
> [ ] +1 Release this package as Apache Wayang v0.6.0
> [ ] +0
> [ ] -1 Do not release this package because ...
>
> To learn more about Apache Wayang (Incubating), please see
> https://wayang.apache.org/
>
> Release notes:
> https://github.com/apache/incubator-wayang/blob/rel/0.6.0/RELEASE_NOTES
>
> The tag to be voted on is wayang-0.6.0 (commit 9fe19a1):
> https://github.com/apache/incubator-wayang/tree/rel/0.6.0
>
> The release files, including signatures, digests, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/wayang/0.6.0/rc4
>
> Signatures used for Wayang RC's can be found in this file:
> https://dist.apache.org/repos/dist/dev/incubator/wayang/KEYS
>
> The staging repository for this release can be found at:
>
> https://repository.apache.org/content/repositories/orgapachewayang-1005/org/apache/wayang
>
> Build instructions:
>
> https://github.com/apache/incubator-wayang/blob/rel/0.6.0/README.md#how-to-use-wayang
>
> Thanks,
> Bertty Contreras Rojas
>

Re: Require websites to have standard download URL?

[Alexander Alten]

Good idea, +1

—Alex 

> On 17. Sep 2021, at 15:23, sebb  wrote:
> 
> Many of the podling websites have a download page of the form:
> 
> https://.apache.org/download/
> 
> Given that every website must have a download page, and that the
> /download/ URL can easily be redirected to an alternate page, it might
> be worth considering making this URL a requirement for all podling
> websites.
> 
> Sebb
> 
> -
> 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: [MENTORS] Download pages and links to podling releases

[Alexander Alten]

Hi Justin,

Wayang works on the first release atm, thats why we don’t have a download page 
;)

Stay safe, great work from you here btw!
—Alex 

—
Alexander Alten
PPMC Apache Wayang (incubating)

> On 16. Sep 2021, at 03:18, Justin Mclean  wrote:
> 
> Hi,
> 
> Can mentors please make themselves familiar with the requirements for 
> download pages and links [1] as we seem to have a number of projects that are 
> not providing downloads in the required manner.
> 
> In general:
> - Please use https://www.apache.org/dyn/closer.lua 
> <https://www.apache.org/dyn/closer.lua> for releases
> - Please use https://downloads.apache.org/  for hashes and signatures
> 
> 
> Form a quick check these project don’t seem to have an obvious download page:
> Age
> Annotator
> BlueMarlin 
> Liminal
> Linkis
> Marvin
> SDAP
> Sedona
> Wayang
> 
> Now in some cases these are newish projects and they haven’t made a release, 
> however others on that list have made releases and really should have a 
> download page. If they do have a download page please provide the URL.
> 
> These projects look to have issue with the download links themselves:
> BRPC - https://brpc.apache.org/download/ <https://brpc.apache.org/download/>
> Crail - http://crail.apache.org/download/ <http://crail.apache.org/download/>
> DataLab - http://datalab.apache.org/#download 
> <http://datalab.apache.org/#download>
> Doris - http://doris.apache.org/master/en/downloads/downloads.html 
> <http://doris.apache.org/master/en/downloads/downloads.html>
> Heron - https://heron.apache.org/download <https://heron.apache.org/download>
> Hivemall - https://hivemall.apache.org/download.html 
> <https://hivemall.apache.org/download.html>
> Kyuubi - https://kyuubi.apache.org/releases.html 
> <https://kyuubi.apache.org/releases.html>
> Livy - https://livy.apache.org/download/ <https://livy.apache.org/download/>
> Milagro - https://milagro.apache.org/docs/downloads/ 
> <https://milagro.apache.org/docs/downloads/>
> Nemo - https://nemo.apache.org/pages/downloads/ 
> <https://nemo.apache.org/pages/downloads/>
> NLPCraft - https://nlpcraft.apache.org/download.html 
> <https://nlpcraft.apache.org/download.html>
> NuttX - https://nuttx.apache.org/download/ 
> <https://nuttx.apache.org/download/>
> PageSpeed - https://pagespeed.apache.org/doc/download 
> <https://pagespeed.apache.org/doc/download>
> PonyMail - https://ponymail.apache.org/downloads.html 
> <https://ponymail.apache.org/downloads.html>
> Spot - https://spot.apache.org/download/ <https://spot.apache.org/download/>
> Teaclave - https://teaclave.apache.org/download/ 
> <https://teaclave.apache.org/download/>
> Training - https://training.apache.org/downloads.html 
> <https://training.apache.org/downloads.html>
> 
> This list was autogenerated by a script and may have got some things wrong. 
> If you need details on a particular project and it’s links please check here. 
> [1]
> 
> Thanks,
> Justin
> 
> 1. https://gist.github.com/justinmclean/60a824a2f3fe97e519ed25d7c39a47ed
> 
> 
> 1. https://infra.apache.org/release-distribution.html#download-links


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

Re: [VOTE]Release Apache Liminal (incubating) 0.0.3rc4-INCUBATING

[Alexander Alten]

+1 (unbinding)

Sry - was a bit late:)

—Alex 

> On 11. Aug 2021, at 20:15, JB Onofré  wrote:
> 
> +1 (binding)
> 
> Regards 
> JB
> 
>> Le 11 août 2021 à 19:25, Davor Bonaci > > a écrit :
>> 
>> +1 (binding)
>> 
>>> On Mon, Aug 9, 2021 at 7:17 AM Lior Schachter  wrote:
>>> 
>>> We would like to have a re-vote on RC4 of version 0.0.3 - after fixing the 
>>> packaging of the tag and uploading it to SVN.
>>> 
>>> This version introduces out-of-the-box functionality to author and execute 
>>> ML workflows (data fetching-feature engineering-training-inference) in the 
>>> local machine and in AWS using Airflow, Kubernetes and Spark.
>>> 
>>> Liminal community vote and result threads:
>>> Vote:
>>> https://lists.apache.org/thread.html/rcdc714d4de15cb12e2387e8dc8fe2eac1497ed2af55e760bb42ecc64%40%3Cdev.liminal.apache.org%3E
>>> 
>>> Result:
>>> https://lists.apache.org/thread.html/ra05372eed5c9ab5c3cf97c16ca93a33ffcc4b797cc341bf4ceaac079%40%3Cdev.liminal.apache.org%3E
>>> 
>>> Installation and testing instructions can be found in the README included.
>>> 
>>> The release files, including signatures, digests, etc. can be found at:
>>> 
>>> https://dist.apache.org/repos/dist/dev/incubator/liminal/0.0.3rc4-INCUBATING/
>>> 
>>> The tag to be voted on:
>>> 
>>> https://github.com/apache/incubator-liminal/releases/tag/0.0.3rc4-incubating
>>> 
>>> The SHA512 Checksum for these artifacts is:
>>> 
>>> apache-liminal-0.0.3rc4-incubating-source.tar.gz:
>>> 
>>> 1BC663C2 6317E840 3292B7BE E2023011 EE0DBAD8 8D05A908 3D68534C 360F2125 
>>> B7981E90 082466C0 F16314E6 14434C60 584357C6 8E8207EB BA9FD21E E0AC110A
>>> 
>>> Release artifacts are signed with the following key:
>>> 
>>> https://dist.apache.org/repos/dist/dev/incubator/liminal/KEYS
>>> 
>>> For more information about the contents of this release, 
>>> see:https://issues.apache.org/jira/projects/LIMINAL/versions/12349981
>>> 
>>> 
>>> Please vote on releasing this package as Apache Liminal 0.0.3-INCUBATING:
>>> 
>>> [ ] +1 Release this package as Apache Liminal 0.0.3-INCUBATING
>>> [ ] +0 No opinion
>>> [ ] -1 Do not release this package because ...
>>> 
>>> Regards,
>>> Lior Schachter
>>> 
>>> 
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org 
> 
> For additional commands, e-mail: general-h...@incubator.apache.org 
> 

Re: [VOTE] Accept Linkis into the Apache Incubator

[Alexander Alten]

Looks promising!

+1 (unbinding)

Good luck,
 --Alex 

> On 27. Jul 2021, at 08:22, ShaoFeng Shi  wrote:
> 
> +1 (binding)
> 
> Linkis is a good open-source tool and integrates well with many Apache big
> data projects. Adding it to the incubator will help more people find it and
> improve their data platform management.
> 
> Best regards,
> 
> Shaofeng Shi 史少锋
> Apache Kylin PMC
> Email: shaofeng...@apache.org
> 
> Apache Kylin FAQ: https://kylin.apache.org/docs/gettingstarted/faq.html
> Join Kylin user mail group: user-subscr...@kylin.apache.org
> Join Kylin dev mail group: dev-subscr...@kylin.apache.org
> 
> 
> 
> David Dai  于2021年7月27日周二 下午12:31写道：
> 
>> +1
>> 
>> Linkis builds a computation middleware layer to reduce the difficulty for
>> users to use multiple compute engines, and it seems that they have built a
>> community around Links
>> I'd like to see Links enter the Apache incubator for better development
>> 
>> 
>> 
>> Best Regards
>> 
>> 
>> 
>> ---
>> Apache DolphinScheduler PMC Chair
>> David Dai
>> lidong...@apache.org
>> Linkedin: https://www.linkedin.com/in/dailidong
>> Twitter: @WorkflowEasy 
>> ---
>> 
>> 
>> On Tue, Jul 27, 2021 at 10:37 AM 张铎(Duo Zhang) 
>> wrote:
>> 
>>> +1
>>> 
>>> Wei-Chiu Chuang  于2021年7月27日周二 上午10:22写道：
 
 +1 (binding)
 
 Quickly glance through the project doc and looks like it's an active
 community already.
 
 The Apache Livy (incubating) is a similar project offering REST API for
 Spark. HBase has REST API through its Thrift server. Hadoop has YARN
>> REST
 API and WebHDFS REST API.
 But an unified REST API service for many data systems is necessary,
>>> because
 those who invest heavily in these Open Source projects tend to use many
>>> of
 these systems together, not just one.
 
 On Mon, Jul 26, 2021 at 11:12 PM 俊平堵  wrote:
 
> Dear all,
> 
> 
> Following up the [DISCUSS] thread on Linkis[1], I would like to call
>> a
> VOTE to accept Linkis into the Apache Incubator. Please cast your
> vote:
> 
>  [ ] +1, bring Linkis into the Incubator
>  [ ] +0, I don't care either way
>  [ ] -1, do not bring Linkis into the Incubator, because...
> 
> The vote will open for at least 72 hours. Only votes from the
> Incubator PMC are binding, but welcome for the votes from everyone.
> 
> Please check out the Linkis Proposal from the incubator wiki[2].
> [1]
> 
>>> 
>> https://lists.apache.org/thread.html/r5d3af665795ebd3028ca9978e92af5d650a43b6680470d16e43f3847%40%3Cgeneral.incubator.apache.org%3E
> [2]
>>> https://cwiki.apache.org/confluence/display/INCUBATOR/LinkisProposal
> 
> Regards,
> Junping Du
> 
>>> 
>>> -
>>> 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: [VOTE] Accept Kyuubi into the Apache Incubator

[Alexander Alten]

+1 (unbinding)

All the best :) 

> On 14. Jun 2021, at 16:09, KimmKing  wrote:
> 
> +1 
> 
> 
> 
> 
> 
> 
> 
> --
> 
> Kimm King(kimmk...@apache.org/kimmk...@163.com)
> Apache Dubbo PMC Member
> github: kimmking
> 
> 
> 
> 
> 
> At 2021-06-14 21:57:27, "Willem Jiang"  wrote:
>> Hi all,
>> 
>> Following up the [DISCUSS] thread on Kyuubi[1], I would like to call a
>> VOTE to accept Kyuubi into the Apache Incubator.
>> 
>> Please cast your vote:
>> 
>> [ ] +1, bring Kyuubi into the Incubator
>> [ ] +0, I don't care either way
>> [ ] -1, do not bring Kyuubi into the Incubator, because...
>> 
>> The vote will open at least for 72 hours, and only votes from the
>> Incubator PMC are binding, but votes from everyone are welcome.
>> 
>> Please check out the Kyuubi Proposal from the incubator wiki[2].
>> 
>> [1] 
>> https://lists.apache.org/thread.html/rbd3224354d80c495ddf604853a1d8153c422cdf8d154738d34a8b5e2%40%3Cgeneral.incubator.apache.org%3E
>> [2] https://cwiki.apache.org/confluence/display/INCUBATOR/KyuubiProposal
>> 
>> Regards,
>> 
>> Willem Jiang
>> 
>> Twitter: willemjiang
>> Weibo: 姜宁willem
>> 
>> -
>> 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: [DISCUSS] Incubating Proposal of Kyuubi

[Alexander Alten]

Hey,

Looks like an interesting project, competition to Starburst. How does it
compare to Apache Dremel?

 +1 (non-binding) for incubation.

Thanks and stay safe,
--alex

On Mon, May 31, 2021, 08:21 Kent Yao  wrote:

> Dear all,
>
> We want to propose Kyuubi as a new Apache Incubator project.
>
> Kyuubi is a distributed multi-tenant Thrift JDBC/ODBC server for
> large-scale data management, processing, and analytics, built on top
> of Apache Spark and designed to support more engines (i.e., Apache
> Flink). We are aiming to make Kyuubi an "out-of-the-box" tool for data
> warehouses and data lakes. Kyuubi concentrates on improving the
> experience for non-Spark users, making it easy for them to use Spark
> as a service and focus on business data of their own, not where it
> stores, how it computes. NetEase has open-sourced Kyuubi since 2018,
> https://github.com/NetEase/kyuubi.
>
> Many thanks to Willem Jiang (Champion), Jeff Zhang, Duo Zhang, Akira
> Ajisaka for being the mentors of the Kyuubi project and helping us set
> up this proposal. The proposal can be found at
> https://cwiki.apache.org/confluence/display/INCUBATOR/KyuubiProposal.
>
> Looking forward to your feedback and thank you very much.
>
> Best regards,
> Kent Yao
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Accept ShenYu into the Apache Incubator

[Alexander Alten-Lorenz]

+1 (unbinding) 

Good luck :)

Sent from my iPhone

> On 26. Apr 2021, at 15:21, Willem Jiang  wrote:
> 
> Hi all,
> 
> Following up the [DISCUSS] thread on ShenYu[1] I would like to call a
> VOTE to accept ShenYu Aka Soul into the Apache Incubator.
> 
> Please cast your vote:
> 
>  [ ] +1, bring ShenYu into the Incubator
>  [ ] +0, I don't care either way
>  [ ] -1, do not bring ShenYu into the Incubator, because...
> 
> The vote will open at least for 72 hours and only votes from the
> Incubator PMC are binding, but votes from everyone are welcome.
> 
> Please check out the ShenYu Proposal from the incubator wiki[2].
> 
> [1]https://lists.apache.org/thread.html/r2632d213ed45b72267bde1e9cbffc39430887c0cf36933389fc85521%40%3Cgeneral.incubator.apache.org%3E
> [2]https://cwiki.apache.org/confluence/display/INCUBATOR/ShenYuProposal
> 
> Regards，
> 
> Willem Jiang
> 
> Twitter: willemjiang
> Weibo: 姜宁willem
> 
> -
> 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: [DISCUSS] YunionCloud Proposal

[Alexander Alten-Lorenz]

Hi Jian,

We had the same problem with wayang (formerly rheem). You need to check the 
trademarks in section 9 of:
US, EU, India, CN

as well as github, bitbucked, web

We developed a gsheet with our champion to find a name which is able to 
trademark, and has some relation to our project. Please note, when your project 
graduate to an TLP, all this ™ issues come along. And later it’s a real large 
task with INFRA to rebrand / rename everything. So typically we love to see 
those issues solved in the incubation process. 

Stay safe,
—alex 

Sent from my iPhone

> On 14. Apr 2021, at 09:07, Jian Qiu  wrote:
> 
> Hi, Dave,
> 
> When we decide to donate project to Apache Incubator, we consider several
> candidate names and make a vote in our community, the results are
> as follows:
> 
> * YunionCloud - a cloud union of Clouds, 26 vote
> * UnioneCloud - to unify many clouds into One Cloud, 10 vote
> * OpenYunion -  open source Cloud Union, 5 vote
> * OpenMHCP - open source Multi/Hybrid Cloud Platform, 2 vote
> 
> So we decided to choose YunionCloud as the new name. But we did not
> realize it conflicted with our company domain name.
> 
> As you suggested, we would like to consider UnioneCloud as the project name.
> 
> Would you consider UnioneCloud an appropriate project name?
> 
> Many thanks,
> 
> Jian Qiu
> 
> Willem Jiang  于2021年4月14日周三 上午9:47写道：
> 
>> Hi Dave,
>> 
>> I understand your concern. Actually,  I had a long discussion with the
>> team about the project name, but I missed that the company's domain
>> name has a close relationship with the project name.
>> Now the development team is working on finding a new name for it.  We
>> will come back with a new project name for this proposal.
>> 
>> Regards,
>> 
>> Willem Jiang
>> 
>> Twitter: willemjiang
>> Weibo: 姜宁willem
>> 
>>> On Tue, Apr 13, 2021 at 1:26 PM Dave Fisher  wrote:
>>> 
>>> This looks like an interesting project.
>>> 
>>> My concern is that the donation comes from https://www.yunion.cn which
>> has a similar name to the podling and that might cause trademark confusion.
>>> 
>>> Regards,
>>> Dave
>>> 
 On Apr 11, 2021, at 9:40 PM, Jian Qiu  wrote:
 
 Dear all,
 
 We would like to propose YunionCloud as a new Apache Incubator project.
 
 YunionCloud is a unified multi-cloud/hybrid-cloud management platform.
>> It
 is an IaaS platform capable of managing on-premise resources, including
 virtual machines and BareMetals. Further, it is extended to manage
 resources from other cloud platforms, including public and private
>> cloud
 providers. It provides consistent APIs and Web UI to access
>> heterogeneous
 resources from multi-cloud/hybrid-cloud. The platform is implemented in
 Golang, portable and lightweight, and can be deployed in Kubernetes
 clusters.
 
 The proposal can be found at
 
>> https://cwiki.apache.org/confluence/display/INCUBATOR/YunionCloud++Proposal
 
 The project has been open-sourced since March 2019 at GitHub
 https://github.com/yunionio/yunioncloud
 
 The project used to be called OneCloud, but we are in the process of
 changing the name to YunionCloud to avoid potential trademark
>> conflicts.
 
 Many thanks to Willem Jiang as our champion and mentor to guide us to
>> set
 up this proposal. We still need 2-3 mentors to set us on the track. If
>> you
 are interested, please kindly let me know. Besides, we are eager to
>> hear
 any of your thoughts on this project.
 
 Looking forward to your feedback and thank you for your time.
 
 Best regards,
 
 Jian Qiu, Co-found of YunionCloud
 sword...@gmail.com
>>> 
>>> 
>>> -
>>> 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
>> 
>> 

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

Re: 回覆：Re: [DICUSS] Retire Samoa

[Alexander Alten-Lorenz]

The project looks dead since a while 
+1 for retirement (non-binding)

—Alex 

Sent from my iPhone

> On 11. Feb 2021, at 06:27, Liu Ted  wrote:
> 
> +1 for retirement.
> 
> Ted 
> 
>   在 2021 年 2月 月 11 日週四，時間：13:13 ， Ralph Goers  
> 寫道：   I don’t really see anything to discuss.
> 
> Ralph
> 
>> On Feb 10, 2021, at 7:22 PM, Justin Mclean  wrote:
>> 
>> Hi,
>> 
>> My message to the Samoa asking them to consider retirement got no response  
>> [1] so I this think it time to discuss their retirement. Are there any 
>> objections to returning the project?
>> 
>> Thanks,
>> Justin
>> 
>> 1. 
>> https://lists.apache.org/thread.html/rb513f7ba5cc5dd1ba9adbf9fe8dbbb52db40066f04a9fed9fd2f7293%40%3Cdev.samoa.apache.org%3E
>> -
>> 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
> 
> 

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

Re: [VOTE] Graduate Apache Daffodil to a top-level project

[Alexander Alten-Lorenz]

+1 non-binding 

Thanks,
—Alex 

Sent from my mobile 

> On 9. Feb 2021, at 23:03, Mike Beckerle  wrote:
> 
> Folks,
> 
> I would now call for people to please officially vote on this proposal.
> 
> This vote thread will be open for 72 hours - ending on Friday Feb 12,
> 5:15pm ET.US (UTC-5)
> 
> The discussion thread already contained votes (eleven +1, including 4
> binding, and no 0 or -1), and no negative discussion points, so I am
> incorporating that thread by reference here.
> 
> Discussion thread:
> https://lists.apache.org/thread.html/r1340f079a36ccc7498231eebbe9a5a0e69570f436d213fa665ca48c0%40%3Cgeneral.incubator.apache.org%3E
> 
> 
> The draft board proposal is below for your review. As you all know this is
> business boilerplate except for our project name, charter statement, the
> original PMC slate, and VP/Chairperson put forward.
> 
> 
> Regards,
> Mike Beckerle
> Daffodil PMC Chair Elect, Committer
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> *Establish the Apache Daffodil 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 an
> implementation of the Data Format Description Language (DFDL) used to
> convert between fixed format data and more readily processed forms such
> as XML or JSON.*
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> *NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Daffodil Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
> RESOLVED, that the Apache Daffodil Project be and hereby is responsible
> for the creation and maintenance of software related to an
> implementation of the Data Format Description Language (DFDL) used to
> convert between fixed format data and more readily processed forms such
> as XML or JSON; and be it further*
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> *RESOLVED, that the office of "Vice President, Apache Daffodil" 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 Daffodil
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache Daffodil
> Project; and be it further RESOLVED, that the persons listed
> immediately below be and hereby are appointed to serve as the initial
> members of the Apache Daffodil Project:*
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> *  * Brandon Sloane>  *
> Christofer Dutz   >  * Dave Fisher
>  >  * Dave Thompson
> >  * John Interrante
> >  * John Wass
> >  * Joshua Adams
> >  * Kevin Ratnasekera
> >  * Mike Beckerle
> >  * Steve Lawrence
> >  * Taylor Wise
> >  * Olabusayo Kilo
> >*
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> * NOW, THEREFORE, BE IT FURTHER RESOLVED, that Mike Beckerle be appointed
>  to the office of Vice President, Apache Daffodil, to serve in accordance
>with and subject to the direction of the Board of Directors and the
> Bylaws of the Foundation until death, resignation, retirement, removal
> or disqualification, or until a successor is appointed; and be it
> further RESOLVED, that the Apache Daffodil Project be and hereby is
> tasked with the migration and rationalization of the Apache Incubator
> Daffodil podling; and be it further RESOLVED, that all
> responsibilities pertaining to the Apache Incubator Daffodil podling
> encumbered upon the Apache Incubator PMC are hereafter discharged.*
> 
> 
> -

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

Re: [VOTE] Accept EventMesh into Apache Incubator

[Alexander Alten]

+1, non-binding,
looking forward

best,
 --alex

On Fri, Feb 5, 2021 at 11:05 AM vongosling  wrote:
>
> +1, binding
> Good luck ~
>
> Eason Chen  于2021年2月1日周一 下午2:44写道：
>
> > Hi,
> >
> > After the discussion of EventMesh proposal (discussion thread is here[1]),
> > I would like to call a VOTE to accept it into the Apache Incubator.
> >
> > Please cast your vote:
> >
> >   [ ] +1, bring EventMesh into Incubator
> >   [ ] +0, I don't care either way
> >   [ ] -1, do not bring EventMesh into Incubator, because...
> >
> > The vote will open at least for 72 hours and only votes from the Incubator
> > PMC are binding.
> >
> > The project's proposal is available at [2].
> >
> > [1]
> >
> > https://lists.apache.org/thread.html/rcb4bc1e5b4994d377aba4191737ff7c1f7e375fb9044cfbebe236e95%40%3Cgeneral.incubator.apache.org%3E
> > [2]https://cwiki.apache.org/confluence/display/INCUBATOR/EventMeshProposal
> >
>
>
> --
> Nothing is impossible

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

Re: [DISCUSS] Graduate Apache Daffodil to a top-level project

[Alexander Alten-Lorenz]

+1 non-binding. 

Apache Daffodil is a great addition the the ASF community and codebase, it’s 
active and in use. And I personally like it :) 

Thanks,
—Alex 

Sent from my iPhone

> On 4. Feb 2021, at 21:35, Dave Fisher  wrote:
> 
> Hi -
> 
> I’m +1 for Daffodil to go to TLP.
> 
> They have been active and operating in the Apache Way for a long time. They 
> participate in Apachecon.
> 
> Slowness was with Community Growth and they have managed to grow their 
> community in the last year.
> 
> Regards,
> Dave
> 
>> On Feb 4, 2021, at 11:01 AM, Mike Beckerle  wrote:
>> 
>> Incubator Folks,
>> 
>> We have completed a vote on our community list d...@daffodil.apache.org as
>> follows:
>> 
>> Vote Thread:
>> https://lists.apache.org/thread.html/r91af73ae28284945ffe881cea7877766213eaa405da21e233d85eb83%40%3Cdev.daffodil.apache.org%3E
>> 
>> In summary, we have all +1 votes including all 3 mentors.
>> 
>> Our maturity model can be reviewed here:
>> 
>> https://cwiki.apache.org/confluence/display/DAFFODIL/Apache+Daffodil+Maturity+Model+Assesment
>> 
>> If there is anyone in the IPMC that has any questions or concerns that
>> would block our ability to graduate, please bring these issues into this
>> discussion.
>> 
>> Unless there are issues that need to be resolved, this discussion will end
>> next Tuesday, Feb 8 2021. 5pm ET.US (UTC-5) (that is 72 hours of weekdays)
>> 
>> If this discussion produces a positive consensus or no objections, I will
>> proceed to a vote using lazy consensus
>> https://www.apache.org/foundation/voting.html.
>> 
>> Regards,
>> Mike Beckerle
>> Daffodil PPMC, Committer
> 
> 
> -
> 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: [DISCUSS] EventMesh Proposal

[Alexander Alten]

Hi,

Fully agree with Justin, we from Wayang had the same problem. We
renamed the project before we submitted the proposal, and we
documented everything.
I’d encourage you to find a name which is TM ready in the US, India,
CN and EU (if possible). You can’t graduate (or better it is unlikely)
if a project name is not protectable by the ASF. And changing the
whole INFRA after a podling is voted into the incubator is a huge
effort.

--alex

On Tue, Feb 2, 2021 at 9:52 AM Justin Mclean  wrote:
>
> Hi,
>
> On one hand we don’t have a policy that say you must have to have done a name 
> search before becoming a piddling, on the other changing a name does incur a 
> large community cost and Infra would prefer that podlings don’t change names. 
> Most podlings do the name search just before graduation. In a lot of cases it 
> fairly obvious there is not going to be an issue, with a generic name like 
> this it may be best to wait until the name is approved before calling the 
> results of the vote.
>
> Thanks,
> 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: [VOTE] Graduate Apache Ratis as TLP Project

[Alexander Alten-Lorenz]

+1 non-binding

Best,
—alex



> On 1. Feb 2021, at 09:14, Willem Jiang  wrote:
> 
> +1 binding.
> 
> Willem Jiang
> 
> Twitter: willemjiang
> Weibo: 姜宁willem
> 
> On Sat, Jan 30, 2021 at 4:32 AM Uma gangumalla  wrote:
>> 
>> Dear Incubator Community,
>> 
>> We have discussed Apache Ratis Podling graduation in the incubator general
>> DISCUSS thread[1] and We did not see any objections to proceed for voting.
>> Here is the official vote for graduating Apache Ratis project as TLP.
>> 
>> Please provide your in the following options:
>> [ ] +1 - Recommend graduation of Apache Ratis as a TLP
>> [ ]  0 - I don't feel strongly about it, but don't object
>> [ ] -1 - Do not recommend graduation of Apache Ratis because...
>> 
>> The VOTE will open for at least 72 hours.
>> 
>> Just to summarize again:
>> Apache Ratis project is a very active project and the community has grown
>> well by following the Apache way in the process. It produced several
>> releases by having diverse people as release managers. I and the community
>> strongly believe that it's ready for graduation.
>> 
>> The Apache Ratis project has been an Apache incubator project for nearly 3
>> year. Since then the community has grown and followed Apache Way. Some
>> highlights include:
>> * 7 releases given ( including 1.0.0 and 0.0.1 alpha ) by having
>> different people as release managers
>> * 50 contributors ( from report)
>> * 28 committers
>> * More than 1161 Jiras created, 905 resolved or closed
>> * > 293 pull requests in github
>> * One of the biggest positives for this community is that most of the
>> members in this community have a lot of experience in other Apache projects
>> already.
>> 
>> Some additional note about the resolution below:
>> The current PPMC will be transitioned to the PMC. We have invited some of
>> the mentors in the current PPMC who like to stay involved.
>> We are also adding Siddharth and Jie Wang into PMC as we believe they are
>> committed to the project and a good addition to PMC.
>> 
>> We have already voted for Ratis TLP in the Ratis Podling community. Please
>> find the voting threads for reference. Ratis PPMC DISCUSS thread: [2],
>> Ratis PPMC Vote: [3] and Ratis Community: [4]
>> 
>> To make easy for you to review, here is the *resolution text*[5] copied:
>> ==
>> Establish the Apache Ratis 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 java implementation for RAFT consensus protocol.
>> 
>> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
>> (PMC), to be known as the "Apache Ratis Project", be and hereby is
>> established pursuant to Bylaws of the Foundation; and be it further
>> 
>> RESOLVED, that the Apache Ratis Project be and hereby is responsible for
>> the creation and maintenance of software related to A java
>> implementation for RAFT consensus protocol; and be it further
>> 
>> RESOLVED, that the office of "Vice President, Apache Ratis" 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 Ratis
>> Project, and to have primary responsibility for management of the
>> projects within the scope of responsibility of the Apache Ratis Project;
>> and be it further
>> 
>> RESOLVED, that the persons listed immediately below be and hereby are
>> appointed to serve as the initial members of the Apache Ratis Project:
>> 
>> * Anu Engineer  [Hadoop, Ozone PMC,
>> Incubator Committer]
>> * Arpit Agarwal [ ASF Member, Hadoop, Ozone,
>> Incubator PMC]
>> * Enis Soztutar [ASF Member, Hadoop, HBase,
>> Incubator PMC and also PMC in curator, gora, phoenix]
>> * Hanisha Koneru[Hadoop, Ozone PMC,
>> Incubator Committer]
>> * Jie Wang  [Incubator, Ozone Committer]
>> * Jing Zhao [Hadoop PMC, Incubator Committer]
>> * Jitendra Nath Pandey   [ASF Member, Hadoop, Ozone,
>> Incubator PMC and also PMC in ambari, atlas, tez]
>> * Josh Elser [ASF Member, HBase, Incubator
>> PMC, and also PMC in accumulo, calcite, fluo, phoenix, rya]
>> * Lokesh Jain   [Hadoop, Ozone PMC, Incubator
>> Committer]
>> * Marton Elek[Hadoop, Ozone PMC, Incubator
>> Committer]
>> * Mingliang Liu  [Hadoop PMC, Incubator
>> Committer]
>> * Mukul Kumar Singh  [Hadoop, Ozone PMC, Incubator
>> Committer]
>> * Shashikant Banerjee   [Hadoop, Ozone PMC,
>> Incubator Committer]
>> * Siddharth Wagle[Ambari, Ozone PMC, Hadoop,
>> Incubator Committer]
>> * Tsz-wo Sze [ASF Member, Hadoop, Ozone
>> PMC, Incubator Committer]
>> * Uma Maheswara Rao G   [ASF Member, Hadoop, Ozone,
>> Incubator 

Re: [DISCUSS] Wayang Proposal

[Alexander Alten-Lorenz]

Hey JB,

On behalf of the Wayang team, we are happy to have you as a mentor and we
have already updated the proposal (thanks Chris!). Thanks JB :)

best,
 --alex

On Fri, Dec 11, 2020 at 4:50 PM Rodrigo Pardo Meza 
wrote:

> Hi Jean,
>
> Nice to meet you. Thanks for supporting Wayang proposal.
>
> You get my +1 to join in the mentoring team.
>
> Best regards!
>
> El vie, 11 dic 2020 a las 12:44, bertty contreras (<
> berttycontre...@gmail.com>) escribió:
>
> > Hi JB,
> >
> > It will be so nice that you join to wayang, you have my +1
> >
> > Best Regards,
> > Bertty
> >
> > El mié, 9 dic 2020 a las 11:02, Alexander Alten-Lorenz (<
> a...@scalytics.io
> > >)
> > escribió:
> >
> > > resent to the ML since Exim does not accept MIME Content-Type
> > > 'text/html' (#5.2.3)
> > >
> > > Hey JB,
> > >
> > > Wayang is  an intelligent scheduler to leverage multiple frameworks
> > > and is doing spills / tasks of an RRD by themselves, when this speed
> > > up the processing. We see us in the middle of Apache Spark, Apache
> > > Beam and Apache Nemo. Personally I see us more into Apache Flink, but
> > > with major advantages as described before. Our focus is more into AI /
> > > ML and the productionizing of models, helping data engineers to get
> > > the job with the right tool done in less time instead of always the
> > > same.
> > >
> > > For mentoring, you get my +1  Would be great to have you in the
> > > mentoring team!
> > >
> > > Best,
> > > --alex
> > >
> > >
> > > On Wed, Dec 9, 2020 at 2:58 PM Alexander Alten-Lorenz <
> a...@scalytics.io>
> > > wrote:
> > > >
> > > > Hey JB,
> > > >
> > > >
> > > >
> > > > Wayang is  an intelligent scheduler to leverage multiple frameworks
> and
> > > is doing spills / tasks of an RRD by themselves, when this speed up the
> > > processing. We see us in the middle of Apache Spark, Apache Beam and
> > Apache
> > > Nemo. Personally I see us more into Apache Flink, but with major
> > advantages
> > > as described before. Our focus is more into AI / ML and the
> > productionizing
> > > of models, helping data engineers to get the job with the right tool
> done
> > > in less time instead to use always the same.
> > > >
> > > >
> > > >
> > > > For mentoring, you get my +1 Would be great to have you in the
> > mentoring
> > > team!
> > > >
> > > >
> > > >
> > > > Best,
> > > >
> > > > --alex
> > > >
> > > >
> > > >
> > > > --
> > > >
> > > > Alexander Alten - Lorenz
> > > >
> > > > Chief Technology Officer
> > > >
> > > > Scalytics - Code once. Deploy on any cloud
> > > >
> > > >
> > > >
> > > > m:   alexan...@scalytics.io
> > > >
> > > > ln:   www.linkedin.com/in/alexanderalten/
> > > >
> > > > m:   +49 151 156 81561
> > > >
> > > >
> > > >
> > > > Scalytics, Inc.
> > > >
> > > > Web: scalytics.io
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > From: Jean-Baptiste Onofre
> > > > Sent: Wednesday, December 9, 2020 2:48 PM
> > > > To: general@incubator.apache.org
> > > > Cc: Alexander Alten-Lorenz; Rodrigo Pardo Meza
> > > > Subject: Re: [DISCUSS] Wayang Proposal
> > > >
> > > >
> > > >
> > > > Hi,
> > > >
> > > >
> > > >
> > > > As it seems a bit close to Apache Beam, I would be interested by
> follow
> > > and/or mentor the project.
> > > >
> > > >
> > > >
> > > > Please let me know if you want an additional mentor on this podling.
> > > >
> > > >
> > > >
> > > > By the way, what’s Wayang position regarding Apache Beam and Apache
> > Nemo
> > > ?
> > > >
> > > >
> > > >
> > > > Regards
> > > >
> > > > JB
> > > >
> > > >
> > > >
> > > > > Le 6 déc. 2020 à 12:13, Christofer Dutz  >
> > a
> >

Re: [VOTE] Accept Wayang into the Apache Incubator

[Alexander Alten-Lorenz]

neous Developers **
> > >
> > > The initial committers are already geographically distributed among
> > Chile, Germany, and Qatar. During incubation, one of our main goals is to
> > increase the heterogeneity of the current community and we will work hard
> > to achieve it.
> > >
> > > ** Reliance on salaried developers **
> > >
> > > Wayang is already being developed by a mix of full time and volunteer
> > time. Only 2 of the initial committers are working full time on this
> > project (Scalytics). So, we are confident that the project will not
> > decrease its development pace. Furthermore, we are committed to recruit
> > additional committers to significantly increase the development pace of the
> > project.
> > >
> > > ** Relationships with other Apache products **
> > >
> > > Wayang is somehow related to Apache Spark as its developing interface is
> > inspired from Spark. In contrast to Spark, Wayang is not a data processing
> > platform, but a mediator between user applications and data processing
> > platforms. In this sense, Wayang is similar to the Apache Drill project,
> > and Apache Beam. However, Wayang significantly differs from Apache Drill in
> > two main aspects. First, Apache Drill provides only a common interface to
> > query multiple data storages and hence users have to specify in their query
> > the data to fetch. Then, Apache Drill translates the query to the
> > processing platforms where the data is stored, e.g. into mongoDB query
> > representation. In contrast, in Wayang, users only specify the data path
> > and Wayang decides which are the best (performance-wise) data processing
> > platforms to use to process such data. Second, the query interface in
> > Apache Drill is SQL. Wayang uses an interface based on operators forming
> > DAGs. In this latter point, we are currently developing a PIGLatin-like
> > query language for Wayang. In addition, in contrast to Apache Beam, Wayang
> > not only allows users to use multiple data processing platforms at the same
> > time, but also it provides an optimizer to choose the most efficient
> > platform for the task at hand. In Apache Beam, users have to specify an
> > appropriate runner (platform).
> > > Given these similarities with the two Apache projects mentioned above,
> > we are looking forward to collaborating with those communities. Still, we
> > are open and would also love to collaborate with other Apache communities
> > as well.
> > > ** An excessive fascination with the Apache Brand **
> > >
> > > Wayang solves a real problem that currently users and developers have to
> > deal with at a high cost: monetary cost, high design and development
> > efforts, and very time consuming. Therefore, we believe that Wayang can be
> > successful in building a large community around it. We are convinced that
> > the Apache brand and community process will significantly help us in
> > building such a community and to establish the project in the long-term. We
> > simply believe that ASF is the right home for Wayang to achieve this.
> > >
> > > === Documentation ===
> > >
> > > Further details, documentation, and publications related to Wayang can
> > be found at https://docs.rheem.io/rheem/
> > >
> > > === Initial Source ===
> > >
> > > The current source code of Wayang resides in Github:
> > > https://github.com/rheem-ecosystem/rheem
> > >
> > > === External Dependencies ===
> > >
> > > Wayang depends on the following Apache projects:
> > >
> > > * Maven
> > > * HDFS
> > > * Hadoop
> > > * Spark
> > >
> > > Wayang depends on the following other open source projects organized by
> > license:
> > >
> > > org.json.json: Json (http://json.org/license.html)
> > > SnakeYAML: Apache 2.0
> > > Java Unified Expression Language API (Juel): Apache 2.0
> > > ProfileDB Instrumentation: Apache 2.0
> > > Gson: Apache 2.0
> > > Hadoop: Apache 2.0
> > > Scala: Apache 2.0
> > > Antlr 4: BSD
> > > Jackson: Apache 2.0
> > > Junit 5: EPL 2.0
> > > Mockito: MIT
> > > Assertj: Apache 2.0
> > > logback-classic: EPL 1.0 LGPL 2.1
> > > slf4j: MIT
> > > GNU Trove: LGPL 2.1
> > > graphchi: Apache 2.0
> > > SQLite JDBC: Apache 2.0
> > > PostgreSQL: BSD 2-clause
> > > jcommander: Apache 2.0
> > > Koloboke Collections API: Apach

Re: [DISCUSS] Wayang Proposal

[Alexander Alten-Lorenz]

resent to the ML since Exim does not accept MIME Content-Type
'text/html' (#5.2.3)

Hey JB,

Wayang is  an intelligent scheduler to leverage multiple frameworks
and is doing spills / tasks of an RRD by themselves, when this speed
up the processing. We see us in the middle of Apache Spark, Apache
Beam and Apache Nemo. Personally I see us more into Apache Flink, but
with major advantages as described before. Our focus is more into AI /
ML and the productionizing of models, helping data engineers to get
the job with the right tool done in less time instead of always the
same.

For mentoring, you get my +1  Would be great to have you in the
mentoring team!

Best,
--alex


On Wed, Dec 9, 2020 at 2:58 PM Alexander Alten-Lorenz  wrote:
>
> Hey JB,
>
>
>
> Wayang is  an intelligent scheduler to leverage multiple frameworks and is 
> doing spills / tasks of an RRD by themselves, when this speed up the 
> processing. We see us in the middle of Apache Spark, Apache Beam and Apache 
> Nemo. Personally I see us more into Apache Flink, but with major advantages 
> as described before. Our focus is more into AI / ML and the productionizing 
> of models, helping data engineers to get the job with the right tool done in 
> less time instead to use always the same.
>
>
>
> For mentoring, you get my +1 Would be great to have you in the mentoring team!
>
>
>
> Best,
>
> --alex
>
>
>
> --
>
> Alexander Alten - Lorenz
>
> Chief Technology Officer
>
> Scalytics - Code once. Deploy on any cloud
>
>
>
> m:   alexan...@scalytics.io
>
> ln:   www.linkedin.com/in/alexanderalten/
>
> m:   +49 151 156 81561
>
>
>
> Scalytics, Inc.
>
> Web: scalytics.io
>
>
>
>
>
> From: Jean-Baptiste Onofre
> Sent: Wednesday, December 9, 2020 2:48 PM
> To: general@incubator.apache.org
> Cc: Alexander Alten-Lorenz; Rodrigo Pardo Meza
> Subject: Re: [DISCUSS] Wayang Proposal
>
>
>
> Hi,
>
>
>
> As it seems a bit close to Apache Beam, I would be interested by follow 
> and/or mentor the project.
>
>
>
> Please let me know if you want an additional mentor on this podling.
>
>
>
> By the way, what’s Wayang position regarding Apache Beam and Apache Nemo ?
>
>
>
> Regards
>
> JB
>
>
>
> > Le 6 déc. 2020 à 12:13, Christofer Dutz  a écrit 
> > :
>
> >
>
> > Hi and welcome on this new communication channel.
>
> >
>
> > I'd like to add, that I really liked how the project approached me and how 
> > they reacted when I told them the old project name Rheem would probably not 
> > go down well and that I would suggest changing the name.
>
> >
>
> > I gave them some tips what things are important for Apache and what we lay 
> > emphasis on and the team started brainstorming and doing all the trademark 
> > checks, taking options off the list where problems could be expected.
>
> >
>
> > So, upon acceptance here, the project would do the renaming together with 
> > the groupId and package changing, which would be required anyway.
>
> >
>
> > Right now, there are 3 people signed up as mentors, however knowing that 
> > not always are all mentors available at every given time, it would be cool 
> > if we could find 1-2 more to help out.
>
> >
>
> >
>
> > Chris
>
> >
>
> >
>
> >
>
> > -Ursprüngliche Nachricht-
>
> > Von: Bertty Contreras 
>
> > Gesendet: Freitag, 4. Dezember 2020 17:16
>
> > An: general@incubator.apache.org
>
> > Cc: Alexander Alten-Lorenz ; Rodrigo Pardo Meza 
> > 
>
> > Betreff: [DISCUSS] Wayang Proposal
>
> >
>
> > Dear all,
>
> >
>
> > Rodrigo and Bertty, Senior Software Engineers at Scalytics, are two of the 
> > main developers of the Wayang system. We write to you because we would like 
> > to bring your attention to our Proposal for Incubation in the Apache 
> > foundation at 
> > https://cwiki.apache.org/confluence/display/INCUBATOR/WayangProposal
>
> >
>
> > Please note that Wayang was named Rheem before, but we had to rename the 
> > project because of trademark issues.
>
> > You can find the original project web page at:
>
> > https://rheem-ecosystem.github.io/
>
> >
>
> > Best,
>
> > Bertty
>
> >
>
> > -
>
> > 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: [VOTE] Graduate HCatalog from the incubator and become part of Hive

[Alexander Alten-Lorenz]

+1, non-binding

- Alex

On Feb 5, 2013, at 10:06 AM, Sushanth Sowmyan khorg...@gmail.com wrote:

 And my axe! Erm... I mean, my +1.
 
 
 On Mon, Feb 4, 2013 at 10:18 PM, Alan Gates ga...@hortonworks.com wrote:
 FYI.
 
 Alan.
 
 Begin forwarded message:
 
 From: Alan Gates ga...@hortonworks.com
 Date: February 4, 2013 10:18:09 PM PST
 To: hcatalog-...@incubator.apache.org
 Subject: [VOTE] Graduate HCatalog from the incubator and become part of Hive
 
 The Hive PMC has voted to accept HCatalog as a submodule of Hive.  You can 
 see the vote thread at 
 http://mail-archives.apache.org/mod_mbox/hive-dev/201301.mbox/%3cCACf6RrzktBYD0suZxn3Pfv8XkR=vgwszrzyb_2qvesuj2vh...@mail.gmail.com%3e
  .  We now need to vote to graduate from the incubator and become a 
 submodule of Hive.  This entails the following:
 
 1) the establishment of an HCatalog submodule in the Apache Hive Project;
 2) the adoption of the Apache HCatalog codebase into the Hive HCatalog 
 submodule; and
 3) adding all currently active HCatalog committers as submodule committers 
 on the Hive HCatalog submodule.
 
 Definitions for all these can be found in the (now adopted) Hive bylaws at 
 https://cwiki.apache.org/confluence/display/Hive/Proposed+Changes+to+Hive+Bylaws+for+Submodule+Committer.
 
 This vote will stay open for at least 72 hours (thus 23:00 PST on 2/7/13).  
 PPMC members votes are binding in this vote, though input from all is 
 welcome.
 
 If this vote passes the next step will be to submit the graduation motion 
 to the Incubator PMC.
 
 Here's my +1.
 
 Alan.
 

--
Alexander Alten-Lorenz
http://mapredit.blogspot.com
German Hadoop LinkedIn Group: http://goo.gl/N8pCF


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