Re: Proposed Resolution: Establish Apache Flagon TLP

[Justin Mclean]

Hi,

> Only thing I see is that two proposed of the PMC members are not signed up to 
> the private list:
>* Laura Mariano 
>* Steve York 


These people are still not signed up to the private list.

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

[MENTORS] missing reports and signoffs

[Justin Mclean]

Hi,

The report will be submitted on Wednesday.

The following reports are missing:
BlueMarlin
brpc
Hop
Livy
PonyMail
Wayang
Weex

The following still need mentor sign off:
Liminal
Milagro 
YuniKorn

Thanks,
Justin

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

Re: [VOTE] Graduate Apache Gobblin (Incubating) as a TLP

[Justin Mclean]

Hi,

Changing my vote to +1 (binding)

Thanks,
Justin

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

Re: [IP CLEARANCE] OpenWhisk IDE plugins

[Justin Mclean]

Hi,

I assume the .jar in the zip file is not part of the donation?

Thanks,
Justin

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

Re: [DISCUSS] Graduate Apache Gobblin (Incubating) as a TLP

[Justin Mclean]

Hi,

Thanks for doing that - everything looks OK to me.

Thanks,
Justin

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

Re: [VOTE] Heron Release 0.20.3-incubating Release Candidate 9

[Justin Mclean]

HI,

+1 (binding)

I checked:
- incubating in name
- signatures and hashes correct
- LICENSE and NOTICE good
- al source files have ASF headers
- no unexpected binary files
- I didn’t build as I don’t have the prerequisites installed

I’m not sure why the BUILD file is empty. Int would be good to have simple 
build instructions contained within the release in an obvious place rather than 
on the web site.

Also you should not be referencing this version on the website until it the 
IPMC vote has finished. "The current version of Heron is 0.20.3-incubating-rc9” 
[1][2] You should also have some sort of disclaimer on that page [2] as you are 
pointing users to unreleased code (both this rc and master) [3]

Thanks,
Justin

1. http://heron.incubator.apache.org/docs/getting-started-local-single-node
2. http://heron.incubator.apache.org/versions
3. http://www.apache.org/legal/release-policy.html#publication


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

[jira] [Commented] (INCUBATOR-253) Issues with MXNet releases and their distribution

[Justin Mclean (Jira)]

[ 
https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17258034#comment-17258034
 ] 

Justin Mclean commented on INCUBATOR-253:
-

LEGAL-516 has been resolved it would be good to see a summary of what is still 
outstanding.

> Issues with MXNet releases and their distribution
> -
>
> Key: INCUBATOR-253
> URL: https://issues.apache.org/jira/browse/INCUBATOR-253
> Project: Incubator
>  Issue Type: Improvement
>    Reporter: Justin Mclean
>    Assignee: Justin Mclean
>Priority: Major
>
> The main issues are:
> 1. Source and convenance binary releases containing Category X licensed code.
> 2. Website giving access to downloads of non released/unapproved code.
> 3. Website giving access to releases containing Category X licensed code.
> 4. Web site doesn't given enough warning to users of the issues with non 
> (P)PMC releases or making it clear that these are not ASF releases.
> 5. Maven releases containing Category X licensed code.
> 6. PiPy releases containing Category X licensed code.
> 7. Docker releases containing Category X licensed code.
> 8 Docker releases containing unreleased/unapproved code.
> 9. Trademark and branding issues with PiPy and Docker releases. 
> 10. Trademark and brand issues with naming of releases. 
> 11. Developer releases available to users and public searchable 
> https://repo.mxnet.io / https://dist.mxnet.io
> 12. Releases and other nightly builds on https://repo.mxnet.io / 
> https://dist.mxnet.io containing category X licensed code.
> 13. Lack of clarity on all platforms for what is an ASF release and what is 
> not.
> 14. Branding and release of 3rd parties containing unreleased code. (e.g. 
> https://docs.nvidia.com/deeplearning/frameworks/mxnet-release-notes/rel_20-03.html)
> For PiPy see:
> https://pypi.org/project/mxnet/
> For Docker see:
> https://hub.docker.com/u/mxnet
> For web site pages see:
> https://mxnet.apache.org/get_started?
> https://mxnet.apache.org/get_started/download
> I may of missed something, if so please add it.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

Re: [DISCUSS] Graduate Apache Gobblin (Incubating) as a TLP

[Justin Mclean]

HI,

> 4. Regarding docker, per policy [1] I thought unreleased tags are fine (ie.
> if its nightly or snapshot), where-as the *latest* tag should point to an
> (approved) released code. Seems like my understanding was incorrect, so I
> will remove the unreleased tags from there as well.

You're correct that the latest tag should point to the the last approved 
release version of the code. I was not sure this was happening in this case. Re 
other tags it's generally OK if they are very clearly marked as not for public 
consumption/for project internal development use only. If they get excessive 
number of downloads you may need to reconsider putting them there as it may be 
the general public is using them.

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

Re: Link to a page that seems to be missing

[Justin Mclean]

Hi,

Here is the last version of that page (from 2017):
https://web.archive.org/web/20170629200901/http://incubator.apache.org/facilities.html

I can see facilities.xml in the old Incubator/content  content area but no 
facilities.ad in the new area. Perhaps it was not converted? I couldn’t find 
any discussion about this, does anyone remember why it may have been removed?

Thanks,
Justin



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

Re: [DISCUSS] Graduate Apache Gobblin (Incubating) as a TLP

[Justin Mclean]

HI,

> 1. 3rd party logos being eaten by pacman on the homepage: We have removed
> this animation, and created a ticket to follow-up with Trademarks for
> future usage of that animation.

There are still trademarks on that page that are not mentioned in the footer 
disclaimer. You might also have to look at [1][2][3][4] on what you can and 
cannot do with these 3rd party trademarks.

> 4. Docker not following guidelines: We have deleted the pre-apache repo (
> https://hub.docker.com/r/gobblin ), and updated the apache/gobblin on
> DockerHub to bring it inline with the guidelines.

It looks like you may have unrealised code available via docker? [5] Please 
note this [6] from the distribution policy. In particular unreleased materials 
must not be distributed through channels which encourage use by anyone outside 
the project development community.

Thanks,
Justin

1. https://www.oracle.com/legal/trademarks.html
2. https://www.oracle.com/legal/logos.html
3. 
http://www.oracle.com/us/technologies/java/java-licensing-logo-guidelines-1908204.pdf
4. https://aws.amazon.com/trademark-guidelines/
5. https://hub.docker.com/r/apache/gobblin/tags?page=1=last_updated
6. https://infra.apache.org/release-distribution.html#unreleased








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

Re: NOTICE file for binary release

[Justin Mclean]

Hi,

Without access to a release it is a little hard to confirm, but it looks 
reasonable to me.

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

Re: [VOTE] Release Apache Hop (incubating) 0.50-rc2

[Justin Mclean]

HI,

Sorry but it’s -1 (binding) as it contains Category B source code and header 
issues and is not using the WIP disclaimer. [1]

 I suggest you use the work in progress disclaimer, and in it list the issues 
that need to be fixed before graduation. Fixing some of teh header issues would 
make it easier to review as well.

I checked:
- Incubating in name
- DISCLAIMER exists but is not work in progress 
- LICENSE is missing mention of 3rd party included software [2][3][5][6]
- NOTICE may need updating if the release contains code from Apache Hadoop
- There a large number of files that are missing ASF headers. This makes it 
hard to review.
- There are a large number of files without correct headers copyright  Hitachi 
Vantara.
- Files incorrectly have the ASF header onto of anther license header e.g [4]
- Includes Category B course code
- No unexpected binary files
- Unable to compile on OSX but not sure if that’s a supported platform. It gets 
to step 467 out of 474. (Hop Assemblies Plugins Dist)

Thanks,
Justin

1. 
https://incubator.apache.org/policy/incubation.html#work_in_progress_disclaimer
2. OpenSansLight font
3. 
./plugins/actions/ftp/src/main/java/org/apache/hop/workflow/actions/ftpput/FtpClient.java
4. 
./ui/src/main/java/org/apache/hop/ui/pipeline/transforms/tableinput/SqlValuesHighlight.java
5. ./assemblies/static/src/main/resources/LICENSE ( Copyright (c) 2005, 
European Commission project)
6 ./assemblies/static/src/main/resources/docs/English/welcome/css/bootstrap.css
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Hop (incubating) 0.50-rc2

[Justin Mclean]

Hi,

> Hop plans to fix these issues in a later incubating release. I hope that 
> exceptions to release policy can be made for these and similar issues in this 
> early-stage incubating release.

If you have used the work in progress DISCLAIMER and listed the potential 
issues in that file this is fine.

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

Re: [DISCUSS] Graduate Apache Ratis as TLP

[Justin Mclean]

Hi,

I notice you use [1]. Are the conversations there being brought back to the 
mailing list? There doesn’t seem to be a lot of conversation happening on your 
mailing list other than GitHub traffic, have you considered moving the GitHub 
traffic off the dev list?

I notice the download links on your front page and not using the  correct links 
[1], they shouldn’t  point directly to the download area

This also seem a little odd [2], do you know why it exists.

Thanks,
Justin

1. https://www.apache.org/dist/incubator/ratis/1.0.0/ 

2. https://elek.github.io/ratis-site/

Re: [VOTE] Graduate Apache Gobblin (Incubating) as a TLP

[Justin Mclean]

Hi,

-1 (binding) due to docker and trademark issues, but happy to change my vote to 
+1 once those are on teh way to bee corrected.

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

Re: [DISCUSS] Graduate Apache Gobblin (Incubating) as a TLP

[Justin Mclean]

Hi,

I suggest you run your home page past trademarks. There's a large number of 3rd 
party logos used without attribution there and I’m not sure how some of those 
trademark owners would feel about a pacman eating their logos. You also have 
links on your home page to various commercial entires without the no follow 
attribute. In general there should be no links to 3rd parties on your front 
page, they can images or links on another page but they should be no-follow 
links.

Your home page also includes google analytic, while policy has not be set, the 
general advice is to not use Google Analytics and at some future point it’s 
likely that all ASF projects will be asked to stop using it.

I note that until very recently you have not voted in any PPMC members. Is 
there a reason for that?

Your docker releases [1][2] are not following the guidelines here. [3]

Thanks,
Justin

1. https://hub.docker.com/r/gobblin
2, https://hub.docker.com/r/apache/gobblin
3. https://incubator.apache.org/guides/distribution.html#docker
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Issue with clutch2report

[Justin Mclean]

Hi,

I just had an issue with clutch2report and for some unknown reason it was 
trying to use a podling that has graduated (TVM). The podlings.xml file is 
correct as far as I can see and it doesn’t appear in the current clutch report. 
I put in a work around, but if someone want to try and fix what the actual 
issue is please go ahead.

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

[MENTORS] Podling reporting timeline for January

[Justin Mclean]

Hi,

Here is the time line for the reports for this month.

Wed January 06  Podling reports due by end of day
Sun January 10  Shepherd reviews due by end of day
Sun January 10  Summary due by end of day
Tue January 12  Mentor signoff due by end of day
Wed January 13  Report submitted to Board
Wed January 20  Board meeting

Reports can be entered here [1]

Thanks,
Justin


1. https://cwiki.apache.org/confluence/display/INCUBATOR/January2021


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

Re: [VOTE] Graduate Apache Gobblin (Incubating) as a TLP

[Justin Mclean]

Hi,

> I closed the vote after 72 hours of starting the vote (which was after 72
> hours of discussion time). Are you recommending adding more time to the
> vote?

72 hours is just a guideline for release votes not for graduation. Generally 
you want to get consensus from the entire IPMC and your mentors for graduation. 
Given the time of the year and what is happening in the world you might want to 
give IPMC members a little more time is all I’m saying.

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

Re: [VOTE] Graduate Apache Gobblin (Incubating) as a TLP

[Justin Mclean]

Hi,

You might want to give the IPMC a little more time to have a look at the 
project and give some more feedback. It would be unfortunate if an issue was 
found that prevented the project from graduating.

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

Re: NOTICE file for binary release

[Justin Mclean]

Hi,

> Last release we had feedback that the NOTICE file for the binary release 
> needs to show the licenses of the depdendencies distributed alongside the 
> code.

In general the NOTICE file does not do this, license information goes in the 
LICENSE file. Please see [1]

If some of the code in including in the release is Apache licensed you made see 
to add the contents of their NOTICE files to your.

If something is a dependancy and not included in the release then nothing needs 
to be done.

Thanks,
Justin

1. https://apache.org/dev/licensing-howto.html
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [LAZY CONSENSUS] Re: [incubator] branch master updated: Update incubation.ad

[Justin Mclean]

Hi,

I have no objections to most of the changes.

This has changed the DISCLAIMER text, would we require all podlings to update 
their DISCLAIMERS to match?

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

Re: Trying to become incubator project..

[Justin Mclean]

Hi,

In order to be accepted as an incubating project you need to put together a 
proposal. The Incubator PMC would also have to agree that the project is a good 
fit for the ASF. I would suggest you take a look at this [1] and some other 
incubator proposals [2] (newer ones are at the top). If you could expand on why 
you want to become an ASF project that would also help.

You would need to change the license as all Apache projects need to licensed 
under the Apache license. Having MySQL as a dependancy may also be an issue as 
it is GPL licensed. Apache project can’t have non optional dependancies that 
are GPL licensed.

From a quick glance your  project doesn’t seem to be very active, that might 
make it difficult to attract other developers. It would also be good to know 
your projects experience with Open Source projects. Do you have anyone involved 
that is active at the ASF or another open source community?

Thanks,
Justin

1. http://incubator.apache.org/cookbook/
2. https://cwiki.apache.org/confluence/display/INCUBATOR/Proposals
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Heron Release 0.20.3-incubating Release Candidate 8

[Justin Mclean]

Hi,

>> LICENSE is also missing the license for the trykker font and may be missing 
>> other things.
> 
> Good catch as that file was in the .rat-excludes. This font is Class B and 
> should not be included. Heron will need to find another Serif Font.
> 
> https://scripts.sil.org/cms/scripts/page.php?item_id=OFL_web


I think inclusion of fonts under the OFL may be a little more nuanced than 
that. Generally you can’t include compiled code in a source release, a binary 
font file may not be considered code and is unlikely to be modified, so it may 
be possible to include this in a source release. Perhaps best to ask on 
legal-discuss?

I know of several projects who do include OFL licensed fonts. A quick search 
shows  Atlas, Brooklyn, Cordova, ECharts, Falcon, Flex, Flink, Geode, Hivemall, 
Jena, MyFaces, ShardingSphere, Solr, Superset, Syncope, Taz, Usergrid, Wicket, 
Yetus, Zepplin and others mentioning it in their LICENSE file. I’ve not checked 
if it in their source release but do know that it is the case for some of these 
projects. Also possibly OFBiz.

I recall this being discussed but can’t find the discussion and legal JIRAs 
don’t seem much help other than to say its category B. [1][2]

But replacing it with a font under with a category A license is also an option.

Thanks,
Justin

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

Re: [VOTE] Heron Release 0.20.3-incubating Release Candidate 8

[Justin Mclean]

HI,

-1 (binding) due to license and notice issues

I checked:
- incubating in name
- LICENSE has issues (see below)
- NOTICE has wrong year
- DISCLAIMER exists (not WIP one)
- no unexpected binary files
- ASF files have ASF headers

I’m a little confused by the LICENSE file. 

First off it uses URLs to link to the LICENSE text, the full license text often 
needs to be included as part of the license conditions (from ALv2, MIT and BSD 
style licenses so need to be included in the releases. While the URL are useful 
they can break over time or worse the license change, you should point to the 
license file in the licenses directory. Also part of the BSD and MIT licences 
include a copyright line and this will vary with each bit of included code.

JSXTransformer is listed under the Apache 2.0, MIT, BSD 2 clause and BSD 3 
clause licenses. It may be that this files include 3rd party code under 
different licenses or the file itself is under multiple licenses. If it was 
under multiple licenses you would generally select which one you want to use. 
If not then each of those pieces of 3rd party code is likely to have its own 
name and copyright holder (for MIT and BSD licenses) which need to be included 
or pointed to by the LICENSE file.

LICENSE is also missing the license for the trykker font and may be missing 
other things.

Thanks,
Justin


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

Re: [VOTE] Apache Gobblin 0.15.0 release RC2

[Justin Mclean]

Hi,

Might be best to close this one and ask people to vote in the other thread for 
less confusion.

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

Re: [VOTE] Apache Gobblin 0.15.0 release RC2

[Justin Mclean]

Hi,

Is this the same as the other vote thread?

Thanks,
Justin

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

Re: [VOTE] Apache Gobblin 0.15.0 release RC2

[Justin Mclean]

Hi,

+1 (binding)

I checked:
- incubating in name
- LICENSE and NOTICE are fine
- DISCLAIMER exists
- No unexpected binary files in release
- All files have ASF headers
- I was not able to compile at first but managed to get (see below)

This is the error I get when building via ./gradlew build:
Deprecated Gradle features were used in this build, making it incompatible with 
Gradle 5.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See 
https://docs.gradle.org/4.9/userguide/command_line_interface.html#sec:command_line_warnings

I got the jar (as instructed in the readme) from:
 
https://github.com/apache/incubator-gobblin/raw/0.12.0/gradle/wrapper/gradle-wrapper.jar
 

Should that 0.12.0 be 0.15.0? I tried changing it and it compiled, so might 
best to update your readme instructions.

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

Re: [DISCUSS] Wayang Proposal

[Justin Mclean]

Hi,

> Right now, there are 3 people signed up as mentors, however knowing that not 
> always are all mentors available at every given time, it would be cool if we 
> could find 1-2 more to help out.

In no way reflecting on the mentors who have volunteered and I’m sure they will 
do a good job

In recent times I've notice that incubating projects with a large number of 
initial mentors seem to have a very slow start. I’m not sure if the issue is 
that each mentor assumes someone else will do the job or something else but 3 
initial mentors seems to be the sweet spot.

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

Re: [VOTE] Release Apache NuttX (Incubating) 10.0.0 [RC0]

[Justin Mclean]

Hi,

+1 (binding) but a lot more needs to be done on the LICENSE and headers

I checked:
- incubating in name
- DISCLAIMER exists
- a good start have been made on LICENSE
- NOTICE looks fine
- No unexpected binary files
- More work needs to be done on adding ASF headers

I not sure that using key with a short expiry date is a good idea. Think the 
problem is that unless the KEYS file is updated regularly it quite possible for 
someone to get an error message that the key has expired.

Re the notices in NOTICE I think these are probably OK as they could be 
considered optional, but would be best to try and get the license terms 
changed. If that can’t be done I would do as suggested double check on legal 
discuss.

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

Re: [LAZY CONSENSUS] Suitable Name Search Documentation

[Justin Mclean]

Hi,

I think the issue may be more clarifying and simplifying the original policy 
language. Perhaps that can be done at the some time?

Justin



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

Re: svn commit: r1883912 - /incubator/public/trunk/content/shepherd_assignments.json

[Justin Mclean]

HI,

> Superset and TVM graduated and that’s not reflected in your report 
> preparation.

Sorry I has assumed that the new projects had taken care of that.

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

[MENTORS] Report timeline

[Justin Mclean]

Hi,

The time line is as follows:

Wed December 02 Podling reports due by end of day 
Sun December 06 Shepherd reviews due by end of day 
Sun December 06 Summary due by end of day 
Tue December 08 Mentor signoff due by end of day 
Wed December 09 Report submitted to Board 
Wed December 16 Board meeting 


Reports can be added here:
https://cwiki.apache.org/confluence/display/INCUBATOR/December2020

Thanks,
Justin


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

Re: [VOTE] Release Apache Weex (Incubating) 0.29.0-RC1

[Justin Mclean]

HI,

I also see only 1 +1 vote in the thread in your dev list normally you need 3 +1 
votes from PPMC members before bring it t the IPMC to vote on. I suggest you 
ask your mentors and other PPMC to vote on the dev list and cancel this vote 
here on the incubator list.

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

Re: [VOTE] Graduate Apache ECharts as TLP (round 2)

[Justin Mclean]

Hi,

> The description of [1] is generated from GitHub release, so it will be
> updated with our next release, which is expected to happen in a few more days.

Good to hear.

> The description of [2] is generated from GitHub description. We can update
> the GitHub description, adding "Apache ECharts is ..." if you are OK with
> that.

That would be a good help it need to be clear that ECharts is an Apache project.

> We have made a lot of pull requests to fix README files and descriptions of
> third-party extensions like [3], making sure that they refer to the project 
> as "Apache
> ECharts (incubating)”.

I think the issue is more than people might be confused and think these are 
parts of the Apache project. e.g. "ECharts-GL is an extension pack of Apache 
ECharts (incubating), which providing 3D plots, globe visualization and WebGL 
acceleration.”

> See [a] for more information. What would you suggest adding to make the
> description more accurate, maybe adding "This is not an official Apache 
> ECharts project”?

So yes I think add some text to make it clear these are not part of the Apache 
ECharts project would help.

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

Re: [VOTE] Graduation of Apache DataSketches Project to TLP

[Justin Mclean]

Hi,

+1 (binding) All the best!

Thanks,
Justin


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

Re: [VOTE] Release the Apache Pegasus 2.1.0

[Justin Mclean]

Hi,

+1 (binding) but it would be good to see progress on adding all license 
information / fixing all headers

I checked:
- incubating in name
- DISCLAIMER (WIP) exists
- LICENSE is missing some licenses
- NOTICE seems OK
- Unclear if all ASF source files have ASF headers. It would be best to have a 
clearer separation of 3rd party code and ASF code if possible.

In the rsdn directory I’m slightly confused by the content of CONTRIBUTING.md 
and the LICENSE file containing the MIT license. Should that file be in the top 
level?

Thanks,
Justin



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

Re: [VOTE] Release Apache ECharts (incubating) 5.0.0 (release candidate 3)

[Justin Mclean]

Hi,

+1 (binding)

I checked:
- signatures and hashes are fine
-  incubating in name
- DISCLAIMER exists
- LICENSE and NOTICE fine
- All source files have ASF headers
- No unexpected binary files

Thanks,
Justin

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

Re: Where to get feedback on a project before formulating a proposal

[Justin Mclean]

Hi,

> The idea was first brought up over a year ago by a member of the community,
> although it's been me dragging my feet.  They are actually an ASF member.

Being an ASF member that can be a mentor or the champion. Have you asked them 
if they would be willing to do that?

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

Re: [VOTE] Graduate Apache ECharts as TLP (round 2)

[Justin Mclean]

Hi,

+0  

I think a little more attention needs to given to branding and trademarks e.g. 
[1][2][3][4] The last ones in particular are concerning as they come from Baidu 
and there seem to be others as well [8]

Thanks,
Justin


1. https://www.npmjs.com/package/echarts
2. https://www.jsdelivr.com/package/npm/echarts?path=dist
3. https://www.npmjs.com/package/ngx-echarts
4 https://github.com/ecomfe/vue-echarts
5. https://github.com/ecomfe/echarts-gl
6. https://github.com/ecomfe/echarts-stat
7. https://github.com/ecomfe/echarts-wordcloud
8. https://github.com/ecomfe?q=echarts==




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

Re: Missing graduation resolutions

[Justin Mclean]

Hi,

> The Superset graduation resolution was already submitted to the board. In
> fact it made the agenda at the last board meeting but was tabled to give
> the board more time for due diligence. Let me know if it needs to be
> resubmitted or anything.

I’ve resubmitted it so it should be fine for this meeting.

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

Re: Missing reports from Incubator report

[Justin Mclean]

Hi,

> There's been some confusion over annotator's reporting schedule.
> It seems several team members had a (presumably mistaken?) 
> recollection of having reported in October.

It did report in October, but didn’t get sign off from any of the mentors.

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

Missing reports from Incubator report

[Justin Mclean]

Hi,

I’ve just submitted the board report [1] and we were missing the follow reports:
  - Annotator
 - BlueMarlin
 - Livy
 - S2Graph
 - Toree
 - Warble

Thanks,
Justin

1. https://whimsy.apache.org/board/agenda/2020-11-18/Incubator

Missing graduation resolutions

[Justin Mclean]

Hi,

Several projects have discussed graduation but I’m not seeing any proposals 
submitted. [1] It best to get them in early so board members can review them in 
time.

I think we should have proposals for:
 - TVM
 - Superset
 - Flagon
 - ECharts?

I’ve added Superset.

Thanks,
Justin

1. https://whimsy.apache.org/board/agenda/2020-11-18/
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [MENTORS] Incubator report timeline for November 2020

[Justin Mclean]

Hi,

> How can I edit the following page? I am the owner of Blue Marlin project and 
> would like to submit my report.
> 
> https://cwiki.apache.org/confluence/display/INCUBATOR/November2020 
> 
he permissions for your PPMC had not been added and I've just added them, so 
you should be able to edit that page now.

Kind Regards,
Justin 

Re: Proposed Resolution: Establish Apache Flagon TLP

[Justin Mclean]

Hi,

Everything looks fine to me.

Only thing I see is that two proposed of the PMC members are not signed up to 
the private list:
* Laura Mariano 
* Steve York 

And i would be nice to have you logo here [1]

Thanks,
Justin

1. https://apache.org/logos/?#flagon
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Apache StreamPipes 0.67.0 (incubating) release

[Justin Mclean]

Hi,

+1 (binding)

This is an easy release to check

I checked:
- incubating in name
- signatures and hashes are fine
- LICENS and NOTICE are fine
- no binary files
- all source files have ASF headers

It not immediately clear have you can compile from the instructions included 
within the release and this [1] seems out of date.

Thanks,
Justin

1. https://cwiki.apache.org/confluence/display/STREAMPIPES/Validating+a+release
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[MENTORS] Incubator report timeline for November 2020

[Justin Mclean]

Hi,

Here’s the reporting timeline. Report as usual can be entered on the Wiki [1]

Wed November 4th Podling reports due by end of day 
Sun November 8th Shepherd reviews due by end of day 
Sun November 8th Summary due by end of day 
Tue November 10th Mentor signoff due by end of day 
Wed November 11th Report submitted to Board 
Wed November 18th Board meeting 

Expected to report are:
Annotator
BlueMarlin
DataSketches
DolphinScheduler  
Doris
ECharts
Heron
Hop
Liminal  
Livy
Milagro
NLPCraft
PageSpeed
Pinot
Ratis
S2Graph
SDAP
Sedona
Toree
Training
Tuweni
Warble  
Weex

There were a several podlings last month that didn’t submit reports or didn’t 
get sign-off from mentors, so the list is a little larger than usual.

Thanks,
Justin  

1. https://cwiki.apache.org/confluence/display/INCUBATOR/November2020



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

Re: [VOTE] Release the Apache Pegasus 2.1.0

[Justin Mclean]

Hi,

+1 (binding)

Both the issues of the missing header and licensing is mentioned in the 
DISCLAIMER so I think that’s OK, but progress will need to be made on these in 
the next release.

I checked:
- incubating in name
- signatures and hashes are fine
- DISCLAIMER_WIP exists and contains what needs to be worked on
- LICENSE and NOTICE exits
- LICENSE is missing a number of included 3rd party licenses
- Files are missing ASF headers
- No unexpected binary files
- Unable to compile from source, but may be my setup or I’m on a non supported 
platform (OSX)

Thanks,
Justin








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

Re: [VOTE] Release Apache MXNet (incubating) version 1.8.0.rc1

[Justin Mclean]

HI,

> Thanks, Justin. After removing stale issues and adding the statement on GPU 
> license, assuming we address any other license issue in the next rc, should 
> we name it as simply DISCLAIMER instead of DISCLAIMER-WIP? 

When all issue have been resolved then I would name it DISCLAIMER, probably 
best to keep DISCLAIMER WIP at this piont.

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

Podling termination by the IPMC

[Justin Mclean]

Hi,

As requested by Dave. IMO This is going to happen infrequently and possibly 
never. I can only think of a couple of occasions when this has been discussed 
in the last five years. Things generally work out one way or another before 
this step needs to be taken.

The current IPMC policy[1] states:
"The Incubator PMC SHOULD notify a podling of any policy violations. It MAY 
consider the termination of a Podling if violations are not corrected."

I would think that the conditions that this would occur would be something like:
- Podling has been a long time in the Incubator.
- Podling has been repeatedly asked by the IPMC to correct policy violations, 
and they have not done so or had made little real progress. 
- Podling has refused to comply with directions given by the IPMC.
- Podling has required repeated intervention by the IPMC to correct policy 
violations and doesn't self-correct.
- The same or similar policy violations keep on coming up.
- The podling is reactive, not proactive in finding solutions to these policy 
violations.
- The issues are ongoing for a period of 3 or more months.
- It's unlikely that the podling will graduate even if the policy violations 
were fixed.
- It's likely that the policy violations would reoccur once the project is a 
TLP.
- The IPMC and Podlings Mentors agree this is the best course of action. (And 
hopefully, the PPMC agree as well, but that may not happen in all cases.)
.
But each situation it's going to be a little different, and it may be hard to 
come up with a set of guidelines that work in all situations. Given that I not 
sure we need to put the time and effort into defining what these are, but if 
someone wants to do so, go ahead. If you think my list above is too lenient or 
not forgiving enough please speak up.

I can think of some other actions the IPMC could take (depending on the 
situation) as well:
- Change the composition of the PPMC or committers
- Direct Infra to remove the podlings releases
- Involve branding/trademark/legal to issue a legal notice to remove infringing 
3rd party releases

Hopefully, events like this will be the exception and rarely occur..

Generally what has happened previously, is before it reached this stage, the 
podling decides that the ASF is not a good fit for them and moves elsewhere.

Thanks,
Justin


1. https://incubator.apache.org/policy/incubation.html#termination
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache MXNet (incubating) version 1.8.0.rc1

[Justin Mclean]

Hi,

> Let’s discuss outside the immediate context of MxNet reasons for the IPMC to 
> suspend a podling.

Sure, it would be best to start a seperate thread for that. I think however it 
would be so infrequent and each situation different that it would be hard to 
come up with some that would work in general. What to do about this situation 
has already been discussed on the IPMC private list.

Thanks,
Justin

Re: [VOTE] Release Apache MXNet (incubating) version 1.8.0.rc1

[Justin Mclean]

Hi,

> If NVIDIA changes the license then it must be very soon. If so then the issue 
> is gone.

And the issue may not be gone unless the license change is retroactive. 
Currently the project has maven artefacts in the Apache repo that contain 
category X code. [1]

Thanks,
Justin

1. https://issues.apache.org/jira/browse/INFRA-20442

Re: [VOTE] Release Apache MXNet (incubating) version 1.8.0.rc1

[Justin Mclean]

HI,

> Don’t make a noncompliant binary release.

The project is (sadly) already doing this [1], they are hoping the licensing 
issue can be sorted, but its taken more than 5 months and little visible 
progress on that seems to have been done. NVIDIA is considering  changing, but 
to what we don’t know.

> Tell your users how to make a noncompliant build on their own knowing the 
> risks.

They don’t want to do that, as it is too hard for users to compile.

> Third parties like NVIDIA can make their own decision and release, but can’t 
> call it Apache MxNext, but have to use “powered by” if they use the brand.

This has been brought many times by the IPMC over many months, but it seems 
they still seem to have branding and naming issues. [2]

Thanks,
Justin

1. https://pypi.org/project/mxnet/
2. https://ngc.nvidia.com/catalog/containers/nvidia:mxnet

Re: [VOTE] Release Apache MXNet (incubating) version 1.8.0.rc1

[Justin Mclean]

HI,

Is there anything from the known issues in  [1] that needs to be added?

Justin

1. https://issues.apache.org/jira/browse/INCUBATOR-253

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

Re: [VOTE] Release Apache MXNet (incubating) version 1.8.0.rc1

[Justin Mclean]

Hi,

Re the licensed files missing from LICENSE here are some examples[1][2][3][4], 
but I haven’t done a full check so there are probably more.

Thanks,
Justin

1. 
./3rdparty/onnx-tensorrt/third_party/onnx/third_party/pybind11/tests/test_gil_scoped.cpp
2. 
./3rdparty/onnx-tensorrt/third_party/onnx/third_party/pybind11/tests/test_tagbased_polymorphic.cpp
3. 
./3rdparty/onnx-tensorrt/third_party/onnx/third_party/pybind11/tests/test_union.cpp
4. ./3rdparty/mkldnn/cmake/blas.cmake


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

Re: [VOTE] Release Apache MXNet (incubating) version 1.8.0.rc1

[Justin Mclean]

Hi,

> Thanks for the vote. It looks like we forgot to remove the mentions of the 
> resolved issues in the DISCLAIMER-WIP. Checking the linked issues, all of 
> them have been resolved in 1.8. Is this still a blocking issue if the actual 
> issues that the DISCLAIMER-WIP links to are addressed?

The DISCLAIMER WIP needs to be keep up to date. When I looked not all of these 
issues were resolved.

> Between 1.8 submodules [1] and that of 1.7 [2] there hasn't been any addition 
> of submodule. For the four modules with updated commits (dmlc-core, mkldnn, 
> nvidia-cub, onnx-tensorrt), I didn't find any license change. What's missing?

If you compare the copyright statements between the two release you’ll see 
there are a number of differences and mention of bundled 3rd party licenses are 
missing from the LICENSE file.

> Regarding NVIDIA licensing, I'm not sure what the standard practice is given 
> that we are indeed open sourcing our GPU source code with ALv2 and the NVIDIA 
> licensing only comes into picture in binary distribution and not in a source 
> release. Advice is appreciated.

You need to tell your users that using the software in this way that it is not 
compatible with the Apache license. I think the DISCLAIMER would be a good 
place to do this.

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

Re: [VOTE] Graduate Apache Superset (incubating) as a Top Level Project

[Justin Mclean]

Hi,

The resolution was put on the board agenda, but given it was received less than 
24 hours before the board meeting it was decided to postpone it till next 
month, to give board members time to properly consider the proposal.

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

Re: [VOTE] Release Apache MXNet (incubating) version 1.8.0.rc1

[Justin Mclean]

Hi,

-1 (binding) Please see [1] and note which sort of issues need to be fixed 
before making a new release.

While it does include the WIP declaimers, it includes several knows issues that 
have been outstanding for several releases. It also fails to mention teh issue 
with Nvidia licensing and its incompatibility with the Apache license. The PPMC 
needs to take action on correcting licensing issues in one release before 
creating other releases.

When comparing to the 1.7 release, new 3rd part code has been added, and the 
LICENSE file has not been updated to list all of the included code. The project 
needs to follow the terms of 3rd party licenses, which generally state  to 
including the text of the license and follow ASF policy on licenses.

Thanks,
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] Graduate Apache Superset (incubating) as a Top Level Project

[Justin Mclean]

HI,

+1 (binding)

Thanks for addressing everything I brought up here and on your private list. 
There's still a little more to do, but it’s being dealt with, so I’m all good 
with you graduating. Do keep an eye on how you are handling those synchronous 
meetings and try to make sure everyone can contribute and information is 
brought back to the list.

Congratulations!

Thanks,
Justin


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

Re: Is there a check list for podling renames?

[Justin Mclean]

Hi,

> I could not find one; seems to me it would be useful to document
> everything that has to be done by the podling and what is done by
> Infra.

There is not one that I know of. Hopefully they are rare, as they cause a bit 
of work for Infra.

Thanks,
Justin


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

Re: [DISCUSS] Graduate Apache Superset (incubating) as a TLP

[Justin Mclean]

Hi,

>  I’ve stuck to the basic directions in [2] of sending a “friendly” email (AND 
> Slack message, in our case), in private, to the community member. 

That is certainly the best first step with dealing with something like this.

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

Re: [DISCUSS] Graduate Apache Superset (incubating) as a TLP

[Justin Mclean]

Hi,

> I hope that everyone is now subscribed after the last round of nagging, but I 
> still have no way to confirm who’s not on the list.

Daniel Gaspar is still not subscribed, but all others have, I don’t see that as 
a blocker to graduation.

> After taking this up with our mentors, we’ve seemingly landed on an agreed 
> plan to address this by making the following adjustments/commitments:
> 
> • Announcing the meetings in advance (this just happened on the dev@ list, 
> actually)
> • Rotating the time slot to be more accommodating to other regions
> • Increasing grow community/public attendance
> • Sharing out the notes to the list after each meeting
> • Sharing out video of the meetings after they transpire, whenever available
> • Committing to not making any community-wide decisions in these meetings

That sounds like a better approach. I still think it is better to use 
asynchronous communication on the mailing and not have these sort of meetings.

> Let me/us know if there are further actions needed on any of these three 
> points

Those three seem fine. They are fine but there is still an issue with 
branding/trademarks and some docker images. What is the PPMC doing about this?

Thanks,
Justin

Re: Some instructions are misleading on mentor page

[Justin Mclean]

Hi,

I agree this could be clearer:

"Mentors MUST be on the IPMC. This should be checked prior to beginning 
incubation. Any prospective Mentors who are not yet on the IPMC should ask to 
be added (by election). Email the application to priv...@incubator.apache.org.”

How about this:

"Mentors MUST be on the IPMC. This should be checked before beginning 
incubation. Any prospective Mentors who are not yet on the IPMC, and who are 
ASF members, should ask to be added. Email the application to 
priv...@incubator.apache.org. Any prospective Mentors who are not ASF members 
or IPMC members could be voted onto the IPMC by the IPMC in the normal way, but 
unless the proposed Mentors have been active in the Incubator, this is unlikely 
to happen."

Thanks,
Justin





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

Re: [DISCUSS] Graduate Apache Superset (incubating) as a TLP

[Justin Mclean]

Hi,

> (1) PPMC members not subscribed to the private list.
> 
> I have no way to see who is or isn’t on the list

Whimsey should show that to PMC member with a * next to their name. Currnly 
still not subscribed are:
Aaron Suddjian
Bogdan Kyryliuk
Chris Williams
Daniel Gaspar
Serena Jiang

There is also a ralme...@gmail.com subscribed who doesn’t seem to be on your 
PPMC, they probably should be removed.

> (2) Synchronous Meetings

The biggest issue I see is the this is not being announced or discussed on the 
mailing list and what is discussed in those meetings is not brought back to the 
list. Having these external discussions is a huge barrier to people who want to 
contribute to the project but for one reason or another (e.g. time zones or day 
job or other commitments) can’t attend that meeting. By having these you are 
basically limiting people who can attend to full time employees paid to work on 
the project in a similar time zone, that excludes a lot of people.This was 
mentioned as an issue in a previous board report but nothing seems to have been 
done about it. One of the core values of Apache projects is that discussions 
need to be asynchronous and inclusive. It would be helpful if your mentors 
added their thoughts about this.

> (3) Links to other companies
> 
> I’ve reached out to our mentors (via the private@ list, in case we can get 
> any other input as well) on the issue, and hope to hear back soon about how 
> other TLPs (e.g. Drill, Airflow, Beam, and surely more), have surmounted this 
> logo usage issue.

I’ve seen this handled in a few ways, either it put on a page other than the 
main page or they don’t link to those companies. also be aware that some 
companies are more protective of their trademarks and you may even need to get 
permission to use their logos in this way.

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

Re: BlueMarlin Slow Bootstrap into Incubator

[Justin Mclean]

HI,

> It is out of date and COMPLETELY misses DNS requests!

I believe it’s up to date, but as always PRs welcome.

It's mentioned under Resources:
"The first resources to be created are LDAP and DNS. These should be requested 
via Apache Infra JIRA → New Podling Parent Request”

The podlings.xml file need to updated before that can be done as described in 
the document.

Thanks,
Justin


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

Re: BlueMarlin Slow Bootstrap into Incubator

[Justin Mclean]

Hi,

As I said it’s looks to be a DNS issue, bluemarlin.incubator.apache.org 
 resolves but bluemarlin.apache.org 
 doesn’t. So depending on which domain you use 
it you get different results. This hasn’t been fixed yet.

Thanks,
Justin

Re: BlueMarlin Slow Bootstrap into Incubator

[Justin Mclean]

Hi,

> This project needs to have the incubator/their mentors guide them through the 
> podling creation process. They need to submit a dns creation infra ticket and 
> perform other needed actions to establish the podling.


The mailing list have been created and I’ve been able to send email to them so 
it look like DNS has been set up but not correctly.

bluemarlin.incubator.apache.org resolves but bluemarlin.apache.org doesn’t.

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

[MENTORS] Sign off podling reports due Tuesday 13th

[Justin Mclean]

Hi,

Report sign offs are due on Tuesday 13th and all reports should be submitted by 
now. We are still missing:
Livy
Pegasus
S2Graph
SDAP

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

Re: [VOTE] Graduate Apache Flagon (incubating) as a Top Level Project

[Justin Mclean]

Hi,

Thanks for your answers.

Re the logo URL I though that redirected but doesn’t they 
https://apache.org/logos/

The points were (and were repeated for 4 reports):

 1. Grow the Flagon Committer/Contributor/Community Base
 2. Refine release processes for core analytic product (Distill)
 3. Finalize (through vote) Flagon logo, get marketing approvals (e.g swag)

So it looks like the project did intend to release Distill?

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

Re: [VOTE] Graduate Apache Flagon (incubating) as a Top Level Project

[Justin Mclean]

Hi,

> Only UserALE.js has been released under SensSoft (Incubating) and Flagon 
> (Incubating) names. No other products have been released so this is a 
> non-topic in my opinion. 


So assuming 2 of the products are no longer maintained but it looks like the 
other 2 without releases are. Are they going to be maintained and is there some 
intention of making a releases of them in the future?

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

Re: [VOTE] Graduate Apache Flagon (incubating) as a Top Level Project

[Justin Mclean]

Hi,

> I have absolutely no idea what this is. It is not referenced from the 
> Incubator Website navigation. Can you please provide a link?

See [1]. However it is not required to be filled in for a project to graduate.

Thanks,
Justin

1. http://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: [DISCUSS] Graduate Apache Superset (incubating) as a TLP

[Justin Mclean]

Hi,

These change all look fine. So it seem the only outstanding things (unless any 
IPMC member brings up something else) are:
- PPMC member not subscribe to the private list
- How to deal with the synchronous meetings
- Links to other companies on your front page. Have one of your mentors (or any 
ASF member in your project) take a look at this thread on the incubator private 
list [1].

Thanks,
Justin

1. 
https://lists.apache.org/thread.html/r68df1ac8c2895071ca81e5183ad181891c98bbe1e379488653568327%40%3Cprivate.incubator.apache.org%3E
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Graduate Apache Flagon (incubating) as a Top Level Project

[Justin Mclean]

HI,

> I don’t care which products you have as long as the most recent for each is a 
> proper Apache release.

I could be mistaken (given the name change)  but there only seems to be only 
Apache releases for UserALE.js, although two of the products may be no longer 
used and have been dropped. The releases that have been made look fine to me. 
Perhaps an update of the website is needed to show this more clearly?

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

Re: [VOTE] Graduate Apache Flagon (incubating) as a Top Level Project

[Justin Mclean]

Hi,

I didi my usual check and most things look good, but I can see a couple of 
minor things. Hopefully the mentors can comment on the following:
- Logo is missing form logos.apache.org
- A few of the proposed PMC are not subscribed to the private list (Alex, 
Laura, Steve)
- It’s been a long time since the project added any committers (Looks like the 
last was Arthi on 2017-01-24?)
- There doesn’t seem to be a lot of traffic on the mailing lists (dev and 
especially user)
- There seems to be several products (UserALE, Distill, Tap and Stout) but I 
only see release votes for UserALE. How are the other products released?
- There also seem to be a python version of UserALE but I don’t see any release 
votes for it either.
- The last four board reports have listed the same goals to reach graduation. 
Has any progress been made on these?

Thanks,
Justin



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

Re: New distribution guidelines

[Justin Mclean]

Hi,

Thanks for the feedback.

> There's some spurious text at the start of the page.

I’ll remove this.

> Also, what does the acronym IP mean?

IP = Intellectual property

> - "Releases must be placed in the Apache mirror system."
> Which releases are being referred to here? Source and binaries, or just 
> sources?

The intention was source releases (but both can be placed there), I’ll update 
it to say that.

> - "Source releases and convenience binaries need to be made from IPMC
> and PPMC approved ASF releases."
> As it stands, the sentence appears to be recursive.

It means you can’t make a release from a random point in version control. 
Releases distributed on other platforms need to come from what was contained in 
a voted releases. Can you suggest some better wording? Perhaps simplifying to 
“Convenience binaries need to be made from IPMC approved ASF releases” is 
better?

> - "Where possible it should be pointed out that Apache project make
> source releases and convenience binaries are just a convenience for
> end user."
> Does not read well.

I agree how about "Apache projects make source releases but can if needed 
provide convenience binaries to end users.”?

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

New distribution guidelines

[Justin Mclean]

Hi PPMC members,

New distribution guidelines, that we have been working on for some time, have 
been published here:
https://incubator.apache.org/guides/distribution.html

They contain information on distributing releases on 3rd party platforms 
including Maven, GitHub, Docker, NPM and PiPy.

Note that these are good suggestions on best practice and incubating projects 
can do things differently, but if you follow these guidelines, you are less 
likely to have issues on graduation.

If you have any questions or feedback on these guidelines, please do so on the 
Incubator general list.

Thanks,
Justin

[VOTE][RESULT] Distribution guidelines for platforms

[Justin Mclean]

HI,

So this passes with 6 +1 vest and one -0 vote. Thanks to everyone who taken 
part in this conversation and others over the last couple of years to make this 
happen.

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

Re: [DISCUSS] Graduate Apache Superset (incubating) as a TLP

[Justin Mclean]

Hi,

> I’m not too surprised to hear that one or more people haven’t sent emails to 
> the list… most of the engagement happens on the GitHub repo and on Slack. 
> With help from our mentor, I’ve already reached out to folks who were 
> erroneously not on the private list (for varied reasons), and I believe most 
> have signed up already since then. Whimsy shows that 19 of 22 PPMC members 
> are on the list presently, but I have no way of seeing which three are not.

Currently the following people are not subscribed:
Aaron Suddjian
Beto Dealmeida
Bogdan Kyryliuk
Chris Williams
Daniel Gaspar
Michelle Thomas
Serena Jiang


> All that having been said, we’ve reviewed the list and feel these PPMC 
> members are indeed active within the community and/or in good standing with 
> the community.

That sounds fine to me.

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

Re: [DISCUSS] Graduate Apache Superset (incubating) as a TLP

[Justin Mclean]

Hi,

> Thanks for bringing up your concern here. The synchronous meeting you 
> describe does have an agenda with meeting minutes/notes [1], which are open 
> to the public, and was previously shared on the dev list [2]

I note those in attendance are listed by company affiliation, contributors 
should act as individuals not what company they are affiliated with. The last 
time it was shared on the list was more than a year ago, this does't seem open 
and transparent communication that an ASF project needs to follow. These 
discussions need to be brought back to the mailing they need so they can 
involve the wider community especially those who can’t attend due to other 
commitments, including their day job or time zone issues.

> From this point forward, we will make it clear that all are invited, and we 
> will share out the notes after each meeting.

A better solution might be to not have them at all and have the discussion 
asynchronous on the mailing list. This this can be inconvenient it it give 
better value to the whole community not just those who know about and can 
attend those meetings.

> Let us know if this assuages the concern, and if not, we’ll address further.

It still a concern IMO, and I see it was noted as a concern in a board report, 
but doesn’t seem to have been addressed. I can see improvements in this project 
in a lot of other areas. It would be good to hear from other IPMC members and 
your mentors on this subject.

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

Re: [DISCUSS] Graduate Apache Superset (incubating) as a TLP

[Justin Mclean]

Hi,

I know at one point this project was have bi-weekly synchronous meetings. Is 
this still happened? My concern is that I don’t see any information of what 
happens at these meetings being brought back to the mailing list.

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

Re: [DISCUSS] Graduate Apache Superset (incubating) as a TLP

[Justin Mclean]

Hi,

With your proposed PMC list I can see a number of the people mentioned  don’t 
seem to be active and a number are not signed up to the project private mailing 
list. A quick check found at least one who looks to have not sent a single 
email to the mailing list during the entire incubation project. Has the project 
asked if these people want to be on the new PMC? When a projects graduates it 
sometimes a good idea to reduce the new PMC list to people who are active in 
the project and prepared to take on responsibility of being PMC members.

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

Re: [DISCUSS] Graduate Apache Superset (incubating) as a TLP

[Justin Mclean]

Hi,

I think there's a couple of minor thing that need some minor 
fixes/clarification.

I was looking at your website and can’t see where I can download the released 
versions  form the Apache mirrors [1]. (This relates to CD10 in the maturity 
model and the distribution part.)

I  assume the main way people install Apache eSuperset is via PyPi [4]. It 
would be good to update the logo and information on that page and make it 
clearer that Superset is an Apache project. (This releases to LC50 in the 
maturity model)

It looks like your web set is missing a few of the required links as well [2] 
[3]

You might also want to check with trademarks about the links on the front pages 
to other commercial products and companies as usually this is not allowed. some 
of these companies would also have conditions around how their trademarks can 
be used.


Thanks,
Justin

1.https://dist.apache.org/repos/dist/release/incubator/superset/
2. https://whimsy.apache.org/pods/project/superset
3. https://incubator.apache.org/guides/sites.html
4. https://pypi.org/project/apache-superset/
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Logo

[Justin Mclean]

Hi,

Your might want to ask apache central services you help you with a logo.

Thanks,
Justin


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

Re: [VOTE] Distribution guidelines for platforms

[Justin Mclean]

Hi Dave,

Much appreciated.

Thanks,
Justin

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

Re: [VOTE] Distribution guidelines for platforms

[Justin Mclean]

Hi Dave,

Just wondered if you have reconsider you -1 vote after the discussion here and 
elsewhere?

What more would you required in order to vote +1 on this?

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

[Mentors] Timeline for Octobers Report due Wednesday October 7th

[Justin Mclean]

Hi,

The report can be found here [1]

Timeline for October report:
Wed October 7th Podling reports due by end of day
Sun October 11thShepherd reviews due by end of day
Sun October 11thSummary due by end of day
Tue October 13thMentor signoff due by end of day
Wed October 14thReport submitted to Board
Wed October 21stBoard meeting

Podlings/projects expected to report are:

AGE
APISIX
Annotator
BlueMarlin
DLab
Flagon
Gobblin
Liminal
Livy
MXNet
Milagro
NuttX
Pegasus
Pony Mail
S2Graph
SDAP
Sedona
TVM
Teaclave
TubeMQ
Warble
Weex
YuniKorn

We’ve has a number of no report projects that have missed two reports in a row, 
please make sure the reports are submitted this time.

S2Graph
SDAP
Warble
Weex

Thanks,
Justin


1. https://cwiki.apache.org/confluence/display/INCUBATOR/October2020


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

Re: [VOTE] Graduate Apache IoTDB as TLP

[Justin Mclean]

Hi,

The project has become a TLP so there no need to vote any more :-)

Thanks,
Justin

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

Re: [DISCUSS] Apache TVM Graduation

[Justin Mclean]

Hi,

> Thanks Justin. As mentioned in the last email. We are following the
> previous naming convention of similar conferences like "Kafka Summit" and
> "Spark + AI Summit”.

I believe are slightly different sort of events as they are not run by the 
project but by another 3rd party / commercial entity, so they can’t use Apache 
in the name of the the conference, but please double check with trademarks.

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

Re: [DISCUSS] Apache TVM Graduation

[Justin Mclean]

Hi,

> The TVM PPMC would certainly be more than happy to follow trademarks
> suggestions on event brandings and make sure the event is compliant.
> To follow up the naming compliance. Notably, in the main page the project
> name "Apache (incubating) TVM" is used in the first and most prominent
> reference [1].

No it doesn’t the first and most prominent reference is in the title, which 
you’ll note the policy explicitly mentions. The title fails to mention this is 
an Apache project.

Thanks,
Justin


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

Re: [DISCUSS] Apache TVM Graduation

[Justin Mclean]

Hi,

The conference hasn’t yet been approved by trademarks, but a request to use 
that domain has been asked [1]. I don’t think this is an issue unless 
trademarks says otherwise. My guess is that they may want a little more 
information to see if it complies with event branding policy [2]. It btw 
doesn’t currently seem to comply with [3]

Thanks,
Justin


1. 
https://lists.apache.org/thread.html/r8559979c58fb92f08f3e253522dc227a51313dafff2ec19076e1093c%40%3Ctrademarks.apache.org%3E
2. https://www.apache.org/foundation/marks/events
3. https://www.apache.org/foundation/marks/events#naming
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] Apache TVM Graduation

[Justin Mclean]

Hi,

Sorry my mistake, I meant to say tvm.ai not tvm.io, but as I said subdomains on 
tvm.ai are not redirecting. For instance discuss.tvm.ai stays as it is. Other 
sub-domains include ci.tvm.ai , tracking.tvm.ai and docs.tvm.ai that I’ve 
found. There might be others, of those four, only docs redirects.

I notice that forum [1] also states "Open source community on end to end stack 
for deploying deep learning workloads to hardware backends tvmlang.org.” Who 
controls tvmlang.org? It not clear on that page that this is a space for 
discussion about an Apache project.

Thanks,
Justin

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

Re: [DISCUSS] Apache TVM Graduation

[Justin Mclean]

Hi,

Thanks for the response. I think the docker issue is resolved.

I still have concerns about use of tvm.io. I have discovered several other 
subdomains (six in total) that do not redirect to the Apache site, there might 
be others. It's still unclear who has control of this domain name. The issue 
here, is not the use of the forum but of the domain name and who it is 
controlled by, branding policy is clear on the use of such names. I suggest you 
discuss this with trademarks / branding.

I still have concerns about the low number of release (i..e two) and there have 
been only a singe release manager. It’s generally expected that a project make 
3 or 4 releases with a couple of different release managers, this certainly 
isn’t a hard rule but two in this case doesn’t seem enough. How much effort 
would it be to make another release with a different release manager?

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

Re: [DISCUSS] Apache TVM Graduation

[Justin Mclean]

Hi,

The "install from source” page should probably point people to the source 
releases rather than the latest code in GitHub.

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

Re: [DISCUSS] Apache TVM Graduation

[Justin Mclean]

Hi,

> I am sure there are many other binary packaging out there that use Apache
> project names, for example this one for Apache Spark:
> https://hub.docker.com/r/bitnami/spark/

What other Apache projects do (Spark in particular for various reasons) are not 
always good examples to follow. But you'll note in this case it:
a) Calls it Apache Spark
b) Includes a link to space.apache.org
b) In this case it seem clear it is a 3rd party, unlike TVM.

IMO It should also have a trademark disclaimer and I’m not sure that the way 
they have set up latest would be compliant with ASF policy. Ignoring the latest 
tag you note that the tags also match Apache releases.

> Are you concern about the name? The Docker image hub clearly stated this is
> not official Docker image from Apache TVM podling. I think that is enough
> to indicate this is not done by Apache TVM as community.

The docker images, if you found them on their own, give no indication that is 
an Apache project or that this are not official releases. If I search for 
“docker tvm” I get this link [1]. There is very little information on that 
page, no recognition of Apache trademarks and no disclaimers.There are also 
versions tagged that are not Apache releases. 

Why didn’t the project use Infra’a docker offering? [3]

> And I am kind of surprise about your comment and question about the number
> of downloads.

A large number of downloads may indicate that users are using the docker images 
rather than the offical sources. This may be fine if they are released 
versions, but is probably not be fine if they are not. Hence the latest tag 
being problematic.

I find it odd in the TVM case there are more releases in Docker using the same 
numbering system as the Apache releases. Why this discrepancy?

Thanks,
Justin

1. https://hub.docker.com/u/tvmai
2. https://www.apache.org/foundation/marks/#products
3. https://hub.docker.com/u/apache
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] Apache TVM Graduation

[Justin Mclean]

Hi,

On that installation pages it does says "We provide docker utility scripts to 
help developers to setup development environment. They are also helpful run 
through TVM demo and tutorials.” and "You can find some un-official prebuilt 
images in https://hub.docker.com/r/tvmai/.” IMO this doesn’t match with them 
being just CI images used for testing.

With the documentation I note in one place it says "to use the official Docker 
Image.” 

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

Re: [DISCUSS] Apache TVM Graduation

[Justin Mclean]

Hi,

> Then why do they have 40K+ downloads? It also doesn’t explain the version 
> numbers.

Sorry 4K I misread that, but even that seem high for something that is used for 
testing.

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

Re: [DISCUSS] Apache TVM Graduation

[Justin Mclean]

Hi,

> - As you can see that the domain redirects to https://tvm.apache.org/.
>  So hopefully there is no confusion here.

In some cases it does not. e.g. discuss.tvm.ai IMO this is a graduation blocker.

> P2: releases
> - The PPMC has a well documented release process[1]
>  that anyone can go and produce a release.
> - While we understand that it is good to produce more releases,
>  hopefully it is not a hard blocker, as the most important thing
>  for the PMC to be able to make high-quality Apache releases.

IMO this is a graduation blocker. A project meeds to make several releases with 
different release managers. Even if it is well documented only having one 
release manager is a large risk. If the process is well documented and easy to 
do then why haven’t you produced more releases?


> P2: Docker image
> 
> - These docker images do not contain tvm, instead they contain CI
> environment
>  to set up dependencies(e.g. compilers libraries) for running integration
> tests.

Then why do they have 40K+ downloads? It also doesn’t explain the version 
numbers.

> - These images are not Apache releases, there is a clear disclaimer
>  that they are thirdparty and not part of the ASF release[1].

If they are not Apache releases then they cannot use the TVM name.

> - The PPMC also clearly understand the need to protect Apache brand, and
>  clearly differentiate Apache release from thirdparty ones by adding
> disclaimers[3] to places when they are referred to.

You need to do more than just add a disclaimer.

>  name that does not contain tvm. Please note again these binaries are only
>  used for integration test purposes, the community do not intend to
> advertise them as Apache releases.

Except they are [1]

Thanks,
Justin

1. https://tvm.apache.org/docs/install/index.html
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] Apache TVM Graduation

[Justin Mclean]

Hi,

I’m also concerned that the person who seems responsible for these docker 
images seems to be the proposed chair of the project.

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

Re: [DISCUSS] Apache TVM Graduation

[Justin Mclean]

Hi,

I also have several concerns.

1.  Use of the tvm.ai domain - has permission been obtained from trademark to 
use this domain? Who has control of it?

2.  With only 2 releases with 1 release manager I don’t think the project is 
mature enough to graduate,

3. Branding/trademarks on these docker images [1] I’m concerned that users are 
using these rather than the official releases. I note they include version 
numbers that are not Apache releases. Do these contain unreleased code?

4. I also have concerns about the review position. It would seem that this  
gives a path for people to contribute code to become committers but not other 
forms of contribution.


1. https://hub.docker.com/u/tvmai
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org