Re: [VOTE] Release Apache XTable (Incubating) 0.1.0-incubating

[Justin Mclean]

Hi,

> Thanks for sharing LEGAL-469 Justin. I have seen it at some point but
> as time passed I forgot its existence.
> 
> The DISCLAIMER-WIP contains the following snippet:
> Some of the incubating project’s releases may not be fully compliant
> with ASF policy. For example, releases may have incomplete or
> un-reviewed licensing conditions. What follows is a list of issues the
> project is currently aware of (this list is likely to be incomplete):
> List of known issues goes here
> 
> I didn't perform a thorough license check cause it was implied by the
> disclaimer that this rather OK for this type of release. If we need to
> check for all licenses involved then I don't see much point in having
> this WIP file.

As the WIP disclaimer states, "List of known issues goes here”, so you need to 
know (in general) what the issues are, particularly if they are Category X 
related the users need to be aware of those. It doesn't need to be perfect, as 
it's an incubating project, but you should still do a basic check.

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

Re: [ANNOUNCE] Release Apache Gravitino (incubating) 0.6.0

[Justin Mclean]

Hi,

> Maybe you could label the link just a bit different so people don't think 
> that it is a download link.

It is the download link, as all downloads going via closer.lua links do this 
and are required by [1]. I’ve added some text to the page to remind people to 
follow the instructions and verify the release before using it.

Kind Regards,
Justin

1. https://infra.apache.org/release-download-pages.html#links

Re: [ANNOUNCE] Release Apache Gravitino (incubating) 0.6.0

[Justin Mclean]

HI,

> Could you please update your downloads page with instructions (or a link to 
> instructions) on how to verify the release?

If you click on the source release, you will get instructions on how to verify 
the release.

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 XTable (Incubating) 0.1.0-incubating

[Justin Mclean]

Hi,

While we have had some previous incubating projects use the WIP DISCLAIMER and 
not have complete LICENSE and NOTICE information, that was not the original 
intent.

From [1]

Blocker - must be fixed and and revoted on:
- 3rd party Category X or Category B bundled code licenses not listed in LICENSE

Kind Regards,
Justin

1. https://issues.apache.org/jira/browse/LEGAL-469
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Answer(Incubating) v1.4.0-RC1

[Justin Mclean]

Hi,
> 
> On Docker Hub, you have a 1.4.0-RC1 image.
> https://hub.docker.com/r/apache/answer/tags
> 
> I don't think you should be making Docker images available for
> 1.4.0-RC1 until the release vote is passed.

As per [1] it is fine as long as it is clearly marked.

Kind Regards,
Justin

1. https://incubator.apache.org/guides/distribution.html

Re: [VOTE] Release Apache Answer(Incubating) v1.4.0-RC1

[Justin Mclean]

Hi,

+1 jmclean (IPMC/PPMC) carried over from the dev list.

Kind Regards,
Justin

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

Re: Proposal: Recording votes in podlings

[Justin Mclean]

Hi,

+1 It sounds like a good idea to me.

Justin

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

Re: [VOTE] Accept Polaris into the ASF Incubator

[Justin Mclean]

+1 (binding)

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

Re: [DISCUSS] PolarisProposal to the incubator

[Justin Mclean]

Hi,

My issue is not that this is a single-vendor project or that people have been 
recognised for non-code contributions - both are fine. I would suggest that the 
project slims down the initial committer list and not split it into PPMC and 
committers. As part of the incubating process, you can vote in new committers 
and PPMC members for their contributions.

Kind Regards,
Justin

> On 2 Aug 2024, at 3:33 am, Jean-Baptiste Onofré  wrote:
> 
> Hi Dave,
> 
> Thanks for your message.
> 
> I'm a bit confused now: it seems that we have a consensus that the
> Polaris proposal is solid and correct (according to the number of
> positive feedback in this discussion so far).
> 
> Justin expressed concerns, asking to update the proposal. As said, I
> understand the comment, and would be happy to change the proposal.
> 
> Who's having the same concern and request to change the proposal ?
> Should we move forward to a vote with the current proposal as Dave proposed ?
> 
> I don't want to frustrate anyone here. I have the feeling that if I
> don't change the proposal, at least Justin would not be happy, and, on
> the other hand, if I change the proposal, others would not be happy.
> So, I'm open to suggestions.
> 
> I think the Polaris proposal is solid, the contributions (code and non
> code) are there, the community is small but eager to grow (and that's
> the purpose of the incubator).
> 
> Regards
> JB
> 
> 
> On Thu, Aug 1, 2024 at 6:39 PM Dave Fisher  wrote:
>> 
>> Hi Justin,
>> 
>>> In short, this seems to me (and I could be wrong) like a project mostly 
>>> from a single vendor, but the proposal has been made to make it look like 
>>> more people are involved. It may well be that these people will be 
>>> involved, but I’d prefer if the project was upfront about this and added 
>>> committers the usual way during incubation.
>> 
>> When and where should a “single vendor” collaborate on a common code 
>> project? If we block “single vendor” projects from Incubation then it’s time 
>> to start one of our periodic the Incubator is broken discussions.
>> 
>> The Incubator has many retired podlings that failed to form a community. 
>> That went from 3 or 4 to 1 or 0 community members. One example was 
>> ODFToolkit which came in at the same time as OpenOffice.org. ODFToolkit 
>> lingered for about 7 or 8 years. OpenOffice.org had an unusual anyone can 
>> signup to be an Initial Committer which brought the number to 73! As the 
>> current VP, OpenOffice I would not be wrong to say that the project would be 
>> in the Attic if that approach were not taken.
>> 
>>> In short, the initial commit list looks problematic to me.
>> 
>> Podlings and PMCs are not one size fits all.
>> 
>>> 
>>> P.S. The repo landing page/readme has some ASF trademark issues that would 
>>> be good to address.
>> 
>> That is part of Incubation.
>> 
>> Best,
>> Dave
>> 
>> 
>> -
>> 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: Request for SVN Robot Access for KIE Podling

[Justin Mclean]

Hi,

Given it is shared already, option 2 seems fine. It is version control, so any 
issues, if they occur, should be able to be easily corrected.

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

Re: [DISCUSS] PolarisProposal to the incubator

[Justin Mclean]

Hi,

I notice a number of people offering to be mentors. Experience has shown that 
three or four mentors seem to be best. More than that, and you can end up with 
a situation where everyone thinks everyone else is doing the job, so no one 
does it. If a mentor is not active during incubation they can be replaced.

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

Re: [DISCUSS] PolarisProposal to the incubator

[Justin Mclean]

Hi,

> I understand your comment, and it's important to me.
> If it's a concern for you, I'm happy to rework the initial committer
> list with the team (also removing PPMC list to use the default layout)
> and grow the PPMC/committers when in the incubator.

I think that would be in the best interests of the project. That way, you would 
have a larger pool of people to add during graduation when they do make 
contributions and recognise merit. The final composition of the PMC can be 
decided on graduation.

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

Re: [DISCUSS] PolarisProposal to the incubator

[Justin Mclean]

Hi,

In general, projects joining the incubator need two things: 
- A codebase
- a community around it

While this isn't a hard requirement, building either while in incubation can be 
difficult.

The first issue I see is it’s not clear to me that there is a community here.

The split between PPMC / committers is also unusual.

It also seems there’s a disconnect between the people who have contributed to 
the project and those on the initial PMC/committer list. I understand history 
has been lost. Is there any reason why history wasn’t preserved? But given it 
comes from a single vendor, I would assume that the commits in the new repo 
would then give an accurate representation of who is involved from outside that 
vendor since the plan/announcement to make it open source. However looking at 
the commits, 80%+ of the people involved come from that single vendor which and 
most of the proposed PPMC/committers have no activity in the project. How have 
these people contributed? 

Looking closer, other than jbonofre or snazy, I can see these commits from 
non-Snowflake people, and that is it.
anoopj - 1 commit (fixing a basic typo)
ajantha-bhat - 2 commits (minor doc changes)

From the information provided, it seems that a lot of the proposed PMCs have 
not been involved with the project at all. Mentors are there to help a project, 
adding extra existing PMC members to the PPMC to just help out is also rather 
unusual. So both the PPMC/committer split and the composition seem problematic 
to me.

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 Answer(Incubating) v1.3.6-RC1

[Justin Mclean]

Hi,

+1 (binding) carry over from dev list I did all of my usual checks

Kind Regards,
Justin

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

Re: [DISCUSS] PolarisProposal to the incubator

[Justin Mclean]

Hi,

I sent a reply earlier, but my email is acting up and looks like it didn’t get 
through. I have some concerns with this proposal.

In general, the incubator likes projects to have a code base and a small 
community, I’m not seeing a community here. Trying to build one during 
incubation can be difficult. We have recently rejected proposals in a similar 
state, asking them to come back when they have more of a community around the 
project.

The PPMC/committer split is unusual.

There seems to be little relation to people who have contributed to the project 
and the initial committer list. A large number of the people involved in 
commits (80+%) are from one vendor, with two exceptions, and two others have 
made one or two minor commits of a couple of lines.

Adding people to PPMC to help out also seems unusual, as that is the mentor's 
job.

In short, this seems to me (and I could be wrong) like a project mostly from a 
single vendor, but the proposal has been made to make it look like more people 
are involved. It may well be that these people will be involved, but I’d prefer 
if the project was upfront about this and added committers the usual way during 
incubation.

In short, the initial commit list looks problematic to me.

Kind Regards,
Justin

P.S. The repo landing page/readme has some ASF trademark issues that would be 
good to address.
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Amoro(incubating) 0.7.0-incubating rc2

[Justin Mclean]

Hi,

There is probabkly a few way to deal with this. I’m not sure the existing 
NOTICE is actually incorrect - i.e. the artefact was delevloped at the ASF and 
as a whole that is copyright the ASF, but I coudl also see people thinking that 
it means it contains ASF code.

Kind Regards,
Justin


> On 23 Jul 2024, at 8:04 pm, PJ Fanning  wrote:
> 
> I'm not sure the NOTICE files in your shade jars are correct.
> 
> This is a snippet from your amoro-shade-jackson-2-2.14.2-0.7.0-incubating.jar
> 
> Apache Amoro-shade
> Copyright 2006-2024 The Apache Software Foundation
> 
> This product includes software developed at
> The Apache Software Foundation (http://www.apache.org/).
> 
> amoro-shade-jackson-2
> Copyright 2024 The Apache Software Foundation
> 
> This project includes software developed at
> The Apache Software Foundation (http://www.apache.org/).
> 
> 
> This jar appears to have no code developed by the Apache Software Foundation. 
> It appears to only contain shaded classes from non-ASF projects - 
> specifically Jackson and Snakeyaml.
> 
> 
> 
> On 2024/07/22 07:20:21 Xavier Bai wrote:
>> +1, I deployed it in our environment and looks good.
>> 
>> Jinsong Zhou  于2024年7月22日周一 14:39写道：
>> 
>>> Hello Incubator PMC,
>>> 
>>> The Apache Amoro community has voted and approved the release of Apache
>>> Amoro(incubating) 0.7.0-incubating rc2.
>>> We now kindly request the IPMC members review and vote for this release.
>>> 
>>> Apache Amoro (incubating) is a Lakehouse management system built on open
>>> data lake formats.
>>> 
>>> Amoro community vote thread:
>>> https://lists.apache.org/thread/cnjq4vll060qx98r2rzcjk6jn25fhv38
>>> 
>>> Vote result thread:
>>> https://lists.apache.org/thread/9b8n0p2n19ovrdlcqxfhy83wxgg9pwyv
>>> 
>>> The official Apache source release to be deployed to dist.apache.org:
>>> 
>>> https://dist.apache.org/repos/dist/dev/incubator/amoro/0.7.0-incubating-RC2/
>>> 
>>> This source release has been signed with a PGP available here (Apache ID:
>>> jinsongzhou):
>>> https://downloads.apache.org/incubator/amoro/KEYS
>>> 
>>> All artifacts to be deployed to the Maven Central Repository:
>>> https://repository.apache.org/content/repositories/orgapacheamoro-1065
>>> https://repository.apache.org/content/repositories/orgapacheamoro-1064
>>> 
>>> Git branch for the release:
>>> https://github.com/apache/amoro/tree/v0.7.0-rc2
>>> https://github.com/apache/amoro-shade/tree/v0.7.0-rc2
>>> 
>>> Please download, verify, and test.
>>> 
>>> The VOTE will pass after 3 binding approve.
>>> 
>>> [ ] +1 approve
>>> [ ] +0 no opinion
>>> [ ] -1 disapprove with the reason
>>> 
>>> To learn more about Apache Amoro, please see https://amoro.apache.org/
>>> 
>>> Checklist for reference:
>>> 
>>> [ ] Download links are valid.
>>> [ ] Checksums and signatures.
>>> [ ] LICENSE/NOTICE files exist
>>> [ ] No unexpected binary files
>>> [ ] All source files have ASF headers
>>> [ ] Can compile from source
>>> 
>>> Best,
>>> Jingsong
>>> 
>> 
> 
> -
> 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: PMC is a committee

[Justin Mclean]

Hi,

I’m not sure the incubator’s remit is to make changes that affect all TLPs. The 
discussion about MPMC vs. PMC should probably be on the member's list. Making 
the change and then notifying them may come across the wrong way.

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

Re: [DISCUSS] GravitinoProposal to the incubator

[Justin Mclean]

HI,

> Looks interesting, It will be good, if it's extend to xtable( as I
> see, it's currently only iceberg).

No one that I know of is working on xtable integration, but as we’re now an ASF 
incubating project anyone can propose and work on that.

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

Re: [QUESTION] Can we use an AGPL components [minio] in OpenServerless?

[Justin Mclean]

Hi,

I would ask legal-disc...@apache.org, but it would not be allowed unless it is 
an optional dependency. However, it depends on the exact details.

Kind Regards,
Justin

> On 5 Jul 2024, at 6:45 pm, Michele Sciabarra  
> wrote:
> 
> If this is not the right place to ask this question please ignore it and
> let me know where I should ask.
> 
> We are starting the OpenServerless project and checking licenses.
> 
> We have one component in our project, Minio, which is AGPL Licensed.
> 
> We know AGPL is not to be used in Apache Code but here we really do not
> link nor change it, we just use it and access through their API as a
> generic S3 storage.
> 
> We do not even use their library to access it, we use the AWS SDK for
> generic S3.
> 
> My understanding of the AGPL is: we have to provide the code of it and any
> modification EVEN if it is accessed through the network. This is fine, we
> are complying with the license providing a downloadable tarball of the
> exact version we are using.
> 
> Aside from that, can we use it in OpenServerless? It just deploys a minio
> component, it does not modify it in any way.
> 
> Please advise...
> 
> --
> Michele Sciabarrà - msciaba...@apache.org - linkedin.com/in/msciab
> Apache OpenServerless Founder - reddit.com/r/openserverless
> Apache OpenWhisk PMC member - Author Learning Apache OpenWhisk
> 


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

Re: Bylaws != Guidelines

[Justin Mclean]

Hi,

By the point of time, the Incubator guidelines were introduced:
- Projects were strongly encouraged not to have bylaws and to use what was 
documented in policy
- If they wanted bylaws, they should call them guidelines

The reasons for this include that bylaws cannot cover every situation, and just 
about all of our policies are in fact guidelines not bylaws. If a project has a 
good reason for doing something differently than is documented, they can do 
that.

I don’t have the time right now, but if you search the archives, you should be 
able to find conversations about this.

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

[jira] [Closed] (INCUBATOR-284) Ask for the permission to use some Github CI action

[Justin Mclean (Jira)]

 [ 
https://issues.apache.org/jira/browse/INCUBATOR-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Justin Mclean closed INCUBATOR-284.
---
Resolution: Won't Fix

Should be an INFRA ticket

> Ask for the permission to use some Github CI action
> ---
>
> Key: INCUBATOR-284
> URL: https://issues.apache.org/jira/browse/INCUBATOR-284
> Project: Incubator
>  Issue Type: Improvement
>Reporter: Yu Qi
>Priority: Major
>
> Our incubator project (Gravitino) has used the following GitHub CI actions
> ```
> madrapps/jacoco-report@v1.6.1
> carloscastrojumo/github-cherry-pick-action@v1.0.9
> actions/add-to-project@v0.5.0
> ```
> When transferring it to ASF, they can't work because Apache prohibits using 
> them in the GitHub CI by default, so I created this issue to request to allow 
> them in Gravitino, thanks. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Re: [VOTE] Accept OzHera into the ASF incubator

[Justin Mclean]

Hi,

> Hi, Justin, about the proposal, we have already mentioned that 'with
> the current contributors primarily coming from Xiaomi', and also 'the
> majority of core developers working on the OzHera project are salaried
> by Xiaomi', which reflects the current status of the project.

Yes, the proposal does make that clear.

> And in the discussion thread, the team also mentioned that they have
> already attracted some external developers, although the contributions
> are not enough to make them initial committers.

When I looked at a couple of contributions from external developers, they were 
pretty simple, and I think at most two commits from a person (but I could have 
misremembered that and have it wrong). Given the low activity from external 
people, I understand why you would not make them initial committers, but then 
also claiming there’s a community of external developers is stretching things a 
bit.

> We hope that during the incubation time the project can build a diverse 
> community, and
> finally successfully graduate and become a TLP. Of course there are
> risks that the project fails to do so and can not graduate, but I do
> not think this is a blocker for entering the incubator right?

Taking up valuable time from Incubator volunteers can be a concern if the 
project isn't ready to join the incubator.

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

Re: [VOTE] Accept OzHera into the ASF incubator

[Justin Mclean]

Hi,

> Is this considered a blocker for a project to enter incubator? I do
> see it could be a concern during the project's graduation, but for
> entering into incubator as well?

It is a concern on entering the incubator, especially for a project that has 
been open source for some time. It would be a much bigger concern at graduation 
and, in fact, would stop graduation in most cases.

> Some folks developed the project at their org, they are opesnourcing
> it via Apache Incubator & will build a community with folks from
> diverse organizations during their stay at Incubator, is that not a
> valid path?

It can be very tough to grow a community from almost nothing in the incubator, 
so we prefer projects to have an existing community around them.

Kind Regards,
Justin


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

Re: [VOTE] Accept OzHera into the ASF incubator

[Justin Mclean]

HI,

> Are there any remaining inaccuracies in the proposal?

Yes I believe there are:
"Outstanding contributors are the cornerstone of this project, and they include 
not only developers from Xiaomi and other companies but also individual 
developers who are encouraged to contribute. In this project, exceptional 
contributors are recognized and rewarded, fostering a collaborative and 
inclusive environment where decisions and project development are driven by 
capabilities and contributions.”

Can anyone point to any outstanding or exceptional contributors, not from 
Xiaomi?

If you look at the composition of the initial committers, some other claims 
made also seem exaggerated.

> Is it possible that we can try to build the community while OzHera is part of 
> the
> Incubator? If the team can't attract outside committers then they will
> find it hard to graduate as a TLP.

In general, there are two things we require for an external project to become 
an incubating one:
- have a code base to donate
- have a (small) community

Growing a community from nothing while in the Incubator is very difficult, 
especially if the project has yet to be able to develop a community while being 
an open-source project. While I wish the project the best, it may still be too 
early to join the incubator, which in turn may harm its graduation chances.

That being said, my -1 is not a veto, and if enough other IPMC members feel it 
should join the incubator, then that is fine with me.

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

Re: [VOTE] Accept OzHera into the ASF incubator

[Justin Mclean]

Hi,

-1 (binding) As I said in the discussion thread, I have concerns about this 
project. The proposal did not accurately reflect its state, it has little or no 
community around it and a single corporate entity is behind it.

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 Answer(Incubating) v1.3.5-RC1

[Justin Mclean]

Hi,

+1 (binding)

I checked the source release:
- incubating in the name
- signatures and hashes are fine
- DISCLAIMER exists
- LICENSE and NOTICE are fine
- No unexpected binary files
- My environment is not set up to be able to build

One very minor issue I assume the year in ./docs/release/NOTICE needs updating, 
also the licenserc.toml fil has this incorrect line in it:
copyrightOwner = "tison ”

Kind Regards,
Justin



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

Re: [External Mail]Re: [DISCUSS] OzHera to the incubator

[Justin Mclean]

Hi,

I have three main concerns:
1. All of the initial committers are from one company.
2. Very few contributors and just about all seem to be from the same company 
(one or two with a couple of commits may not be)
3. The project activity has been quite low over the last 5 months

I do not see this reflected in the proposal, e.g. "Outstanding contributors are 
the cornerstone of this project, and they include not only developers from 
Xiaomi and other companies but also individual developers who are encouraged to 
contribute?” Where are these other companies and developers? or "In this 
project, exceptional contributors are recognized and rewarded,“ Who has been 
rewarded and how? Also " It has also attracted members from different companies 
such as JD.com, Kwai, Shopee, and others.” Why are people from these companies 
not on the initial committer list or show up as making contributions?

The proposal also states "The contributors of OzHera are actively involved in 
Apache community projects, “, looking at the people involved, and I may have 
missed something, I’m not seeing a lot of activity in ASF projects.

The proposal also also mentions "and every member can access the project 
roadmap, issues, and code through various channels such as mailing lists and 
JIRA” Where are these existing JIRA/lists?

Under community, it states " broader promotion and participation from companies 
and individuals.” this is a bit of a concern. Projects should not join the ASF 
because they want companies involved and for promotion purposes.

There are two main requirements to join the ASF incubator: one is to have a 
small community, and the other is to have a code base. We may still need more 
on the community side here. The proposal, as written, seems to paint an overly 
optimistic picture of the project. Before considering it further, I would like 
to see it updated to reflect the actual reality of the current project and 
spell out the risks to community growth beyond the involvement of a single 
company.

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

Re: [DISCUSS] GravitinoProposal to the incubator

[Justin Mclean]

Hi,

Thanks for all the +1’s, but this is the discussion, not the vote, the vote 
comes next.

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

Re: [DISCUSS] GravitinoProposal to the incubator

[Justin Mclean]

Hi,

> I would be willing to be an additional mentor or join the initial set of
> team members if there is interest.

Thanks, Larry, for offering. I’ve added you to the proposal as a mentor.

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

Re: What is sufficient Incubation notification for Git repos?

[Justin Mclean]

Hi,

> Whilst the DISCLAIMER file is helpful, and having '(Incubating)' in
> the repo description/About, neither of these are all that obvious.

Yep, that should be done.

> It seems to me that the repo README should also contain the Incubator
> disclaimer, as is done on website pages.

That is also my expectation.

See for instance:
https://issues.apache.org/jira/browse/INFRA-25790

Kind Regards,
Justin

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

Re: KIE - Question about "staging" binaries/artifacts

[Justin Mclean]

Hi,

> Thank you all for the inputs, but we still seeking clarity on NPM.
> 
> We - Apache KIE podling - are trying to get a single release procedure for
> all binaries, but with lack of NPM infra for staging makes it really
> complex.
> 
> I notice that OpenDAL publishes to NPM, is there anyone involved in OpenDAL
> here that could help us sort this out?
> 
> For container images, we have similar issue with staging… less of issue is
> the build.

I would publish them, tag them as release candidates, and then update that 
tag/description if the release vote passes.

Also see our distribution guidelines [1] for other important information on 
publishing to non-official channels.

Kind Regards,
Justin

1. https://incubator.apache.org/guides/distribution.html

Re: [VOTE] Release Apache ResilientDB, Incubating, v1.10.0-RC1

[Justin Mclean]

Hi,

A few questions occurred to me when looking at the website:
- You list sponsors, how do these companies sponsor the project?
- You list 1.9.0 for download, but there is no link to the KEYS files
- You list Mohammad Sadoghi as the “Principle Investigator” This is problematic 
from an ASF point of view. An ASF community doesn't have a leader.
- There are people listed on the page that are not part of the PMC 
- You list members of a “founding team”, again this is problematic. You can’t 
claim this as it is now an ASF project and run by the community.
- you use resilientdb.com email address for contact and support.
- The relationship between cloud offering and rsview and the ASF project is 
unclear. Are these also open source, or do they intend to be commercial 
offerings?
- Again the connection with ResillientApp is unlear.
- The website is misisng the required ASF links to the foundation, events, 
license, thanks, security, and privacy. [1] 

I suggest you engage with your mentors and get them to provide advice here.

Kind Regards,
Justin

1. https://whimsy.apache.org/pods/
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

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

[Justin Mclean]

Hi,

+1 binding. We already have other requirements for the project to indicate that 
they are incubating (e.g. website disclaimer, DISCLAIMER, and release artifact 
name) that are more visible than having it in repo names.

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 ResilientDB, Incubating, v1.10.0-RC1

[Justin Mclean]

HI,

> Thanks for letting me know.
> I have removed those dependencies.

What goes in the license file is any 3rd party licenses that are included in 
the source release, not those that are dependencies. But unless it is optional, 
you also can’t have any GPL dependencies.

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 ResilientDB, Incubating, v1.10.0-RC1

[Justin Mclean]

HI,

I assume you mean [1] I’ve not looked at it in detail, but I note you include 
GPL licensed code. GPL-licensed code is Category X and can’t be used in an ASF 
project.

Kind Regards,
Justin


1. https://github.com/apache/incubator-resilientdb/blob/master/LICENSE

Re: [VOTE] Release Apache ResilientDB, Incubating, v1.10.0-RC1

[Justin Mclean]

Hi,

It’s -1 (binding) from me. I think you should use Apache Rat to check the 
release.

I checked:
- incubating in artifact name
- signatures and hashes are correct
- DISCLAIMER exists
- LICENSE is missing mention of 3rd party code included in the release
- NOTICE doesn't include correct text (missing URL)
- Files are missing ASF headers 
- no unexpected binary files
- I did not try to compile from the source

Files missing headers - you need to work out if these are 3rd party files or 
not.
./INSTALL.sh
./INSTALL_MAC.sh./entrypoint.sh./script.js./platform/consensus/ordering/common/algorithm/protocol_base.cpp./platform/consensus/ordering/common/algorithm/protocol_base.h./platform/consensus/ordering/poe/algorithm/poe.cpp./platform/consensus/ordering/poe/algorithm/poe.h./platform/statistic/test_server.sh./scripts/format.sh
./scripts/deploy/performance/pbft_performance.sh
./scripts/deploy/performance/poe_performance.sh
./scripts/deploy/performance/run_performance.sh
./scripts/deploy/script/deploy.sh
./scripts/deploy/script/env.sh
./scripts/deploy/script/generate_config.sh
./scripts/deploy/script/generate_key.sh
./scripts/deploy/script/load_config.sh./service/tools/contract/api_tools/example_contract/compile.sh./service/tools/contract/service_tools/start_contract_service.sh
./service/tools/kv/server_tools/start_kv_service.sh./service/tools/kv/server_tools/start_kv_service_monitoring.sh./service/tools/utxo/service_tools/start_utxo_service.sh./service/utxo/start_contract_server.sh
./tools/generate_certificate.sh
./tools/generate_client.sh
./tools/generate_cluster.sh
./tools/generate_key.sh

3rd party files that need to be mentioned in LICENSE:
./benchmark/protocols/poe/kv_server_performance.cpp
./common/crypto/hash.cpp
./common/crypto/hash.h
./common/crypto/hash_test.cpp
./common/crypto/key_generator.cpp
./common/crypto/key_generator.h
./common/crypto/mock_signature_verifier.h
./common/crypto/signature_utils.cpp
./common/crypto/signature_utils.h
./common/crypto/signature_verifier.cpp
./common/crypto/signature_verifier.h
./common/crypto/signature_verifier_interface.cpp
./common/crypto/signature_verifier_interface.h
./common/crypto/signature_verifier_test.cpp
./common/test/json_test.cpp
./common/test/test_macros.h
./common/utils/utils.cpp
./common/utils/utils.h
./node_modules/fs.realpath/old.js
./platform/consensus/ordering/common/framework/consensus.cpp
./platform/consensus/ordering/common/framework/consensus.h
./platform/consensus/ordering/common/framework/performance_manager.cpp
./platform/consensus/ordering/common/framework/performance_manager.h
./platform/consensus/ordering/common/framework/response_manager.cpp
./platform/consensus/ordering/common/framework/response_manager.h
./platform/consensus/ordering/common/framework/transaction_utils.cpp
./platform/consensus/ordering/common/framework/transaction_utils.h
./platform/consensus/ordering/poe/framework/consensus.cpp
./platform/consensus/ordering/poe/framework/consensus.h
./platform/consensus/ordering/poe/framework/consensus_test.cpp
./service/tools/utxo/wallet_tool/cpp/addr_utils.cpp
./service/tools/utxo/wallet_tool/cpp/addr_utils.h
./service/tools/utxo/wallet_tool/cpp/key_utils.cpp
./service/tools/utxo/wallet_tool/cpp/key_utils.h
./service/tools/utxo/wallet_tool/pybind/wallet_tools_py.cpp./node_modules/lodash.union/index.js./node_modules/lodash.difference/index.js./node_modules/brace-expansion/index.js./node_modules/ignore/index.js./node_modules/once/once.js./node_modules/inherits/inherits.js
...and many other files in node_modules

Kind Regards,
Justin







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

Re: License for text content

[Justin Mclean]

Hi,

The CC BY 4.0 is not compatible with the Apache license, so I would avoid it if 
you can. While the Apache license is intended for code, it’s OK to use for 
documentation as well.

Kind Regards,
Justin

> On 2 May 2024, at 1:25 pm, tison  wrote:
> 
> Hi,
> 
> IIUC, the Apache License 2.0 is mainly to license code and related stuff
> that constructs the final software.
> 
> However, projects may also create text content like documents. Is it
> appropriate to use Apache License 2.0 for them (since quite a few terms may
> not be applicable)? Or what licenses shall we use?
> 
> For example, a website repo can contain both code and docs. In my personal
> site, I wrote:
> 
>> Code is licensed under Apache-2.0, words and images are licensed under CC
> BY 4.0.
> 
> But I don't know if we can write the same to a site repo of an ASF project.
> 
> Best,
> tison.


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

Re: [VOTE] Release Apache StreamPark(Incubating) 2.1.4-rc1

[Justin Mclean]

Hi,

> Thanks for your clarification. We have submitted a PR[1] to address this
> issue. I believe this issue will be resolved quickly.
> 
> [1] https://github.com/apache/incubator-streampark/pull/3689

That looks good to me, thanks.

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 StreamPark(Incubating) 2.1.4-rc1

[Justin Mclean]

Hi,

> * Some false positive on testing assertions utils. Match rate < 50%, file
> is small, and those utilities are trivial. Even when I go to the "origins",
> they are lost or changed a lot. Clearly not the same origin.

Even if they have changed a lot, that could still be an issue. Copying an 
earlier version of a file is still an issue that needs to be dealt with. Even 
copying 5% of something needs to be treated correctly. The files seem to have 
permissive licenses, so there is no category X licensing issue, at least.

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 StreamPark(Incubating) 2.1.4-rc1

[Justin Mclean]

Hi,

-1 (binding) from me

I checked:
- incubating in name
- signatures and hashes correct
- disclaimer exists
- LICENSE is missing some info on the MIT license
- NOTICE looks fine
- I didn't compile from source

So a condition of including MIT licensed code is to include the relevant MIT 
license text. That seems to be missing for for vue-vben-admin , as I can’t find 
it anywhere in the release. Oddly, the license file here [1] is an Apache one, 
not an MIT one, and it also fails to mention the MIT code under it.

It looks like additional third-party code might also be in the release, but it 
is difficult to tell. I think you should run SCANOSS 
(https://www.softwaretransparency.org/download) on your release and look into 
its results. 

Kind Regards,
Justin


1. streampark-console/streampark-console-webapp/LICENSE
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Verification of download pages and links

[Justin Mclean]

Hi,

> Here is a patch to cover a minimal download page [1], which is derived from
> OpenDAL's download page [2]. Welcome to leave comments if you find any
> issues or things we can improve on.
> 
> [1] https://github.com/apache/datafusion/pull/10271
> [2] https://opendal.apache.org/download

The link to the source download and keys and hashes is broken.

Kind Regards,
Justin

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

Re: Verification of download pages and links

[Justin Mclean]

Hi,

Projects need to make source releases on ASF infrastructure and have a download 
page for good reasons. Some users need a place to verify and download a trusted 
release. Having it hosted on ASF infrastructure means people can 100% trust it, 
unlike 3rd party providers. 3rd party providers have gone rogue in the past 
(e.g . Source Forge), disappeared (e.g. Google Code), or had multiple serious 
issues (e.g. NPM). Also by placing a release in the ASF distribution area / a 
project download page gives confidence that the ASF release process has been 
followed and that it is not a release by a 3rd party or an unofficial release 
of some sort.  IMO, all projects need to have a download page, even if it may 
not be used by the majority of users.

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

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

[Justin Mclean]

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 project is clearly 
understood to be an incubating p[project and what that means, rather than the 
exact wording.

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 Fury(incubating) v0.5.0-rc3

[Justin Mclean]

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 fact, may have been 
copied themselves.

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

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

[Justin Mclean]

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 that the 
infrastructure, communications, and decision making process have stabilized in 
a manner consistent with other successful ASF projects. While incubation status 
is not necessarily a reflection of the completeness or stability of the code, 
it does indicate that the project has yet to be fully endorsed by the ASF.”

Kind Regards,
Justin

> On 24 Apr 2024, at 9:48 pm, tison  wrote:
> 
> 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 to each repo's README. This can
> be regarded as treating those READMEs a homepage for the repo and,
>> 
>> 1. Name the project as "Apache Foo (Incubating)" in its first and most
> prominent uses, hopefully and H1 heading.
>> 2. Add a footer including the Incubator logo and DISCLAIMER, like the
> current footer of Apache Answer (Incubating) [3]
>> [3] https://answer.apache.org/
> 
> Be sure that you know we don't barely drop the prefix, but we need a formal
> way to "make it clear that a podling's repo is in the incubating status",
> which can be achieved currently by  its prefix.
> 
> Best,
> tison.
> 
> 
> Wilfred Spiegelenburg  于2024年4月23日周二 13:12写道：
> 
>> For Go based projects dropping the incubator reference in the git repo
>> makes things easier also when graduating. Packages and dependencies are
>> referenced based on the repository name. Renaming the repository either
>> requires changes throughout the code base to remove the incubator reference
>> or the packages will always have the incubator reference in them.
>> 
>> Wilfred
>> 
>> On 2024/04/23 01:22:02 tison wrote:
>>> Hi,
>>> 
>>> Recently, the new added podlings, namely Amoro and Hertzbeat, have their
>>> GitHub repo in the names:
>>> 
>>> * https://github.com/apache/amoro
>>> * https://github.com/apache/hertzbeat
>>> 
>>> ... which is different to the other 20+ podlings and 200+ repos [1]
>>> existing (this number counts retired ones and those for the Incubator PMC
>>> itself, but it's approximate).
>>> 
>>> [1]
>>> 
>> https://github.com/orgs/apache/repositories?language=&q=incubator-&sort=&type=all
>>> 
>>> My opinion is to agree that generally:
>>> 
>>> 1. The incubator prefix comes from the SVN days where all podlings were
>> under
>>> the incubator SVN tree.
>>> 2. Dropping the incubator- prefix for podling's GitHub repo can reduce
>> some
>>> graduation tasks (although it's somewhat a milestone and ceremony for the
>>> podling, and INFRA does not find it a large job, as well as it won't
>> break
>>> downstream almost due to redirections).
>>> 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.
>>> 
>>> With these premises, I started this thread with the following proposals
>> and
>>> questions.
>>> 
>>> 1. Establish a consensus to allow podling's GitHub repo to have a name
>>> without incubator- prefix.
>>> 2. Allow other 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. However, find a way to clarify that a repo belongs to a podling.
>>> 
>>> For 4, I'd propose to add the "incubating" words to each repo's README.
>>> This can be regarded as treating those READMEs a homepage for the repo
>> and,
>>> 
>>> 1. Name the project as "Apache Foo (Incubating)" in its first and most
>>> prominent uses, hopefully and H1 heading.
>>> 2. Add a footer including the Incubator logo and DISCLAIMER, like the
>>> current footer of Apache Answer (Incubating) [3]
>>> 
>>> [3] https://answer.apache.org/
>>> 
>>> This method, however, can be a new chore for podlings that have many
>>> satellite repos that may previously claim their incubating status by
>> naming
>>> the repos incubator-foo-satellite. But it's just another template to
>>> follow, so it won't be a big deal.
>>> 
>>> Looking forward to your thoughts on this proposal and any suggestions to
>>> improve the implementation part.
>>> 
>>> 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: gene

Re: [VOTE] Release Apache Fury(incubating) v0.5.0-rc3

[Justin Mclean]

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 OK to include it
> here since both are written by me.

That should be fine, but having an ASF header on the files may be a little 
misleading? What do you think?

> For files [1][2][3][4], could you give more details how those files include
> code from OpenSumi. The OpenSumi core developer
> bytemain[9] does commit some code to Fury, see his commits[10]. But I
> talked to him offline, he said he didn't copy code from
> OpenSumi.

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.

> For Fury ArrayAsList, could you give more details how this class is copied
> from somewhere? It's just a simple wrapper for java
> object arrays.

A possible explanation for what has happened here is that the developer used AI 
to generate the code, and it’s duplicated that code from somewhere. Do you know 
if that is the case?

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 Fury(incubating) v0.5.0-rc3

[Justin Mclean]

HI,

Sorry, it’s -1 (binding) from me as it looks like there is additional 
third-party code without correct headers or mentioned in LICENSE.

I checked:
- incubating in name
- signatures and hashes are fine
- LICENSE has some issues (see below)
- NOTICE is fine
- It looks like some 3rd party code incorrectly has ASF headers (see below)
- All source files have ASF headers

For the LICENSE file:
- there are several references to a benchmark directory, but it is not included 
in the release
- there seems to be 3rd part code from OpenSumi here [1][2][3][4]
- there seems to be code from Ray here [5][6]
- this file may have been copied from somewhere [7]

Kind Regards,
Justin

1. /javascript/packages/fury/lib/gen/datetime.ts
2. /javascript/packages/fury/lib/gen/index.ts
3. /javascript/packages/fury/lib/fury.ts
4. /javascript/packages/fury/lib/classResolver.ts
5. 
/java/fury-core/src/main/java/org/apache/fury/io/MemoryBufferWritableChannel.java
6. /java/fury-core/src/main/java/org/apache/fury/io/MockWritableChannel.java
7. 
/java/fury-core/src/main/java/org/apache/fury/serializer/collection/ArrayAsList.java
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Questions about a new project entering Apache Incubator

[Justin Mclean]

HI,

So, I had an informal chat with Infra, and they don't care which one they do, 
but is it some work for them to change from “incubator-foo” to “foo” on 
graduation. I’m curious as to why some people in this thread think this is a 
big issue if the project clearly states it is an incubating project. I will 
note that Hertzbeat put the GitHub name in their propopal, and no one said 
anything about it.

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

Re: [MENTORS] May report timeline - reports due May 2024

[Justin Mclean]

HI,

As Sdap has just graduated, it doesn’t need to report.

Kind Regards,
Justin



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

Re: Questions about a new project entering Apache Incubator

[Justin Mclean]

Hi,

Both of these projects are new and just getting set up. I'd give them a
little time to do that. Infra in recent years have asked to minimise work
for them on graduation. We recently dropped the requirement for having
incubating in podling domain names so I don't see it's needed in repo names
as long as it clear the project is an incubating project.
Kind Regards,
Justin


On Wed, 17 Apr 2024, 1:47 pm Willem Jiang,  wrote:

> With the "incubator" profix, it's easy for us to tell if the project
> belongs to the incubator and it is still in the incubating process.
> Currently I cannot find any disclaimer document[1] in the repo root
> directory from [2][3] to tell if they are still in the incubator or
> not.
>
> [1]https://incubator.apache.org/policy/incubation.html#disclaimers
> [2]https://github.com/apache/amoro
> [3]https://github.com/apache/hertzbeat
>
> Willem Jiang
>
> On Wed, Apr 17, 2024 at 11:06 AM Calvin Kirs  wrote:
> >
> > Podlings are not yet fully accepted as part of the Apache Software
> > Foundation.
> >
> > I haven't specifically witnessed any formal decision or process for
> > removing the "incubator" prefix from repository names.
> >
> > Unless there are compelling reasons to remove the "incubator" prefix, I
> > believe it's important to maintain a clear distinction between Podlings
> and
> > TLPs, especially in situations where confusion is likely to arise.
> >
> > On Wed, Apr 17, 2024 at 10:32 AM Sheng Wu 
> wrote:
> >
> > > Same mistake for Armoro as Hertzbeat team was misguided from
> > > https://github.com/apache/amoro/issues/2700
> > >
> > > This is not discussed AFAIK, and the description is not correct.
> > > GitHub supported renaming and repository path forward automatically
> > > years ago. apache/incubator-foo -> apache/foo is transparent and both
> > > addresses work.
> > >
> > > This should not be changed randomly considering many other projects
> > > are using incubator- prefix. This renaming causes confusion. IPMC are
> > > making sure the website has `incubating` and disclaimer as always,
> > > suddenly some projects even could use repository names without
> > > prefixes. This is wrong.
> > >
> > > Mentors of Armoro and Hertzbeat should follow the existing
> > > requirements, and PPMC members of these two projects should ask INFRA
> > > to rename, adding the incubator- prefix back.
> > >
> > > Sheng Wu 吴晟
> > > Twitter, wusheng1108
> > >
> > > Xuanwo  于2024年4月17日周三 10:19写道：
> > > >
> > > > > For projects in incubation, is it no longer necessary for the
> project
> > > > > name to have the "incubator-" prefix as it used to be?
> > > >
> > > > Based on the discussions in this mailing list, the only change made
> is
> > > the removal of `incubator` from the domain. Now, users access `
> > > polding.apache.org` instead of `polding.incubator.apache.org` by
> default.
> > > >
> > > > The project and releases are still required to include "incubator",
> and
> > > it's important for the PPMC to clearly communicate that this project
> > > remains under incubation.
> > > >
> > > > In this case, I believe Hertzbeat PPMC made a mistake. I will suggest
> > > they rename it to incubator-hertzbeat.
> > > >
> > > > On Mon, Apr 15, 2024, at 14:23, rat O wrote:
> > > > > First of all, congratulations to HertzBeat for successfully
> entering
> > > > > the Apache Incubator.
> > > > >
> > > > > I noticed that the project has created an issue for an unknown
> license
> > > > > and is ready to address it. I'm sure the project will also address
> > > > > other unknown licenses, if they exist.
> > > > >
> > > > > I wonder if the situation of having a significant amount of
> non-English
> > > > > languages in the codes, like these
> > > > >
> > >
> https://github.com/apache/hertzbeat/blob/master/warehouse/src/main/java/org/apache/hertzbeat/warehouse/config/WarehouseProperties.java
> > > ,
> > > > >
> > >
> https://github.com/apache/hertzbeat/blob/master/common/src/main/java/org/apache/hertzbeat/common/entity/manager/NoticeRule.java
> > > ,
> > > > >
> > >
> https://github.com/apache/hertzbeat/blob/master/common/src/main/java/org/apache/hertzbeat/common/config/AviatorConfiguration.java
> > > > > ...
> > > > > , will all of them also be addressed in the future?
> > > > >
> > > > > For projects in incubation, is it no longer necessary for the
> project
> > > > > name to have the "incubator-" prefix as it used to be?
> > > >
> > > > --
> > > > 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
> > >
> > >
> >
> > --
> > Best wishes！
> > CalvinKirs
>
> -

Re: Should we mention license of other projects in NOTICE file

[Justin Mclean]

Hi,

Any license information goes in LICENSE, not NOTICE. If you include something 
that is MIT or BSD licensed, nothing goes in the NOTICE. The NOTICE file will 
include re-located copyright statements removed from files and the contents of 
any Apache code you have included NOTICE files.

1. is BSD licensed, so just put the text in LICENSE
2. is Apache licensed, It’s a good idea to list that in the LICENSE file (but 
not required). It has no NOTICE file, so there is nothing to go in your NOTICE 
file.

Kind Regards,
Justin

> On 13 Apr 2024, at 3:53 pm, Shawn Yang  wrote:
> 
> Dear Community,
> 
> I'm fixing the license issue of Apache Fury to comply with ASF requirements
> for the first release for Fury under ASF.
> 
> Currently we borrowed some code from other projects such as
> v8-fast-api-calls.h[1] in v8 and Preconditions[2] in guava. We mentioned
> their license in our NOTICE file[3].
> 
> I'm wondering whether we should move those mentions into the LICENSE file,
> and mention the NOTICE of those projects in our NOTICE instead.
> 
> I did some research, but didn't know which is better:
> 1) Projects like flink[4] and pytorch[5] mention the license of other
> projects in the NOTICE file.
> 2) But other projects such as spark[6] and arrow[7] all put the mentions
> into the `LICENSE` file.
> 
> Are those both ways legal? Do we have a best practice here?
> 
> 1.
> https://github.com/apache/incubator-fury/blob/main/javascript/packages/hps/src/v8-fast-api-calls.h
> 2.
> https://github.com/apache/incubator-fury/blob/main/java/fury-core/src/main/java/org/apache/fury/util/Preconditions.java
> 3. https://github.com/apache/incubator-fury/blob/main/NOTICE
> 4. https://github.com/apache/opendal/blob/master/NOTICE
> 5. https://github.com/pytorch/pytorch/blob/main/NOTICE
> 6. https://github.com/apache/spark/blob/master/LICENSE
> 7. tttps://github.com/apache/arrow/blob/main/LICENSE.txt
> 
> 
> Best regards,
> Chaokun Yang


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

[MENTORS] Missing podling reports

[Justin Mclean]

Hi,

We are missing a large number of reports this month. Mentors, can you please 
help your projects submit reports on time.

We are still waiting on reports from:
- Annotator
- Gluten
- HoraeDB
- HugeGraph
- Liminal
- Pony Mail
- ResilientDB
- Teaclave
- XTable

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

Re: Trademarks and incubation (was: [DISCUSS] Graduate Apache AGE Incubating as a Top Level Project)

[Justin Mclean]

Hi,

> Question: where did the incubation process fail in this case?  How can we 
> prevent something like this from happening again?

The Incubator pointed out the issue during a graduation discussion at the end 
of 2021 (which put off graduation). The people involved said they would not use 
the name AgeDB and would stop using it in a week. They became a TLP in early 
2022. From what I can see, the AgeDB website was created in mid 2023.

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

Re: Update project maturity model to include trademark and branding?

[Justin Mclean]

Hi,

> Besides, the maturity model is applied for all ASF projects and under the
> management of ComDev pmc.
> 
> Shall we cc this thread to dev@community.a.o or start a new thread after we
> have a consensus within the Incubator first?

I had intended to bring it up on dev@community.a.o for refinement and 
discussion, but unfortunately, I did not do so. It is probably overdue to do so.

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

Re: Registering a release

[Justin Mclean]

Hi,

>> You might want to remove those old releases there, as they are automatically 
>> archived here:
>> https://archive.apache.org/dist/incubator/sdap/
> 
> Would that affect the closer.lua download links on our website?

Yes, but it’s not needed for old releases because they presumably don’t get as 
many downloads. See 
https://infra.apache.org/release-distribution.html#download-links

Kind Regards,
Justin

Re: [MENTORS] April report timeline - reports due April 2024

[Justin Mclean]

Hii,

Please note that Kie doesn't need to report.

Kind Regards,
Justin

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

Re: Registering a release

[Justin Mclean]

Hi,

In SDAPs case:
https://dist.apache.org/repos/dist/release/incubator/sdap/

You might want to remove those old releases there, as they are automatically 
archived here:
https://archive.apache.org/dist/incubator/sdap/

Kind Regards,
Justin

Re: Registering a release

[Justin Mclean]

Hi,

I’m not sure what you mean by registering a release. All ASF releases need to 
go here:
https://dist.apache.org/repos/dist/release/

Kind Regards,
Justin

> On 21 Mar 2024, at 10:29 am, Julian Hyde  wrote:
> 
> Can someone remind me where I go (whimsy or reporter, I presume) to
> register a release from a podling (in this case SDAP)?
> 
> In Calcite, a top-level project that deploys Java artifacts to Maven
> Central, the process has been straightforward. I believe I even
> received an email from Reporter sending me to the registration page.
> But for SDAP I can't figure out where to register the release.
> 
> Thanks!
> 
> Julian
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 

Re: [VOTE] Podling web sites: make (incubator.) optional in podling urls

[Justin Mclean]

+1 binding

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

[RESULT][VOTE] Accept Amoro into the ASF Incubator

[Justin Mclean]

HI,

Thanks to everyone who voted. [1]

There are 15 +1 binding votes, 19 +1 non-binding votes, and no 0 or -1 votes, 
so the vote has passed. 

Binding +1 votes:
Yu Li
Ayush Saxena
PJ Fanning
Felix Cheung
Craig Russell
Zili Chen (tison)
Xinyu Zhou
Xin Wang  
Jean-Baptiste Onofré 
Duo Zhang
Furkan Kamaci
Paul King
Junping Du (JP)
Kent Yao
Willem Jiang
 
Non-binding +1 votes +1:
Alex Porcelli
Keyong Zhou
Imba Jin
Nicholas Jiang
Bi Yan
Conrad Jam
roryqi
Huajie Wang
Shaoyun Chen  
Jingsong Li 
Suyan
Xuanwo
Cheng Pan
Hulk Lin
Zhongming Hua
Shaokang Lv
Yu Xiao
gaojun2048
Lifeng Nie

Kind Regards,
Justin

 [1] https://lists.apache.org/thread/56n4rtxq1q7c0m3bxp1n7lcj551555nk



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

Re: [DISCUSS] Graduate Apache Paimon (Incubating) as a Top Level Project

[Justin Mclean]

Hi,

> Thanks for pointing this out Justin. The description of the first
> mentioned vedio (a CoC Asia talk) [1] has been updated (thanks @Willem
> for the help), and PPMC is actively working on correcting the second
> one.

Those two links were only some of the instances I found. I suggest you do some 
Google searches to find more.

Kind Regards,
Justin


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

Re: [DISCUSS] Graduate Apache Paimon (Incubating) as a Top Level Project

[Justin Mclean]

HI,

In your discussion on graduation, you refer to the proposed chair as “the 
founder of Paimon”. While this person may have come up with the initial design 
before it was an Apache project, the project is run by the community. Please do 
not refer to anyone as a founder of an Apache project. I have noticed this 
language used in other places as well e.g. [1]  Also stating an Apache project 
is from a company e.g " from Ververica” [2] is not accurate, again the 
community runs a project not a company. If possible the PPMC should look into 
getting this corrected.

Kind Regards,
Justin

1. https://www.youtube.com/watch?v=AdRuYgtbzrQ
2. https://www.youtube.com/watch?v=7cD7eFzaNew
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] Incubating Proposal for GraphAr

[Justin Mclean]

Hi,

Thanks for checking that, and yes indeed it seems I looked at the wrong repro.

Kind Regards,
Justin

> On 4 Mar 2024, at 6:09 pm, tison  wrote:
> 
> Hi Justin,
> 
> I checked the initial committers group and that is, according to [1][2]
> 
> Initial Committers
> * Weibin Zeng (Alibaba, weibin@gmail.com) -> @acezen #1 in the
> contributor graph
> * Xue Li (Alibaba, lx_cla...@qq.com) -> @lixueclaire #2 in the contributor 
> graph
> * Zhe Wang (Southwest Minzu University, thesp...@qq.com) -> @Thespica
> #3 in the contributor graph
> * Semyon Sinchenko (Raiffeisen Bank International,
> ssinche...@protonmail.com) -> @SemyonSinchenko #5 in the contributor
> graph
> * He Tao (Alibaba, sighing...@gmail.com) -> @sighingnow in the
> contributor graph.
> 
> Starting from #6, commits are <=5. Note that the "main project repo"
> mentioned here is "alibaba/GraphAr" [1].
> 
> It seems you are using alibaba/GraphScope as the source, which is a
> downstream project of the proposed project; it's not included in the
> donation proposal.
> 
> Best,
> tison.
> 
> [1] https://github.com/alibaba/GraphAr/graphs/contributors
> [2] https://cwiki.apache.org/confluence/display/INCUBATOR/GraphArProposal
> 
> Justin Mclean  于2024年3月4日周一 14:59写道：
>> 
>> HI,
>> 
>> I was looking at your initial committer list and noticed, according to 
>> GitHub, that:
>> - sighingnow is #1 in activity
>> - acezen is #6 in activity
>> - lixueclaire is #30 in activity
>> - Thespica is not a commmiter in the main project. Is the repo elsewhere, 
>> and does that intend to be donated to teh ASF?
>> - SemyonSinchenko is not a committer in the main project. Is the repo 
>> elsewhere, and does that intend to be donated to the ASF?
>> 
>> While contributions to a project can be in other forms other than code, I 
>> can count six other people who have made 100+ commits to the main repo. Why 
>> are they not included in the initial committer 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
> 


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

Re: [DISCUSS] Incubating Proposal for GraphAr

[Justin Mclean]

HI,

I was looking at your initial committer list and noticed, according to GitHub, 
that:
- sighingnow is #1 in activity
- acezen is #6 in activity
- lixueclaire is #30 in activity
- Thespica is not a commmiter in the main project. Is the repo elsewhere, and 
does that intend to be donated to teh ASF?
- SemyonSinchenko is not a committer in the main project. Is the repo 
elsewhere, and does that intend to be donated to the ASF?

While contributions to a project can be in other forms other than code, I can 
count six other people who have made 100+ commits to the main repo. Why are 
they not included in the initial committer list?

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

[VOTE] Have Amoro join the Incubator

[Justin Mclean]

Hi,

Following on from the discussion of the Amoro proposal [1][2], let's vote on 
having it join the Incubator.

Please cast your vote:

[ ] +1, have it join the Incubator as an incubating project
[ ] +0, I have no strong opinion either way
[ ] -1, do not have it join the Incubator because...

Kind Regards,
Justin

1. https://cwiki.apache.org/confluence/display/INCUBATOR/AmoroProposal
2. https://lists.apache.org/thread/7t2bm6x19zq2d79cn8jj2wqd3f2t3k00

Re: [DISCUSS] Apache Amoro proposal

[Justin Mclean]

HI,

As the discussion seems to have died down, I’ll put this up for a vote.

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

Re: [DISCUSS] Incubating Proposal for GraphAr

[Justin Mclean]

Hi,

> 2. Slack Channel:
> We intend to continue maintaining the Slack channel as an additional 
> real-time communication platform for both users and developers. Slack 
> provides a convenient and efficient means of real-time communication. It can 
> serve as an additional tool for people to connect with the GraphAr community.

Just be mindful that Slack can’t be used to make decisions that need to happen 
on the project’s mailing list and that not everyone due to work, time zones or 
other reasons can participate in real time conversatons. It would be best if 
you moved to the ASF's Slack instance, as it has a permanent history and is 
managed by the ASF. Out of interest, who currently owns and manages this Slack 
instance?

Kind Regards,
Justin

Re: [DISCUSS] Graduate Apache SDAP (Incubating) as a Top Level Project

[Justin Mclean]

Hi,

+1 (binding) as well - all the best.

Kind Regards,
Justin


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

Re: [VOTE] Graduate Apache Pekko (incubating) as a TLP

[Justin Mclean]

Hi,

+1 from me and best wishes on your journey as a TLP.

Kind Regards,
Justin

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

Re: Podling web sites: .incubator. required?

[Justin Mclean]

HI,

> I would propose that as part of our official policy we recommend the 
> podling's url as https://podling.apache.org and get rid of the .incubator. in 
> the url.
> 
> WDYT?


+1 from me.

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

Re: [NOTICE] Incubation Report for February 2024

[Justin Mclean]

HI,

The report_runbook.py script tells you most of what to do. A few more projects 
need t report than listed below, including some new projects that need to 
report monthly. I’ve also left the monthly properties as is.

The report_email.py script will send an email to this list with the important 
dates, and who needs to report, the report_reminders.py script will send each 
podling a reminder email.

There are some instructions here[1], but they could be improved.

Kind Regards,
Justin

1. https://incubator.apache.org/guides/chair.html

> On 24 Feb 2024, at 1:44 pm, tison  wrote:
> 
> Hi,
> 
> I'm trying to create an Incubation Report page for February 2024 at
> [1], including the following podlings according to the report group
> info that they should report in this month:
> 
> * answer
> * fury
> * horaedb
> * streampark
> 
> But it still lacks information that I need some help:
> 
> 1. What is the desired timeline and shepherd assignments?
> 2. Missing IPMC level report. Perhaps the only way is going through
> the mailing list?
> 3. Missing other projects need a report. I guess we have a script to
> list out from the podling.xml file, but I don't find it. I may write
> it when I have some spare time if there is no one. I don't promise :P
> 
> Best,
> tison.
> 
> [1] https://cwiki.apache.org/confluence/display/INCUBATOR/February2024
> 
> -
> 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] March report timeline - reports due March 2023

[Justin Mclean]

Please ignore this as I put in the wrong year

> On 25 Feb 2024, at 12:12 pm, jmcl...@apache.org wrote:
> 
> Dates for next board report:
> Wed March 01 - Podling reports due by end of day
> Sun March 05 - Shepherd reviews due by end of day
> Sun March 05 - Summary due by end of day
> Tue March 07 - Mentor signoff due by end of day
> Wed March 08 - Report submitted to Board
> Wed March 15 - Board meeting
> 
> 
> Expected to report this month are:
> - baremaps
> - kie
> - marvin-ai
> - nemo
> - nlpcraft
> - opendal
> - pagespeed
> - spot
> - toree
> - training
> - uniffle
> - wayang
> 
> 
> Reports as usual can be submitted here [1]
> 
> Thanks,
> Justin
> 
> 
> 1. https://s.apache.org/incubator-report
> 1. https://cwiki.apache.org/confluence/display/INCUBATOR/Report
> 1. https://cwiki.apache.org/confluence/display/INCUBATOR/March2023
> 
> -
> 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

[DISCUSS] Apache Amoro proposal

[Justin Mclean]

Hi,

I would like to propose a new project to the ASF incubator - Apache Amoro. I’m 
one of the mentors, but there are a lot of other people involved who have done 
all of the hard work.

Amoro is a Lakehouse management system built on open data lake formats like 
Apache Iceberg and Apache Paimon (Incubating). Working with compute engines 
including Apache Flink, Apache Spark, and Trino, Amoro brings pluggable and 
self-managed features for Lakehouse to provide out-of-the-box data warehouse 
experience, and helps data platforms or products easily build infra-decoupled, 
stream-and-batch-fused and lake-native architecture. You can find the proposal 
here. [1]

We are looking forward to anyone's feedback or questions.

Thanks,
Justin

[1] https://cwiki.apache.org/confluence/display/INCUBATOR/AmoroProposal
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: podling reports for January 2024

[Justin Mclean]

Hi,

I’ll sort this out in the next 24 hours.

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

Re: [RESULT][VOTE] Graduate Apache OpenDAL (incubating) as a TLP

[Justin Mclean]

Hi,

> Also, for trademark attribution, I understand the databend.rs, if it
> refers to OpenDAL, it should contain a Footer like Datastax does[2].

Datastax has had recent issues regarding trademarks; please follow the policy, 
not what other 3rd party companies do.

I can see the project, from what you have provided, has fixed a number of 
issues pointed out to them. However, they don’t seem to understand that they 
are responsible for managing their brand and protecting the ASF trademarks.

Kind Regards,
Justin


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

Re: [RESULT][VOTE] Graduate Apache OpenDAL (incubating) as a TLP

[Justin Mclean]

Hi,

The (P)PMC must be able to do this independently. Just look at each of the 
resources you listed and ask yourself:
- Is Apache Foo being used in the most prominent place?
- Are we using the trademark symbol?
- Does the page include trademark attribution for any Apache trademarks used?

Our full trademark policy covers a lot more than this, but that’s a good start.

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

Re: [RESULT][VOTE] Graduate Apache OpenDAL (incubating) as a TLP

[Justin Mclean]

Hi,

I’ll also note that this site (which I assume you have control of) also doesn’t 
comply with our policy. [1]

Kind Regards,
Justin

1. https://xuanwo.io/

Re: [RESULT][VOTE] Graduate Apache OpenDAL (incubating) as a TLP

[Justin Mclean]

Hi,

Several of those pages still do not comply with our trademark policy; the TM 
symbol needs to be used, and a trademark attribution included.

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

Community over code incubator track

[Justin Mclean]

Hi,

There's less than 20 hours to go before submissions close and I'd like to
see some more submissions to the incubator track. Talks about your journey
as an incubating project or if you just want to promote your project are
welcome. Please submit your last minute tasks at
https://sessionize.com/coceu-2024

Kind Regards,
Justin

Re: [QUESTION] Oracle JDBC Driver as a test dependency

[Justin Mclean]

Hi,

> In your source release anything in Category A is fair game.  Things in
> Category B are not.  Things in Category X never are.

While correct, that’s not the full story; you also can’t have anything as a 
dependency whose license is a category X one.

Kind Regards,
Justin

Re: [QUESTION] Handling of licensing issues for dependencies of dependencies

[Justin Mclean]

HI,

> I was performing a more thorough check of our dependencies in preparation of 
> opening graduation discussions with the Incubator PMC and found at least one 
> package that, while not directly used in the code, is installed as a 
> dependency of multiple top-level dependencies that is LGPL licensed. The 
> dependencies that rely on this are themselves not a license issue (BSD-3 & 
> MIT licenses). How is this situation usually handled?

You will need to remove or replace that dependency. 

> I also found a package that has a license that isn't listed on the 3rd party 
> licenses page: HPND [1][2] which, from what I can tell, is similar to the 
> BSD-3 or MIT licenses, though I just wanted to double-check on that...

HPND looks fine to me, as it could be treated as a BSD-like or MIT-like 
license, depending on what parts you include.

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 Celeborn(Incubating) 0.3.2-incubating-rc2

[Justin Mclean]

Hi,

+1 (binding)

I checked in the source release:
- incubating in the name
- signatures and hashes are fine
- DISCLAIMER exists
- LICENSE looks good
- The NOTICE file needs to be updated and likely does not contain all the 
needed information. For example, The Flink Remote Shuffle Project NOTICE 
file[1] contains:
This product includes software developed at The Alibaba Group Holding Ltd
(https://www.alibaba.com/).
- no unexpected binary files.
- all files have ASF headers
- can compile from source

Kind Regards,
Justin

1. https://github.com/flink-extended/flink-remote-shuffle/blob/main/NOTICE
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [RESULT][VOTE] Release Apache OpenDAL, incubating, 0.44.0-rc.1 - Incubator Vote Round 1

[Justin Mclean]

Hi,

It’s best to wait for 72 hours before closing a vote.

Kind Regards,
Justin

> On 31 Dec 2023, at 1:19 pm, Liuqing Yue  wrote:
> 
> Hi Incubator PMC,
> 
> The vote to release Apache OpenDAL(incubating) 0.44.0-rc.1 has passed with
> 3 +1 binding and 1 +1 non-binding votes, no +0 or -1 votes.
> 
> Binding votes：
> 
> - tison
> - Sheng Wu
> - He Xiaoqiao
> 
> Non-Binding votes:
> 
> - Xuanwo
> 
> Vote thread: https://lists.apache.org/thread/dpb2lzjdgcmz4j68s5ksklp9m9xcdcf4
> 
> Thanks for reviewing and voting for our release candidate.
> 
> We will proceed with publishing the approved artifacts and sending out
> the announcement soon.
> 
> Thanks
> 
> Liuqing
> 
> -
> 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 OpenDAL (incubating) as a TLP - Incubator

[Justin Mclean]

Hi,

> If today, someone on the internet, for any reason, buys a domain name
> and redirects it to opendal.apache.org. You don't even have contact to
> that person. Do you still argue that the PMC should take control of
> that domain?

Of course not, the issue is not with redirecting a domain. The issue mostly 
exists with existing domains. A 3rd party, if they had control of a domain 
name, foo.x.com could stop redirecting it to foo.apache.org and point foo.x.com 
at their own competing product. If that domain was well known and used by the 
community around foo, that would most likely be an issue.


> The case becomes complex when web saas involved. Anyone can possibly
> build a {user-id}.github.io or {app-name}.vercel.com and redirects it
> to opendal.apache.org in a few minutes.
> 
> If you said, these are violations so the PMC should spend time
> investigating and trying to take them down. This sounds reasonable,
> but of course, if you cannot find the person, you can hardly take it
> down, Negotiating with the saas provider can take a lot of time and
> they may not support your requirement.

Just about all providers have take-down mechanisms we can use if the name is 
one of our trademarks. If a PMC found itself in this position, the owner wasn't 
responsive, and the site’s content was in clear violation of our policy, it 
would be best to involve trademarks to help and it’s a fairly straightforward 
matter to request the site to be taken down.

Kind Regards,
Justin


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

Re: [DISCUSS] Graduate Apache OpenDAL (incubating) as a TLP - Incubator

[Justin Mclean]

Hi,

> As an analogy, think of answer.dev and answer.apache.org. You are in
> the thread of a similar situation[1].

This projct has just entered incubation and is not seeking to graduate. It will 
need to hand over ownership of that domain name before it does.

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

Re: Update project maturity model to include trademark and branding?

[Justin Mclean]

HI,

>> TB40 The project performs some monitoring of 3rd party use of its 
>> trademarks, addressing any instances of misuse.
> 
> Do you have some examples of how podlings or TLPs perform this today?

This varies from project to project:
- Some projects have PMC members working at a company who use their trademark, 
and they make sure that things are correctly done.
- Some projects have people who actively look out for these types of issues and 
report them.
- Some projects are more active and set up automated Google searches and the 
like.
- Not all issues occur on web pages. Some of these issues arise at conferences 
or 3rd party events and are often noticed by PMC members or ASF members.

> It's unclear to me how I can understand and follow this guideline:
> Shall the PMC check over the Internet? Is any 3rd party even with a
> very low page rank should the PMC spend time to address it; or else
> the PMC fail to meet this guideline?

Yes, in most cases, the PMC should spend time addressing it. This is described 
in full at [1], how the project wishes to implement this is up to them.

Kind Regards,
Justin

1. https://www.apache.org/foundation/marks/responsibility

Re: [VOTE] Graduate Apache OpenDAL (incubating) as a TLP - Incubator

[Justin Mclean]

Hi,

> As for branding and trademarks, the OpenDAL (P)PMC is actively
> handling known issues, including Anything referred in...

I’m not sure they are. What about, for instance, various download pages e.g. 
[1] and the ownership of the opendal.databend.rs  
domain name?

IMO, It would be best to delay the vote until after these issues have been 
resolved.

Kind Regards,
Justin


1. https://pypi.org/project/opendal/

Update project maturity model to include trademark and branding?

[Justin Mclean]

Hi,

It seems the updated podling report template has not had the impact it was 
hoped to have around issues of branding and trademarks.

It was pointed out on the trademark list that the current maturity model [1]  
is missing checks for trademarks and branding.

Here is my first attempt at it; feedback, thoughts, etc, are welcome.

Trademarks and Branding
TB10 The project correctly uses “Apache Foo” as the project name where required.
TB20 The project complies with ASF’s branding and trademark policy in all 
places it controls.*
TB30 The project resolves any potential trademark issue pointed out to it 
promptly.
TB40 The project performs some monitoring of 3rd party use of its trademarks, 
addressing any instances of misuse.

* Including its website, documentation, 3rd party download services or any 
other locations.

With some changes and increased focus on security, we might want to review the 
existing points that mention security.

Kind Regards,
Justin

1. https://community.apache.org/apache-way/apache-project-maturity-model.html


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

Re: [VOTE] Graduate Apache OpenDAL (incubating) as a TLP - Incubator

[Justin Mclean]

Hi,

-1 (binding) until the branding and trademark issues have been resolved and the 
podling has a better understanding of what is involved here.

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

Re: [DISCUSS] Branding in Thirdparty Platform Distribution

[Justin Mclean]

HI,


> Users should run `npm install xxx`, `pip install xxx`, or `cargo add xxx` 
> to include our library in their dependency list. Users should write code 
> in their own libraries or applications using statements such as `use xxx` 
> or `import xxx`. Adding the prefixes `apache-` or `asf-` could significantly
> increase the workload for the entire community. In severe cases, users may 
> halt library updates to prevent having to replace `xxx` throughout their code.

This is no different to any project that comes to the ASF via the incubator. 
Many of them need to change names, often before joining the incubator, and all 
need to change their name to be in the form “Apache Foo”.

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

Re: [DISCUSS] Graduate Apache OpenDAL (incubating) as a TLP - Incubator

[Justin Mclean]

Hi,

> The domain `opendal.databend.rs` is owned by Databend Labs and was used as 
> the 
> primary domain before OpenDAL entered the incubation stage. The PMC will 
> coordinate
> with Databend Labs to ensure that all instances are updated to 
> `opendal.apache.org`.

It would be best if the domain was controlled by the (P)PMC. Having a 3rd party 
in control of a domain that currently redirects to the ASF site is not ideal. 

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

Re: [DISCUSS] Graduate Apache OpenDAL (incubating) as a TLP - Incubator

[Justin Mclean]

Hi,

> Thanks for your reply to report potential branding issues. The PMC is
> actively responding to these comments.
> 
> * https://github.com/apache/incubator-opendal/pull/3829/files
> * https://github.com/apache/incubator-opendal/pull/3830/files
> * https://github.com/apache/incubator-opendal/pull/3831/files
> * https://github.com/apache/incubator-opendal/pull/3833/files
> * https://github.com/apache/incubator-opendal/pull/3838/files

Thanks for that.

> For third-party references, when a PMC member notices one that can be
> confusing, there is a reaction:
> 
> * https://github.com/GreptimeTeam/greptimedb/pull/2653/files
> * https://github.com/zwpaper/dilu/pull/1/files
> * https://github.com/datafuselabs/databend-docs/pull/285/files

I noticed the domain opendal.databend.rs mentioned there. Who owns that domain?

> These are instances for "manage its brand and ASF’s trademarks". I
> believe that the PMC becomes more experienced on branding topics with
> your reports; thank you.

The point is I shouldn't have to report these; the (P)PMC should be managing 
this on their own.

>>> About the https://opendal.apache.org/docs/python/opendal.html,
>>> Please see https://incubator.apache.org/guides/distribution.html.
> 
> The first sentence of this page currently is "Apache OpenDAL™ Python binding".

But the first and more prominent mention of OpenDAL doesn’t include Apache. The 
page is also missing mention of ASF’s trademarks. I think you need a little 
more branding and naming is needed to comply with ASF's policy.

Other pages I click on have no mention of Apache. e.g. 
https://opendal.apache.org/docs/python/opendal/layers.html Other document pages 
have similar issues, e.g. https://opendal.apache.org/docs/haskell/OpenDAL.html. 
I think a little more work needs to be done here, and again, I shouldn't have 
to point out the issues. Please look at your documentation and the policy and 
see what needs to be fixed, or better still, discuss it on your mailing list. 
It’s far better that you work out what needs to be corrected on your own than 
for someone outside your project to list what might not be in line with policy.

> As for the package name, I argued for the current guidelines in [1]
> that you can follow. You may have different opinions and that's OK.
> Xuanwo explained more technical details and community feedback in [1].

Other projects have different reasons for doing what they do; don’t confuse 
that with permission to do what they do without a reason.

Kind Regards,
Justin

Re: [VOTE] Release Apache Celeborn(Incubating) 0.3.2-incubating-rc1

[Justin Mclean]

Hi,

> We just checked their repo and found the PR[1] which added Celeborn's code
> in their repo. We got in touch with them and they told us that the code was
> deleted a month ago. I also checked their release[2] and didn't find
> Celeborn's code in their source ball. So I guess this is no longer a
> problem?

Thanks for looking into that; that looks to be a non-issue. Can anyone answer 
my other questions?

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

Re: [DISCUSS] Branding in Thirdparty Platform Distribution

[Justin Mclean]

Hi,

> The proposal here is to improve the expression on NPM / PyPI for the
> package name to be either:
> 
> 1. apache-projectname
> 2. projectname

Existing ASF policy has this to say:
- "All PMCs must to comply with the Apache Project Branding Requirements.” [1]
- “PMCs are directly responsible for ensuring all of their project's web 
content complies with the Apache Project Branding Requirements.” [2]
- "PMCs are responsible for evaluating and if needed addressing any infringing 
use of their project's marks by third parties” [3]

In regards to naming:
- "All top level projects (TLPs) must use the format Apache Foo for their 
branding” [4]
- "The primary branding for any project or product name must be in the form of 
"Apache Projectname”. " [5]
- "The first and most prominent references to a project or product on every 
page, and uses in page titles or headers, must use the "Apache Projectname" 
form of the name. “ [5]

This is one reason why every single poding report asks, “Is the PPMC managing 
the podling's brand / trademarks?”.

In short, IMO, using the short name would not be in line with current policy, 
but that is probably more of a question for trademarks. For instance, it might 
be OK if the page made it very clear that this was an ASF project and the users 
were downloading “Apache Foo” and included appropriate trademark attribution.

Kind Regards,
Justin

1. https://www.apache.org/foundation/marks/responsibility#compliance
2. https://www.apache.org/foundation/marks/responsibility.html#website
3. https://www.apache.org/foundation/marks/responsibility.html#police
4. https://www.apache.org/foundation/marks/pmcs#naming
5. https://www.apache.org/foundation/marks/pmcs#branding



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

Re: [DISCUSS] Branding in Thirdparty Platform Distribution

[Justin Mclean]

Hi,

I’ll note these guidelines were discussed and voted on by the IPMC a while 
back. Legal and trademarks also reviewed them and had input, and the work is 
based on existing policy and years of discussion. They, however, have only had 
minor updates since being formed.

Kind Regards,
Justin


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

Re: [DISCUSS] Graduate Apache OpenDAL (incubating) as a TLP - Incubator

[Justin Mclean]

Hi,

-1 (binding) to graduation, the PMC needs to understand the importance of and 
follow our randing policy; something seems to have been missed here.

> About the  https://opendal.apache.org/docs/python/opendal.html, it is
> already on the apache.org site. It is obvious that it belongs to the
> ASF.

As part of the website, it needs to follow the ASF branding guidelines; there 
are no expectations.

> About other distribution platforms, using short names, rather than
> apache or asf prefixes is a common practice.

Please see https://incubator.apache.org/guides/distribution.html. It should not 
be common practice.

> For other projects, which are not controlled by the committers, it
> takes time to add Apache. None of the found ones seem to hurt ASF
> branding.

The PMC needs to manage its brand and ASF’s trademarks, registered or 
otherwise; it seems they have not been doing so.

Kind Regards,
Justin

Re: [DISCUSS] Graduate Apache OpenDAL (incubating) as a TLP - Incubator

[Justin Mclean]

HI,


>> 2. https://opendal.apache.org/docs/python/opendal.html

This is not fixed. I suggest the PMC members have a good read of our branding 
policy to understand what is needed here. [1] At a minimum, the project needs 
to be referred to as “Apache OpenDAL”, and the trademark attribution needs to 
be added. Please see [2] as well, in particular [3] and [4], but there are 
other issues here as well.

> NOTE: pypi.org, crates.io, docs.rs will be updated after our next release 
> published.

Can you fix the description and add the trademark attributions without making a 
release?

Kind Regards,
Justin

1. https://www.apache.org/foundation/marks/responsibility
2. https://www.apache.org/foundation/marks/pmcs
3. https://www.apache.org/foundation/marks/pmcs#naming
4. https://www.apache.org/foundation/marks/pmcs#attributions

Re: [LICENSE QUESTION] Use jmh as a benchmark tool

[Justin Mclean]

Hi,

As listed in that document, a GPL license with a classpath exception is 
category X, so everything that applies to other category X licenses applies to 
that license. System dependencies that users or developers typically have 
installed that don't impact the license of the compiled package are generally 
OK, so most versions of Java are OK.

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 Celeborn(Incubating) 0.3.2-incubating-rc1

[Justin Mclean]

Hi,

Sorry, but it is -1 (binding) for now. Clearing up some of the issues below may 
mean that I change my vote.

I checked
- incubating in artifact name
- signatures and hashes are correct
- LICENSE mentions 1 3rd party file from Guava; however, the NOTICE lists both 
Apache Spark and Apache Flink, so I think other files may have been copied into 
the code base, and LICENSE is missing information or the NOTICE is incorrect.
- There is some overlap with some files with [1]; this is concerning as these 
files are under a GPL license. Would you happen to know who has copied from 
whom here? If ASF files have been re-licensed under the GPL license, what is 
the PMC doing about this? What is the relationship, if any, between this 
company and the PMC?
- This file [2] seems to have been copied from Kyuubi?
- No unexpected binary files
- All files have correct source headers
- I didn't compile from the source

Kind Regards,
Justin

1. https://github.com/alldatacenter/alldata
2. /dev/checkout_pr.sh

Re: [VOTE] Release Apache HugeGraph (Incubating) 1.2.0 rc1

[Justin Mclean]

Hi,

+1  (binding)

I checked all source releases.

- incubating in names
- all release include LICENSE, NOTICE and DISCLAIMER
- The NOTICE file for huge graph-computer could be improved, as it contains 
unnecessary information. "Copyright 2012 and onwards JanusGraph Authors” is 
clearly not correct.
- The NOTICE file for the main source release duplicate information, i.e. "This 
product includes software developed at The Apache Software Foundation 
(http://www.apache.org/).” and also includes text that is not required.
- No unexpected binary files
- All files have correct headers, except this file might have an incorrect 
header. [1]
- was unable to compile but probably my setup

Kind Regards,
Justin

1. ./hugegraph-server/hugegraph-dist/src/assembly/static/bin/wait-storage.sh


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