Hi,
If you look at [1] you notice it states "Modified Apache 2.0 License” so this
is actually not an Apache license and it should not be called that.
Justin
1. https://github.com/PixarAnimationStudios/USD/blob/release/LICENSE.txt
Hi,
> 1. All flaticon icons [1] are replaced with blueprintjs icons [2] that have
> Apache 2.0 license.
You may need to double check that, this has come up before and they where using
a modified version of the Apache license.[1]
> 2. For images created by ourselves, do we need to formally
Hi,
Sorry but it’s -1 (binding) from me.
I checked:
- incubating in names
- signature and hashes are correct, although you name want to rename it from
"test key for apache”
- LICENSE is missing license information from [1]
- NOTICE is fine
- Looks like this file incorrectly has an ASF header on
Hi,
> And to be sure, we should go through the community vote step again before
> making another voting thread in general@incubator.apache.org. Is this
> correct? Thanks in advance!
Yes your PPMC will ned to vote on the new release candidate before bringing it
for a vote by the incubator PMC.
Hi,
Sorry but t’s -1 (binding) from me. There are a number of icons and other PNG
files in the release and their license is not included in the LICENSE file.
I’ve not checked them all but some seem to come from [1], not that attribution
is required and that the license may not be compatible
Hi,
In this release I noticed a number of png files that look to be icons or logos.
Where did these files come from and how are they licensed?
Kind Regards,
Justin
-
To unsubscribe, e-mail:
HI,
+1 (binding)
Kind Regards,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
HI,
For me it dies in step 18:
[INFO] Apache InLong - TubeMQ Docker All .. FAILURE [ 0.010 s]
With:
Could not resolve dependencies for project
org.apache.inlong:tubemq-all:pom:1.2.0-incubating: Failure to find
org.apache.inlong:tubemq-server:tar.gz:bin:1.2.0-incubating
Kind
Hi,
+1 (binding)
I checked:
- incubating in name
- signatures and hashes are correct
- LICENSE and NOTICE are file
- No unexpected binary files
- ASF file have ASF headers
- Couldn't compile from source but probably just my setup
Kind Regards,
Justin
Hi,
Depends on what you mean by short. The process can be seen here in the cookbook
[2]. We also have Apache Way and incubator talks recording from previous
ApacheCons that may be useful. There’s some older talks linked to here (under
Incubator Talks). [1]
Kind Regards,
Justin
1.
Hi,
> We have released quite a few versions before entering the incubator.
> After entering the Apache incubator and making a project rename,
> we kept the soul 2.3.0 version document [1] on the website.
> Do we need to delete it?
I would just make it clear it’s not an Apache release.
Kind
Hi,
+1 (binding)
I checked:
- incubating in name
- signatures and hashes are correct
- LICENSE and NOTICE are fine
- no unexpected binary files
- all ASF files have ASF headers
- can compile from source
Kind Regards,
Justin
Hi,
Looks good to me.
A couple of very minor things:
- I noticed 5 releases mentioned on your website, not 4, does one of them
predate Incubation?
- These [1][2] could do with a bit more information about the project.
- It would be nice if the name was updated to “Apache Shenyu” here [3]
Kind
Hi,
+1 (binding)
I checked:
- incubating in name
- signatures and hashes are fine
- LICENSE looks good (but I did not check everything)
- NOTICE is fine but it would be good to update the year
- ASF files have ASF headers
- No unexpected binary files
- I didn’t compile from source
Kind Regards,
Hi,
Can someone on the project please respond to this.
Kind Regards,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
Hi,
I’ve put together a talk list for the next month incubator report [1] Do we
have any volunteers willing to help out? If so just put your name next tp a
task.
If you need more detail on how to do a task just ask. The report run book
report_reminders.py and these pages [2][3] can also help.
Hi,
The report has been submitted and currently the follow podlings will be asked
to report next month:
• Hivemall
• SDAP
• Spot
• MarvinAI (did not get mentor sign off)
• Livy
- Nemo
Nemo asked to report next month. Livy is in the process of
Hi,
> Thanks for your review. I still have some questions, I don't know if
> the IPMC departure is based on the date of the send email to leave, or
> whimsy, in fact, Kevin A. McGrail was already on the list to leave the
> IPMC last month.
It's probably not that important which date is used,
Hi,
Calvin thanks for your help in putting the report together, I’ve added a little
more detail (including information on Doris) and reviewed what you submitted.
Kind Regards,
Justin
-
To unsubscribe, e-mail:
Hi,
+1 (binding)
Kind Regards,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
Hi,
> This is a little confusing, since mentor sign off isn't due until Tuesday.
That is correct mentors still have time to sign off reports, sorry I should
have made that clearer.
Thanks,
Justin
-
To unsubscribe, e-mail:
Hi,
Thanks for that I’ll review later today.
Kind Regards,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
Hi,
We are missing reports from:
- Hivemall*
- Livy*
- Nemo
- SDAP*
- Spot
We are missing mentor sign off on:
- Kyuubi
- Marvin-AI
- PonyMail*
- DevLake
* Also did not report last month
Kind Regards,
Justin
-
To unsubscribe,
Hi,
Sorry for the delay in checking the but I am also -1 binding as I can’t verify
the signature and teh disclaimer is missing.
I checked:
- incubating in name
- while sha512 is correct it looks like the signature is missing from the KEYS
file
- DISCLAIMER is missing
- LICENSE looks fine (but
HI,
Depending on who is involved in the project, it may not even require to go
through the incubator again. Having more details would help with this.
Kind Regards,
Justin
-
To unsubscribe, e-mail:
Hi,
It is also a little odd that the graduation process (including the vote on the
dev list) is being driven by someone who is not on the PPMC of the project. Is
there any reason for this?
Kind Regards,
Justin
-
To
Hi,
> We have made a lot of progress in the last few weeks on the outstanding
> items you identified in your last email[1]. We have already made changes to
> the AWS-owned offerings on the marketplace to ensure we are in compliance.
A quick search still shows there are issues there by other 3rd
Hi,
There are a number of trademark issues that have been outstanding for a long
time, sometime these can take time to resolve, but we have PPMC members
involved in some of those companies.
The MXNet website doesn’t follow ASF policy on how to use it own name, so this
may be a part of the
Hi,
> And I have suggested to skip the pod report of brpc this month,
> Because I have submit the pod report last month.
It would be best if they did report this month, otherwise they will be asked to
report next month.
Kind Regards,
Justin
Hi,
The podling report are due today and we are missing:
BRCP
Hivemall
Kvrocks
Kyuubi*
Livy
Marvin-AI
Nemo
PonyMail
SDAP
Spot
Wayang
If you are a mentor of one of the above projects could you please encourage
them to submit a report as soon as they can.
Kind Regards,
Justin
* Has a draft/work
Hi,
+1 (binding) if you need help with anything please ask on the list
Kind Regards,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
Hi,
I’ll review and help where needed.
Kind Regards,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
Hi,
Out of interest how many of the new proposed PMC are involved with the
StarRocks project?
Kind Regards,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail:
Hi,
+1 (binding). Best of luck in your journey as a top level project!
Kind Regards,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
Hi,
Thanks for offering to help. To help manage who does what I’ve created a page
here [1] just put your name next to something if you want to do it. If you need
help with anything just ask.
Kind Regards,
Justin
1.
Hi,
+1 binding
I checked:
- incubating in name
- signatures and hashes correct
- disclaimer exists
- LICENSE and notice are file
- all ASF source files have ASF headers
- no unexpected binary files
- can compile from source
Kind Regards,
Justin
Hi,
> There’s a typo in this paragraph that makes it impossible to
> understand/changes the original meaning.
Apologies I meant to say "I don’t think that is the case.”. From what I can see
trademarks have not approved FireStorm as a name. If the project wants to enter
the incubator with that
Hi,
> After the board meeting:
> - Update podlings.xml to mark podling that did not report, ones whose report
> was missing but reported and podlings at the end of their monthly reporting
> period
> - assign podling shepherds using assign_shepherds.py
> - run clutch script (./clutch2.sh) and
Hi,
The issue was the future assuagement of shepherds, so I fixed that and I’ll
resend the reminders. This may mean that a couple of podlings got a reminder
when they don’t need to report. If you are not listed in the wiki there no need
to submit a report.
Kind Regards,
Justin
HI,
Look like there's a small issue with the Incubator reminder script and it send
out some reminders to the wrong podlings. What was listed in the wiki is
correct.
Kind Regards,
Justin
-
To unsubscribe, e-mail:
Hi,
Please submit your podling reports here [1]
Reporting timeline is:
Wed June 1st -- Podling reports due by end of day
Sun June 5th -- Shepherd reviews due by end of day
Sun June 5th -- Summary due by end of day
Tue June 7th -- Mentor signoff due by end of day
Wed June 8th
HI,
> According to the trademarks@ current cursory feedback, looks like project
> name "Firestorm" is OK.
I don’t this that is the case. Trademark checked “FlameStorm”, and said that if
Firestorm was as issue then FlameStorm would also be an issue. I don’t believe
they have checked FireStorm.
Hi,
> We have reached out to a few companies that were in violation, but have not
> yet received any indication that they will fix them.
Despite having PPMC members who work for those companies?
> In this case, what are your suggestions on how to deal with these? Do we have
> legal resources
Hi,
The project was aware of these issues before the graduation proposal was
submitted, and some issues had been outstanding for more than a year. I
understand it can be complex and take time dealing with 3rd parties about these
issues, but I do have to ask if there are people from StarRocks
Hi,
The call for presentations For ApacheCon North America ends in at few days on
00:01 UTC on May 23rd, 2022. If you like to submit a talk about an incubating
project or the incubator itself please do so at https://cfp.apachecon.com/.
Kind Regards,
Justin
Hi,
> It’s a bit different from my impression, could I know it’s fine to have many
> projects sharing much similar functions or aiming in parallel here?
It's 100% fine and we have many TLP that do similar things as each other.
Kind Regards,
Justin
Hi,
It would be good if the project could work together, but there isn’t anything
wrong with having two similar incubating projects. If the projects decide not
to join forces, we would welcome an incubating proposal from the other project.
The ASF doesn't pick projects to use, we let the wider
Hi,
I’d run that past trademarks@ mailing list. It might be like calling your fast
food restaurant McDoogles and hoping no-one notices the name is similar to
McDonalds.
Kind Regards,
Justin
-
To unsubscribe, e-mail:
Hi,
The new project name doesn’t need to be a registered trademark, but you would
still need to pick a name that is now likely to have any trademark issues.
The project may want to get the ASF to register the mark at a later date, but
it wold be best to talk abut that on the trademarks@ list.
Hi,
> Thanks for your reply. The trademark "firestorm" as a software has already
> been submitted the registration by Tencent in China, I'm not sure is that
> enough or not.
If that trademark is approved it would need to be transferred to the ASF before
graduation. Even f it was approved there
Hi,
> But the py file is still missing license headers and have different
> authors[2]. We don't know how to solve this problem.
You may need to look at the history f the files to see if that provide some
clues or how contributions to the project are licensed. You could also contact
the
Hi,
Sounds like an interesting project. I also think the name may be problematic
from a trademark point of view. It might be best to do a trademark search as
see if there are any issues. Changing the name is difficult, but is much much
harder if it needs to be done later.
Kind Regards,
HI,
There is also an issue with the naming and use of ASF trademark of this product:
https://github.com/StarRocks/flink-connector-starrocks
And this:
https://github.com/StarRocks/apache-orc
And this:
https://github.com/StarRocks/spark-starrocks-connector
Kind Regards,
Justin
HI,
> I searched their website and found this is a link "trademarks"[1] at the
> bottom of every page. Does this meet the requirements?
No as explained before it does not. Most of the answers can be found in the
trademark FAQ including [1][2][3] There are further issues with pages like [4].
Hi,
Some are recent (in 2022) but I don’t know how or if the author(s) are related
to either project. Taking one at random [1] it was published on 15-5-2022 and
looks to me not following ASF trademark policy and potentially misleading
users, although It’s hard to say for certain as I can only
Hi,
Thanks for the update on the trademark transfer.
There are still some branding and trademark issues outstanding, a simple google
search shows this. e.g. search for "Baidu Doris" or "DorisDB". For instance,
this page (updated 4 days ago) [1] or this page [2] (updated 7 days ago) and
Hi,
In short:
- There are still some trademark and branding issues, including some that the
PPMC have been made aware of and have been outstanding for more than a year.
- Have the Doris trademark(s) been transferred to the ASF? AFAIK they have not.
[1][2] This issue has also been brought up wth
Hi,
Thanks for promptly fixing that branding issue. However, there are still a few
unanswered questions here, and until they are answered, I’m -1 on graduation to
TLP. Perhaps one of the podling mentors or PPMC members could answer?
Kind Regards,
Justin
Hi,
It looks like some of the previous trademark/branding issues that have been
raised (around a year ago) still need to be resolved. What is the status with
this?
For instance:
https://cloud-tencent-com.translate.goog/product/cdwdoris?_x_tr_sl=auto&_x_tr_tl=en&_x_tr_hl=en-US&_x_tr_pto=wapp
HI,
One other issue is trademark ownership, previously it been stated that Baidu
owns the Doris trademark in China. Have this trademark been transferred to the
ASF? [1][2]
Kind Regards,
Justin
1. https://www.apache.org/foundation/marks/faq/#incubator
2.
Hi,
> 2. I didn't find ASF branding issue on this site[2]. Could you help to point
> out?
There are several issues but in general this is not being followed [1] So in
short use of trademark symbol and missing trademark disclaimer,
Kind Regards,
Justin
1.
Hi,
> Could the ASF Foundation Legal Department have **more effective** support
> on trademark issues?
I’m not sure that the project has involved trademarks to provide support. I
certainly found a few things that I was unaware of and that had not been
mentioned in the project reports.
> As
Hi,
>> I confirmed in the py4j-0.10.7-src.zip file, and the backport.py file
>> clearly states that it is all licensed under the PSF License.
>>
>> So can it be considered that py4j-0.10.7-src.zip is licensed under
>> BDS license, except that backport.py is under PSF license
I would double
Hi,
I've brought up the StarRocks header license issue on the legal discuss mailing
list, to see what can be done about it.
Kind Regards,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional
Hi,
> 2. LICENSE is missing license from files in this zip It’s looks like
> they are under the PSF License not the BSD license.
> The license of the file py4j-0.10.7-src.zip does specify the BSD
> license on their official website [1]
> We specify py4j-0.10.7-src.zip in the LICENSE file under
Hi,
It’s easy enough to change the headings, we would need to regenerate the
pre-generated reports but’s that’s not a big deal.
The first change seems fine to me, for the second we might what to come up with
something shorter.
Note that when we have tweaked the titles in the past, it tends to
Hi,
I think there may still be some issues around DorisDB [1] and StarRocks,
although these might not be a graduation issues.
For instance StarRocks claims it’s "Free and Open Software” but it actually
under the Elastic License 2.0.
There are some minor ASF branding/trademark issues on their
Hi,
+1 (binding)
I checked:
- incubating in name
- signatures and hashes are fine
- disclaimer exists
- LICENSE and NOTICE are good
- All source files files have ASF headers
- No unexpected binary files
Kind Regards,
Justin
-
Hi,
Sorry but it’s -1 binding from me as there a binary in the source release.
There’s also a minor license issue.
I also notice you have 5 mentors, have you asked them to check the release?
It also looks like to me that the binary license and notice file are listing
all dependancies rather
Hi,
Perhaps this helps or clarifies? The wiki uses markup where whitespace is not
that important for displaying content. It will mostly display the same no
matter where new lines or spaces are. In the board report whitespace / line
length matters and we have tools that depend on the report
Hi,
> - Confluence version doesn't appear reformatted
I’m not sure what you mean here, confluence was having issues saving updates so
that may be a symptom of that? In general the reformatting has no impact on the
wiki page itself but does on the board report.
> - Marvin-AI, Spot have no
Hi,
As noted here [2] the board report should not be the sole responsibility of the
chair to put together.
Here's what is roughly needed for each board report.
After the board meeting:
- Update podlings.xml to mark podling that did not report, ones whose report
was missing but reported and
Hi,
You are currently down to report this month as the report attribute in
podlings.xml is set too true. This is probably an error. The incubator has also
missed a couple of reports, and that has caused some confusion. Your report has
been included in the Incubator report submitted to the
Hi,
Thanks for the clarification.
Kind Regards,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
Hi,
I’ve submitted the report, if any last minute changes need to be made then they
can be made in whimsy.
Kind Regards,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail:
Hi,
In general, votes should last 72 hours to allow people to respond. It is
unusual for a graduation vote to only be held for 24 hours. Is there any reason
for needed for the short voting time?
Kind Regards,
Justin
-
To
Hi,
> I don't believe this is the issue
I believe it is. If you modify the Json and rerun the clutch you’ll notice it
updates content/clutch/podlings_graduated.txt. Other script like report_who.py
no longer list YuniKorn as needing to report.
Kind Regards,
Justin
HI,
The AWS Marketplace also looks to have multiple issues. I note this was
discussed on your private list some time back.
https://aws.amazon.com/marketplace/search/results?searchTerms=MxNet
Kind Regards,
Justin
-
To
Hi,
> 2. A lot of the processes error'd out, assuming they're one time runs.
> Because the entire year's worth of reports were pre-made, it doesn't work
> right. Some of what I noticed:
>
> - I can't rerun shepherd assignments (I had to delete the entry in the json
> file)
Once generated, you
Hi,
The page history and page comparison helps a bit but it’s still not great. The
TLP reporting tool would need support for some extra fields and ability for
mentor sign off before it could be used.
Kind Regards,
Justin
-
To
Hi,
A while back when I looked at the MxNet project there seemed to be a lot of
trademark and branding issues. Have theses been addressed by the project?
A quick google search seems to show they may not have been and some more work
is needed here?
https://hub.docker.com/u/mxnet
HI,
Confluence decided to come good so the text is now updated in there as well.
Kind Regards,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail:
(eventmesh) Justin Mclean
Comments:
- [ ] (eventmesh) Von Gosling
Comments:
### IPMC/Shepherd notes:
## Flagon
Flagon is a software tool usability testing platform
Flagon has been incubating since 2016-07-13.
### Three most important unfinished issues to addr
Hi,
For the incubator report I did the following:
- Reflowed
- Fixed up the formatting
- Removed the extra text for the "Have your mentors been helpful and
responsive?” and "Is the PPMC managing the podling's brand / trademarks?”
questions.
- Signed off my podlings
- Removed non reporting
Hi John,
Thanks for putting this together, much appreciated. I notice there’s some
formatting that still ned to be corrected before it can be submitted, there are
tools that rely on this formatting so I take a look and fix for you* in the
next 1/2 hour.
Kind Regards
Justin
* There some
HI,
Also the vote is open for a minimum of 72 hours. There should be no reason to
extend it, it ends when you have enough +1 votes and more +1 than -1’s.
Kind Regards,
Justin
-
To unsubscribe, e-mail:
Hi,
If you have time to report then I would do so.
Kind Regards,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
Hi,
> Some source code files are cherry picked from that 'mxparser' library and
> redistributed, both in Source and Binary forms, as part of that 'stax'
> library.
Which may be fine it just depends on the license of each file in question.
Knowing where they are originally from is nice but not
Hi.
> These Non-Generated Sources Files with the "Extreme! Lab, Indiana
> University" license:
> - com/bea/xml/stream/MXParser.java
This is probably OK but that legal JIRA hasn’t been resolved.
> These Non-Generated Sources Files have "Copyright (c) 2002 by BEA Systems.
> All Rights Reserved."
Hi,
Looking at the source jar at [1] it contains the Apache 2.0 license and the non
generated source files files have Apache headers so I think we can say this is
OK.
Kind Regards,
Justin
1. https://repo1.maven.org/maven2/stax/stax/1.2.0/
Hi,
> stax:stax:jar:1.2.0 is not used directly by DataLab but as a dependency of
> com.azure:azure-identity:jar:1.3.0:compile that has MIT license
The license of stax:stax:jar:1.2.0 is what is relevant here, just because it is
a dependancy of a MIT licensed jar doesn’t make it acceptable. Do
Hi,
> I went to sign off on Pony Mail's report and I noticed clicking on their
> report from the TOC doesn't bring me to their section. It does for the few
> other podlings I checked. Is it because it's spelled "Pony Mail" but the
> link goes to "#ponymail” ?
Yep that the issue I generally
Hi,
The incubation list for for conversations about new project proposals, releases
and graduations and similar things. I think this thread has got off topic and
you should probably carry on the conversation back on the logging project lists.
Building a community around EOLed software, even if
HI,
> The connector is released to maven for the convenience of users. It is not
> a new version of Doris. It is base on Doris 0.15 release.
It may be based on 0.15 but would contain other bits of unreleased code right?
If so it needs to follow the normal release process. See [1], [2] and [3].
Hi,
> as Sebb mentioned, some PPMC members might have used an email that is not
> recognized by LDAP.
The extra subscribers are yourself and John Gemignani, who both are also
subscribed to the list.
> I already reached out to them and asked them to double check.
Currently Jasper Blues, Nick
Hi,
> This problem with -LICENSE and NOTIC , do we need to remove the licenses
> and notices of Category B and X?
Only licenses from software included in the source release need to be mentioned
in LICENSE and NOTICE not all dependancies. This may make the LICENSE file
different for the
Hi,
+1 (binding)
I checked:
- incubating in name
- signatures and hashes are fine
- DISCLAIMER exists
- LICENSE and NOTICE are correct
- No unexpected binary files
- all source files have ASF headers
- can compile from source
Kind Regards,
Justin
Hi,
The official release area is
https://dist.apache.org/repos/dist/dev/incubator/doris/ not maven. This email
should also include a link to your KEYS file and to the vote on your dev list.
Kind Regards,
Justin
-
To
Hi,
Sorry but t’s -1 binding from me.
I checked:
- incubating in name
- signatures and hashes are fine
- DISCLAIMER exists
- LICENSE and NOTICE are not correct and include licenses that are not Category
A licenses. One;y code that is Category A can be included in a source release
and there
Hi,
> * Dehowe Feng
> * Eya Badal
> * Felix Cheung
> * Jasper Blues
> * John Gemignani
> * Josh Innis
> * Juan Pan
> * Kevin Ratnasekera
> * Mason Sharp
> * Nick Sorrell
> * Pieterjan De Potter
> * Raphael
301 - 400 of 3327 matches
Mail list logo
