Re: [DISCUSS] Incubating Proposal for StreamPark

2022-08-25 Thread benjobs
Hi Justin, > How will the existing web site and domain be managed? 1) this website projects will be donated to apache, it has been stated that in Proposal [1] 2) I applied for this domain, and I manage and control it, Currently used to provide official websites and documents, I will cooperate wi

Re: [DISCUSS] Incubating Proposal for StreamPark

2022-08-25 Thread Justin Mclean
HI, How will the existing web site and domain be managed? [1] Kind Regards, Justin 1. http://www.streamxhub.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@in

Re: [DISCUSS] Incubating Proposal for StreamPark

2022-08-25 Thread benjobs
Hi Justin, we already know that some category-X class dependencies in StreamPark has risk. We had create an issue[1] to track this. and category-X dependencies list have been updated in Proposal [2], this issue planned to be solved in future releases, until the requirements are fully met. [1] h

Re: [DISCUSS] Incubating Proposal for StreamPark

2022-08-25 Thread Justin Mclean
HI, To be clear, this doesn’t need to be solved right now, but the project needs a plan to resolve these issues. i.e. replace the dependencies or some other action. What is decided may also impact your first ASF release and how long it takes to do that. Kind Regards, Justin ---

Re: [DISCUSS] Incubating Proposal for StreamPark

2022-08-25 Thread Cheng Pan
> Please note that Cheng Pan's comment is their own question, which isn't > associated with StreamPark's situation. @tison, I just make the mysql connector license issue clear, it helps the StreamPark team to make decisions about how to resolve the issue. > 1) in kafka connector of streampark spa

Re: [DISCUSS] Incubating Proposal for StreamPark

2022-08-25 Thread Justin Mclean
Hi, > As @benjobs replied in > https://lists.apache.org/thread/ql5k7j72p2s6hrw6clgpbwp4kmznj1b8, is the > category X issue resolved? I can see that MySQL isn't a hard dependency to > deliver the platform. No it has not, just because it’s not a hard dependancy doesn’t resolve the issue. And also

Re: [DISCUSS] Incubating Proposal for StreamPark

2022-08-25 Thread tison
> How about simply changing to Postgres? There is an ongoing issue as mentioned above https://github.com/streamxhub/streampark/issues/1447. @Cheng Pan If you'd like to discuss more on dependencies policy, you can start a dedicated thread. @Justin & @Calvin Please note that Cheng Pan's comment is

Re: [DISCUSS] Incubating Proposal for StreamPark

2022-08-25 Thread Christofer Dutz
How about simply changing to Postgres? I wouldn't expect StreamPark to depend on some MySQL special features. Simply changing to Postgres should probably resolve the problem, right? Chris On 25.08.22, 08:43, "Calvin Kirs" wrote: Yes, this is consistent with what Justin said. If he is optio

Re: [DISCUSS] Incubating Proposal for StreamPark

2022-08-25 Thread Cheng Pan
Thanks for the clarification. Thanks, Cheng Pan On Thu, Aug 25, 2022 at 4:27 PM Justin Mclean wrote: > > Hi, > > > 1. the project hardly depends on mysql-connector, w/o mysql-connector, > > the project can not work totally. > > This would not be allowed (IMO). > > > 2. some optional functionalit

Re: [DISCUSS] Incubating Proposal for StreamPark

2022-08-25 Thread Justin Mclean
Hi, > 1. the project hardly depends on mysql-connector, w/o mysql-connector, > the project can not work totally. This would not be allowed (IMO). > 2. some optional functionalities of the project require > mysql-connector, w/o mysql-connector, the project still works. This might be OK, but woul

Re: [DISCUSS] Incubating Proposal for StreamPark

2022-08-25 Thread Justin Mclean
Hi, > I would like to learn why mysql-connector is not compatible with the Apache > license? Short version it’s GPL and the “FOSS exception” license is no longer valid. Even it it was it (from my reading) it places a restriction on software that it can only be used with open source software.