To preview the render result I made
https://github.com/apache/incubator-fury/pull/1574 to showcase.
You can head to
https://github.com/apache/incubator-fury/tree/tisonkun-patch-1 to see the
render version. I made two candidates:
1. Inline the DISCLAIMER with an IMPORTANT callout
2. Add a badge wi
Hi Justin,
Thank you, and that's not in a hurry. I'd just like to make the status
clear and ensure we can make progress instead of subjective arguing.
Now I know you use ScanOSS and I'd suggest other members in Fury try to
check the project with this tool. I'll try it out if I find some time, and
Hi,
> 4. To clarify that a repo belongs to a podling, introduce a guideline or
> policy to help PPMCs include the DISCLAIMER in the README of all their
> repos.
Alternatively, perhaps we can come up with something a little shorter shorter
that points to DISCLAIMER? What is important is that the
HI,
I’m happy to share it, but as I said, I'm travelling right now and don't have
access. I used ScanOSS workbench, but there are other checkers out there. And
yes, tools like this can sometimes give false positives, and it can sometimes
be unclear where things were originally copied or, in fac
Hi,
Recently I made two patches to improve the content of StreamPark website:
* https://github.com/apache/incubator-streampark-website/pull/347
* https://github.com/apache/incubator-streampark-website/pull/349
They should showcase several common mistakes and less-than-awesome we can
improve:
1.
> For Go based projects dropping the incubator reference in the git repo
makes things easier also when graduating
I support this statement. For Java or Rust release, we generally don't
include the incubator prefix in dep ID. But Golang dependency relies on the
name of the GitHub repository. So it
> Of course we'd like to add the license info
As you can see, for files we're clear that is derived, we keep their
license headers, and add a link to the origin.
[1]
https://github.com/apache/incubator-fury/blob/dd9f9128d24b418f6a420880c7780ce83d6448a2/licenserc.toml#L28-L54
So what I'm confused
On Thu, Apr 25, 2024 at 10:36 AM Justin Mclean
wrote:
> Hi,
>
> I’m currently travelling and may be slow in responding to emails.
>
> > The MemoryBufferWritableChannel[5] and MockWritableChannel[6] was
> written
> > by me before we open-sourced Fury and
> > I submitted it to Ray in PR[8] ,which
> That should be fine, but having an ASF header on the files may be a
little misleading? What do you think?
Could you elaborate a bit on "misleading"? Shawn owned the code and he
contributed the code under Apache License 2.0, and also he has filed an
iCLA. So it follows the headers write:
Licens
> It certainly looks like some code was copied; one file, for instance, is
about 70% the same. This is not an issue as it is under a compatible MIT
license, but that needs to be mentioned in the LICENSE file.
Could you please tell the file name and the file on OpenSumi that is
overlapped? Of cours
Hi,
I would be for requiring the incubator disclaimer text in the project's README:
"Apache FOO is an effort undergoing incubation at The Apache Software
Foundation (ASF), sponsored by the Apache Incubator. Incubation is required of
all newly accepted projects until a further review indicates th
Hi,
Thank you very much for the guidance from our mentors.
We have updated the download page: https://devlake.apache.org/download
Best,
Zikuan An
Zikuan An 于2024年4月24日周三 12:41写道：
> Hi Willem,
>
>
> Thank you so much for taking the time to review the download links on the
> DevLake website and
Hi,
I’m currently travelling and may be slow in responding to emails.
> The MemoryBufferWritableChannel[5] and MockWritableChannel[6] was written
> by me before we open-sourced Fury and
> I submitted it to Ray in PR[8] ,which was planned to optimize zero-copy
> serialization in Ray. I think it's
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
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]
>
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://github.com/apache/opendal/blob/main/.github/workflows/release_python.yml#L114-L139
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
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 such info (typically as
part of the footer). If you find any pod
Thanks for your participation!
For people who support drop the incubator- prefix, please describe you
opinion on:
> 3. It's still significant to make it clear that a podling is in the
incubating status and thus a DISCLAIMER to protect the ASF branding.
> I'd propose to add the "incubating" words
Since it's valid that the LICENSE content to benchmark is redundant, I
suggest we cancel this RC and start a new RC.
In order to resolve the other potential compliance issues before the
next RC is out, I'd appreciate if Justin can confirm that the reply above
is clear, that is:
* 5-6 is authored
My understanding is that the Incubator disclaimer text [1] should be
present on all website pages and in announcement emails, so consumers
are clear about the status of the software.
However there are quite a few podlings where the text is only present
on some of the web pages, and most announce e
Hi Sebb,
The published install page[1] should look good now, could you check it
again?
1. https://fury.apache.org/docs/start/install
Best Regards,
Chaoun Yang
On Wed, Apr 24, 2024 at 3:44 PM sebb wrote:
> On Wed, 24 Apr 2024 at 08:29, Shawn Yang wrote:
> >
> > Hi Sebb,
> >
> > I hi
On Wed, 24 Apr 2024 at 08:29, Shawn Yang wrote:
>
> Hi Sebb,
>
> I highlight that the current release is not an asf release in the install
> page in PR https://github.com/apache/incubator-fury-site/pull/113.
>
> Could you take a look at it again?
I have just looked at the PR you just raised, and
Hi Sebb,
I highlight that the current release is not an asf release in the install
page in PR https://github.com/apache/incubator-fury-site/pull/113.
Could you take a look at it again?
Thanks for taking time to review Fury's release.
Best regards,
Chaokun Yang
On Wed, Apr 24, 2024 at 3:20 PM s
There is now a link to a potential download page, which is great.
However, the install page does not make it obvious that the 0.4.1
release is not an ASF release.
That information should be shown prominently at the start of the page,
not buried in a note near the end.
On Tue, 23 Apr 2024 at 16:07
25 matches
Mail list logo
