Hi Justin
Right now, I updated our rat exclude config as following, is this allowed? The
concern may about JSON file for our test cases data and frontend/UI dependency
descriptions, but JSON format is not allowed to add the header.
org.apache.rat
apache-rat-plugin
0.12
-1 (binding) due to source under CC-BY license which is Cat B. It can be used
but not included in source release.
Regards
JB
On 03/23/2018 10:16 AM, Mohammad Asif Siddiqui wrote:
> Hi All,
>
> This is a call for vote to release Apache ServiceComb Java-Chassis
> (Incubating) version 1.0.0-m
This is not uncommon, at least for filtering the initial PPMC members at
the point of graduation. Obviously it should be the PPMC who decides this
in a regular consensus.
What would be unusual (and perhaps controversial) is using the graduation
for "removing" PPMC members who had been voted in dur
Hi -
This would be a legitimate thread on private@, or in a generic email on dev@
asking for and suggesting responses on private@. The principle is allowing
personnel/personal decisions to remain private at the individual’s choice.
Regards,
Dave
Sent from my iPhone
> On Mar 23, 2018, at 8:
Will do, thanks.
On Fri, Mar 23, 2018 at 19:04 John D. Ament wrote:
> On Fri, Mar 23, 2018 at 9:02 PM David Neuman
> wrote:
>
> > Great, thanks a lot for the info John. Since I have spoken to each of
> the
> > PMC members in question individually, I think we are safe to make our
> > changes an
Yes. I think our exclusion file of rat is too wide, Jiang has also pointed that
out.
I am closing this vote. Thanks everyone to help us. We are going to fix them. :)
--
Sheng Wu
Apache SkyWalking original creator and PPMC member
-- Original -
Hi,
Perhaps a silly question but I notice several people say they used rat to check
this release. Rat clearly shows the jars, does rat need to flag these in a more
serious way or were they hidden by a too wide rat exclusion file?
Thanks,
Justin
--
-1.
Here are the checkings those I did:
I can build the binary from the source kit.
We need separate License and NOTICE file for binary and source release.
I just checked RAT plugin setting on the parent POM.
There are some exclusion of the configuration, protocol even the test data,
we need to a
Hi,
Seems to be two open vote threads which is slightly confusing, so re posting
this just so it doesn’t get lost in the other thread.
-1 binding for including compiled code in a source release. Also LICENSE and
NOTICE look to be listing dependancies not bundled items [4][5]
I checked:
- incub
Hi,
-1 binding for including compiled code in a source release. Also LICENSE and
NOTICE look to be listing dependancies not bundled items [4][5]
I checked:
- incubating in name
- signatures and hashes good
- DISCLAIMER exists
- LICENSE lists items that are not bundled in the source release pleas
Hi Justin,
Thanks for pointing that out. I just filled a JIRA[1] for it and submit
quick fix for it.
[1]https://issues.apache.org/jira/browse/SCB-427
Willem Jiang
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On
I need to get more familiar with that license list!
Changing to -1 to have licensing fixed
On 23 March 2018 at 19:22, Justin Mclean wrote:
> Hi,
>
> Sorry but it’s -1 binding from me as the source release contains some
> CC-BY licensed content in plain text. [1][2] CC-BY is considered Category
Hi,
-1 binding as NOTICE is incorrect. This normally would be is a minor thing but
you have been previously asked to fix this. [1]
Also unable to build from source please include instruction on how to build
from source in the releasee.
I checked:
- incubating in name
- signatures and hashed go
Hi,
-1 binding due to bundled crypto code. If the crypto process been done and just
not recorded yet or I missed it happy to change my vote.
Everything else is mostly OK. I checked:
- incubating in name
- signature and hashes good
- DISCLAIMER exists
- LICENSE and NOTICE look OK (except for belo
Hi IPMC,
I have been invited and are going to give a speech about Apache SkyWalking
(Incubating) in QCon Beijing 2018. The subject is `the Development of
SkyWalking, from a small project into global community`. Most things in that
speech will be about the project itself, and its development, s
On Fri, Mar 23, 2018 at 9:02 PM David Neuman
wrote:
> Great, thanks a lot for the info John. Since I have spoken to each of the
> PMC members in question individually, I think we are safe to make our
> changes and have them continue on as committers.
>
Remember, if it didn't happen on list it d
Great, thanks a lot for the info John. Since I have spoken to each of the
PMC members in question individually, I think we are safe to make our
changes and have them continue on as committers.
On Fri, Mar 23, 2018 at 16:27 John D. Ament wrote:
> Its quite common that people stop working on open
Hi,
-1 for other reasons than stated by other people. i.e. the source file LICENSE
file needs work.
Although "unapproved licenses" is misleading as it’s just that those files
don’t (and shouldn’t) have headers.
I checked:
- incubating in artefact name
- signatures and hashes correct
- LICENSE
Hi,
Sorry but it’s -1 binding from me as the source release contains some CC-BY
licensed content in plain text. [1][2] CC-BY is considered Category B [3] and
can’t be included in a source release. These files also incorrectly IMO have
ASF headers.
Everything else is good. I checked:
- name inc
Hi,
+1 binding
I checked:
- name includes incubating
- DISCLAIMER exists
- LICENSE and NOTICE all good
- No unexpected binary files
- All source files have ASF headers
- Can compile form source
Thanks,
Justin
-
To unsubscribe,
Hi,
+1 binding
I checked:
- name includes incubating
- DISCLAIMER exists
- LICENSE and NOTICE all good
- No unexpected binary files
- All source files have ASF headers
- Can compile form source
Thanks,
Justin
-
To unsubscribe,
John,
OK. Thanks. :) We shared a check list document for SkyWalking committer and
ppmc to vote.
---Original---
From: "John D. Ament"
Date: Sat, Mar 24, 2018 06:20 AM
To: "general";
Subject: Re: [VOTE] Release Apache SkyWalking (incubating) version
5.0.0-alpha(2nd round)
Sheng,
Its perfe
Its quite common that people stop working on open source projects.
However, part of the Apache way is merit never expires. While you may not
want to include them in your PMC, keeping them available as a committer
isn't a bad thing.
Most podlings I've seen will send an email "here's the proposed P
I suspect its a bad/out dated mail template, or secretary did extra work.
I haven't had to do anything for new podling committers in quite a while.
If something does come up, feel free to ping me and I'll help get it
situated.
I'll also see if I can figure out how to get the email from root update
Sheng,
Its perfectly acceptable for PPMC members to vote on the release here.
>From my point of view, it gives me a better feeling that the PPMC knows the
steps required to have a valid release go out the door, what checks have to
be done. So I encourage PPMC members to vote here, please don't di
For Apache OpenWhisk we are in same situation so it would be good to understand
the guideline on how to handle such situation.
- Carlos Santana
@csantanapr
> On Mar 23, 2018, at 4:06 PM, Dave Neuman wrote:
>
> Hey IPMC,
> I had a question about altering the PMC for graduation.
> We have a few
Hey IPMC,
I had a question about altering the PMC for graduation.
We have a few folks who are no longer active participants in our project
that are still a part of our PMC. In the process of generating our
graduation resolution we were wondering if we could take the opportunity to
have these membe
* Rat check ok
* Signatures ok
I'm having issues building from source. I fixed on issue involving protoc
by installing version 2.5 (as used in the travis config) and adding it to
my PATH for the build. However, I came across another error:
[ERROR] Failed to execute goal org.apache.maven.plugins:
+1
* Signatures ok
* Build and test ok
* Rat check has errors regarding files in
java-chassis-distribution/src/release/licenses/, though adding that to the
excludes in the root pom.xml fixes those errors.
On 23 March 2018 at 04:16, Mohammad Asif Siddiqui
wrote:
> Hi All,
>
> This is a call for
Forwarding my +1 from the dev list.
James
On Thu, Mar 22, 2018 at 8:31 AM Henk P. Penning wrote:
> On Thu, 22 Mar 2018, Ohad Shacham wrote:
>
> > Date: Thu, 22 Mar 2018 13:29:55 +0100
> > From: Ohad Shacham
> > To: general@incubator.apache.org
> > Subject: [VOTE] Release Apache Omid 0.9.0.
Xin
You have already voted in SkyWalking dev mail list. That thread is already
included in this mail. This vote is for IPMC and other Apache community people
to check our release.
Thanks.
On 2018/03/23 14:00:55, xin zhang wrote:
> +1
>
> Checked the signed Keys and checksum.
> Checked the b
When I got the email from root@apache it said:
Please grant additional karma to the projects in your domain
you wish the user to have commit to.
Only PMC chairs can grant karma. If needed, please post to the general@/
dev@/private@ list of your project asking for someone with sufficient
karma t
+1
Checked the signed Keys and checksum.
Checked the binary with the examples.
Run the rat to verify the License header issue.
DISCLAIMER exists
Verify the nexus Staging repo by running the demo example
Compiled from source
Checked for archive matching git tag
On Fri, Mar 23, 2018 at 11:13 AM,
On 22 March 2018 at 17:36, Robert Butts wrote:
> Ah, thanks for the clarification.
>
> Ok, the 2.0.0 RPMs have been removed from dist
Huh? I still see files here:
https://dist.apache.org/repos/dist/release/incubator/trafficcontrol/2.0.0-incubating/
Please remove the folder and its contents.
>
Hi All,
This is a call for vote to release Apache ServiceComb Java-Chassis (Incubating)
version 1.0.0-m1
Apache ServiceComb (Incubating) Community has voted and approved the release.
Vote Thread :
https://lists.apache.org/thread.html/b778a8787435b963c0743c518c3bc0b4c419a4010edc369
35 matches
Mail list logo
