> https://github.com/apache/incubator-fury/pull/1574/commits/2ac9d808af75d17c0ea74a9755fe165b13de15f2
>
> That is, keep the first and most prominent uses in form "Apache Foo
> (incubating)" and add a hyperlink to "incubating" to the DISCLAIMER. This
> should be a shorter solution and at least as g
On the one hand, we release sources. We should ensure that the source code
is released (on our platform), or else the pivotal character "open source"
is challenged.
On the other hand, library users do always "download" the software with a
dependency manager, and thus, a heavy download page may nev
Here is a new situation for projects that may not carry source releases
heavily: [1]
[1] https://github.com/apache/datafusion/pull/10233/files#r1579895024
They may not even maintain a download page, but just leverage
https://downloads.apache.org/.
I suggest we rethink the form of distribution an
hi tison:
Thanks very much for your thorough checking work. You even found such a
minor issue as the version number mismatch in the README.md file, We have
created an issues[1] to tracking DISCLAIMER and README.md issue
[1] https://github.com/apache/incubator-streampark/issues/3680
> This is n
On Thu, 25 Apr 2024 at 16:56, tison wrote:
>
> Thanks for your explanation and good catch. I sent [1] to improve the case
> here and it should be resolved now.
>
> [1] https://github.com/apache/incubator-streampark-website/pull/351
>
> To search other pages, perhaps you can try to read the /sitema
Hi Willem,
Good point. I suppose the current incubator- prefix doesn't give more
information than the "incubator" words itself.
Thus, trying to merge the inputs above, I made a third candidate:
*
https://github.com/apache/incubator-fury/pull/1574/commits/2ac9d808af75d17c0ea74a9755fe165b13de15f2
Thanks for your explanation and good catch. I sent [1] to improve the case
here and it should be resolved now.
[1] https://github.com/apache/incubator-streampark-website/pull/351
To search other pages, perhaps you can try to read the /sitemap.xml file to
find pages. Although I can see some hidden
On Thu, 25 Apr 2024 at 15:18, tison wrote:
>
> > The array is a list of pages in which the disclaimer could not be found.
>
> I do a quick check for the podlings I'm familiar with:
>
> For StreamPark, it reports:
>"disclaimers": [
> 14,
> [
> "https://streampark.incubator.a
> The array is a list of pages in which the disclaimer could not be found.
I do a quick check for the podlings I'm familiar with:
For StreamPark, it reports:
"disclaimers": [
14,
[
"https://streampark.incubator.apache.org/team";,
"https://streampark.incubator.apache
On Wed, 24 Apr 2024 at 13:05, tison wrote:
>
> Hi Sebb,
>
> > quite a few podlings where the text is only present on some of the web
> pages
>
> [1] you refers writes:
>
> >> Podling web sites MUST include a clear disclaimer on their website
>
> So, IMO it's clear that every page should contain su
Hi,
This is mainly for IPMC members. But I think it's suitable to discuss
publicly also.
I suggest we actively give positive feedback on podlings making progress on
improving themselves.
We're all volunteers. TBH, most IPMC members do not participate in the
development of podling too much. So, i
+1 binding with a few suggestions.
I checked:
* Download links valid.
* Signature and checksum match.
* LICENSE, NOTICE and DISCLAIMER are included in both source and binary
releases. The content looks good to me.
* No binary files in the source release
Below are two suggestions:
1. You may eva
Hi,
The release for Apache Fury(incubating) v0.5.0-rc3 is canceled.
We didn't include the benchmark code in the source release, but the
LICENSE file did contain the reference to benchmark code.
This has been fixed in [1]
1. https://github.com/apache/incubator-fury/pull/1562
We will propose a ne
Hi tison,
My previous reply is a little confusing. What the "we don't release furyjs
in 0.5.0" means
is that we don't upload release bundles to npm in this release.
Best,
Chaokun Yang
On Thu, Apr 25, 2024 at 5:36 PM tison wrote:
> Let me first summarize the result of the feedback on LICENSE is
Let me first summarize the result of the feedback on LICENSE issues:
> - there are several references to a benchmark directory, but it is not
included in the release
This is correct. We made [10] to address it. And We're preparing a new
release candidate.
[10] https://github.com/apache/incubator
> close this vote and start a new release candidate later.
There is no blocker to cancel this vote now. You can test the new release
packaging logics correctly exclude benchmark license info and we're ready
to make the next RC.
To cancel a vote. You can send a reply to this thread with a replaced
Hi tison,
Thanks for the suggestion, we don't release furyjs in 0.5.0.
We can cooperate with OpenSumi after we make the first formal release of
furyjs
under ASF later.
Best,
Chaokun
On Thu, Apr 25, 2024 at 5:11 PM tison wrote:
> Hi Shawn,
>
> Thanks for sharing the finding. I can see the depe
Hi Shawn,
Thanks for sharing the finding. I can see the dependency from OpenSumi to
Fury as in [1] now.
[1] https://github.com/search?q=repo:opensumi/core%20fury&type=code
After we make the first formal release, we can cooperate with OpenSumi to
upgrade to an incubating release and thus update t
Hi Justin,
Thanks for sharing this tool. I checked the code in Fury with this tool.
Here is the result:
1) [5][6] are osscan results.
2) Those files has duplication with package/lib/worker-host.js in
opensumi[7]
Opensumi relies on furyjs, so it packaged the code in apache fury into its
release b
Just have a comment on the Github repo descriptions of Incubating projects:
" We need to have word of (Incubating) in the repo description."
It can be updated by editing the file of .asf.yaml in the repo.
Willem Jiang
On Tue, Apr 23, 2024 at 9:23 AM tison wrote:
>
> Hi,
>
> Recently, the new ad
Hello Incubator Community:
This is a call for a vote to release Apache StreamPark(Incubating) version
2.1.4-RC1.
The Apache StreamPark community has voted on and approved a proposal to
release Apache StreamPark(Incubating) version 2.1.4-RC1.
We now kindly request the Incubator PMC members review a
21 matches
Mail list logo
