Re: [VOTE] Apache Gobblin 0.12.0 release RC2

[sebb]

On 1 April 2018 at 09:21, Justin Mclean  wrote:
> Hi,
>
>> Can you elaborate a bit ? I checked the NOTICE file and it looks good to me. 
>> It mentions the included dependencies like bootstrap.
>
> Dependancies should not be mentioned in NOTICE. if something is bundled then 
> it's license and copyright needs to be in LICENSE not NOTICE.

Huh?
AIUI:

non-bundled Dependencies are irrelevant to the contents of NOTICE and LICENSE.
Though of course the license does affect whether it is allowed to be a
dependency.

NOTICE and LICENSE are only for bits that are bundled in the release artifact.
The LICENSE file must reflect the license(s) for all the bundled bits.
The NOTICE file must include all required notices and nothing more.

Bundled 3rd party code *can* affect the NOTICE file.
That's why it is important to only include required notices.

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

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

Re: [VOTE] Release Apache SkyWalking (incubating) version5.0.0-alpha(3rd round)

[sebb]

On 1 April 2018 at 01:43, 吴晟 Sheng Wu  wrote:
> Hi sebb,
>
>
> I see your point, that is why we provide the build document[1] if you want to 
> build from GitHub tag. Git submodules are used in our project for binding 
> multi repos. The source codes tar is provided by running some source code 
> release process, by following project document[2] and script [3].

I see.
So cloning the Git repo is not sufficient to get all the code (unless
there is an option to automatically include submodules that I have
missed).

>
> And for `dependency-reduced-pom.xml`, it is generated in building the 
> project, when we run build and tar source code. If you think we should not 
> include it, I think we can add an exclusion in next release.

That would be a good idea.

>
> Is that good enough for you?

I think there is a problem with the build process, because the source
artifact contains other items that are not in Git.

$ diff -r incubator-skywalking/ apache-skywalking-apm-incubating-5.0.0-alpha
Only in incubator-skywalking/: .git
Only in incubator-skywalking/: .github
Only in incubator-skywalking/: .gitignore
Only in incubator-skywalking/: .travis.yml
Only in incubator-skywalking/apm-protocol/apm-network/src/main/proto: .git
Only in apache-skywalking-apm-incubating-5.0.0-alpha/apm-sniffer/apm-agent:
dependency-reduced-pom.xml
Only in apache-skywalking-apm-incubating-5.0.0-alpha/apm-sniffer/apm-agent-core:
dependency-reduced-pom.xml
Only in apache-skywalking-apm-incubating-5.0.0-alpha/apm-sniffer/apm-agent-core:
file:
Only in 
apache-skywalking-apm-incubating-5.0.0-alpha/apm-sniffer/apm-toolkit-activation/apm-toolkit-log4j-1.x-activation:
dependency-reduced-pom.xml
Only in incubator-skywalking/: docs
Only in incubator-skywalking/skywalking-ui: .git
Only in incubator-skywalking/skywalking-ui: .gitignore
Only in incubator-skywalking/skywalking-ui: .travis.yml
Only in apache-skywalking-apm-incubating-5.0.0-alpha/skywalking-ui: etc
Only in incubator-skywalking/: tools

In the above listing, incubator-skywalking is the git clone produced by:
$ git clone --depth 1
https://github.com/apache/incubator-skywalking.git -b v5.0.0-alpha
$ cd incubator-skywalking
$ git submodule init
$ git submodule update
and apache-skywalking-apm-incubating-5.0.0-alpha is the unpacked
version of apache-skywalking-apm-incubating-5.0.0-alpha-src.tgz

The files that are only in Git are generally OK.

However there should not generally be any files in the source archive
that are not also in Git.

Apart from the poms, there are two such directories:

apm-sniffer/apm-agent-core/file:
skywalking-ui/etc

The latter is empty.
However the former contains quite a few directories which look to be
crud from the build process.

>
> [1] 
> https://github.com/apache/incubator-skywalking/blob/v5.0.0-alpha/docs/en/How-to-build.md#build-from-github
> [2] 
> https://github.com/apache/incubator-skywalking/blob/v5.0.0-alpha/docs/en/How-to-release.md#build-and-sign-the-source-code-package
> [3] 
> https://github.com/apache/incubator-skywalking/blob/v5.0.0-alpha/tools/releasing/create_source_release.sh
>
>
> --
> Sheng Wu
> Apache SkyWalking original creator and PPMC member
>
>
>
>
>
>
>
> -- Original --
> From:  "sebb";
> Date:  Sun, Apr 1, 2018 08:28 AM
> To:  "general";
>
> Subject:  Re: [VOTE] Release Apache SkyWalking (incubating) 
> version5.0.0-alpha(3rd round)
>
>
>
> On 1 April 2018 at 00:53, 吴晟 Sheng Wu  wrote:
>>> Please include the SCM URL in the VOTE email, as the tag and commitId
>>> aren't much use without it.
>>
>>
>>
>> Hi Sebb
>>
>>
>> The SCM url with tag is this : 
>> https://github.com/apache/incubator-skywalking/tree/v5.0.0-alpha
>>
>>
>> Thanks.
>
> I see.
>
> However that does not actually have a tag with the name '5.0.0-alpha'
>
> Also, when I compare the contents of
> apache-skywalking-apm-incubating-5.0.0-alpha-src.tgz with the tag,
> there are several files in the source release that don't appear to
> have a counterpart in the Git repo.
>
> For example, apm-sniffer/apm-agent/dependency-reduced-pom.xml
>
> skywalking-ui/*
>
> That does not seem right
>
>>
>> --
>> Sheng Wu
>> Apache SkyWalking original creator and PPMC member
>>
>>
>>
>>
>>
>>
>>
>> -- Original --
>> From:  "sebb";
>> Date:  Sun, Apr 1, 2018 07:41 AM
>> To:  "general";
>>
>> Subject:  Re: [VOTE] Release Apache SkyWalking (incubating) version 
>> 5.0.0-alpha(3rd round)
>>
>>
>>
>> On 31 March 2018 at 05:07, 吴晟 Sheng Wu  wrote:
>>&

Re: [VOTE] Apache Gobblin 0.12.0 release RC2

[sebb]

On 1 April 2018 at 13:28, Justin Mclean  wrote:
> Hi,
>
>> non-bundled Dependencies are irrelevant to the contents of NOTICE and 
>> LICENSE.
>
> Yep 100% agree.
>
>> Though of course the license does affect whether it is allowed to be a
>> dependency.
>
> Also agree.
>
>> NOTICE and LICENSE are only for bits that are bundled in the release 
>> artifact.
>
> Yep 100% in agreement.
>
>> The LICENSE file must reflect the license(s) for all the bundled bits.
>
> Yep - in this case it’s missing some stuff here but that’s minor.
>
>> The NOTICE file must include all required notices and nothing more.
>
> And in this case it includes more than is needed. Do you disagree?

I have not looked at the NOTICE file.
I was responding to your statement:

"if something is bundled then it's license and copyright needs to be
in LICENSE not NOTICE."

As noted above, I don't think that is true.

>> Bundled 3rd party code *can* affect the NOTICE file.
>> That's why it is important to only include required notices.
>
> But usually doesn’t with MIT or BSD licenses as is the case here. In most 
> cases required notices are quite rare.

Indeed, but that does not make the statement true.

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

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

Re: [VOTE] Release Apache SkyWalking (incubating) version5.0.0-alpha(3rd round)

[sebb]

On 1 April 2018 at 14:03, John D. Ament  wrote:
> From reading through this, I think I understand the confusion faced.
>
> Typically when we see a source release, its tied to a single git repo.
> Generating the source release in this case involves a special type of git
> checkout, which IMHO is just fine.
>
> It just needs to be documented that when you clone the repo, it's using the
> --recurse-submodules flag.  This should result in
>
> Cloning into 'incubator-skywalking'...
> remote: Counting objects: 114594, done.
> remote: Compressing objects: 100% (38/38), done.
> remote: Total 114594 (delta 10), reused 29 (delta 2), pack-reused 114539
> Receiving objects: 100% (114594/114594), 134.38 MiB | 4.55 MiB/s, done.
> Resolving deltas: 100% (44254/44254), done.
> Submodule 'apm-protocol/apm-network/src/main/proto' (
> https://github.com/apache/incubator-skywalking-data-collect-protocol.git)
> registered for path 'apm-protocol/apm-network/src/main/proto'
> Submodule 'skywalking-ui' (https://github.com/apache/incubator-skywalking-ui)
> registered for path 'skywalking-ui'
> Cloning into
> '/Users/johnament/src/apache/incubator-skywalking/apm-protocol/apm-network/src/main/proto'...
> remote: Counting objects: 52, done.
> remote: Compressing objects: 100% (44/44), done.
> remote: Total 52 (delta 34), reused 10 (delta 8), pack-reused 0
> Cloning into
> '/Users/johnament/src/apache/incubator-skywalking/skywalking-ui'...
> remote: Counting objects: 4374, done.
> remote: Compressing objects: 100% (84/84), done.
> remote: Total 4374 (delta 38), reused 51 (delta 17), pack-reused 4268
>
> Receiving objects: 100% (4374/4374), 3.56 MiB | 6.15 MiB/s, done.
> Resolving deltas: 100% (2107/2107), done.
> Submodule path 'apm-protocol/apm-network/src/main/proto': checked out
> 'c02c12af12116121e25155d1f3fca0fadee5f2e9'
> Submodule path 'skywalking-ui': checked out
> '922c012efd0c385e3c502d06d2730c73452f779d'
>
>
> and then the checks that Sebb is trying should work.
>
> Sheng, do you know if this checkout is documented somewhere?

Also, when GitHub is used to grab the code as a Zip, it does not
include the submodules.

Maybe there is a setting that can tell GitHub to adjust the Zip
contents as well.

> John
>
> On Sun, Apr 1, 2018 at 8:49 AM sebb  wrote:
>
>> On 1 April 2018 at 01:43, 吴晟 Sheng Wu  wrote:
>> > Hi sebb,
>> >
>> >
>> > I see your point, that is why we provide the build document[1] if you
>> want to build from GitHub tag. Git submodules are used in our project for
>> binding multi repos. The source codes tar is provided by running some
>> source code release process, by following project document[2] and script
>> [3].
>>
>> I see.
>> So cloning the Git repo is not sufficient to get all the code (unless
>> there is an option to automatically include submodules that I have
>> missed).
>>
>> >
>> > And for `dependency-reduced-pom.xml`, it is generated in building the
>> project, when we run build and tar source code. If you think we should not
>> include it, I think we can add an exclusion in next release.
>>
>> That would be a good idea.
>>
>> >
>> > Is that good enough for you?
>>
>> I think there is a problem with the build process, because the source
>> artifact contains other items that are not in Git.
>>
>> $ diff -r incubator-skywalking/
>> apache-skywalking-apm-incubating-5.0.0-alpha
>> Only in incubator-skywalking/: .git
>> Only in incubator-skywalking/: .github
>> Only in incubator-skywalking/: .gitignore
>> Only in incubator-skywalking/: .travis.yml
>> Only in incubator-skywalking/apm-protocol/apm-network/src/main/proto: .git
>> Only in apache-skywalking-apm-incubating-5.0.0-alpha/apm-sniffer/apm-agent:
>> dependency-reduced-pom.xml
>> Only in
>> apache-skywalking-apm-incubating-5.0.0-alpha/apm-sniffer/apm-agent-core:
>> dependency-reduced-pom.xml
>> Only in
>> apache-skywalking-apm-incubating-5.0.0-alpha/apm-sniffer/apm-agent-core:
>> file:
>> Only in
>> apache-skywalking-apm-incubating-5.0.0-alpha/apm-sniffer/apm-toolkit-activation/apm-toolkit-log4j-1.x-activation:
>> dependency-reduced-pom.xml
>> Only in incubator-skywalking/: docs
>> Only in incubator-skywalking/skywalking-ui: .git
>> Only in incubator-skywalking/skywalking-ui: .gitignore
>> Only in incubator-skywalking/skywalking-ui: .travis.yml
>> Only in apache-skywalking-apm-incubating-5.0.0-alpha/skywalking-ui: etc
>> Only in incubator-skywalking/: tools
>

Re: [VOTE] Release Apache SkyWalking (incubating) version5.0.0-alpha(3rdround)

[sebb]

Agreed that the Zip/Clone URLs on the GitHub page are not a canonical source.

However it's not at all obvious that using these links will not
actually create a copy of the full source, as I found out.

If it is not possible to update GitHub settings so that the Zip is
complete, then it would be useful if the relevant part of the
documentation made this clear.

AFAIK Git projects with submodules are relatively rare, so IMO
projects that use the feature should make it clear.

On 1 April 2018 at 14:23, peng-yongsheng <8082...@qq.com> wrote:
> Maybe the source codes tar in github is not pass through this voting process.
>
> —
> Yongsheng Peng
> Apache SkyWalking PPMC member
>
>
>
>> 在 2018年4月1日，21:18，吴晟 Sheng Wu  写道：
>>
>> Hi Sebb
>>
>>
>>> Also, when GitHub is used to grab the code as a Zip, it does not
>>> include the submodules.
>>> Maybe there is a setting that can tell GitHub to adjust the Zip
>>> contents as well.
>>
>> Actually I don't know the way to do so. Even there is, Apache may more 
>> prefer to use their own source codes tar ball than the github, right?
>>
>>
>> --
>> Sheng Wu
>> Apache SkyWalking original creator and PPMC member
>>
>>
>>
>>
>>
>>
>>
>> -- Original --
>> From:  "sebb";
>> Date:  Sun, Apr 1, 2018 09:12 PM
>> To:  "general";
>>
>> Subject:  Re: [VOTE] Release Apache SkyWalking (incubating) 
>> version5.0.0-alpha(3rdround)
>>
>>
>>
>> On 1 April 2018 at 14:03, John D. Ament  wrote:
>>> From reading through this, I think I understand the confusion faced.
>>>
>>> Typically when we see a source release, its tied to a single git repo.
>>> Generating the source release in this case involves a special type of git
>>> checkout, which IMHO is just fine.
>>>
>>> It just needs to be documented that when you clone the repo, it's using the
>>> --recurse-submodules flag.  This should result in
>>>
>>> Cloning into 'incubator-skywalking'...
>>> remote: Counting objects: 114594, done.
>>> remote: Compressing objects: 100% (38/38), done.
>>> remote: Total 114594 (delta 10), reused 29 (delta 2), pack-reused 114539
>>> Receiving objects: 100% (114594/114594), 134.38 MiB | 4.55 MiB/s, done.
>>> Resolving deltas: 100% (44254/44254), done.
>>> Submodule 'apm-protocol/apm-network/src/main/proto' (
>>> https://github.com/apache/incubator-skywalking-data-collect-protocol.git)
>>> registered for path 'apm-protocol/apm-network/src/main/proto'
>>> Submodule 'skywalking-ui' 
>>> (https://github.com/apache/incubator-skywalking-ui)
>>> registered for path 'skywalking-ui'
>>> Cloning into
>>> '/Users/johnament/src/apache/incubator-skywalking/apm-protocol/apm-network/src/main/proto'...
>>> remote: Counting objects: 52, done.
>>> remote: Compressing objects: 100% (44/44), done.
>>> remote: Total 52 (delta 34), reused 10 (delta 8), pack-reused 0
>>> Cloning into
>>> '/Users/johnament/src/apache/incubator-skywalking/skywalking-ui'...
>>> remote: Counting objects: 4374, done.
>>> remote: Compressing objects: 100% (84/84), done.
>>> remote: Total 4374 (delta 38), reused 51 (delta 17), pack-reused 4268
>>>
>>> Receiving objects: 100% (4374/4374), 3.56 MiB | 6.15 MiB/s, done.
>>> Resolving deltas: 100% (2107/2107), done.
>>> Submodule path 'apm-protocol/apm-network/src/main/proto': checked out
>>> 'c02c12af12116121e25155d1f3fca0fadee5f2e9'
>>> Submodule path 'skywalking-ui': checked out
>>> '922c012efd0c385e3c502d06d2730c73452f779d'
>>>
>>>
>>> and then the checks that Sebb is trying should work.
>>>
>>> Sheng, do you know if this checkout is documented somewhere?
>>
>> Also, when GitHub is used to grab the code as a Zip, it does not
>> include the submodules.
>>
>> Maybe there is a setting that can tell GitHub to adjust the Zip
>> contents as well.
>>
>>> John
>>>
>>> On Sun, Apr 1, 2018 at 8:49 AM sebb  wrote:
>>>
>>>> On 1 April 2018 at 01:43, 吴晟 Sheng Wu  wrote:
>>>>> Hi sebb,
>>>>>
>>>>>
>>>>> I see your point, that is why we provide the build document[1] if you
>>>> want to build from GitHub tag. Git submodules are used in our p

Re: [VOTE] Apache Gobblin 0.12.0 release RC2

[sebb]

On 1 April 2018 at 14:15, Justin Mclean  wrote:
> Hi,
>
>> I have not looked at the NOTICE file.
>
> Perhaps your should as my statements was in context to that.
>
>> "if something is bundled then it's license and copyright needs to be
>> in LICENSE not NOTICE."
>>
>> As noted above, I don't think that is true.
>
> For what licenses do you think this is not true? license information always 
> goes in license and the license text usually includes the copyright so 
> there’s no need to duplicate it in notice.

Does https://www.apache.org/licenses/example-NOTICE.txt count?

If bundled bits never affect the NOTICE file, why is there a concern
about minimising the NOTICE contents?

> 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.12.0 release RC2

[sebb]

On 1 April 2018 at 15:29, Jim Jagielski  wrote:
>
>
>> On Apr 1, 2018, at 9:35 AM, sebb  wrote:
>>
>>
>> If bundled bits never affect the NOTICE file, why is there a concern
>> about minimising the NOTICE contents?
>>
>
> Let's consider the "touch points" between what we release and
> the downstream user and consumer eco-system. For these
> entities, the 3 "main" files that affect what they can do, as well
> as information that is of primary importance that determines
> their responsibilities are the README, LICENSE and NOTICE
> files:
>
>   o README: because it is the main communication channel between
> the project and downstream
>   o LICENSE: because it provides the distribution requirements
> and conditions
>   o NOTICE: because it provides the addition information that
> is required to be maintained and "transparent" for the
> downstream
>
> In many ways, NOTICE is extra data that must be included
> for all subsequent downstream and distros and, therefore,
> should include only what MUST be folded into the file. That's
> why it is defined as such ("... and nothing more"). We want
> to minimize extraneous work and efforts required for downstreams
> in order to make the use and consumption of Apache code and
> projects as easy as possible. A bloated NOTICE with lots
> of duplicate information unnecessarily adds addition workload
> and, esp, oversight.

Agreed, but I think you may have misunderstood why I wrote:

>> If bundled bits never affect the NOTICE file, why is there a concern
>> about minimising the NOTICE contents?

To my mind, your reply addresses the latter part of the sentence only.

My point was that NOTICE files need to be minimised because otherwise
bundled bits can cause it to become bloated.
i.e. bundled bits *can* affect the NOTICE file.
If bundled bits did not affect the NOTICE file then the file would not
contain anything more than the bare minimum.

I read Justin's statement to imply that bundled bits do not affect the
NOTICE file.
I don't think that is true; I think bundled bits can affect the NOTICE
file (albeit perhaps rarely).

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

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

Re: [ANNOUNCE] Release Apache SkyWalking (incubating) version 5.0.0-alpha

[sebb]

On 4 April 2018 at 02:32, 吴晟 Sheng Wu  wrote:
> Hi all,
>
>
> Apache SkyWalking (incubating) Team is glad to announce the first release of 
> Apache SkyWalking Incubating 5.0.0-alpha
>
>
> SkyWalking: APM (application performance monitor) tool for distributed 
> systems,
> especially designed for microservices, cloud native and container-based 
> (Docker, Kubernetes, Mesos) architectures.
> Underlying technology is a distributed tracing system.
>
>
> Download Links : 
> http://www.apache.org/dyn/closer.cgi/incubator/skywalking/5.0.0-alpha/
>

It's better to use the website download page:

http://skywalking.apache.org/downloads/

This does not vary between releases, and contains links to other
useful information.

> Release Notes : 
> https://github.com/apache/incubator-skywalking/blob/v5.0.0-alpha/CHANGES.md
>
>
> SkyWalking Resources:
> - Issue: https://github.com/apache/incubator-skywalking/issues
> - Mailing list: d...@skywalkiing.incubator.apache.org
> - Documents: 
> https://github.com/apache/incubator-skywalking/blob/v5.0.0-alpha/docs/README.md
>
>
>
>
> - Apache SkyWalking (incubating) Team
>
>
> =
> *Disclaimer*
>
>
> Apache SkyWalking (incubating) is an effort undergoing incubation at The
> Apache Software Foundation (ASF), sponsored by the name of Apache
> Incubator PMC. Incubation is required of all newly accepted
> projects until a further review indicates that the
> infrastructure, communications, and decision making process have
> stabilized in a manner consistent with other successful ASF
> projects. While incubation status is not necessarily a reflection
> of the completeness or stability of the code, it does indicate
> that the project has yet to be fully endorsed by the ASF.
>
>
>
>
>
> --
> Sheng Wu
> Apache SkyWalking original creator and PPMC member

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

Re: [ANNOUNCE] Release Apache SkyWalking (incubating) version 5.0.0-alpha

[sebb]

Also I just realised that the announce message does not have a link to
the main website.

On 4 April 2018 at 09:50, sebb  wrote:
> On 4 April 2018 at 02:32, 吴晟 Sheng Wu  wrote:
>> Hi all,
>>
>>
>> Apache SkyWalking (incubating) Team is glad to announce the first release of 
>> Apache SkyWalking Incubating 5.0.0-alpha
>>
>>
>> SkyWalking: APM (application performance monitor) tool for distributed 
>> systems,
>> especially designed for microservices, cloud native and container-based 
>> (Docker, Kubernetes, Mesos) architectures.
>> Underlying technology is a distributed tracing system.
>>
>>
>> Download Links : 
>> http://www.apache.org/dyn/closer.cgi/incubator/skywalking/5.0.0-alpha/
>>
>
> It's better to use the website download page:
>
> http://skywalking.apache.org/downloads/
>
> This does not vary between releases, and contains links to other
> useful information.
>
>> Release Notes : 
>> https://github.com/apache/incubator-skywalking/blob/v5.0.0-alpha/CHANGES.md
>>
>>
>> SkyWalking Resources:
>> - Issue: https://github.com/apache/incubator-skywalking/issues
>> - Mailing list: d...@skywalkiing.incubator.apache.org
>> - Documents: 
>> https://github.com/apache/incubator-skywalking/blob/v5.0.0-alpha/docs/README.md
>>
>>
>>
>>
>> - Apache SkyWalking (incubating) Team
>>
>>
>> =
>> *Disclaimer*
>>
>>
>> Apache SkyWalking (incubating) is an effort undergoing incubation at The
>> Apache Software Foundation (ASF), sponsored by the name of Apache
>> Incubator PMC. Incubation is required of all newly accepted
>> projects until a further review indicates that the
>> infrastructure, communications, and decision making process have
>> stabilized in a manner consistent with other successful ASF
>> projects. While incubation status is not necessarily a reflection
>> of the completeness or stability of the code, it does indicate
>> that the project has yet to be fully endorsed by the ASF.
>>
>>
>>
>>
>>
>> --
>> Sheng Wu
>> Apache SkyWalking original creator and PPMC member

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

Re: [VOTE] Apache Toree 0.2.0-incubating (RC4)

[sebb]

On 8 April 2018 at 06:51, Luciano Resende  wrote:
> We might need to update the release signing or release guide, in general,
> stating that we should not publish those anymore. The release signing
> slightly mentions that MD5 is weak, but AFAIK does not mention that it
> should not be published anymore.

https://www.apache.org/dev/release-distribution#sigs-and-sums says:
...

SHOULD NOT supply a MD5 checksum file (because MD5 is too broken).

> Anyway, I will remove the MD5 when I publish the artifacts from staging to
> release if the RC is successful and update the release scripts (of various
> projects) to not generate MD5 anymore.
>
> On Sat, Apr 7, 2018 at 9:50 PM, Henk P. Penning  wrote:
>
>> On Sun, 8 Apr 2018, Luciano Resende wrote:
>>
>> Date: Sun, 8 Apr 2018 03:28:37 +0200
>>> From: Luciano Resende 
>>> To: "general@incubator.apache.org" 
>>> Subject: [VOTE] Apache Toree 0.2.0-incubating (RC4)
>>>
>>
>> Hi,
>>
>> All distribution packages, including signatures, digests, etc. can be found
>>> at:
>>>
>>> https://dist.apache.org/repos/dist/dev/incubator/toree/0.2.0
>>> -incubating-rc4/
>>>
>>
>>   please don't publish .md5 files anymore ;
>>   your .sha512's are enough.
>>
>> Luciano Resende
>>>
>>
>>   Groeten,
>>
>>   HPP
>>
>>    _
>> Henk P. Penning, ICT-beta R Uithof MG-403_/ \_
>> Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
>> Leuvenlaan 4, 3584CE Utrecht, NL  F +31 30 253 4553 \_/ \_/
>> http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>
>
>
> --
> Luciano Resende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/

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

Re: Are MySQL driver and MySQL protocol allowed in distribution?

[sebb]

On 13 April 2018 at 11:26, Karl Wright  wrote:
> You can't distribute the MySQL driver, but as long as you don't distribute
> the driver, you are free to solve the problem any way you like.  You can
> require that the user download the driver themselves, or you can develop
> your own driver -- all of those are fine.

This is the policy that I think applies here:

http://www.apache.org/legal/resolved.html#optional

Does the product work without MySQL?
It sounds like that this would be an optional storage method, so
depending on it would be fine.

The uses who want to use MySQL will have to download the driver (and
accept the terms of its license).
Those that don't wish to use MySQL aren't affected.

> Karl
>
>
> On Fri, Apr 13, 2018 at 6:20 AM, 吴晟 Sheng Wu  wrote:
>
>> Hi,
>> Someone asked whether could provide a mysql based storage implemention for
>> SKyWalking.
>> I am aware mysql driver is under GPL, so should not be allowed, right?
>> Then how about the mysql protocol? If they implement the codes by
>> themself, because the storage required a few features compared to the real
>> driver.
>>
>>
>> Thanks
>> Sheng Wu

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

Re: Redirecting pagespeed.incubator.apache.org to modpagespeed.com

[sebb]

On 15 April 2018 at 14:48, Greg Stein  wrote:
> It is unreasonable to assume a podling can do everything on Day One.
>
> Incubation is a *process*, not an instantaneous production of effort.
>
> While the website work is being performed, having
> podling.incubator.apache.org NOT produce a 404 is useful.
>
> Having that page describe the podling is in the Incubator, adding the
> disclaimer, and saying "over  is our original site" is useful.
>
> IMO, you're being unreasonable.

But is it reasonable for the podling ASF website to redirect to their
existing site which does not have the disclaimer and contains
downloads that are not ASF releases and not identified as such?

i.e. would the *content* of

https://www.modpagespeed.com

be acceptable if it were hosted at

http://pagespeed.incubator.apache.org

I don't think that would be right.

> -g
>
>
> On Sun, Apr 15, 2018 at 8:22 AM, John D. Ament 
> wrote:
>
>> My input is a point for pagespeed to consider.  Personally, I'm not
>> comfortable with what's proposed by Druid but it's not worth muddying up
>> pagespeed's inquiry.  My preference is for a podling to get their website
>> moved over quickly (and we need to figure out how to help them make that
>> move quickly).  What I do believe though is that our branding requirements
>> would propagate over to that website as well (which it sounds like Druid
>> has a bit wrong, at least in my take).
>>
>> - Redirecting to another website that's hosting your docs doesn't remove
>> the need for proper naming, so it should be Apache Druid (incubating) or
>> Apache PageSpeed (incubating) upon first entry.
>> - Even if the website is hosted elsewhere, I still expect to see the
>> disclaimer.
>> - The downloads page should indicate these are not Apache releases.
>>
>> Perhaps Mark T has some more input on the branding and naming aspects.
>>
>> John
>>
>> On Sat, Apr 14, 2018 at 12:02 AM Julian Hyde 
>> wrote:
>>
>> > I (as a Druid mentor) suggested the placeholder page, for the exact
>> > reasons Greg describes. Short term, I promise, and better than a 404.
>> >
>> > Julian
>> >
>> > > On Apr 13, 2018, at 20:15, Greg Stein  wrote:
>> > >
>> > > One step at a time. If they want to throw a single page up *today*
>> rather
>> > > than wait six weeks to fully port their website... I would take the
>> page.
>> > > We already had an inquiry on Druid of where their site is.
>> > >
>> > > A placeholder is better than a 404. Unless, of course, you are
>> personally
>> > > volunteering to quickly move their entire site and workflow... ?
>> > >
>> > > Cheers,
>> > > -g
>> > >
>> > >
>> > >> On Fri, Apr 13, 2018, 22:03 John D. Ament 
>> > wrote:
>> > >>
>> > >> Gian, Otto,
>> > >>
>> > >> I can tell you that the proposed plan from Druid is not an OK plan
>> from
>> > my
>> > >> perspective.  One of your short term goals should be moving
>> > infrastructure
>> > >> over to the ASF.  This includes moving your website over.  Redirecting
>> > your
>> > >> ASF webpage to your old webpage will not fly.
>> > >>
>> > >> While we can't give the same level of support as you would see on
>> github
>> > >> pages (maybe we'll get there one day), setting up builds in Jenkins or
>> > >> Buildbot is pretty straight forward.  Even the incubator website runs
>> in
>> > >> this model.
>> > >>
>> > >> It's perfectly acceptable to link to pre-Apache releases on your
>> > website.
>> > >> I'm not sure if any of the docs lead you to believe otherwise, but
>> this
>> > is
>> > >> a fine thing to do.  They just need to be clearly marked as not Apache
>> > >> releases.
>> > >>
>> > >> The disclaimer that we request is meant to be shown on all pages of
>> the
>> > >> podling's website.  Not just the landing page.  If these are user
>> facing
>> > >> documents, then they must have the disclaimer on them.
>> > >>
>> > >> John
>> > >>
>> > >>> On Fri, Apr 13, 2018 at 5:42 PM Gian Merlino  wrote:
>> > >>>
>> > >>> Hi Otto,
>> > >>>
>> > >>> I am just another podling committer, so this isn't authoritative
>> > advice,
>> > >>> but for Druid's incubating page we are planning to put up a
>> placeholder
>> > >>> page with a link to the current community site. It isn't up yet, but
>> > the
>> > >>> html we are planning to use is here:
>> > >>>
>> > >>
>> > https://github.com/apache/incubator-druid-website/blob/
>> asf-site/index.html
>> > >>>
>> > >>> Our rationale was:
>> > >>>
>> > >>> 1) Before the site is migrated, it's better to have a placeholder
>> than
>> > a
>> > >>> 404.
>> > >>> 2) A placeholder with a link can make it more clear that the releases
>> > on
>> > >>> druid.io are not Apache releases.
>> > >>> 3) A placeholder helps satisfy the requirement that podling web sites
>> > >> must
>> > >>> have an incubation disclaimer (
>> > >>> https://incubator.apache.org/guides/branding.html).
>> > >>>
>> > >>> When we migrate the community site to Apache infra then it would
>> > replace
>> > >>> the placeholder.
>> > >>>
>> > >>> Gian
>> > >>>
>> > >>> On Fri, A

Re: Default webpages for new podlings

[sebb]

On 16 April 2018 at 09:34, Bertrand Delacretaz
 wrote:
> On Mon, Apr 16, 2018 at 8:50 AM, Greg Stein  wrote:
>> ...placeholder page. It should explain the situation. Provide links to
>> the incubator and the podling status page, to the original/external site,
>> disclaimer, etc. Just one page. Fast set up. Done...
>
> Yes, BIG +1 to this.
>
> It's not hard to create a single-page site using Jekyll or any of the
> many site generators around. As Greg says, just a few links and brief
> status information, but each podling should have an editable website
> on their apache.org domain very early in incubation. Even if it's a
> single ugly page.

Podlings can create a simple page in Git/SVN, however it won't be
displayed without some Infra setup to copy the html from the SCM to
the host.

Perhaps this needs to be done as part of the initial process of
creating a podling?

Or maybe there could be a temporary holding area under the incubator
SVN tree with RW access for all incubator committers.
The podling website could redirect to that if present. Once the new
site was available, the temporary one would be removed.

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

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

Re: Default webpages for new podlings

[sebb]

On 16 April 2018 at 10:39, Bertrand Delacretaz
 wrote:
> On Mon, Apr 16, 2018 at 11:20 AM, sebb  wrote:
>>... Podlings can create a simple page in Git/SVN, however it won't be
>> displayed without some Infra setup to copy the html from the SCM to
>> the host...
>
> Granted but that's quite easy to do from the podling's side: just push
> the content to the asf-site branch of a Git repository and ask infra
> to activate the sync as in
> https://issues.apache.org/jira/browse/INFRA-12311

Yes, it is simple but it is one other job to do.
And it cannot be done by Infra until it is known what SCM they are want to use.

> How that content is generated does not matter, in a pinch you could
> just edit a single index.html file manually in that asf-site branch
> and be done with it.

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

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

Re: Default webpages for new podlings

[sebb]

On 17 April 2018 at 19:47, Greg Stein  wrote:
> On Mon, Apr 16, 2018 at 8:57 PM, Dave Fisher  wrote:
>>...
>
>> Greg - You know which project I’m thinking about - OpenOffice.org. (1) I
>> can see a way to make Jekyll or something similar function for site
>> generation. Since I did the migration in I ought to be able to migrate out.
>> (2) The main challenge is that the CMS provides good in site patching by
>> new contributors on page. Replacing that method of getting new contributors
>> to easily provide patches is the hurdle AFAICT. Has Infra thought about a
>> solution for this?
>>
>
> The easiest solution is to place your site source into Git, specifically as
> part of our "gitbox" program. That will allow for direct editing on
> github.com. When the edits are saved, then buildbot or jenkins can pick up
> the change, generate/save the site, and pubsub will pick up the
> newly-generated change(s) to the site.

How about creating a dummy podling site using this feature?

> Cheers,
> -g

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

Re: Updating the Board Report Reminder Template

[sebb]

On 24 April 2018 at 09:15, Bertrand Delacretaz
 wrote:
> On Mon, Apr 23, 2018 at 6:13 PM, Dave Fisher  wrote:
>> ...Since the Incubator reports are a public process in a wiki we don’t 
>> really have a process for  in Incubator podling reports...
>
> Correct, I missed that!
>
> I think that's fine, if a podling really needs to report something
> private they can do so via private@incubator.a.o.
>
> So my suggested text changes to
>
> ""Please do not include the names of potential committers or PMC
> members in your report. Candidate names should not be made
> public before people are actually elected."

Or perhaps put the rule first?

"Candidate names should not be made public before people are actually
elected, so please do not include the names of potential committers or
PMC members in your report."

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

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

Re: Publishing Maven artifacts under third-party coordinates (was: Set up Nexus staging profile for Dubbo ...)

[sebb]

On 10 May 2018 at 11:37, Greg Stein  wrote:
> On Thu, May 10, 2018 at 3:31 AM, Huxing Zhang  wrote:
>
>> Hi,
>>
>> On Thu, May 10, 2018 at 3:59 PM, Willem Jiang 
>> wrote:
>> > Is there any plan for going through the vote process of Binary file?
>>
>> Yes, binaries will also go through the vote process.
>
>
> No. It makes no sense.
>
> There is NO WAY to verify a binary. Even compiling from source to binary on
> your machine, and trying to compare against a target binary will generally
> fail since timestamps are embedded. Or maybe there are different compilers
> being used.
>
> The Foundation *never* votes on binaries, because the Foundation DOES NOT
> RELEASE BINARIES. The Foundation only votes/authorizes/releases source
> code. REPEAT: only source code.
>
> Only source. Which is verifiable. Which has provenance.

The LICENCE and NOTICE files that accompany the binary artifact are
text, and IMO should be checked against the contents of the binary
artifact.
For example, if the binary bundles jars from other projects, the L&N
need to agree with the bundled contents.

> Regards,
> -g
> (Member, skipping my Infra hat)

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

Re: Publishing Maven artifacts under third-party coordinates (was: Set up Nexus staging profile for Dubbo ...)

[sebb]

On 10 May 2018 at 16:56, Matt Sicker  wrote:
> I still minimally require proper gpg signatures on binary artifacts. The
> source artifacts are what get far more scrutiny, but the binaries are
> released on apache.org after all.

+1

It may also be possible to verify that the binary package works.
This obviously depends very much on the project.

In the case of Java code, it's possible to verify that the jars
contain the expected package names.
Also that the META-INF directory contains NOTICE and LICENSE files, etc.

> On 10 May 2018 at 10:20, Roman Shaposhnik  wrote:
>
>> On Thu, May 10, 2018 at 4:17 AM, sebb  wrote:
>> > On 10 May 2018 at 11:37, Greg Stein  wrote:
>> >> On Thu, May 10, 2018 at 3:31 AM, Huxing Zhang 
>> wrote:
>> >>
>> >>> Hi,
>> >>>
>> >>> On Thu, May 10, 2018 at 3:59 PM, Willem Jiang 
>> >>> wrote:
>> >>> > Is there any plan for going through the vote process of Binary file?
>> >>>
>> >>> Yes, binaries will also go through the vote process.
>> >>
>> >>
>> >> No. It makes no sense.
>> >>
>> >> There is NO WAY to verify a binary. Even compiling from source to
>> binary on
>> >> your machine, and trying to compare against a target binary will
>> generally
>> >> fail since timestamps are embedded. Or maybe there are different
>> compilers
>> >> being used.
>> >>
>> >> The Foundation *never* votes on binaries, because the Foundation DOES
>> NOT
>> >> RELEASE BINARIES. The Foundation only votes/authorizes/releases source
>> >> code. REPEAT: only source code.
>> >>
>> >> Only source. Which is verifiable. Which has provenance.
>> >
>> > The LICENCE and NOTICE files that accompany the binary artifact are
>> > text, and IMO should be checked against the contents of the binary
>> > artifact.
>> > For example, if the binary bundles jars from other projects, the L&N
>> > need to agree with the bundled contents.
>>
>> +1000! That has been a well established practice in the Incubator and
>> as such I see no reason not to keep following it.
>>
>> In addition to that, a reasonable effort should be put into making sure
>> that the binary bundle doesn't drag in bits with incompatible licenses
>> (such as GPL). That's why verifying LICENSE in the binary bundle
>> is NOT a simple exersize of comparing it to the source bundle.
>>
>> Thanks,
>> Roman.
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>
>
>
> --
> Matt Sicker 

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

Re: [VOTE] Release Apache Daffodil (incubating) 2.1.0-rc3

[sebb]

On 13 May 2018 at 16:51, Matt Sicker  wrote:
> On 11 May 2018 at 19:07, Justin Mclean  wrote:
>
>> Hi,
>> I think the confusion around copyrights in NOTICE files happens because
>> when you bundle a 3rd party ALv2 for with a minimum NOTICE file it is
>> likely that it contains a copyright line you need to copy into your NOTICE
>> file. But for other permissive licenses you don't do this.
>>
>
> And then, for example, if an Apache project were to bundle code from
> another Apache project (and licensed as such), then that code is still
> covered by the same exact NOTICE usually since it's still referring to the
> ASF.

Huh?
There is no single NOTICE file here.
Each ASF NOTICE file is potentially different depending on the included code.

If ASF project A includes code from ASF project B, the project A
NOTICE file may or may not need updating to take account of the NOTICE
file from project B.
This depends on whether the code from project B needs any specific
terms from NOTICE B.

> --
> Matt Sicker 

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

Re: [VOTE] Release Apache NetBeans 9.0 RC1 (incubating) rc1

[sebb]

On 20 May 2018 at 23:33, Emilian Bold  wrote:
> Hi all,
>
> The Apache NetBeans community has voted on and approved a proposal to release 
> Apache NetBeans 9.0 RC1 (incubating) rc1.
>
> We now kindly request that the Incubator PMC members review and vote on this 
> incubator release candidate.
>
> Apache NetBeans 9.0 RC1 (incubating) vote thread:
>
> https://lists.apache.org/thread.html/c2a06adc83e2819e6d96c7dff8d0e22a97001f99bfda12515d4d9609@%3Cdev.netbeans.apache.org%3E
>
> Apache NetBeans 9.0 RC1 (incubating) vote result thread:
>
> https://lists.apache.org/thread.html/94f7a5e4601e26c7edb8264df7df53dd8ed215ecfc568816a162f2af@%3Cdev.netbeans.apache.org%3E
>
> Apache NetBeans 9.0 RC1 (incubating) constitutes all the modules in the 
> Apache NetBeans Git repo, which together provide the NetBeans Platform (i.e., 
> the underlying application framework), as well as all the modules that 
> provide the Java SE-related features of Apache NetBeans.
> In short, Apache NetBeans 9.0 RC1 (incubating) is a full IDE for Java SE 
> development.
>
> Build artifacts available here:
>
> https://dist.apache.org/repos/dist/dev/incubator/netbeans/incubating-netbeans-java/incubating-9.0-rc1-rc1

MD5 hashes are deprecated and should not be used for new releases.

They can just be removed from the dist dir (and download page).
No need to redo the release, but please update scripts to stop creating them.

> The specific artifact to be voted on:
>
> https://dist.apache.org/repos/dist/dev/incubator/netbeans/incubating-netbeans-java/incubating-9.0-rc1-rc1/incubating-netbeans-java-9.0-rc1-source.zip
>
> Included in the above are the DEPENDENCIES, DISCLAIMER, LICENSE, and NOTICE 
> files, as well as a README file with build instructions, which are the same 
> as these:
>
> https://github.com/apache/incubator-netbeans/blob/master/README.md
>
> SHA1: a1a265455c8246f849b14982fa3c36b351b21876
>
> KEYS file:
>
> https://dist.apache.org/repos/dist/release/incubator/netbeans/KEYS
>
> Apache NetBeans Git Repo tag: 9.0-rc1-rc1:
>
> https://github.com/apache/incubator-netbeans/tree/9.0-rc1-rc1
>
> Note: NetBeans license violation checks are managed via the 
> rat-exclusions.txt file:
>
> https://github.com/apache/incubator-netbeans/blob/master/nbbuild/rat-exclusions.txt
>
> Rat report shows no unknown licenses, except for license files:
>
> https://builds.apache.org/job/incubator-netbeans-release/302/artifact/rat-java-temp/nbbuild/build/rat-report.txt
>
> The license files listed in the Rat report are known and an issue exists for 
> solving this:
>
> https://issues.apache.org/jira/browse/NETBEANS-305
>
> Included as a convenience binary, not relevant for the voting purposes (unzip 
> it, run it and you'll see Apache NetBeans):
>
> https://dist.apache.org/repos/dist/dev/incubator/netbeans/incubating-netbeans-java/incubating-9.0-rc1-rc1/incubating-netbeans-java-9.0-rc1-bin.zip
>
> Also included as a convenience binary the NBMs:
>
> https://dist.apache.org/repos/dist/dev/incubator/netbeans/incubating-netbeans-java/incubating-9.0-rc1-rc1/nbms
>
> New & Noteworthy features of the 9.0 Release:
>
> https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+9.0+New+and+Noteworthy
>
> Release specific wiki page:
>
> https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+9.0+RC1
>
> How (and what) to try out the release:
>
> 1. Download the artifact to be voted on and unzip it.
> 2. Build it using the README provided by the artifact.
> 3. Look in nbbuild/netbeans for the NetBeans installation created by the 
> build process.
> 4. Run the NetBeans executable and (if you're running on JDK 8) you'll be 
> prompted to install nb-javac, after agreeing to its licensing terms, and (if 
> you're running on JDK 9), you'll be able to use javac directly from JDK 9 
> and, optionally, you'll be prompted to install nb-javac, after agreeing to 
> its licensing terms.
>
> If the above succeeds, i.e., Apache NetBeans installs and starts up, you will 
> have a development environment that complies with Apache IP requirements and 
> you should vote +1 in this thread.
>
> Please try out the package, using the instructions above, and vote!
>
> The vote is open for 7 days
>
> [ ] +1 Release this package as Apache NetBeans 9.0 RC1 (incubating)
> [ ] 0 I don't feel strongly about it, but I'm okay with the release
> [ ] -1 Do not release this package because...
>
>
> Emilian Bold
> on behalf of the Apache NetBeans PPMC
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

Re: [VOTE]: Release Apache Dubbo (Incubating) 2.6.2 [RC1]

[sebb]

On 21 May 2018 at 08:59, Justin Mclean  wrote:
> Hi,
>
>> As I cannot build the binary without doing some changes on the pom file, I
>> had to vote -1 (binding) here.
>
> You don’t need to modify the pom file to compile you can specify 
> -Dcheckstyle.skip to compile id check style is acting up for you.
>
> Up to you if you want to vote -1 but I just want to remind people here 
> (mostly the Dubbo PMC who are new to this) that:
> - a -1 vote is not a veto (but should be carefully considered)
> - a release only need 3 +1 votes and more +1 than -1 to pass
> - you can vote +0 or change you vote if you think the issue can be fixed next 
> release
>
>> 2. I checked the source zip[1], it is not same with github tag one[2].
>> There are some log files and empty directories which is not in the git
>> repo, I guess it relates to the builder's workspace.
>
> Which is OK many project release are not 100% identical to what is in the 
> release tar what is important is that none of the source code has changed.

Huh?

I don't think there should be anything in the source release that is
not in the source repo.

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

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

Re: [VOTE]: Release Apache Dubbo (Incubating) 2.6.2 [RC1]

[sebb]

On 21 May 2018 at 21:16, Justin Mclean  wrote:
> Hi,
>
>> I don't think there should be anything in the source release that is
>> not in the source repo.
>
> It reasonably  common (from my review of 100’s of releases) that the build 
> process may modify and/or add some files (e.g config files). I wouldn’t 
> expect any code to change or be added.

It's also important that there is nothing in the release tar that is
not in the source repo or which cannot be readily derived from it
(though that is too broad an exception).

I have seen release tars that include spurious files that happened to
be present in the workspace.
In one case a file held private information.

Your original mail said:

>>> Which is OK many project release are not 100% identical to what is in the 
>>> release tar what is important is that none of the source code has changed.

This could be taken to mean that it does not matter what goes into the
release tar other than the source files.

I think it's important to be clear that the release tar should have
minimal changes from the source repo, and what sort of changes are
allowed.

> Thanks,
> Justin

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

Re: [VOTE] Release of Apache Tephra-0.14.0-incubating [rc1]

[sebb]

On 21 May 2018 at 23:51, James Taylor  wrote:
> Hi all,
>
> This is a call for a vote on releasing Apache Tephra 0.14.0-incubating,
> release candidate 1. This is the seventh release of Tephra. The Tephra dev
> community has voted on and approved a proposal to release Tephra
> 0.14.0-incubating, release candidate 1.
>
> PPMC Vote Call: https://s.apache.org/jWVD
>
> PPMC Vote Result: https://s.apache.org/zwog
>
> The source tarball, including signatures, digests, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/tephra/0.14.0-incubating-rc1/src

MD5 hashes are deprecated and should not be used for new releases.

> The tag to be voted upon is v0.14.0-incubating:
> https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.git;a=shortlog;h=refs/tags/v0.14.0-incubating
>
> The release hash is e93942adae0ece286157a8f6a2e5c63b53669e03:
> https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.git;a=commit;h=e93942adae0ece286157a8f6a2e5c63b53669e03
>
> The Nexus Staging URL:
> https://repository.apache.org/content/repositories/orgapachetephra-1011
>
> Release artifacts are signed with the following key:
> http://people.apache.org/keys/committer/jamestaylor
>
> KEYS file available:
> https://dist.apache.org/repos/dist/dev/incubator/tephra/KEYS
>
> For information about the contents of this release, see:
> https://dist.apache.org/repos/dist/dev/incubator/tephra/0.14.0-incubating-rc1/CHANGES.txt
>
> Please vote on releasing this package as Apache Tephra 0.14.0-incubating
>
> The vote will be open for 72 hours.

(at least)

>
> [ ] +1 Release this package as Apache Tephra 0.14.0-incubating
> [ ] +0 no opinion
> [ ] -1 Do not release this package because ...
>
> Thanks,
> James

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

Re: [VOTE] Release Apache Omid 0.9.0.0 (incubating)

[sebb]

On 24 May 2018 at 22:40, Josh Elser  wrote:
> +1 (binding), but with one issue ;)
>
> The source release looks fine, as do sigs/xsums. DISCLAIMER, LICENSE and
> NOTICE are all fine too.
>
> Only thing I see is that your new additions made in
> https://dist.apache.org/repos/dist/dev/incubator/omid/0.9.0.0-rc3/KEYS must
> be reflected in
> https://dist.apache.org/repos/dist/release/incubator/omid/KEYS before a
> release happens.

Might as well maintain the keys directly in:
https://dist.apache.org/repos/dist/release/incubator/omid/KEYS

Seems no point having them in the RC directory.

>
> On 5/21/18 3:39 PM, Ohad Shacham wrote:
>>
>> Hi,
>>
>>
>> The Apache Omid community has voted on and approved a proposal
>> to release Apache Omid 0.9.0.0-incubating.
>>
>> PPMC Vote
>> Call:http://mail-archives.apache.org/mod_mbox/omid-dev/201805.mbox/%3cCAHuxFyOJZ8=ud2xuq2drbgpzznoqpvaunbxpxwyo5gs_xr+...@mail.gmail.com%3e
>>
>>
>> PPMC Vote Result:
>>
>>
>> http://mail-archives.apache.org/mod_mbox/omid-dev/201805.mbox/%3ccanqijeuua0bih+masqpirn2utrfnf7dce+ipylyja6ea03t...@mail.gmail.com%3e
>>
>>
>> PPMC Vote Summary:
>> 3 binding (IPMC member) +1 votes
>> 0 non-binding PPMC member +1 votes
>> No -1 votes
>>
>> Release notes for the 0.9.0.0
>>
>> release:https://dist.apache.org/repos/dist/dev/incubator/omid/0.9.0.0-rc3/RELEASE_NOTES.html
>>
>>
>> Git tag for the release:
>>
>>
>> https://git-wip-us.apache.org/repos/asf/incubator-omid.git/?p=incubator-omid.git;a=tag;h=229831bc377e47431cc7cbc211803069158b5711
>>
>>
>> Sources for the release:
>>
>>
>> https://dist.apache.org/repos/dist/dev/incubator/omid/0.9.0.0-rc3/apache-omid-incubating-0.9.0.0-src.tar.gz
>>
>>
>> Source release verification: PGP Signature:
>>
>>
>> https://dist.apache.org/repos/dist/dev/incubator/omid/0.9.0.0-rc3/apache-omid-incubating-0.9.0.0-src.tar.gz.asc
>>
>>
>> SHA512 Hash:
>>
>>
>> https://dist.apache.org/repos/dist/dev/incubator/omid/0.9.0.0-rc3/apache-omid-incubating-0.9.0.0-src.tar.gz.sha512
>>
>>
>> Keys to verify the signature of the release artifact are available at:
>>
>> https://dist.apache.org/repos/dist/dev/incubator/omid/0.9.0.0-rc3/KEYS
>>
>>
>> We request the permission of IPMC to publish the above release candidate
>> as
>> Apache Omid 0.9.0.0-incubating. Please try out the package and vote. The
>> vote is open for a minimum of 72 hours or until the necessary number of
>> votes (3 binding +1s) is reached. [ ] +1 Release this package as Apache
>> Omid 0.9.0.0-incubating [ ] 0 I don't feel strongly about it, but I'm okay
>> with the release [ ] -1 Do not release this package because... Please add
>> (binding) if your vote is binding.
>>
>>
>> Thanks,
>> Ohad
>>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

Re: [VOTE] Apache Crail 1.0-incubating (RC3)

[sebb]

On 25 May 2018 at 12:10, Jonas Pfefferle  wrote:
> Hi Willem
> You can find the KEYS file here:
> https://dist.apache.org/repos/dist/release/incubator/crail/KEYS
>
> Is that sufficient or do we also need to put the file here:
> https://dist.apache.org/repos/dist/dev/incubator/crail/ ?

Please only one location where the KEYS are maintained.

The one under dist/release is required, so use only that one.

The VOTE mail might as well use the URL which is provided to the general public:

https://www.apache.org/dist/incubator/crail/KEYS

That shows that the KEYS file is ready for the release.

>
> Thanks,
> Jonas
>
>  On Fri, 25 May 2018 11:42:28 +0800
>
>  Willem Jiang  wrote:
>>
>> I found the KEY file from the PPMC voting mail[1].
>> According to note of from apache key home[2], the Key for release should
>> not be the link.
>>
>>   - The KEYS files must be stored in the ASF mirror directories. This
>>   ensures that they are archived along with the releases to which they
>> apply.
>>   - The KEYS file are needed to check signatures of archived releases.
>>   Thus keys should only ever be added to the KEYS file, and never normally
>>   removed. Now the LDAP group for a project will change over time, and a
>>   committer who signed one or more releases may no longer be in the group.
>>   Also if a project moves to the Attic, its LDAP group will be removed.
>>
>> [1]https://www.mail-archive.com/dev@crail.apache.org/msg00268.html
>> [2]https://people.apache.org/keys/
>>
>>
>> Willem Jiang
>>
>> Twitter: willemjiang
>> Weibo: 姜宁willem
>>
>> On Fri, May 25, 2018 at 9:09 AM, Willem Jiang 
>> wrote:
>>
>>> I can build the kit after skipping the test and there is a build
>>> instruction in the README.  I'm sorry I didn't find it at first check.
>>> Now I have some trouble to find the signing key from the distribution
>>> directory.  We normally provide it in the KEY directory.
>>>
>>>
>>> Willem Jiang
>>>
>>> Twitter: willemjiang
>>> Weibo: 姜宁willem
>>>
>>> On Wed, May 23, 2018 at 3:23 PM, Jonas Pfefferle 
>>> wrote:
>>>
 Hi,

 At the moment there is no way to run the tests without setting up a
 configuration for your system (Crail needs hugepage mountpoint, network
 interfaces etc).
 For that reason we instruct people in the README to build with
 "-DskipTests".

 If you want to deploy/configure Crail to run the tests you need to setup
 the CRAIL_HOME environment variable and adapt the Crail configuration
 with
 your network settings etc. Check the README for more detailed
 instructions.

 Thanks,
 Jonas

  On Wed, 23 May 2018 10:33:09 +0800

  Willem Jiang  wrote:

> Hi,
>
> I just tried to build from the source kit and got the test error due to
> missing crail-site.conf.
> I checked the README and cannot find any note for solving this problem.
>
> testRenameFile(org.apache.crail.ClientTest): null/conf/crail-site.conf
> (No
> such file or directory)
>  testRenameFile(org.apache.crail.ClientTest)
>  testlookupDirectory(org.apache.crail.ClientTest):
> null/conf/crail-site.conf (No such file or directory)
>
>
> Willem Jiang
>
> Blog: http://willemjiang.blogspot.com (English)
>  http://jnn.iteye.com  (Chinese)
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Tue, May 22, 2018 at 3:28 PM, Jonas Pfefferle 
> wrote:
>
> Please vote to approve the source release of Apache Crail
> 1.0-incubating
>>
>> (RC3).
>> This release candidate fixes all issues raised in the last IPMC vote:
>> - Add DISCLAIMER
>> - Move IBM copyright from NOTICE file to CREDITS file and fix
>> formatting
>> of Apache copyright
>> - Leading directory name in tar/zip file is now
>> "apache-crail-1.0-incubating-src"
>>
>> The podling dev vote thread:
>>
>> https://www.mail-archive.com/dev@crail.apache.org/msg00268.html
>>
>> The result:
>>
>> https://www.mail-archive.com/dev@crail.apache.org/msg00274.html
>>
>> Commit hash: 0db64fddad52044eab75ee73e1857c7bcf6fae7d
>>
>> https://git1-us-west.apache.org/repos/asf?p=incubator-crail.
>> git;a=commit;h=0db64fddad52044eab75ee73e1857c7bcf6fae7d
>>
>> Release files can be found at:
>> https://dist.apache.org/repos/dist/dev/incubator/crail/1.0-rc3/
>>
>> The vote is open for at least 72 hours and passes if a majority of at
>> least
>> 3 +1 PMC votes are cast.
>>
>> [ ] +1 Release this package as Apache Crail 1.0-incubating
>> [ ] -1 Do not release this package because ...
>>
>> Thanks,
>> Jonas
>>
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>
>> -

Re: karma to edit podling reports (incubator wiki account: javiroman)

[sebb]

On 2 June 2018 at 07:22, Justin Mclean  wrote:
> Hi,
>
> Probably a silly question, but I couldn't find the answer, how do you add 
> someone? Also look like I my no be an admin to add people which may be a good 
> idea if I was.

This is explained on the Front Page:

https://wiki.apache.org/incubator/FrontPage

follow the link to

https://wiki.apache.org/incubator/ContributorsGroup

You don't appear to be listed as an admin.
I can add you if you provide your Wiki name.

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

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

Re: karma to edit podling reports (incubator wiki account: javiroman)

[sebb]

On 2 June 2018 at 10:29, Justin Mclean  wrote:
> HI,
>
>> This is explained on the Front Page:
>> https://wiki.apache.org/incubator/FrontPage
>
> Thanks for that.
>
>> You don't appear to be listed as an admin.
>> I can add you if you provide your Wiki name.
>
> I’m not an admin can you (or someone else) add me. “Justin Mclean” is my wiki 
> name.

OK, you should be able to see the Admin page now (and also edit the
Contributors page)

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

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

Re: [ANNOUNCE] Apache SINGA (incubating) 1.2.0 released

[sebb]

Also you only need one KEYS link, and there should be a description of
how to use KEYS + sig or hash to verify the downloads.

On 15 June 2018 at 14:12, Craig Russell  wrote:
> Dear Singa project,
>
> Please update your download page to add links to the ASC signature files for 
> each of the artifacts.
>
> Regards,
>
> Craig
>
>> On Jun 14, 2018, at 6:51 PM, Moaz Reyad  wrote:
>>
>> We are pleased to announce that SINGA (incubating) 1.2.0 is released.
>>
>> SINGA is a general distributed deep learning platform for training big deep
>> learning models over large datasets. It is designed with an intuitive
>> programming model based on the layer abstraction. SINGA supports a wide
>> variety of popular deep learning models.
>>
>> The release is available at:
>> http://singa.apache.org/en/downloads.html
>>
>> The main features of this release include:
>>
>> -Implement autograd (currently support MLP model)
>> -Upgrade PySinga to support Python 3
>> -Improve the Tensor class with the stride field
>> -Upgrade cuDNN from V5 to V7
>> -Add VGG, Inception V4, ResNet, and DenseNet for ImageNet classification
>> -Create alias for conda packages
>> -Complete documentation in Chinese
>> -Add instructions for running SINGA on Windows
>> -Update the compilation, CI
>>
>> We look forward to hearing your feedback, suggestions and contributions to
>> the project.
>>
>> On behalf of the SINGA team,
>> Moaz Reyad
>
> Craig L Russell
> c...@apache.org
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

Re: [ANNOUNCE] Apache SINGA (incubating) 1.2.0 released

[sebb]

On 21 June 2018 at 11:34, Moaz Reyad  wrote:
> Dear Craig and sebb,
>
> Thank you. The download page is fixed now.

I'm afraid there are still issues.

Download pages must only link to formal releases, so must not include
links to GitHub.
Such links belong on developer-facing pages.

Links to KEYS, sigs and hashes must not use dist.apache.org; instead
use https://www.apache.org/dist/incubator/singa/...

The instructions for verifying a signature are confusing as there is a
missing new-line.

> Best regards,
> Moaz
>
> On Fri, Jun 15, 2018 at 5:14 PM sebb  wrote:
>
>> Also you only need one KEYS link, and there should be a description of
>> how to use KEYS + sig or hash to verify the downloads.
>>
>> On 15 June 2018 at 14:12, Craig Russell  wrote:
>> > Dear Singa project,
>> >
>> > Please update your download page to add links to the ASC signature files
>> for each of the artifacts.
>> >
>> > Regards,
>> >
>> > Craig
>> >
>> >> On Jun 14, 2018, at 6:51 PM, Moaz Reyad  wrote:
>> >>
>> >> We are pleased to announce that SINGA (incubating) 1.2.0 is released.
>> >>
>> >> SINGA is a general distributed deep learning platform for training big
>> deep
>> >> learning models over large datasets. It is designed with an intuitive
>> >> programming model based on the layer abstraction. SINGA supports a wide
>> >> variety of popular deep learning models.
>> >>
>> >> The release is available at:
>> >> http://singa.apache.org/en/downloads.html
>> >>
>> >> The main features of this release include:
>> >>
>> >> -Implement autograd (currently support MLP model)
>> >> -Upgrade PySinga to support Python 3
>> >> -Improve the Tensor class with the stride field
>> >> -Upgrade cuDNN from V5 to V7
>> >> -Add VGG, Inception V4, ResNet, and DenseNet for ImageNet
>> classification
>> >> -Create alias for conda packages
>> >> -Complete documentation in Chinese
>> >> -Add instructions for running SINGA on Windows
>> >> -Update the compilation, CI
>> >>
>> >> We look forward to hearing your feedback, suggestions and contributions
>> to
>> >> the project.
>> >>
>> >> On behalf of the SINGA team,
>> >> Moaz Reyad
>> >
>> > Craig L Russell
>> > c...@apache.org
>> >
>> >
>> > -
>> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> > For additional commands, e-mail: general-h...@incubator.apache.org
>> >
>>

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

Re: [ANNOUNCE] Apache Gobblin (incubating) 0.12.0 released

[sebb]

On 2 July 2018 at 17:38, Abhishek Tiwari  wrote:
> We are pleased to announce that Apache Gobblin (incubating) 0.12.0 is
> released.
>
> Gobblin is a distributed data integration framework that simplifies common
> aspects of big data integration such as data ingestion, replication,
> organization and lifecycle management for both streaming and batch data
> ecosystems.
>
> The release is available at:
> https://gobblin.apache.org/download/

Sorry, but there are some issues with the download page.

- must link to KEYS using https://www.apache.org/dist/incubator/gobblin/KEYS
- must link to release artifacts using ASF mirror system
- must not include direct links to non-ASF releases

> On behalf of the Gobblin team,
> Abhishek Tiwari
>
> =
> *DISCLAIMER*
> Apache Gobblin (incubating) is an effort undergoing incubation at The
> Apache Software
> Foundation (ASF), sponsored by Incubator.
> Incubation is required of all newly accepted projects until a further
> review indicates that the infrastructure, communications, and decision
> making process have stabilized in a manner consistent with other successful
> ASF projects.
> While incubation status is not necessarily a reflection of the completeness
> or stability of the code, it does indicate that the project has yet to be
> fully endorsed by the ASF.

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

Re: [VOTE] Apache MXNet (incubating) 1.2.1 release RC1

[sebb]

On 13 July 2018 at 04:17, Anirudh Subramanian  wrote:
> Hi all,
>
> This is a call for releasing Apache MXNet (incubating) 1.2.1, release
> candidate RC1.
>
> Apache MXNet (incubating) community has voted and approved the release.
>
> Vote thread:
>
> https://lists.apache.org/thread.html/6a0459a54dd0b13fc89f653af91306810aa83d5d1a578a2abbac89fe@%3Cdev.mxnet.apache.org%3E
>
> Results thread:
>
> https://lists.apache.org/thread.html/94dfdc2cee82664a63a47d7ce0a011629903c5fca8ae96057974526f@%3Cdev.mxnet.apache.org%3E
>
> Explanation for RC1:
>
> https://lists.apache.org/thread.html/891c902c28251b0dbb90a64de086c8c5f02c22e070e58d55c923285d@%3Cdev.mxnet.apache.org%3E
>
> The source tarball, including signatures, digests etc. can be found at:
>
> https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.2.1.rc1/
>
> The release tag can be found here:
>
> https://github.com/apache/incubator-mxnet/releases/tag/1.2.1.rc1
>
> The release hash is 106391a1f0ee012b1ea38764d711e76774ce77e1 and can be
> found here:
>
> https://github.com/apache/incubator-mxnet/commit/106391a1f0ee012b1ea38764d711e76774ce77e1
>
> Release artifacts are signed with the following key:
>
> 0D04 3D0F 92CA 7333 22A8  D131 9067 CC8E AF55 CD6D
>
> KEYS file available:
>
> https://dist.apache.org/repos/dist/dev/incubator/mxnet/KEYS

It's better to maintain the KEYS file in a single place, i.e.

https://dist.apache.org/repos/dist/release/incubator/mxnet/KEYS

and quote the following in the VOTE email:
https://www.apache.org/dist/incubator/mxnet/KEYS

> The vote will end at Monday July 16th, 8:10 PDT.
>
> [ ] +1 Release this package as 1.2.1
> [ ] +0 no opinion
> [ ] -1 Do not release this package because ...
>
> Thanks,
>
> Anirudh

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

Policy for podling committers on graduation

[sebb]

When a podling graduates, all the people listed on the board
resolution become both PMC members and committers.

What is the policy for podling committers?

Are they all automatically carried forward as committers?

Or does the podling need to specifically need to re-appoint the
committers that are not mentioned in the graduation resolution?

S.

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

Re: Policy for podling committers on graduation

[sebb]

On 16 July 2018 at 02:08, Hen  wrote:
> +1 to automatically carried forward which I suspect is how it’s been
> handled up to now.

Before LDAP was used for podlings, committers were not distinguished
from PPMC members.
Only those in the TLP resolution were added to the PMC and committer
LDAP groups that were created as part of graduation.

It was up to the new PMC to request additional ids to be added to the
committer group.
This was a way of dropping people who would not be contributing to the
PMC (e.g. mentors may wish to drop out)

When podlings were defined in LDAP, this changed, as there was no
longer any need to create the LDAP groups on graduation.

> On Sat, Jul 14, 2018 at 4:15 AM sebb  wrote:
>
>> When a podling graduates, all the people listed on the board
>> resolution become both PMC members and committers.
>>
>> What is the policy for podling committers?
>>
>> Are they all automatically carried forward as committers?
>>
>> Or does the podling need to specifically need to re-appoint the
>> committers that are not mentioned in the graduation resolution?
>>
>> S.
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>

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

Re: [VOTE] Release Airflow 1.10.0

[sebb]

On 19 July 2018 at 09:15, Bolke de Bruin  wrote:
> Hi Yang,
>
> The source package is the one was voted upon with the PMC and is under vote 
> now.
> The binary package is just a convenience package and not the artefact voted 
> upon. The source package does contain
> the files.

However if you release the binary package, it must have NOTICE and
LICENSE files, and these must agree with the contents of the package.

> * kerberos: airflow/api/auth/backend/kerberos_auth.py
> * elasticmock: tests/utils/log/elasticmock
> * licenses: licenses/
>
> Adding the “licenses/“ folder to the binary package is probably a good idea 
> so we will do so next release. Tests are not included in the binary release 
> for obvious reasons.
>
> Can you please make sure you are reviewing the right artefact?
>
> Cheers
> Bolke
>
>
>> On 19 Jul 2018, at 08:35, Yang Bo  wrote:
>>
>> Hi Bruin,
>>
>> Sorry. I rechecked and found that I downloaded the binary package<
>> https://dist.apache.org/repos/dist/dev/incubator/airflow/1.10.0rc2/apache-airflow-1.10.0rc2+incubating-bin.tar.gz>
>> instead of the source package.
>> The licenses folder is missing and I can't find files relating to
>> elasticmock or flask-kerberos.
>>
>> On Thu, Jul 19, 2018 at 1:28 PM Bolke de Bruin  wrote:
>>
>>> Hi Yang,
>>>
>>> Thanks for reviewing. To your points.
>>>
>>> 1. I verified the number of licenses we are referring to (14) and the
>>> number of licenses included (14). They are equal. Which ones are you
>>> missing?
>>> 2. Flask-Kerberos is actually bundled and part of the source distribution.
>>> Also elasticmock is included as part of the tests.
>>> 3. Good point. We will do so as part of the next release.
>>>
>>> You also mentioned that some .pyc files are included. The files you are
>>> referring to are not part of the source tar.gz as far as I can see. I
>>> downloaded the tar.gz, unpacked it and checked for the files you mentioned.
>>>
>>> Cheers
>>> Bolke
>>>
>>> Verstuurd vanaf mijn iPad
>>>
 Op 19 jul. 2018 om 03:56 heeft Yang Bo  het volgende
>>> geschreven:

 There are also some binary files (*.pyc) in the airflow/config_templates.
 Those should be removed.

> On Thu, Jul 19, 2018 at 9:51 AM Yang Bo  wrote:
>
> Hi,
>
> I found several minor issues regarding the LICENSE in the source
>>> release.
> 1. The LICENSE states that there are corresponding
> licenses/LICENSE-[project] file for third parties but they do not exist.
> 2. There are some libraries that are not bundled in the source release
>>> but
> are listed in the LICENSE file, e.g. ElasticMock, flask-kerberos etc.
>>> The
> LICENSE file should only contain what's actually bundled.
> 3. It's better to provide the version in the LICENSE for third parties
> because the license term may change between versions.
>
>> On Thu, Jul 19, 2018 at 2:40 AM Bolke de Bruin 
>>> wrote:
>>
>> Hello Incubator PMC’ers,
>>
>> The Apache Airflow community has voted and approved the proposal to
>> release
>> Apache Airflow 1.10.0 (incubating) based on 1.10.0 Release Candidate
>>> 2. We
>> now kindly request the Incubator PMC members to review and vote on this
>> incubator release.
>>
>> Airflow is a platform to programmatically author, schedule, and monitor
>> workflows. Use Airflow to author workflows as directed acyclic graphs
>> (DAGs) of tasks. The airflow scheduler executes your tasks on an array
>>> of
>> workers while following the specified dependencies. Rich command line
>> utilities make performing complex surgeries on DAGs a snap. The rich
>>> user
>> interface makes it easy to visualize pipelines running in production,
>> monitor progress, and troubleshoot issues when needed. When workflows
>>> are
>> defined as code, they become more maintainable, versionable, testable,
>>> and
>> collaborative.
>>
>> In this release with took special care of:
>>
>> * Correct License Headers
>> * Removing potential GPL dependency
>> * Better formatting of Disclaimer
>>
>> After a successful IPMC vote Artifacts will be available at:
>>
>> https://www.apache.org/dyn/closer.cgi/incubator/airflow <
>> https://www.apache.org/dyn/closer.cgi/incubator/airflow>
>>
>> Public keys are available at:
>>
>> https://www.apache.org/dist/incubator/airflow/ <
>> https://www.apache.org/dist/incubator/airflow/>
>>
>> apache-airflow-1.10.0rc2+incubating-source.tar.gz
>> <
>>
>>
>>> https://dist.apache.org/repos/dist/dev/incubator/airflow/1.10.0rc2/apache-airflow-1.10.0rc2+incubating-source.tar.gz
>> <
>>
>>> https://dist.apache.org/repos/dist/dev/incubator/airflow/1.10.0rc2/apache-airflow-1.10.0rc2+incubating-source.tar.gz
>>>
>>>
>> is a source release that comes with INSTALL instructions. Along with
>>> it,
>> for
>> convenience, find the binary Python "sdist" as
>> apac

Re: [ANNOUNCE] Apache OpenWhisk, main module (incubating) 0.9.0 released

[sebb]

On 19 July 2018 at 19:32, Vincent S Hou  wrote:
> Hi everyone,
>
> We are pleased to announce that Apache OpenWhisk, main module (incubating) 
> 0.9.0 is released.
>
> OpenWhisk is a cloud-first distributed event-based programming service. It 
> provides a programming model to upload event handlers to a cloud service, and 
> register the handlers to respond to various events. This is the first time 
> that OpenWhisk is released under Apache as an incubator project.
>
> The release is available at:
> https://www.apache.org/dist/incubator/openwhisk/apache-openwhisk-0.9.0-incubating/

Please note that the above is not acceptable for a download link in a
formal announce message, as links to release artifacts must use the
mirror system.

> The official website of OpenWhisk, https://openwhisk.apache.org/, is 
> currently working on the webpage for the download links.

Also announce messages must contain the incubating disclaimer.

> Vincent Hou
> On behalf of the OpenWhisk team
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

Re: [VOTE] Release Airflow 1.10.0

[sebb]

On 19 July 2018 at 11:16, Bolke de Bruin  wrote:
> Hi Sebb,
>
> Gotcha. The vote considers the source package, but arguably the binary 
> package is pretty close. The binary package does contain a LICENSE and NOTICE 
> file, it misses the specific (license)files mentioned in the LICENSE file. 
> The list normally would also be different between source and binary as some 
> of the files (code) do not end up in the binary package (ie. from tests).
>
> So adding the “license” folder to the binary package is on the list, but I 
> hope you allow us to do this for the next release as it is just a convenience 
> package really.
>
> What say you?

I am not keen on approving an artifact without the required N&L files.
Given that it is a convenience package, you could just delete it and
release the source alone.

Do others think it's OK to let it be downloaded as is without the
required files?

> Cheers
> Bolke
>
>
>> On 19 Jul 2018, at 10:33, sebb  wrote:
>>
>> On 19 July 2018 at 09:15, Bolke de Bruin  wrote:
>>> Hi Yang,
>>>
>>> The source package is the one was voted upon with the PMC and is under vote 
>>> now.
>>> The binary package is just a convenience package and not the artefact voted 
>>> upon. The source package does contain
>>> the files.
>>
>> However if you release the binary package, it must have NOTICE and
>> LICENSE files, and these must agree with the contents of the package.
>>
>>> * kerberos: airflow/api/auth/backend/kerberos_auth.py
>>> * elasticmock: tests/utils/log/elasticmock
>>> * licenses: licenses/
>>>
>>> Adding the “licenses/“ folder to the binary package is probably a good idea 
>>> so we will do so next release. Tests are not included in the binary release 
>>> for obvious reasons.
>>>
>>> Can you please make sure you are reviewing the right artefact?
>>>
>>> Cheers
>>> Bolke
>>>
>>>
>>>> On 19 Jul 2018, at 08:35, Yang Bo  wrote:
>>>>
>>>> Hi Bruin,
>>>>
>>>> Sorry. I rechecked and found that I downloaded the binary package<
>>>> https://dist.apache.org/repos/dist/dev/incubator/airflow/1.10.0rc2/apache-airflow-1.10.0rc2+incubating-bin.tar.gz>
>>>> instead of the source package.
>>>> The licenses folder is missing and I can't find files relating to
>>>> elasticmock or flask-kerberos.
>>>>
>>>> On Thu, Jul 19, 2018 at 1:28 PM Bolke de Bruin  wrote:
>>>>
>>>>> Hi Yang,
>>>>>
>>>>> Thanks for reviewing. To your points.
>>>>>
>>>>> 1. I verified the number of licenses we are referring to (14) and the
>>>>> number of licenses included (14). They are equal. Which ones are you
>>>>> missing?
>>>>> 2. Flask-Kerberos is actually bundled and part of the source distribution.
>>>>> Also elasticmock is included as part of the tests.
>>>>> 3. Good point. We will do so as part of the next release.
>>>>>
>>>>> You also mentioned that some .pyc files are included. The files you are
>>>>> referring to are not part of the source tar.gz as far as I can see. I
>>>>> downloaded the tar.gz, unpacked it and checked for the files you 
>>>>> mentioned.
>>>>>
>>>>> Cheers
>>>>> Bolke
>>>>>
>>>>> Verstuurd vanaf mijn iPad
>>>>>
>>>>>> Op 19 jul. 2018 om 03:56 heeft Yang Bo  het volgende
>>>>> geschreven:
>>>>>>
>>>>>> There are also some binary files (*.pyc) in the airflow/config_templates.
>>>>>> Those should be removed.
>>>>>>
>>>>>>> On Thu, Jul 19, 2018 at 9:51 AM Yang Bo  wrote:
>>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> I found several minor issues regarding the LICENSE in the source
>>>>> release.
>>>>>>> 1. The LICENSE states that there are corresponding
>>>>>>> licenses/LICENSE-[project] file for third parties but they do not exist.
>>>>>>> 2. There are some libraries that are not bundled in the source release
>>>>> but
>>>>>>> are listed in the LICENSE file, e.g. ElasticMock, flask-kerberos etc.
>>>>> The
>>>>>>> LICENSE file should only contain what's actually bundled.
>>>>>>> 3.

Re: [VOTE] Release Airflow 1.10.0

[sebb]

On 20 July 2018 at 10:45, Bolke de Bruin  wrote:
> Hi Sebb,
>
> Would you be ok if I replace the binary package and add those files? I can do 
> that without touching the source package. As such I think it would not 
> require a revote at the PMC.

Personally, no, I don't think that would be acceptable.

A VOTE thread is about a particular set of artifacts; you cannot
change any of them without restarting the vote.
Otherwise the vote is invalid.

But I would wait to see if others agree with me.

> Cheers
> Bolke
>
> Verstuurd vanaf mijn iPad
>
>> Op 20 jul. 2018 om 11:17 heeft sebb  het volgende 
>> geschreven:
>>
>>> On 19 July 2018 at 11:16, Bolke de Bruin  wrote:
>>> Hi Sebb,
>>>
>>> Gotcha. The vote considers the source package, but arguably the binary 
>>> package is pretty close. The binary package does contain a LICENSE and 
>>> NOTICE file, it misses the specific (license)files mentioned in the LICENSE 
>>> file. The list normally would also be different between source and binary 
>>> as some of the files (code) do not end up in the binary package (ie. from 
>>> tests).
>>>
>>> So adding the “license” folder to the binary package is on the list, but I 
>>> hope you allow us to do this for the next release as it is just a 
>>> convenience package really.
>>>
>>> What say you?
>>
>> I am not keen on approving an artifact without the required N&L files.
>> Given that it is a convenience package, you could just delete it and
>> release the source alone.
>>
>> Do others think it's OK to let it be downloaded as is without the
>> required files?
>>
>>> Cheers
>>> Bolke
>>>
>>>
>>>> On 19 Jul 2018, at 10:33, sebb  wrote:
>>>>
>>>> On 19 July 2018 at 09:15, Bolke de Bruin  wrote:
>>>>> Hi Yang,
>>>>>
>>>>> The source package is the one was voted upon with the PMC and is under 
>>>>> vote now.
>>>>> The binary package is just a convenience package and not the artefact 
>>>>> voted upon. The source package does contain
>>>>> the files.
>>>>
>>>> However if you release the binary package, it must have NOTICE and
>>>> LICENSE files, and these must agree with the contents of the package.
>>>>
>>>>> * kerberos: airflow/api/auth/backend/kerberos_auth.py
>>>>> * elasticmock: tests/utils/log/elasticmock
>>>>> * licenses: licenses/
>>>>>
>>>>> Adding the “licenses/“ folder to the binary package is probably a good 
>>>>> idea so we will do so next release. Tests are not included in the binary 
>>>>> release for obvious reasons.
>>>>>
>>>>> Can you please make sure you are reviewing the right artefact?
>>>>>
>>>>> Cheers
>>>>> Bolke
>>>>>
>>>>>
>>>>>> On 19 Jul 2018, at 08:35, Yang Bo  wrote:
>>>>>>
>>>>>> Hi Bruin,
>>>>>>
>>>>>> Sorry. I rechecked and found that I downloaded the binary package<
>>>>>> https://dist.apache.org/repos/dist/dev/incubator/airflow/1.10.0rc2/apache-airflow-1.10.0rc2+incubating-bin.tar.gz>
>>>>>> instead of the source package.
>>>>>> The licenses folder is missing and I can't find files relating to
>>>>>> elasticmock or flask-kerberos.
>>>>>>
>>>>>>> On Thu, Jul 19, 2018 at 1:28 PM Bolke de Bruin  
>>>>>>> wrote:
>>>>>>>
>>>>>>> Hi Yang,
>>>>>>>
>>>>>>> Thanks for reviewing. To your points.
>>>>>>>
>>>>>>> 1. I verified the number of licenses we are referring to (14) and the
>>>>>>> number of licenses included (14). They are equal. Which ones are you
>>>>>>> missing?
>>>>>>> 2. Flask-Kerberos is actually bundled and part of the source 
>>>>>>> distribution.
>>>>>>> Also elasticmock is included as part of the tests.
>>>>>>> 3. Good point. We will do so as part of the next release.
>>>>>>>
>>>>>>> You also mentioned that some .pyc files are included. The files you are
>>>>>>> referring to are not part of the source tar.gz as far as I can see. I
>>>>>>> downloaded the t

Re: [ANNOUNCE] Apache OpenWhisk, main module (incubating) 0.9.0 released

[sebb]

On 20 July 2018 at 11:59, Vincent S Hou  wrote:
> Thanks, Sebb.
>
> I will resend the announcement.
> The download links embedded in our official website will not refer to the 
> apache release llink either.

It would be best to link to the official download page in the announce mail.

>
> Best wishes.
> Vincent Hou (侯胜博)
>
> Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud
>
> Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
> Phone: +1(919)254-7182
> Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States
>
> -sebb  wrote: -
> To: general@incubator.apache.org
> From: sebb 
> Date: 07/20/2018 05:09AM
> Subject: Re: [ANNOUNCE] Apache OpenWhisk, main module (incubating) 0.9.0 
> released
>
> On 19 July 2018 at 19:32, Vincent S Hou  wrote:
>> Hi everyone,
>>
>> We are pleased to announce that Apache OpenWhisk, main module (incubating) 
>> 0.9.0 is released.
>>
>> OpenWhisk is a cloud-first distributed event-based programming service. It 
>> provides a programming model to upload event handlers to a cloud service, 
>> and register the handlers to respond to various events. This is the first 
>> time that OpenWhisk is released under Apache as an incubator project.
>>
>> The release is available at:
>> https://www.apache.org/dist/incubator/openwhisk/apache-openwhisk-0.9.0-incubating/
>
> Please note that the above is not acceptable for a download link in a
> formal announce message, as links to release artifacts must use the
> mirror system.
>
>> The official website of OpenWhisk, https://openwhisk.apache.org/, is 
>> currently working on the webpage for the download links.
>
> Also announce messages must contain the incubating disclaimer.
>
>> Vincent Hou
>> On behalf of the OpenWhisk team
>>
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

Re: [ANNOUNCE] Apache NetBeans (incubating) 9.0 released

[sebb]

On 29 July 2018 at 15:22, Emilian Bold
 wrote:
> The Apache NetBeans team is proud to announce the release of Apache
> NetBeans (incubating) 9.0.

Announcements of incubating releases must include the standard disclaimer.

> Apache NetBeans (incubating) 9.0 constitutes all the modules in
> the Apache NetBeans Git repo, which together provide the NetBeans
> Platform (i.e., the underlying application framework), as well as all
> the modules that provide the Java SE-related features of Apache
> NetBeans.
> In short, Apache NetBeans (incubating) 9.0 is a full IDE for Java
> SE development.
>
> Read more on our download page:
>
> https://netbeans.apache.org/download/nb90/nb90.html

The KEYS link currently uses: https://dist.apache.org/
However the dist.apache.org host is only intended for release staging.

Please link instead to

https://www.apache.org/dist/incubator/netbeans/KEYS

> New & Noteworthy features of the 9.0 Release:
>
> https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+9.0+New+and+Noteworthy
>
> Details on Apache NetBeans (incubating) 9.0:
>
> https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+9.0+Final+Release
>
> Download and try out Apache NetBeans (incubating) 9.0:
>
> https://www.apache.org/dyn/closer.cgi/incubator/netbeans/incubating-netbeans-java/incubating-9.0/

Please don't link directly to the closer.cgi page as it does not
provide ready access to the KEYS, sigs, hashes.
Use the download page (as above)

> The specific artifact voted on the IPMC vote thread[1]:
>
> https://www.apache.org/dyn/closer.cgi/incubator/netbeans/incubating-netbeans-java/incubating-9.0/incubating-netbeans-java-9.0-source.zip

As above

> SHA1: ed2098c173460ec81f05635055066da06a7ea82b
> KEYS file: https://dist.apache.org/repos/dist/release/incubator/netbeans/KEYS

As above

> See the below for the donation status of features that have not been donated 
> or included in Apache builds yet, i.e., are not part of Apache NetBeans 
> (incubating) 9.0, e.g., features for working with Java EE, JavaScript, PHP, 
> C/C++, and more:
>
> https://cwiki.apache.org/confluence/display/NETBEANS/Apache+Transition
>
> Work is being done on bringing netbeans.org to Apache. In the
> meantime, refer to the below for all details related to Apache
> NetBeans:
>
> https://cwiki.apache.org/confluence/display/NETBEANS
>
> Emilian Bold
> on behalf of Apache NetBeans PPMC
>
> 1. 
> https://lists.apache.org/thread.html/ab58e2c75d260a91851d8def412b1ef6648aaf4f690b205aaaf53924@%3Cgeneral.incubator.apache.org%3E
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

Re: [ANNOUNCE] Apache NetBeans (incubating) 9.0 released

[sebb]

On 29 July 2018 at 15:43, Emilian Bold  wrote:
>> Announcements of incubating releases must include the standard disclaimer.
>
> I've read that release *artifacts* must include the disclaimer. Where is the 
> announcement email content specified?
>
>> Please link instead to
>>
>> https://www.apache.org/dist/incubator/netbeans/KEYS
>
> OK.
>
>> Please don't link directly to the closer.cgi page as it does not
>> provide ready access to the KEYS, sigs, hashes.
>> Use the download page (as above)
>
> OK.
>
>> > The specific artifact voted on the IPMC vote thread[1]:

This is not really relevant for a general announce mail.

>> > https://www.apache.org/dyn/closer.cgi/incubator/netbeans/incubating-netbeans-java/incubating-9.0/incubating-netbeans-java-9.0-source.zip
>>
>> As above
>>
>> > SHA1: ed2098c173460ec81f05635055066da06a7ea82b
>> > KEYS file: 
>> > https://dist.apache.org/repos/dist/release/incubator/netbeans/KEYS
>>
>> As above
>
> Since I'm not supposed to be linking to any specific artifact,

You can link to a specific place on the download page where the
artifact can be downloaded (along with sig/hash)

> is there any reason to include a link to KEYS or to mention the SHA1?

No, but if you do it must use the correct URL.

> --emi

-
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.19.0 [RC3]

[sebb]

On 30 July 2018 at 08:11, Hanks Zhang  wrote:
> Dear IPMC members,
>
> This is a call for the vote to release Apache Weex (Incubating) version
> 0.19.0.
>
> The Apache Weex community has voted on and approved a proposal to release
> Apache Weex (Incubating) version 0.19.0.
>
> We now kindly request the Incubator PMC members to review and vote on this
> incubator release.
>
> Apache Weex (incubating) is a framework for building Mobile cross-platform
> UIs.
>
> Vote thread:
> https://lists.apache.org/thread.html/40d49fa7338680253be47382c26150a1730992611a26267648f2@%3Cdev.weex.apache.org%3E
>
> Vote result thread:
> https://lists.apache.org/thread.html/47988b39c4748f01efac6010b9c239a094fb332e5cea51e6b0460c0b@%3Cdev.weex.apache.org%3E
>
> The tag to be voted upon:
> https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git;a=shortlog;h=refs/tags/0.19.0-rc3
>
> The source code artifacts can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/weex/0.19.0/RC3/apache-weex-incubating-0.19.0-RC3-src.tar.gz
>
> The SHA-512 checksum for each artifact can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/weex/0.19.0/RC3/apache-weex-incubating-0.19.0-RC3-src.tar.gz.sha512

It would be good to include the hash in the mail itself, i.e.

apache-weex-incubating-0.19.0-RC3-src.tar.gz:
4BF8D1D5 AA369711 9D16CC9C 52A42DEF 88FDAB97 7044B1B6 415E87AB FAEC435D 1B1AFCFC
 810B8851 7B98900B 2918C43A D9483D3C C1DBFC72 7BC14E8C 710D86BA

This makes it easier to tie the artifact to the vote thread (the URL
is ephemeral).

> The signature of this artifact can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/weex/0.19.0/RC3/apache-weex-incubating-0.19.0-RC3-src.tar.gz.asc
>
> The artifacts have been signed with Key: 4FD8BC09C7E9DB81, which can be
> found in the keys file:
> https://dist.apache.org/repos/dist/dev/incubator/weex/KEYS

It would be better to maintain a single set of keys at

https://dist.apache.org/repos/dist/release/incubator/weex/KEYS

This can then be referenced as per the download page:

https://www.apache.org/dist/incubator/weex/KEYS

Remember that the KEYS file is also saved on the archive site so needs
to include all keys for all releases, past and present.

> The compile documentation can be found at:
> https://github.com/apache/incubator-weex/blob/0.19.0-rc3/HOW-TO-BUILD.md
> Weex is a project that contains iOS, Android and Web code. So it may be a
> little complicated to prepare the compiling environment.
>
> Release note about this version:
> https://issues.apache.org/jira/projects/WEEX/issues/WEEX-464
>
>
> The vote will be open for at least 72 hours or until a necessary number of
> votes are reached.
>
> Please vote accordingly:
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason

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

Re: [ANNOUNCE] Apache Gobblin (incubating) 0.12.0 released

[sebb]

I'm afraid the page is still faulty.

Links to sigs and hashes must use

 https://www.apache.org/dist/incubator/gobblin/...

and not the mirror system.

On 3 August 2018 at 19:58, Abhishek Tiwari  wrote:
> Sorry this slipped my mind. I have fixed the issues on the website:
>
> - Updated KEYS link
> - Linked releases to Apache mirror system
> - Removed links to previous non-Apache releases
>
> Thanks Sebb for the suggestions.
>
> Regards
> Abhishek
>
> On Mon, Jul 2, 2018 at 11:03 AM sebb  wrote:
>
>> On 2 July 2018 at 17:38, Abhishek Tiwari  wrote:
>> > We are pleased to announce that Apache Gobblin (incubating) 0.12.0 is
>> > released.
>> >
>> > Gobblin is a distributed data integration framework that simplifies
>> common
>> > aspects of big data integration such as data ingestion, replication,
>> > organization and lifecycle management for both streaming and batch data
>> > ecosystems.
>> >
>> > The release is available at:
>> > https://gobblin.apache.org/download/
>>
>> Sorry, but there are some issues with the download page.
>>
>> - must link to KEYS using
>> https://www.apache.org/dist/incubator/gobblin/KEYS
>> - must link to release artifacts using ASF mirror system
>> - must not include direct links to non-ASF releases
>>
>> > On behalf of the Gobblin team,
>> > Abhishek Tiwari
>> >
>> > =
>> > *DISCLAIMER*
>> > Apache Gobblin (incubating) is an effort undergoing incubation at The
>> > Apache Software
>> > Foundation (ASF), sponsored by Incubator.
>> > Incubation is required of all newly accepted projects until a further
>> > review indicates that the infrastructure, communications, and decision
>> > making process have stabilized in a manner consistent with other
>> successful
>> > ASF projects.
>> > While incubation status is not necessarily a reflection of the
>> completeness
>> > or stability of the code, it does indicate that the project has yet to be
>> > fully endorsed by the ASF.
>>

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

Re: [VOTE]: Release Apache OpenWhisk (Incubating): Client Go and CLI 0.9.0 [RC1]

[sebb]

On 6 August 2018 at 18:47, Vincent S Hou  wrote:
> Dear IPMC members,
>
> This is a call for vote to release Apache OpenWhisk (Incubating): Client Go 
> and CLI, Version 0.9.0.
>
> The Apache OpenWhisk community has voted on and approved a proposal to 
> release Apache OpenWhisk (Incubating): Client Go and CLI, Version 0.9.0.
>
> We now kindly request the Incubator PMC members to review and vote on this 
> incubator release.
>
> Apache OpenWhisk Client Go is a Go client library to access Openwhisk API.
> Apache OpenWhisk CLI is a command-line interface, based on Go client library, 
> to access Openwhisk API.
>
> OpenWhisk Client Go and CLI vote thread:
> https://lists.apache.org/thread.html/da01355c62ec6aedf8cd049ad7449ebdc796528e9015fdb1220a19ad@%3Cdev.openwhisk.apache.org%3E
>
> OpenWhisk Client Go and CLI vote result thread:
> https://lists.apache.org/thread.html/55f6a6e9218a21ad02c6a13624c368d78d40b68d22e1095543ffdd3c@%3Cdev.openwhisk.apache.org%3E
>
> This release comprises of source code distribution only.
>
>
> For Client Go:
> The source code artifact of OpenWhisk Client Go can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-client-go-0.9.0-incubating-sources.tar.gz
>
> The SHA-512 checksum for OpenWhisk Client Go can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-client-go-0.9.0-incubating-sources.tar.gz.sha512

That URL is temporary.
Please include the actual checksum in VOTE emails.
i.e.

openwhisk-client-go-0.9.0-incubating-sources.tar.gz:
D5A69445 EF0082D7 B57FBDA4 13DCB591 0E06372F 0F308D2C 8FA49A80 F99FBF13 6E299EBC
 CCF3722C 832492C4 215FB107 657EB521 0B72A364 9366F7CF 682DCA87

> The signature for OpenWhisk Client Go can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-client-go-0.9.0-incubating-sources.tar.gz.asc
>
>
> For CLI:
> The source code artifact of OpenWhisk CLI can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-cli-0.9.0-incubating-sources.tar.gz
>
> The SHA-512 checksum for OpenWhisk CLI can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-cli-0.9.0-incubating-sources.tar.gz.sha512

openwhisk-cli-0.9.0-incubating-sources.tar.gz:
F033568C 40286D74 CF6B6C5C 26470988 AD560DFA 39C1E521 34F96FF9 9FB86022 5CB6700B
 2862D2C8 35D5C407 F18F3AD0 5B0E26B8 F5178A0E 734C5EAE 763AEB18

> The signature for OpenWhisk CLI can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-cli-0.9.0-incubating-sources.tar.gz.asc
>
>
> KEYS file is available here:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/KEYS

Please maintain the KEYS file here:
https://dist.apache.org/repos/dist/release/incubator/openwhisk/KEYS

and use the following link in emails:
https://www.apache.org/dist/incubator/openwhisk/KEYS

> This key has been validated here: 
> http://pgp.mit.edu/pks/lookup?search=houshengbo&op=index
>
> This is the first time that Apache OpenWhisk: Client Go and CLI request for a 
> release, so there is no file of CHANGELOG.
>
> The documentation can be found at:
> https://github.com/apache/incubator-openwhisk-release/blob/master/releases/0.9.0-incubating/INSTALL.md
>  or
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/doc/INSTALL.md
>
> We are currently using the tool called 
> openwhisk-release(https://github.com/apache/incubator-openwhisk-release) to 
> release all the modules of OpenWhisk. The instruction for release managers 
> can be found at: 
> https://github.com/apache/incubator-openwhisk-release/blob/master/docs/release_instructions.md.
>  This tool
> supports both manual and automated modes to package the source code, sign the 
> artifacts and upload the artifacts into Apache SVN repositories.
>
> The vote will be open for at least 72 hours or until necessary number of 
> votes are reached.
>
> Please vote accordingly:
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
>
> Best wishes.
> Vincent Hou (侯胜博)
>
> Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud
>
> Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
> Phone: +1(919)254-7182
> Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

Re: [ANNOUNCE] Release Apache ECharts (incubating) 4.1.0

[sebb]

On 10 August 2018 at 11:35, SHUANG SU  wrote:
> Hi all,
>
> The Apache ECharts (incubating) team is proud to announce Apache ECharts
> version 4.1.0-incubating.
>
> ECharts is a powerful, interactive charting and visualization library.
>
> Vote thread:
> https://lists.apache.org/thread.html/67dffef28ecffd66689ac991ca027c0868d734629949d958e7b12dd3@%3Cdev.echarts.apache.org%3E

The vote URL is not normally included in announce emails, as they are
published outside the developer community.

> Download Links: http://echarts.apache.org/download

The download page does not use the ASF mirror system, there are no
links to KEYS, sigs or hashes and no details on why/how to verify
downloads using sigs or hashes.

Also the online builder is clever, but does not provide any download
verification.

> Release Notes:
> http://www.apache.org/dist/incubator/echarts/4.1.0/RELEASE_NOTE.txt
>
> Website: http://echarts.apache.org/
>
> ECharts Resources:
> - Issue: https://github.com/apache/incubator-echarts/issues
> - Mailing list: d...@echarts.incubator.apache.org
>
> Thanks

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

Re: [VOTE] Apache Toree 0.2.0-incubating (RC6)

[sebb]

Or equally:

https://www.apache.org/dist/incubator/toree/KEYS

On 13 August 2018 at 18:09, Dave Fisher  wrote:
> Hey Taylor,
>
> https://dist.apache.org/repos/dist/release/incubator/toree/KEYS
>
> Regards,
> Dave
>
> On Aug 13, 2018, at 10:03 AM, P. Taylor Goetz  wrote:
>
> I’m trying evaluate the RC, but I can’t find the KEYS file for the project.
> It doesn’t appear to be in any of the typical locations.
>
> -Taylor
>
> On Aug 9, 2018, at 12:13 PM, Luciano Resende  wrote:
>
> Please vote to approve the release of Apache Toree 0.2.0-incubating (RC6).
>
> The podling dev vote thread:
> https://www.mail-archive.com/dev@toree.incubator.apache.org/msg01798.html
>
> And the result:
> https://www.mail-archive.com/dev@toree.incubator.apache.org/msg01821.html
>
> Tag: v0.2.0-incubating-rc6 (eae2da61828a0c88e2ab64a7ffb9ff7647909a2c)
>
> https://github.com/apache/incubator-toree/tree/v0.2.0-incubating-rc6
>
> All distribution packages, including signatures, digests, etc. can be found
> at:
>
> https://dist.apache.org/repos/dist/dev/incubator/toree/0.2.0-incubating-rc6/
>
> Staging artifacts can be found at:
>
> https://repository.apache.org/content/repositories/orgapachetoree-1013
>
> The vote is open for at least 72 hours and passes if a majority of at least
> 3 +1 PMC votes are cast.
>
> [ ] +1 Release this package as Apache Toree 0.2.0-incubating
> [ ] -1 Do not release this package because ...
>
> --
> Luciano Resende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/
>
>
>

-
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.19.0 [RC3]

[sebb]

On 30 July 2018 at 08:11, Hanks Zhang  wrote:
> Dear IPMC members,
>
> This is a call for the vote to release Apache Weex (Incubating) version
> 0.19.0.
>
> The Apache Weex community has voted on and approved a proposal to release
> Apache Weex (Incubating) version 0.19.0.
>
> We now kindly request the Incubator PMC members to review and vote on this
> incubator release.
>
> Apache Weex (incubating) is a framework for building Mobile cross-platform
> UIs.
>
> Vote thread:
> https://lists.apache.org/thread.html/40d49fa7338680253be47382c26150a1730992611a26267648f2@%3Cdev.weex.apache.org%3E
>
> Vote result thread:
> https://lists.apache.org/thread.html/47988b39c4748f01efac6010b9c239a094fb332e5cea51e6b0460c0b@%3Cdev.weex.apache.org%3E
>
> The tag to be voted upon:
> https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git;a=shortlog;h=refs/tags/0.19.0-rc3
>
> The source code artifacts can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/weex/0.19.0/RC3/apache-weex-incubating-0.19.0-RC3-src.tar.gz
>
> The SHA-512 checksum for each artifact can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/weex/0.19.0/RC3/apache-weex-incubating-0.19.0-RC3-src.tar.gz.sha512

That URL is not immutable; for traceability please include the hash in
the VOTE email

> The signature of this artifact can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/weex/0.19.0/RC3/apache-weex-incubating-0.19.0-RC3-src.tar.gz.asc
>
> The artifacts have been signed with Key: 4FD8BC09C7E9DB81, which can be
> found in the keys file:
> https://dist.apache.org/repos/dist/dev/incubator/weex/KEYS

Please maintain the KEYS file here:
https://dist.apache.org/repos/dist/release/incubator/openwhisk/KEYS

and use the following link in emails:
https://www.apache.org/dist/incubator/openwhisk/KEYS

> The compile documentation can be found at:
> https://github.com/apache/incubator-weex/blob/0.19.0-rc3/HOW-TO-BUILD.md
> Weex is a project that contains iOS, Android and Web code. So it may be a
> little complicated to prepare the compiling environment.
>
> Release note about this version:
> https://issues.apache.org/jira/projects/WEEX/issues/WEEX-464
>
>
> The vote will be open for at least 72 hours or until a necessary number of
> votes are reached.
>
> Please vote accordingly:
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason

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

Re: [ANNOUNCE] Release Apache ECharts (incubating) 4.1.0

[sebb]

On 14 August 2018 at 08:12, SHUANG SU  wrote:
> Thanks.
>
> Sorry for the mistake. The correct vote thread should be
> https://lists.apache.org/thread.html/4a551cd183a7ec74c2f5629b8c2c128f82cff6d044d524fcc4d2a175@%3Cgeneral.incubator.apache.org%3E

I think you misunderstand me.
I am saying that the link should not be included in announce emails as
it is not relevant.

> Is <http://www.apache.org/dist/incubator/echarts/> the Apache mirror link?
> It has been included in the download page http://echarts.apache.org/download
> ,
> (It is the button-like link under the title of "Download Source"). KEYS is
> also included in
> this link.

No, that is a link to the ASF backup mirrors.

The release artifacts must use the ASF dynamic mirror system.

> About the online builder, we've made the auto-check tool to ensure the
> correctness during the process of publish.
> But I have not found a way for end-user to check the downloaded file since
> the online build is totally run on the
> browser, without server and without pre-build. Fortunately we have not
> received a report about any fail on download stage.
> But I am considering may be a shell command can be provided for end-user
> to check the version and some
> features of the content.

The point here is that artifact downloads must be accompanied by
hashes and sigs.


> Thanks
>
>
>
> sebb  于2018年8月13日周一 下午5:21写道：
>
>> On 10 August 2018 at 11:35, SHUANG SU  wrote:
>> > Hi all,
>> >
>> > The Apache ECharts (incubating) team is proud to announce Apache ECharts
>> > version 4.1.0-incubating.
>> >
>> > ECharts is a powerful, interactive charting and visualization library.
>> >
>> > Vote thread:
>> >
>> https://lists.apache.org/thread.html/67dffef28ecffd66689ac991ca027c0868d734629949d958e7b12dd3@%3Cdev.echarts.apache.org%3E
>>
>> The vote URL is not normally included in announce emails, as they are
>> published outside the developer community.
>>
>> > Download Links: http://echarts.apache.org/download
>>
>> The download page does not use the ASF mirror system, there are no
>> links to KEYS, sigs or hashes and no details on why/how to verify
>> downloads using sigs or hashes.
>>
>> Also the online builder is clever, but does not provide any download
>> verification.
>>
>> > Release Notes:
>> > http://www.apache.org/dist/incubator/echarts/4.1.0/RELEASE_NOTE.txt
>> >
>> > Website: http://echarts.apache.org/
>> >
>> > ECharts Resources:
>> > - Issue: https://github.com/apache/incubator-echarts/issues
>> > - Mailing list: d...@echarts.incubator.apache.org
>> >
>> > Thanks
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>

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

Re: [ANNOUNCE] Apache Gobblin (incubating) 0.12.0 released

[sebb]

On 13 August 2018 at 20:00, Abhishek Tiwari  wrote:
> Hi Sebb,
>
> I have updated the links for sha512 and asc. Please check the website.

Looks OK now.

> Abhishek
>
> On Mon, Aug 13, 2018 at 2:05 AM sebb  wrote:
>
>> I'm afraid the page is still faulty.
>>
>> Links to sigs and hashes must use
>>
>>  https://www.apache.org/dist/incubator/gobblin/...
>>
>> and not the mirror system.
>>
>> On 3 August 2018 at 19:58, Abhishek Tiwari  wrote:
>> > Sorry this slipped my mind. I have fixed the issues on the website:
>> >
>> > - Updated KEYS link
>> > - Linked releases to Apache mirror system
>> > - Removed links to previous non-Apache releases
>> >
>> > Thanks Sebb for the suggestions.
>> >
>> > Regards
>> > Abhishek
>> >
>> > On Mon, Jul 2, 2018 at 11:03 AM sebb  wrote:
>> >
>> >> On 2 July 2018 at 17:38, Abhishek Tiwari  wrote:
>> >> > We are pleased to announce that Apache Gobblin (incubating) 0.12.0 is
>> >> > released.
>> >> >
>> >> > Gobblin is a distributed data integration framework that simplifies
>> >> common
>> >> > aspects of big data integration such as data ingestion, replication,
>> >> > organization and lifecycle management for both streaming and batch
>> data
>> >> > ecosystems.
>> >> >
>> >> > The release is available at:
>> >> > https://gobblin.apache.org/download/
>> >>
>> >> Sorry, but there are some issues with the download page.
>> >>
>> >> - must link to KEYS using
>> >> https://www.apache.org/dist/incubator/gobblin/KEYS
>> >> - must link to release artifacts using ASF mirror system
>> >> - must not include direct links to non-ASF releases
>> >>
>> >> > On behalf of the Gobblin team,
>> >> > Abhishek Tiwari
>> >> >
>> >> > =
>> >> > *DISCLAIMER*
>> >> > Apache Gobblin (incubating) is an effort undergoing incubation at The
>> >> > Apache Software
>> >> > Foundation (ASF), sponsored by Incubator.
>> >> > Incubation is required of all newly accepted projects until a further
>> >> > review indicates that the infrastructure, communications, and decision
>> >> > making process have stabilized in a manner consistent with other
>> >> successful
>> >> > ASF projects.
>> >> > While incubation status is not necessarily a reflection of the
>> >> completeness
>> >> > or stability of the code, it does indicate that the project has yet
>> to be
>> >> > fully endorsed by the ASF.
>> >>
>>

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

Re: [VOTE]: Release Apache Dubbo (Incubating) 2.6.3 [RC3]

[sebb]

On 15 August 2018 at 03:56, Jun Liu  wrote:
> Here're some tips of how to verify the RC:
>
> 1. Check signatures and hashes are good
> sha512 dubbo-incubating-${release_version}-bin-release.zip.sha512
> sha512 dubbo-incubating-${release_version}-source-release.zip.sha512
> gpg2 --keyserver pgpkeys.mit.edu --recv-key 208B0AB1D63011C7

Better to get the key from the KEYS file.

> gpg2 --verify dubbo-incubating-2.6.2-source-release.zip.asc 
> dubbo-incubating-2.6.2-source-release.zip
>
> 2. Unzip dubbo-incubating-${release_version}-source-release.zip to the 
> default directory and check the following:
> • Directory with 'incubating' in name 
> dubbo-incubating-${release_version}-bin-release
> • DISCLAIMER exists
> • LICENSE and NOTICE exists and contents are good
> • All files and no binary files exist
> • All files has standard ASF License header
> • Can compile from source
> • All unit tests can pass
> mvn clean test # This will run all unit tests
> mvn clean install -Drat.skip=false -Dcheckstyle.skip=false # 
> Open rat and style plugin to check if every file meets requirements.
> • Release candidates match with corresponding tags, you can find tag 
> link and hash in vote email.
>
> 3. Unzip dubbo-incubating-${release_version}-bin-release.zip and check:
> * 'incubating' in name
> * LICENSE and NOTICE exists and contents are good
>
> Best regards,
> Jun
>
>> On 12 Aug 2018, at 15:12, Jun Liu  wrote:
>>
>> Hello All,
>>
>> This is a call for vote to release Apache Dubbo (Incubating) version 2.6.3.
>>
>> The Apache Dubbo community has voted on and approved a proposal to release 
>> Apache Dubbo (Incubating) version 2.6.3.
>>
>> We now kindly request the Incubator PMC members review and vote on this 
>> incubator release.
>>
>> Apache Dubbo™ (incubating) is a high-performance, java based, open source 
>> RPC framework. Dubbo offers three key functionalities, which include 
>> interface based remote call, fault tolerance & load balancing, and automatic 
>> service registration & discovery.
>>
>> Dubbo community vote thread:
>> https://lists.apache.org/thread.html/9e692f525dfbd004e98707ecac33ab10d07741500433a24370e64c67@%3Cdev.dubbo.apache.org%3E
>>
>> Dubbo community vote result thread:
>> https://lists.apache.org/thread.html/630d7ed97ca06a341a7c6626c34af52eab42515439f76e0810504533@%3Cdev.dubbo.apache.org%3E
>>
>> The release candidates:
>> https://dist.apache.org/repos/dist/dev/incubator/dubbo/2.6.3
>>
>> Git tag for the release:
>> https://github.com/apache/incubator-dubbo/tree/dubbo-2.6.3
>>
>> Hash for the release tag:
>> 22899a4b395411496ebf03c514e7674e8073e0c3
>>
>> Release Notes:
>> https://github.com/apache/incubator-dubbo/blob/dubbo-2.6.3/CHANGES.md
>>
>> The artifacts have been signed with Key : 28681CB1, which can be found in 
>> the keys file:
>> https://dist.apache.org/repos/dist/dev/incubator/dubbo/KEYS
>>
>> The vote will be open for at least 72 hours or until necessary number of 
>> votes are reached.
>>
>> Please vote accordingly:
>> [ ] +1 approve
>> [ ] +0 no opinion
>> [ ] -1 disapprove with the reason
>>
>> Thanks.
>> Jun Liu,
>> The Apache Dubbo (Incubating) Team
>>
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

Re: [DISCUSS] Marvin-AI Incubator Proposal

[sebb]

A warning: there are some areas of Infra which assume that project
names don't include hyphens.
There is one existing project with a hyphen (Empire-db); various
scripts have to be special-cased to handle this.

It would be best not to use marvin-ai as the project id (the display
name does not matter).

On 15 August 2018 at 20:13, Luciano Resende  wrote:
> We would like to start a discussion on accepting Marvin-AI as an Apache
> Incubator project.
>
> The proposal is available at the incubator wiki, and also copied below:
> https://wiki.apache.org/incubator/Marvin-AI
>
> As part of the initial due diligence, we have done a preliminary name
> search and the results are available on the JIRA below:
>
> https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-144
>
> We are also looking for two additional mentors.
>
>
> Thanks in advance for your time reviewing and providing feedback.
>
> ===
>
> = Marvin-AI =
>
> == Abstract ==
>
> Marvin-AI is an open-source artificial intelligence (AI) platform that
> helps data scientists, prototype and productionalize complex solutions with
> a scalable, low-latency, language-agnostic, and standardized architecture
> while simplifies the process of exploration and modeling.
>
> == Proposal ==
>
> Marvin helps non-experienced developers create industry-grade AI
> applications. It has three core components:  a development environment to
> be used during data exploration and hypothesis validation (Toolbox), a
> library which should be extended to create Marvin engines, and a Scala
> application server which interprets engines (Engine Executor).
> A basic premise of Marvin is that it should be language-agnostic, able to
> interpret engines implemented in different programming languages.
>
> == Background ==
>
> The Marvin AI project was initiated as an internal project at B2W Digital
> (Brazil), the largest e-commerce company in Latin America. Nowadays, it is
> used by all data scientists within the B2W team. Oftentimes, data
> scientists don't have an extensive background in software engineering, yet
> are in charge of creating AI applications that need to scale to high
> throughput and provide millisecond-level response times. At B2W, Marvin AI
> plays an important role in this process, abstracting advanced software
> engineering procedures, allowing data scientists to focus on their
> knowledge domain.
>
> == Rationale ==
>
> With recent advances in computer architecture and a corresponding increase
> in the amount of data generated by always-connected devices, AI algorithms
> offer a solution to problems that have long troubled modern corporations.
> Since AI developers come from various fields, such as statistics, physics,
> and math, there exists a strong need for platforms which enable them to
> move from prototypes to enterprise applications. Although some tools claim
> to offer this service, in reality, there is no reliable open-source
> solution.
>
> == Initial Goals ==
>
> The initial goals will most likely be to merge the existing codebase into a
> single repository, migrate it to Apache, and then integrate with the Apache
> development process. Furthermore, we plan for incremental development and
> releases, as per Apache guidelines.
>
> == Current Status ==
>
> === Meritocracy ===
>
> Marvin already works under principles of meritocracy. Today, Marvin already
> has some contributors that are part of other institutions. Although there
> is no formal process defined to become a committer, contributors that make
> major changes/improvements to the platform are naturally granted write
> access to the repository.
>
>
> === Community ===
>
> Acceptance into the Apache foundation would substantially boost both
> Marvin's user and developer communities. The current community includes a
> few experienced developers that have either academic or professional
> experience with AI. The community is largely comprised of data scientists
> working at B2W and other companies such as Cloudera, MIT, Qume Labs,
> Laguro.com, and CBYK. Also, there is a  meetup group of hundreds of users
> who meet regularly to exchange ideas about Marvin and, more generally, AI.
>
> Reference to the group: https://www.meetup.com/marvin-ai/members/
>
> === Core Developers ===
>
> The core developers for Marvin are listed in the contributor's list and
> initial PPMC below. These lists include B2W employees, MIT students, UFSCAR
> researchers, independent contributors, and some employees of other
> companies like Cloudera, Qume Labs, Laguro.com, and CBYK.
>
> === Alignment ===
>
> The initial committers strongly believe that by being part of the Apache
> Software Foundation, Marvin AI will be part of a comprehensive suite for AI
> applications that can process big data and enable enterprises to extract
> value from their data lakes. Also, we hope that by integrating with other
> Apache projects such as Apache Spark, Apache Hadoop; that this will foster
> additional collaboration between these projects f

Re: [DISCUSS] Marvin-AI Incubator Proposal

[sebb]

On 15 August 2018 at 23:37, Luciano Resende  wrote:
> Thanks for the heads up Sebastian, we will have that in mind and remove the
> hyphen if that's what causes the issue (e.g. using to MarvinAI)

Or just Marvin?

Note that the display name can remain as Marvin-AI, however the
project id/mailing-list should not have an embedded hyphen.

> On Wed, Aug 15, 2018 at 3:29 PM sebb  wrote:
>
>> A warning: there are some areas of Infra which assume that project
>> names don't include hyphens.
>> There is one existing project with a hyphen (Empire-db); various
>> scripts have to be special-cased to handle this.
>>
>> It would be best not to use marvin-ai as the project id (the display
>> name does not matter).
>>
>> On 15 August 2018 at 20:13, Luciano Resende  wrote:
>> > We would like to start a discussion on accepting Marvin-AI as an Apache
>> > Incubator project.
>> >
>> > The proposal is available at the incubator wiki, and also copied below:
>> > https://wiki.apache.org/incubator/Marvin-AI
>> >
>> > As part of the initial due diligence, we have done a preliminary name
>> > search and the results are available on the JIRA below:
>> >
>> > https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-144
>> >
>> > We are also looking for two additional mentors.
>> >
>> >
>> > Thanks in advance for your time reviewing and providing feedback.
>> >
>> > ===
>> >
>> > = Marvin-AI =
>> >
>> > == Abstract ==
>> >
>> > Marvin-AI is an open-source artificial intelligence (AI) platform that
>> > helps data scientists, prototype and productionalize complex solutions
>> with
>> > a scalable, low-latency, language-agnostic, and standardized architecture
>> > while simplifies the process of exploration and modeling.
>> >
>> > == Proposal ==
>> >
>> > Marvin helps non-experienced developers create industry-grade AI
>> > applications. It has three core components:  a development environment to
>> > be used during data exploration and hypothesis validation (Toolbox), a
>> > library which should be extended to create Marvin engines, and a Scala
>> > application server which interprets engines (Engine Executor).
>> > A basic premise of Marvin is that it should be language-agnostic, able to
>> > interpret engines implemented in different programming languages.
>> >
>> > == Background ==
>> >
>> > The Marvin AI project was initiated as an internal project at B2W Digital
>> > (Brazil), the largest e-commerce company in Latin America. Nowadays, it
>> is
>> > used by all data scientists within the B2W team. Oftentimes, data
>> > scientists don't have an extensive background in software engineering,
>> yet
>> > are in charge of creating AI applications that need to scale to high
>> > throughput and provide millisecond-level response times. At B2W, Marvin
>> AI
>> > plays an important role in this process, abstracting advanced software
>> > engineering procedures, allowing data scientists to focus on their
>> > knowledge domain.
>> >
>> > == Rationale ==
>> >
>> > With recent advances in computer architecture and a corresponding
>> increase
>> > in the amount of data generated by always-connected devices, AI
>> algorithms
>> > offer a solution to problems that have long troubled modern corporations.
>> > Since AI developers come from various fields, such as statistics,
>> physics,
>> > and math, there exists a strong need for platforms which enable them to
>> > move from prototypes to enterprise applications. Although some tools
>> claim
>> > to offer this service, in reality, there is no reliable open-source
>> > solution.
>> >
>> > == Initial Goals ==
>> >
>> > The initial goals will most likely be to merge the existing codebase
>> into a
>> > single repository, migrate it to Apache, and then integrate with the
>> Apache
>> > development process. Furthermore, we plan for incremental development and
>> > releases, as per Apache guidelines.
>> >
>> > == Current Status ==
>> >
>> > === Meritocracy ===
>> >
>> > Marvin already works under principles of meritocracy. Today, Marvin
>> already
>> > has some contributors that are part of other institutions. Although there
>> > is no formal process defined to become a committer, contributors that
>&

Re: [VOTE]: Release Apache Dubbo (Incubating) 2.6.3 [RC3]

[sebb]

On 16 August 2018 at 12:56, Jun Liu  wrote:
>> Better to get the key from the KEYS file.
>
> I think that would be:
> 1. download and import the KEYS from 
> https://dist.apache.org/repos/dist/dev/incubator/dubbo/KEYS 
> <https://dist.apache.org/repos/dist/dev/incubator/dubbo/KEYS>
> 2. gpg2 --verify dubbo-incubating-2.6.2-source-release.zip.asc 
> dubbo-incubating-2.6.2-source-release.zip
>
> Is that right?

Looks OK.

I use a temporary file as the keyring to ensure that the key is
actually present in the file, e.g.

RING=/tmp/keyring.$$
gpg2 --keyring $RING --no-default-keyring --import KEYS
 gpg2 --keyring $RING --no-default-keyring --verify ...

> What is the exact command to specify the key to use when have multiple keys 
> locally?

I don't know if it's possible to specify the key to be used.

But by starting with an empty keyring one can check that the right key
is in the KEYS file.

> Best regards,
> Jun
>
>> On 15 Aug 2018, at 20:52, sebb  wrote:
>>
>> On 15 August 2018 at 03:56, Jun Liu > <mailto:liu...@apache.org>> wrote:
>>> Here're some tips of how to verify the RC:
>>>
>>> 1. Check signatures and hashes are good
>>>sha512 dubbo-incubating-${release_version}-bin-release.zip.sha512
>>>sha512 dubbo-incubating-${release_version}-source-release.zip.sha512
>>>gpg2 --keyserver pgpkeys.mit.edu <http://pgpkeys.mit.edu/> 
>>> --recv-key 208B0AB1D63011C7
>>
>> Better to get the key from the KEYS file.
>>
>>>gpg2 --verify dubbo-incubating-2.6.2-source-release.zip.asc 
>>> dubbo-incubating-2.6.2-source-release.zip
>>>
>>> 2. Unzip dubbo-incubating-${release_version}-source-release.zip to the 
>>> default directory and check the following:
>>>• Directory with 'incubating' in name 
>>> dubbo-incubating-${release_version}-bin-release
>>>• DISCLAIMER exists
>>>• LICENSE and NOTICE exists and contents are good
>>>• All files and no binary files exist
>>>• All files has standard ASF License header
>>>• Can compile from source
>>>• All unit tests can pass
>>>mvn clean test # This will run all unit tests
>>>mvn clean install -Drat.skip=false -Dcheckstyle.skip=false # 
>>> Open rat and style plugin to check if every file meets requirements.
>>>• Release candidates match with corresponding tags, you can find tag 
>>> link and hash in vote email.
>>>
>>> 3. Unzip dubbo-incubating-${release_version}-bin-release.zip and check:
>>>* 'incubating' in name
>>>* LICENSE and NOTICE exists and contents are good
>>>
>>> Best regards,
>>> Jun
>>>
>>>> On 12 Aug 2018, at 15:12, Jun Liu  wrote:
>>>>
>>>> Hello All,
>>>>
>>>> This is a call for vote to release Apache Dubbo (Incubating) version 2.6.3.
>>>>
>>>> The Apache Dubbo community has voted on and approved a proposal to release 
>>>> Apache Dubbo (Incubating) version 2.6.3.
>>>>
>>>> We now kindly request the Incubator PMC members review and vote on this 
>>>> incubator release.
>>>>
>>>> Apache Dubbo™ (incubating) is a high-performance, java based, open source 
>>>> RPC framework. Dubbo offers three key functionalities, which include 
>>>> interface based remote call, fault tolerance & load balancing, and 
>>>> automatic service registration & discovery.
>>>>
>>>> Dubbo community vote thread:
>>>> https://lists.apache.org/thread.html/9e692f525dfbd004e98707ecac33ab10d07741500433a24370e64c67@%3Cdev.dubbo.apache.org%3E
>>>>
>>>> Dubbo community vote result thread:
>>>> https://lists.apache.org/thread.html/630d7ed97ca06a341a7c6626c34af52eab42515439f76e0810504533@%3Cdev.dubbo.apache.org%3E
>>>>
>>>> The release candidates:
>>>> https://dist.apache.org/repos/dist/dev/incubator/dubbo/2.6.3
>>>>
>>>> Git tag for the release:
>>>> https://github.com/apache/incubator-dubbo/tree/dubbo-2.6.3
>>>>
>>>> Hash for the release tag:
>>>> 22899a4b395411496ebf03c514e7674e8073e0c3
>>>>
>>>> Release Notes:
>>>> https://github.com/apache/incubator-dubbo/blob/dubbo-2.6.3/CHANGES.md
>>>>
>>>> The artifacts have been signed with Key : 28681CB1, which can be found in 
>>&g

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

[sebb]

On 11 September 2018 at 04:48, Dave Fisher  wrote:
> Hi -
>
> The Apache Pulsar project is ready to graduate as a TLP. They entered
> Incubation on June 1, 2017, have had many releases and have grown the
> community.
>
> At the mentors request they did a maturity model analysis [1] and wrote
> contribution guidelines. [2]
>
> The Graduation Proposal was written and discussed on the dev list. [3] At
> the mentor's recommendation the By-Laws Clause was removed.
>
> The new prospective PMC is set and the VOTE thread in the podling is here
> [4] with these results. [5]
>
> Let’s see if there is any discussion here on general@incubator before moving
> onto a VOTE.
>
> Regards,
> Dave
>
> [1]
> https://github.com/apache/incubator-pulsar/wiki/Apache-Maturity-Model-Assessment-for-Pulsar
> [2] http://pulsar.incubator.apache.org/en/contributing/
> [3]
> https://lists.apache.org/thread.html/b0914461f57253237e4a3c9151342f6d4fa37359dfc98a07adf9f36f@%3Cdev.pulsar.apache.org%3E
> [4]
> https://lists.apache.org/thread.html/93198abe36564a9e11a2a1bfe3ea8f35998444dbafea830f8b39df7b@%3Cdev.pulsar.apache.org%3E
> [5]
> https://lists.apache.org/thread.html/64841a07ba3dee2271f4098f9142afd41acffae1736275592aab4c83@%3Cdev.pulsar.apache.org%3E
>
>
> 
>
> Establish the Apache Pulsar Project
>
> WHEREAS, the Board of Directors deems it to be in the best interests of
> the Foundation and consistent with the Foundation's purpose to establish
> a Project Management Committee charged with the creation and maintenance
> of open-source software, for distribution at no charge to the public,
> related to a highly scalable, low latency messaging platform running on
> commodity hardware. It provides simple pub-sub and queue semantics over
> topics, lightweight compute framework, automatic cursor management for
> subscribers, and cross-datacenter replication.

Such detail as provided in the last sentence is unusual for graduation
resolutions.
I think the last sentence should be dropped from the resolution.

> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Pulsar Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache Pulsar Project be and hereby is responsible
> for the creation and maintenance of software related to a highly
> scalable, low latency messaging platform running on commodity hardware.
> It provides simple pub-sub and queue semantics over topics, lightweight
> compute framework, automatic cursor management for subscribers, and
> cross-datacenter replication; and be it further

See above.

> RESOLVED, that the office of "Vice President, Apache Pulsar" be and
> hereby is created, the person holding such office to serve at the
> direction of the Board of Directors as the chair of the Apache Pulsar
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache Pulsar
> Project; and be it further
>
> RESOLVED, that the persons listed immediately below be and hereby are
> appointed to serve as the initial members of the Apache Pulsar Project:
>
> * Boyang Jerry Peng 
> * Brad McMillen 
> * David Fisher 
> * Francis Christopher Liu 
> * Hiroyuki Sakai 
> * Ivan Brendan Kelly 
> * Jai Asher 
> * Jia Zhai 
> * Jim Jagielski 
> * Joe Francis 
> * Ludwig Pummer 
> * Masahiro Sakamoto 
> * Masakazu Kitajo 
> * Matteo Merli 
> * Nozomi Kurihara 
> * P. Taylor Goetz 
> * Rajan Dhabalia 
> * Sahaya Andrews 
> * Sanjeev Kulkarni 
> * Sebastián Schepens 
> * Siddharth Boobna 
> * Sijie Guo 
> * Yuki Shiga 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Matteo Merli be appointed
> to the office of Vice President, Apache Pulsar, to serve in accordance
> with and subject to the direction of the Board of Directors and the
> Bylaws of the Foundation until death, resignation, retirement, removal
> or disqualification, or until a successor is appointed; and be it
> further
>
> RESOLVED, that the Apache Pulsar Project be and hereby is tasked with
> the migration and rationalization of the Apache Incubator Pulsar
> podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> Pulsar podling encumbered upon the Apache Incubator PMC are hereafter
> discharged.
>

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

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

[sebb]

Just noticed that the download page links to

https://archive.apache.org/dist/incubator/pulsar/

for current sigs and hashes.
It should use the following for current releases:

https://www.apache.org/dist/incubator/pulsar/

The host archive.apache.org is only for archived releases.

[Also the page includes SHA1 links; these have since been deprecated
and could just be dropped]

The link to the KEYS file is correct.



On 11 September 2018 at 12:32, Justin Mclean  wrote:
> Hi,
>
>> Even Events is there under the Community tab.
>
> That seems to be project events rather than Apache events - but again it’s a 
> very minor thing.
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

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

[sebb]

On 12 September 2018 at 16:40, Dave Fisher  wrote:
> Hi -
>
> The Apache Pulsar project is ready to graduate as a TLP. They entered
> Incubation on June 1, 2017, have had many releases and have grown the
> community.
>
> Vote:
> [ ] +1 - Recommend Graduation of Apache Pulsar as a TLP
> [ ] -1 - Do not recommend graduation of Apache Pulsar because ….
>
> At the mentors request they did a maturity model analysis [1] and wrote
> contribution guidelines. [2]
>
> The Graduation Proposal was written and discussed on the dev list. [3] At
> the mentor's recommendation the By-Laws Clause was removed.
>
> The new prospective PMC is set and the VOTE thread in the podling is here
> [4] with these results. [5]
>
> Regards,
> Dave
>
> [1]
> https://github.com/apache/incubator-pulsar/wiki/Apache-Maturity-Model-Assessment-for-Pulsar
> [2] http://pulsar.incubator.apache.org/en/contributing/
> [3]
> https://lists.apache.org/thread.html/b0914461f57253237e4a3c9151342f6d4fa37359dfc98a07adf9f36f@%3Cdev.pulsar.apache.org%3E
> [4]
> https://lists.apache.org/thread.html/93198abe36564a9e11a2a1bfe3ea8f35998444dbafea830f8b39df7b@%3Cdev.pulsar.apache.org%3E
> [5]
> https://lists.apache.org/thread.html/64841a07ba3dee2271f4098f9142afd41acffae1736275592aab4c83@%3Cdev.pulsar.apache.org%3E
>
>
> 
>
> Establish the Apache Pulsar Project
>
> WHEREAS, the Board of Directors deems it to be in the best interests of
> the Foundation and consistent with the Foundation's purpose to establish
> a Project Management Committee charged with the creation and maintenance
> of open-source software, for distribution at no charge to the public,
> related to a highly scalable, low latency messaging platform running on
> commodity hardware. It provides simple pub-sub and queue semantics over
> topics, lightweight compute framework, automatic cursor management for
> subscribers, and cross-datacenter replication.

Such detail as provided in the last sentence is unusual for graduation
resolutions.
I think the last sentence should be dropped from the resolution; it's
not necessary.

> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Pulsar Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache Pulsar Project be and hereby is responsible
> for the creation and maintenance of software related to a highly
> scalable, low latency messaging platform running on commodity hardware.
> It provides simple pub-sub and queue semantics over topics, lightweight
> compute framework, automatic cursor management for subscribers, and
> cross-datacenter replication; and be it further

Ditto

> RESOLVED, that the office of "Vice President, Apache Pulsar" be and
> hereby is created, the person holding such office to serve at the
> direction of the Board of Directors as the chair of the Apache Pulsar
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache Pulsar
> Project; and be it further
>
> RESOLVED, that the persons listed immediately below be and hereby are
> appointed to serve as the initial members of the Apache Pulsar Project:
>
> * Boyang Jerry Peng 
> * Brad McMillen 
> * David Fisher 
> * Francis Christopher Liu 
> * Hiroyuki Sakai 
> * Ivan Brendan Kelly 
> * Jai Asher 
> * Jia Zhai 
> * Jim Jagielski 
> * Joe Francis 
> * Ludwig Pummer 
> * Masahiro Sakamoto 
> * Masakazu Kitajo 
> * Matteo Merli 
> * Nozomi Kurihara 
> * P. Taylor Goetz 
> * Rajan Dhabalia 
> * Sahaya Andrews 
> * Sanjeev Kulkarni 
> * Sebastián Schepens 
> * Siddharth Boobna 
> * Sijie Guo 
> * Yuki Shiga 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Matteo Merli be appointed
> to the office of Vice President, Apache Pulsar, to serve in accordance
> with and subject to the direction of the Board of Directors and the
> Bylaws of the Foundation until death, resignation, retirement, removal
> or disqualification, or until a successor is appointed; and be it
> further
>
> RESOLVED, that the Apache Pulsar Project be and hereby is tasked with
> the migration and rationalization of the Apache Incubator Pulsar
> podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> Pulsar podling encumbered upon the Apache Incubator PMC are hereafter
> discharged.

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

Re: Email to be sent to inactive mentors

[sebb]

On 17 September 2018 at 02:39, Justin Mclean  wrote:
> Hi,
>
> Current 1/3 of those asked have responded with:
> -17 mentors have asked to retire/step down
> - 3 will continue (including one who asked to step down but changed their 
> mind and has been added back)
>
> Of the total above 1 mentor was miss-identified as missing as they are mostly 
> active in GitHub and not on the mailing list.

Maybe I am missing something here, but how would GitHub contributions
contribute to mentoring?
Or are you just looking for any activity rather than mentoring activity itself?

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

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

Re: Email to be sent to inactive mentors

[sebb]

On 17 September 2018 at 12:10, Justin Mclean  wrote:
> Hi,
>
>> Maybe I am missing something here, but how would GitHub contributions 
>> contribute to mentoring?
>
> Well I thought it wouldn't which is why I didn’t include it, but as some 
> projects use GitHub issues a lot, so some stuff tends to get discussed there 
> rather than on the dev list.

"If it did not happen on a mailing list then it did not happen"
If the GitHub issues are not being copied to the mailing lists, then
again I don't see how that contributes to the mentoring process.

> There’s a few other factors in this case, but I think it’s on it way to being 
> sorted. I'll bring it to the mentors attention and see what they think. 
> (Sorry for being obtuse, but this is a public list.)

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

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

Re: Email to be sent to inactive mentors

[sebb]

On 17 September 2018 at 23:02, Dave Fisher  wrote:
> A mapping is made on id.apache.org and shown on whimsy. A patch to add a 
> github username column to the roster page in whimsy would make life easier.

Please raise an enhancement JIRA .

> Regards,
> Dave
>
> Sent from my iPhone
>
>> On Sep 17, 2018, at 2:24 PM, Ted Dunning  wrote:
>>
>> Indeed.
>>
>> And even if it seems obvious, that isn't always obviously correct.
>> Establishing a mapping or using an Apache ID is important.
>>
>>> On Mon, Sep 17, 2018 at 4:45 PM Dave Fisher  wrote:
>>>
>>> Github id does not often equal Apache id. It is not always obvious.
>>>
>>> Regards,
>>> Dave
>>>
>>> Sent from my iPhone
>>>
>>>> On Sep 17, 2018, at 12:35 PM, Ted Dunning  wrote:
>>>>
>>>> Obviously, lots of informational activity occurs off the mailing list. A
>>>> great example is answering questions on stack overflow. And ApacheCon
>>> talks
>>>> which actually led to certain decisions being made should definitely be
>>>> echoed back to the mailing list.
>>>>
>>>> But apart from all of that GitHub issues should definitely be mirrored
>>> back
>>>> to the mailing list.  There's no way to justify that an issue tracker is
>>>> not echoed back.
>>>>
>>>>> On Mon, Sep 17, 2018, 14:05 Julian Hyde  wrote:
>>>>>
>>>>> By that argument there’s no point speaking at ApacheCon. Because it
>>>>> doesn’t happen on a mailing list.
>>>>>
>>>>> So let’s not be so strict.
>>>>>
>>>>> Clearly there are many ways that a mentor can assist. Some of them are
>>> not
>>>>> measurable (such as having a phone call). But I think any measurable
>>>>> activity should count.
>>>>>
>>>>> Julian
>>>>>
>>>>>
>>>>>> On Sep 17, 2018, at 8:55 AM, sebb  wrote:
>>>>>>
>>>>>> On 17 September 2018 at 12:10, Justin Mclean >>>
>>>>> wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>>> Maybe I am missing something here, but how would GitHub contributions
>>>>> contribute to mentoring?
>>>>>>>
>>>>>>> Well I thought it wouldn't which is why I didn’t include it, but as
>>>>> some projects use GitHub issues a lot, so some stuff tends to get
>>> discussed
>>>>> there rather than on the dev list.
>>>>>>
>>>>>> "If it did not happen on a mailing list then it did not happen"
>>>>>> If the GitHub issues are not being copied to the mailing lists, then
>>>>>> again I don't see how that contributes to the mentoring process.
>>>>>>
>>>>>>> There’s a few other factors in this case, but I think it’s on it way
>>> to
>>>>> being sorted. I'll bring it to the mentors attention and see what they
>>>>> think. (Sorry for being obtuse, but this is a public list.)
>>>>>>
>>>>>>> Thanks,
>>>>>>> Justin
>>>>>>> -
>>>>>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>>>>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>>>>>>
>>>>>>
>>>>>> -
>>>>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>>>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>>>>>
>>>>>
>>>>>
>>>>> -
>>>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>>>>
>>>>>
>>>
>>>
>>> -
>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>>
>>>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

Re: [ANNOUNCE] Apache OpenWhisk nodejs, java, docker, python, php and swift runtimes (incubating) 1.12.0 released

[sebb]

On Fri, 28 Sep 2018 at 21:35, Vincent S Hou  wrote:
>
> Hi everyone,
>
> We are pleased to announce that Apache nodejs, java, docker, python, php and 
> swift runtimes (incubating) 1.12.0 are released.

Minor nit: that should be "Apache OpenWhisk ..."

> OpenWhisk has 6 default runtime environments for users to develop their 
> actions: nodejs, java, docker, python, php and swift.
>
> The download links of the current release is available at:
> https://openwhisk.apache.org/downloads.html
>
> Vincent Hou
> On behalf of the OpenWhisk team
>
> =
> *DISCLAIMER*

Only one disclaimer is needed for each announce.

> Apache OpenWhisk Runtime nodejs (incubating) is an effort undergoing 
> incubation at The

That should be

Apache OpenWhisk (incubating) is an effort undergoing incubation ...

> Apache Software
> Foundation (ASF), sponsored by Incubator.
> Incubation is required of all newly accepted projects until a further
> review indicates that the infrastructure, communications, and decision
> making process have stabilized in a manner consistent with other successful
> ASF projects.
> While incubation status is not necessarily a reflection of the completeness
> or stability of the code, it does indicate that the project has yet to be
> fully endorsed by the ASF.

Drop the rest

> Apache OpenWhisk Runtime java (incubating) is an effort undergoing incubation 
> at The
> Apache Software
> Foundation (ASF), sponsored by Incubator.
> Incubation is required of all newly accepted projects until a further
> review indicates that the infrastructure, communications, and decision
> making process have stabilized in a manner consistent with other successful
> ASF projects.
> While incubation status is not necessarily a reflection of the completeness
> or stability of the code, it does indicate that the project has yet to be
> fully endorsed by the ASF.
>
> *DISCLAIMER*
> Apache OpenWhisk Runtime docker (incubating) is an effort undergoing 
> incubation at The
> Apache Software
> Foundation (ASF), sponsored by Incubator.
> Incubation is required of all newly accepted projects until a further
> review indicates that the infrastructure, communications, and decision
> making process have stabilized in a manner consistent with other successful
> ASF projects.
> While incubation status is not necessarily a reflection of the completeness
> or stability of the code, it does indicate that the project has yet to be
> fully endorsed by the ASF.
>
> Apache OpenWhisk Runtime python (incubating) is an effort undergoing 
> incubation at The
> Apache Software
> Foundation (ASF), sponsored by Incubator.
> Incubation is required of all newly accepted projects until a further
> review indicates that the infrastructure, communications, and decision
> making process have stabilized in a manner consistent with other successful
> ASF projects.
> While incubation status is not necessarily a reflection of the completeness
> or stability of the code, it does indicate that the project has yet to be
> fully endorsed by the ASF.
>
> *DISCLAIMER*
> Apache OpenWhisk Runtime php (incubating) is an effort undergoing incubation 
> at The
> Apache Software
> Foundation (ASF), sponsored by Incubator.
> Incubation is required of all newly accepted projects until a further
> review indicates that the infrastructure, communications, and decision
> making process have stabilized in a manner consistent with other successful
> ASF projects.
> While incubation status is not necessarily a reflection of the completeness
> or stability of the code, it does indicate that the project has yet to be
> fully endorsed by the ASF.
>
> Apache OpenWhisk Runtime swift (incubating) is an effort undergoing 
> incubation at The
> Apache Software
> Foundation (ASF), sponsored by Incubator.
> Incubation is required of all newly accepted projects until a further
> review indicates that the infrastructure, communications, and decision
> making process have stabilized in a manner consistent with other successful
> ASF projects.
> While incubation status is not necessarily a reflection of the completeness
> or stability of the code, it does indicate that the project has yet to be
> fully endorsed by the ASF.
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

Re: [DISCUSS] Mandatory relocation of Apache git repositories on git-wip-us.apache.org

[sebb]

On Wed, 12 Dec 2018 at 18:03, Roy Lenferink  wrote:
>
> The repo has moved to gitbox now [1]. The jenkins job still needs to be
> updated though [2]. If someone with the appropriate permissions can help
> with that, that would be nice.

Done

> - Roy
>
> [1] https://gitbox.apache.org/repos/asf/incubator.git
> [2] https://builds.apache.org/view/H-L/view/Incubator/job/Incubator%20Site/
>
> Op di 11 dec. 2018 om 17:43 schreef Roy Lenferink :
>
> > Perfect. I have created an issue with INFRA for this and will post a
> > message to the list once the repo has been migrated.
> >
> > In the meantime I tried to update the Jenkins job responsible for
> > generating the Incubator website, but I noticed I haven't got enough
> > permisssions to do so.
> > Can a PMC chair assist and maybe add me to the hudson-jobadmin group in
> > whimsy?
> >
> > Thanks
> > - Roy
> >
> > Op di 11 dec. 2018 om 07:07 schreef Justin Mclean <
> > jus...@classsoftware.com>:
> >
> >> +1 no objections from me
> >>
> >> -
> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> For additional commands, e-mail: general-h...@incubator.apache.org
> >>
> >>

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

Re: Discussion board vs. user mailing list in incubating project

[sebb]

On Mon, 14 Jan 2019 at 16:19, Matt Sicker  wrote:
>
> On Mon, 14 Jan 2019 at 07:15, Sebastian  wrote:
> > So to rephrase this question, if the project finds a way to archive the
> > discussions to ASF-controlled infra (e.g., to a dedicated mailinglist),
> > than they could keep using the board?
>
> That's my understanding. It applied to the ASF Slack, for example, or
> IRC, or other communication channels in general. The idea is that you
> want your project's decision making to be asynchronously accessible by
> all interested parties via ASF infrastructure.

I thought the rule was that decisions have to be made on ASF mailing lists.
It's fine to have discussions elsewhere, but the results must be
brought back to a mailing list for the actual decision.
Or has that rule been changed? If so, is it documented anywhere?

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

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

[VOTE] Shut down unused/inactive incubator lists

[sebb]

The following lists are all but inactive:

announce@ Last post Jan 2008
android-interest@ Last post Mar 2011
dev@ - only general circulars
jaxws-tck@ (private) Last post 2012
projects@ Last post Jul 2011
user@ - only general circulars

I think they should be shut down.

Please vote so an Infra Jira can be raised to shut them down.
They can have a bounce message added to direct posters to
general@/private@ as appropriate

[  ] +1
[  ] -1 - give a reason please

Please vote by end January 2019

Sebb.

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

Re: [IPMC] What to do with retired podling repositories

[sebb]

In the past, SVN repos have just been made read-only.
(The intention was to move them to
http://svn.apache.org/viewvc/incubator/RETIRED/ but that never
happened)

I think it would be a mistake to drop the repos.
There's no guarantee that the code is available anywhere else, and it
seems wrong to throw away any effort spent on it at the ASF.

On Mon, 14 Jan 2019 at 10:25, Greg Stein  wrote:
>
> If they didn't graduate, then they aren't Apache projects. So as Myrle says, 
> "what are they doing on our servers?" For the retired podlings, our copy of 
> their code could be misleading, relative to where it came from, or where the 
> community may have newly forked it.
>
> Not an Infra opinion,
> -g
>
>
> On Mon, Jan 14, 2019 at 12:12 AM Myrle Krantz  wrote:
>>
>> If we can’t name a reason for keeping the data, I’d be inclined to just
>> delete.  We are not data squirrels.
>>
>> : o),
>> Myrle
>>
>> On Sun, Jan 13, 2019 at 10:15 AM Daniel Gruno  wrote:
>>
>> > Hello IPMC and other folks,
>> >
>> > We have a big bunch of retired podlings with git repositories on
>> > git-wip-us. As we are working on retiring this service, we need to
>> > address what happens with these old project repositories.
>> >
>> > The retired podlings we need to address are:
>> > blur, cmda, concerted, corinthia, cotton, gearpump, gossip, hdt, horn,
>> > htrace, iota, mrql, openaz, pirk, provisionr, quickstep, ripple, s4,
>> > slider, wave
>> >
>> > Before February 7th, we at ASF Infra, would love if the incubator could
>> > decide what happens to these repositories, either individually or as a
>> > whole.
>> >
>> > Some suggested options are:
>> >
>> > 1) delete the repositories
>> > 2) rename them to incubator-retired-$foo.git
>> > 3) Do nothing, but put a note on github etc that they retired.
>> > 4) punt it to the attic if possible (you'd have to coordinate with the
>> > Attic PMC then)
>> > 5) Something else??
>> >
>> > Please talk among yourselves and let Infra know :)
>> >
>> > With regards,
>> > Daniel on behalf of ASF Infra.
>> >
>> > -
>> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> > For additional commands, e-mail: general-h...@incubator.apache.org
>> >
>> >

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

Re: [VOTE] Shut down unused/inactive incubator lists

[sebb]

Raised https://issues.apache.org/jira/browse/INFRA-17831

On Sat, 26 Jan 2019 at 07:21, Xin Wang  wrote:
>
> +1
>
> 在 2019年1月26日星期六，Jun Liu  写道：
>
> > +1
> >
> > Jun
> >
> > > On Jan 21, 2019, at 8:11 AM, sebb  wrote:
> > >
> > > The following lists are all but inactive:
> > >
> > > announce@ Last post Jan 2008
> > > android-interest@ Last post Mar 2011
> > > dev@ - only general circulars
> > > jaxws-tck@ (private) Last post 2012
> > > projects@ Last post Jul 2011
> > > user@ - only general circulars
> > >
> > > I think they should be shut down.
> > >
> > > Please vote so an Infra Jira can be raised to shut them down.
> > > They can have a bounce message added to direct posters to
> > > general@/private@ as appropriate
> > >
> > > [  ] +1
> > > [  ] -1 - give a reason please
> > >
> > > Please vote by end January 2019
> > >
> > > Sebb.
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> >
> >

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

Re: [VOTE] Shut down unused/inactive incubator lists

[sebb]

Done

On Sun, 10 Feb 2019 at 18:34, sebb  wrote:
>
> Raised https://issues.apache.org/jira/browse/INFRA-17831
>
> On Sat, 26 Jan 2019 at 07:21, Xin Wang  wrote:
> >
> > +1
> >
> > 在 2019年1月26日星期六，Jun Liu  写道：
> >
> > > +1
> > >
> > > Jun
> > >
> > > > On Jan 21, 2019, at 8:11 AM, sebb  wrote:
> > > >
> > > > The following lists are all but inactive:
> > > >
> > > > announce@ Last post Jan 2008
> > > > android-interest@ Last post Mar 2011
> > > > dev@ - only general circulars
> > > > jaxws-tck@ (private) Last post 2012
> > > > projects@ Last post Jul 2011
> > > > user@ - only general circulars
> > > >
> > > > I think they should be shut down.
> > > >
> > > > Please vote so an Infra Jira can be raised to shut them down.
> > > > They can have a bounce message added to direct posters to
> > > > general@/private@ as appropriate
> > > >
> > > > [  ] +1
> > > > [  ] -1 - give a reason please
> > > >
> > > > Please vote by end January 2019
> > > >
> > > > Sebb.
> > > >
> > > > -
> > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > For additional commands, e-mail: general-h...@incubator.apache.org
> > > >
> > >
> > >

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

[RFC] Mentors and podling LDAP memberships

[sebb]

Are podling mentors expected to be in the LDAP owners group (i.e. on
the PPMC) and in the members group (i.e. committers)?

This affects Whimsy: should it report discrepancies, e.g. mentors not
in the committers group?

It also potentially affects graduation: normally at least some mentors
drop out at graduation, i.e. are not part of the initial PMC. This
would generally imply that they should also be dropped from the LDAP
owners group, and possibly the committers group as well. Is that the
case?

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

Re: Updating HTrace podling page with retirement status

[sebb]

On Mon, 26 Nov 2018 at 12:34, Colm O hEigeartaigh  wrote:
>
> Hi all,
>
> Unless I'm missing something, the HTrace podling page (
> http://htrace.incubator.apache.org/) has no indication that the project has
> been retired (http://incubator.apache.org/projects/htrace.html). The
> website should be updated to make the status clear.

I think the website for retired projects is normally deleted and the
URL should redirect to the status page.

For example, blur status page
http://incubator.apache.org/projects/blur.html
links to
http://incubator.apache.org/blur/
which redirects back to the status page.

This is done in one of the following files:

For incubator.apache.org/podling URLs:
https://gitbox.apache.org/repos/asf?p=incubator.git;a=blob;f=assets/.htaccess

For podling.incubator.apache.org URLs using svnpubsub:
https://svn.apache.org/repos/asf/incubator//site/[publish|etc]

For podling.incubator.apache.org URLs using gitpubsub:
Something like the following:
https://gitbox.apache.org/repos/asf/incubator-retired--site.git
However this appears to be read-only


> Colm.
>
>
> --
> Colm O hEigeartaigh
>
> Talend Community Coder
> http://coders.talend.com

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

Re: Incubator release votes

[sebb]

On Tue, 26 Feb 2019 at 20:01, Ted Dunning  wrote:
>
> Kevin,
>
> Can you explain what checking you did to justify your vote?
>
> This is important so that others can know what has already been done.

IMO the +1 ought to be added to the vote thread, not here.

>
>
> On Tue, Feb 26, 2019 at 8:02 AM Kevin A. McGrail 
> wrote:
>
> > On 2/26/2019 8:20 AM, David P Grove wrote:
> > > 
> > > Or in the case of the current OpenWhisk podling voting thread [1], our
> > only
> > > mentor has already voted +1, but after a week we still need two more IPMC
> > > votes to be able to proceed.
> > >
> > > Please help
> > > 
> >
> > Sorry, I was not aware of that issue.  I'm monitoring for the podlings I
> > help with but not as much with general@
> >
> > I vote +1.
> >
> > --
> > Kevin A. McGrail
> > Member, Apache Software Foundation
> > Chair Emeritus Apache SpamAssassin Project
> > https://www.linkedin.com/in/kmcgrail - 703.798.0171
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >

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

Re: New distribution guidelines

[sebb]

There's some spurious text at the start of the page:

"Skip to end of metadata Created by ASF Infrabot, last modified by
Justin Mclean on Jul 14, 2020 Go to start of metadata"

Also, what does the acronym IP mean?

I think there are some ambiguities:

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

- "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.

- "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 don't understand "source releases ... are just a convenience for end user.".
Does not make sense to me.

On Mon, 5 Oct 2020 at 05:26, Justin Mclean  wrote:
>
> 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

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

Is there a check list for podling renames?

[sebb]

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.

For example, I just found out that Infra have to be asked to redirect
the old website address:

https://issues.apache.org/jira/browse/INFRA-20975

Though as far as I know, emails are automatically redirected.
This should be confirmed.

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

Tamaya retired, but there is no indication on its website

[sebb]

Tamaya retired in April 2020, however the website makes no mention of
this, and the incubator releases are still on the ASF mirror system.

There may be other resources that have not been shut down.

JIRA and Github do appear to have been addressed.

Sebb.

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

Redirecting retired podling websites

[sebb]

It's currently quite awkward fixing up retired podling websites so
they redirect to the status page.
There are currently about 6 such podlings, dating back to Nov 2013.

[It's easy enough to do this for incubator sub-sites (e.g.
http://incubator.apache.org/wave), as these can use a single .htaccess
file; that is not the case for the above sites otherwise they would
have been fixed ages ago]

Recent podlings use websites like http://ariatosca.apache.org/ and/or
http://ariatosca.incubator.apache.org/
The redirects need to be added in each website source.

This can be difficult to do, see INFRA-21451 re Tamaya.
This was opened on Feb 21st and has yet to be completed.

I have proposed an Infra PR which should make it much easier to set up
the redirect to the status file.

The idea is to set up a special directory:
 http://incubator.apache.org/retired/

For each retired podling, create a marker directory, e.g.
tamaya/

If the web server detects that there is a directory matching the first
part of the web host name (e.g. tamaya), then it redirects to
http://incubator.apache.org/projects/tamaya.html (e.g.)

Simples.

Sebb.
P.S. Attic works in a similar way, but adds a banner instead of redirecting.

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

Re: Redirecting retired podling websites

[sebb]

On Wed, 31 Mar 2021 at 17:48, Dave Fisher  wrote:
>
> Hi Sebb,
>
> I noticed you did a lot of updates to .htaccess [1] - I have some inline 
> questions.
>
> > On Mar 30, 2021, at 4:31 PM, Dave Fisher  wrote:
> >
> > Hi Sebb,
> >
> >> On Mar 30, 2021, at 4:22 PM, sebb  wrote:
> >>
> >> It's currently quite awkward fixing up retired podling websites so
> >> they redirect to the status page.
> >> There are currently about 6 such podlings, dating back to Nov 2013.
> >>
> >> [It's easy enough to do this for incubator sub-sites (e.g.
> >> http://incubator.apache.org/wave), as these can use a single .htaccess
> >> file; that is not the case for the above sites otherwise they would
> >> have been fixed ages ago]
> >>
> >> Recent podlings use websites like http://ariatosca.apache.org/ and/or
> >> http://ariatosca.incubator.apache.org/
> >> The redirects need to be added in each website source.
> >>
> >> This can be difficult to do, see INFRA-21451 re Tamaya.
> >> This was opened on Feb 21st and has yet to be completed.
> >>
> >> I have proposed an Infra PR which should make it much easier to set up
> >> the redirect to the status file.
> >>
> >> The idea is to set up a special directory:
> >> http://incubator.apache.org/retired/
> >>
> >> For each retired podling, create a marker directory, e.g.
> >> tamaya/
> >
> > I can add a step in the clutch2.sh shell script to maintain these 
> > placeholders.
>
> Do you still need retired/${podling} marker directories?

Not yet.

Infra have not yet applied the PR, so the marker directories won't
have any effect yet.

> >
> >>
> >> If the web server detects that there is a directory matching the first
> >> part of the web host name (e.g. tamaya), then it redirects to
> >> http://incubator.apache.org/projects/tamaya.html (e.g.)
> >
> > I think we should also review the .htaccess for the incubator. More 
> > tomorrow.
>
> Would you explain .htaccess comments like:
> # 
> https://gitbox.apache.org/repos/asf?p=incubator-retired-pirk.git;a=blob;f=.htaccess;hb=refs/heads/asf-site
> # https://svn.apache.org/repos/asf/incubator/sirona/site/.htaccess

There was a TODO for the retired podling; I replaced it with details
of where the htaccess file is located.
(The redirect cannot be done in [1])

>
> Would .htaccess redirects like the following break anything?
> RedirectMatch Permanent ^/sirona(/.*)?$ 
> http://incubator.apache.org/projects/sirona.html

Redirects would not work.

Or rather, they would only apply to http(s)://incubator.apache.org/sirona/*

I don't think that would do any harm, but the original website was
http(s)://sirona.apache.org/ so they would not be particularly useful.

> If possible I think that the whole set of graduated and retired .htaccess 
> could be generated.

Not sure it's worth the effort of coding, testing and maintaining such
a generator.

Changes are not that frequent, and are pretty easy to do by reference
to an existing entry.

In any case, I don't think there will be (m)any more changes to [1] --
podling redirects will have to be made elsewhere.

When current podlings retire, the htaccess entry has to be made in the
podling website.

However if Infra apply the PR, redirects can be enabled simply by
setting up the retired/ marker directory.

> [1] https://raw.githubusercontent.com/apache/incubator/master/assets/.htaccess
>
> All The Best,
> Dave
>
> >
> > Regards,
> > Dave
> >
> >>
> >> Simples.
> >>
> >> Sebb.
> >> P.S. Attic works in a similar way, but adds a banner instead of 
> >> redirecting.
> >>
> >> -
> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> For additional commands, e-mail: general-h...@incubator.apache.org
> >>
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

Re: Redirecting retired podling websites

[sebb]

On Wed, 31 Mar 2021 at 22:28, sebb  wrote:
>
> On Wed, 31 Mar 2021 at 17:48, Dave Fisher  wrote:
> >
> > Hi Sebb,
> >
> > I noticed you did a lot of updates to .htaccess [1] - I have some inline 
> > questions.
> >
> > > On Mar 30, 2021, at 4:31 PM, Dave Fisher  wrote:
> > >
> > > Hi Sebb,
> > >
> > >> On Mar 30, 2021, at 4:22 PM, sebb  wrote:
> > >>
> > >> It's currently quite awkward fixing up retired podling websites so
> > >> they redirect to the status page.
> > >> There are currently about 6 such podlings, dating back to Nov 2013.
> > >>
> > >> [It's easy enough to do this for incubator sub-sites (e.g.
> > >> http://incubator.apache.org/wave), as these can use a single .htaccess
> > >> file; that is not the case for the above sites otherwise they would
> > >> have been fixed ages ago]
> > >>
> > >> Recent podlings use websites like http://ariatosca.apache.org/ and/or
> > >> http://ariatosca.incubator.apache.org/
> > >> The redirects need to be added in each website source.
> > >>
> > >> This can be difficult to do, see INFRA-21451 re Tamaya.
> > >> This was opened on Feb 21st and has yet to be completed.
> > >>
> > >> I have proposed an Infra PR which should make it much easier to set up
> > >> the redirect to the status file.
> > >>
> > >> The idea is to set up a special directory:
> > >> http://incubator.apache.org/retired/
> > >>
> > >> For each retired podling, create a marker directory, e.g.
> > >> tamaya/
> > >
> > > I can add a step in the clutch2.sh shell script to maintain these 
> > > placeholders.
> >
> > Do you still need retired/${podling} marker directories?
>
> Not yet.
>
> Infra have not yet applied the PR, so the marker directories won't
> have any effect yet.

The PR has now been applied.

> > >
> > >>
> > >> If the web server detects that there is a directory matching the first
> > >> part of the web host name (e.g. tamaya), then it redirects to
> > >> http://incubator.apache.org/projects/tamaya.html (e.g.)
> > >
> > > I think we should also review the .htaccess for the incubator. More 
> > > tomorrow.
> >
> > Would you explain .htaccess comments like:
> > # 
> > https://gitbox.apache.org/repos/asf?p=incubator-retired-pirk.git;a=blob;f=.htaccess;hb=refs/heads/asf-site
> > # https://svn.apache.org/repos/asf/incubator/sirona/site/.htaccess
>
> There was a TODO for the retired podling; I replaced it with details
> of where the htaccess file is located.
> (The redirect cannot be done in [1])
>
> >
> > Would .htaccess redirects like the following break anything?
> > RedirectMatch Permanent ^/sirona(/.*)?$ 
> > http://incubator.apache.org/projects/sirona.html
>
> Redirects would not work.
>
> Or rather, they would only apply to http(s)://incubator.apache.org/sirona/*
>
> I don't think that would do any harm, but the original website was
> http(s)://sirona.apache.org/ so they would not be particularly useful.
>
> > If possible I think that the whole set of graduated and retired .htaccess 
> > could be generated.
>
> Not sure it's worth the effort of coding, testing and maintaining such
> a generator.
>
> Changes are not that frequent, and are pretty easy to do by reference
> to an existing entry.
>
> In any case, I don't think there will be (m)any more changes to [1] --
> podling redirects will have to be made elsewhere.
>
> When current podlings retire, the htaccess entry has to be made in the
> podling website.
>
> However if Infra apply the PR, redirects can be enabled simply by
> setting up the retired/ marker directory.

The PR has been applied, so it should now work.

> > [1] 
> > https://raw.githubusercontent.com/apache/incubator/master/assets/.htaccess
> >
> > All The Best,
> > Dave
> >
> > >
> > > Regards,
> > > Dave
> > >
> > >>
> > >> Simples.
> > >>
> > >> Sebb.
> > >> P.S. Attic works in a similar way, but adds a banner instead of 
> > >> redirecting.
> > >>
> > >> -
> > >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > >> For additional commands, e-mail: general-h...@incubator.apache.org
> > >>
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >

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

Re: Redirecting retired podling websites

[sebb]

On Sat, 3 Apr 2021 at 23:43, Dave Fisher  wrote:
>
>
>
> > On Apr 3, 2021, at 3:38 PM, sebb  wrote:
> >
> > On Wed, 31 Mar 2021 at 22:28, sebb  wrote:
> >>
> >> On Wed, 31 Mar 2021 at 17:48, Dave Fisher  wrote:
> >>>
> >>> Hi Sebb,
> >>>
> >>> I noticed you did a lot of updates to .htaccess [1] - I have some inline 
> >>> questions.
> >>>
> >>>> On Mar 30, 2021, at 4:31 PM, Dave Fisher  wrote:
> >>>>
> >>>> Hi Sebb,
> >>>>
> >>>>> On Mar 30, 2021, at 4:22 PM, sebb  wrote:
> >>>>>
> >>>>> It's currently quite awkward fixing up retired podling websites so
> >>>>> they redirect to the status page.
> >>>>> There are currently about 6 such podlings, dating back to Nov 2013.
> >>>>>
> >>>>> [It's easy enough to do this for incubator sub-sites (e.g.
> >>>>> http://incubator.apache.org/wave), as these can use a single .htaccess
> >>>>> file; that is not the case for the above sites otherwise they would
> >>>>> have been fixed ages ago]
> >>>>>
> >>>>> Recent podlings use websites like http://ariatosca.apache.org/ and/or
> >>>>> http://ariatosca.incubator.apache.org/
> >>>>> The redirects need to be added in each website source.
> >>>>>
> >>>>> This can be difficult to do, see INFRA-21451 re Tamaya.
> >>>>> This was opened on Feb 21st and has yet to be completed.
> >>>>>
> >>>>> I have proposed an Infra PR which should make it much easier to set up
> >>>>> the redirect to the status file.
> >>>>>
> >>>>> The idea is to set up a special directory:
> >>>>> http://incubator.apache.org/retired/
> >>>>>
> >>>>> For each retired podling, create a marker directory, e.g.
> >>>>> tamaya/
> >>>>
> >>>> I can add a step in the clutch2.sh shell script to maintain these 
> >>>> placeholders.
> >>>
> >>> Do you still need retired/${podling} marker directories?
> >>
> >> Not yet.
> >>
> >> Infra have not yet applied the PR, so the marker directories won't
> >> have any effect yet.
> >
> > The PR has now been applied.
>
> So, please review https://incubator.apache.org/podlings_retired.txt

No idea what that file has to do with this thread, or what you expect
me to review.

> If create a retired/$col1 directory on the website the trouble will resolve?

Try creating retired/tamaya/ and see what happens to http://tamaya.apache.org/
It should redirect to http://incubator.apache.org/projects/tamaya.html

N.B. this only needs to be done for retired podlings whose URLs don't
already redirect.

There are only about 6 of those, see:
https://issues.apache.org/jira/browse/INCUBATOR-262

> I want to make sure I'm picking the podling attribute you expect.

The directory name under retired/ must be the same as the unqualified
host name for the podling website.

i.e. tamaya for tamaya.apache.org or tamaya.incubator.apache.org

> Regards,
> Dave
>
> >
> >>>>
> >>>>>
> >>>>> If the web server detects that there is a directory matching the first
> >>>>> part of the web host name (e.g. tamaya), then it redirects to
> >>>>> http://incubator.apache.org/projects/tamaya.html (e.g.)
> >>>>
> >>>> I think we should also review the .htaccess for the incubator. More 
> >>>> tomorrow.
> >>>
> >>> Would you explain .htaccess comments like:
> >>> # 
> >>> https://gitbox.apache.org/repos/asf?p=incubator-retired-pirk.git;a=blob;f=.htaccess;hb=refs/heads/asf-site
> >>> # https://svn.apache.org/repos/asf/incubator/sirona/site/.htaccess
> >>
> >> There was a TODO for the retired podling; I replaced it with details
> >> of where the htaccess file is located.
> >> (The redirect cannot be done in [1])
> >>
> >>>
> >>> Would .htaccess redirects like the following break anything?
> >>> RedirectMatch Permanent ^/sirona(/.*)?$ 
> >>> http://incubator.apache.org/projects/sirona.html
> >>
> >> Redirects would not work.
> >>
> >> Or rather, they would only apply to http(s)://incubator.apache.org/sirona/*
> >>
> >> I don't thi

Re: Redirecting retired podling websites

[sebb]

On Sun, 4 Apr 2021 at 01:31, Dave Fisher  wrote:
>
>
>
> > On Apr 3, 2021, at 4:49 PM, sebb  wrote:
> >
> > On Sat, 3 Apr 2021 at 23:43, Dave Fisher  wrote:
> >>
> >>
> >>
> >>> On Apr 3, 2021, at 3:38 PM, sebb  wrote:
> >>>
> >>> On Wed, 31 Mar 2021 at 22:28, sebb  wrote:
> >>>>
> >>>> On Wed, 31 Mar 2021 at 17:48, Dave Fisher  wrote:
> >>>>>
> >>>>> Hi Sebb,
> >>>>>
> >>>>> I noticed you did a lot of updates to .htaccess [1] - I have some 
> >>>>> inline questions.
> >>>>>
> >>>>>> On Mar 30, 2021, at 4:31 PM, Dave Fisher  wrote:
> >>>>>>
> >>>>>> Hi Sebb,
> >>>>>>
> >>>>>>> On Mar 30, 2021, at 4:22 PM, sebb  wrote:
> >>>>>>>
> >>>>>>> It's currently quite awkward fixing up retired podling websites so
> >>>>>>> they redirect to the status page.
> >>>>>>> There are currently about 6 such podlings, dating back to Nov 2013.
> >>>>>>>
> >>>>>>> [It's easy enough to do this for incubator sub-sites (e.g.
> >>>>>>> http://incubator.apache.org/wave), as these can use a single .htaccess
> >>>>>>> file; that is not the case for the above sites otherwise they would
> >>>>>>> have been fixed ages ago]
> >>>>>>>
> >>>>>>> Recent podlings use websites like http://ariatosca.apache.org/ and/or
> >>>>>>> http://ariatosca.incubator.apache.org/
> >>>>>>> The redirects need to be added in each website source.
> >>>>>>>
> >>>>>>> This can be difficult to do, see INFRA-21451 re Tamaya.
> >>>>>>> This was opened on Feb 21st and has yet to be completed.
> >>>>>>>
> >>>>>>> I have proposed an Infra PR which should make it much easier to set up
> >>>>>>> the redirect to the status file.
> >>>>>>>
> >>>>>>> The idea is to set up a special directory:
> >>>>>>> http://incubator.apache.org/retired/
> >>>>>>>
> >>>>>>> For each retired podling, create a marker directory, e.g.
> >>>>>>> tamaya/
> >>>>>>
> >>>>>> I can add a step in the clutch2.sh shell script to maintain these 
> >>>>>> placeholders.
> >>>>>
> >>>>> Do you still need retired/${podling} marker directories?
> >>>>
> >>>> Not yet.
> >>>>
> >>>> Infra have not yet applied the PR, so the marker directories won't
> >>>> have any effect yet.
> >>>
> >>> The PR has now been applied.
> >>
> >> So, please review https://incubator.apache.org/podlings_retired.txt
> >
> > No idea what that file has to do with this thread, or what you expect
> > me to review.
> >
> >> If create a retired/$col1 directory on the website the trouble will 
> >> resolve?
> >
> > Try creating retired/tamaya/ and see what happens to 
> > http://tamaya.apache.org/
> > It should redirect to http://incubator.apache.org/projects/tamaya.html
> >
> > N.B. this only needs to be done for retired podlings whose URLs don't
> > already redirect.
> >
> > There are only about 6 of those, see:
> > https://issues.apache.org/jira/browse/INCUBATOR-262
> >
> >> I want to make sure I'm picking the podling attribute you expect.
> >
> > The directory name under retired/ must be the same as the unqualified
> > host name for the podling website.
>
> I’m not sure I’m doing what you expected:
>
> A file is created with the directories you expect at 
> http://incubator.apache.org/retired/tamaya/project.txt

There is no need for a file. However AIUI Git does not support empty
directories in checkouts.
It might be better to create an empty index.html file instead.

> The source is here: 
> https://github.com/apache/incubator/blob/master/assets/retired/tamaya/project.txt
>
> However I’m not seeing the redirect.

There was a missing path segment in the directory check, so the server
was not finding the directory.
This has now been fixed, and http://tamaya.apache.org/ does redirect.
(You may need to clear the b

Re: Redirecting retired podling websites

[sebb]

On Sun, 4 Apr 2021 at 12:47, sebb  wrote:
>
> On Sun, 4 Apr 2021 at 01:31, Dave Fisher  wrote:
> >
> >
> >
> > > On Apr 3, 2021, at 4:49 PM, sebb  wrote:
> > >
> > > On Sat, 3 Apr 2021 at 23:43, Dave Fisher  wrote:
> > >>
> > >>
> > >>
> > >>> On Apr 3, 2021, at 3:38 PM, sebb  wrote:
> > >>>
> > >>> On Wed, 31 Mar 2021 at 22:28, sebb  wrote:
> > >>>>
> > >>>> On Wed, 31 Mar 2021 at 17:48, Dave Fisher  wrote:
> > >>>>>
> > >>>>> Hi Sebb,
> > >>>>>
> > >>>>> I noticed you did a lot of updates to .htaccess [1] - I have some 
> > >>>>> inline questions.
> > >>>>>
> > >>>>>> On Mar 30, 2021, at 4:31 PM, Dave Fisher  wrote:
> > >>>>>>
> > >>>>>> Hi Sebb,
> > >>>>>>
> > >>>>>>> On Mar 30, 2021, at 4:22 PM, sebb  wrote:
> > >>>>>>>
> > >>>>>>> It's currently quite awkward fixing up retired podling websites so
> > >>>>>>> they redirect to the status page.
> > >>>>>>> There are currently about 6 such podlings, dating back to Nov 2013.
> > >>>>>>>
> > >>>>>>> [It's easy enough to do this for incubator sub-sites (e.g.
> > >>>>>>> http://incubator.apache.org/wave), as these can use a single 
> > >>>>>>> .htaccess
> > >>>>>>> file; that is not the case for the above sites otherwise they would
> > >>>>>>> have been fixed ages ago]
> > >>>>>>>
> > >>>>>>> Recent podlings use websites like http://ariatosca.apache.org/ 
> > >>>>>>> and/or
> > >>>>>>> http://ariatosca.incubator.apache.org/
> > >>>>>>> The redirects need to be added in each website source.
> > >>>>>>>
> > >>>>>>> This can be difficult to do, see INFRA-21451 re Tamaya.
> > >>>>>>> This was opened on Feb 21st and has yet to be completed.
> > >>>>>>>
> > >>>>>>> I have proposed an Infra PR which should make it much easier to set 
> > >>>>>>> up
> > >>>>>>> the redirect to the status file.
> > >>>>>>>
> > >>>>>>> The idea is to set up a special directory:
> > >>>>>>> http://incubator.apache.org/retired/
> > >>>>>>>
> > >>>>>>> For each retired podling, create a marker directory, e.g.
> > >>>>>>> tamaya/
> > >>>>>>
> > >>>>>> I can add a step in the clutch2.sh shell script to maintain these 
> > >>>>>> placeholders.
> > >>>>>
> > >>>>> Do you still need retired/${podling} marker directories?
> > >>>>
> > >>>> Not yet.
> > >>>>
> > >>>> Infra have not yet applied the PR, so the marker directories won't
> > >>>> have any effect yet.
> > >>>
> > >>> The PR has now been applied.
> > >>
> > >> So, please review https://incubator.apache.org/podlings_retired.txt
> > >
> > > No idea what that file has to do with this thread, or what you expect
> > > me to review.
> > >
> > >> If create a retired/$col1 directory on the website the trouble will 
> > >> resolve?
> > >
> > > Try creating retired/tamaya/ and see what happens to 
> > > http://tamaya.apache.org/
> > > It should redirect to http://incubator.apache.org/projects/tamaya.html
> > >
> > > N.B. this only needs to be done for retired podlings whose URLs don't
> > > already redirect.
> > >
> > > There are only about 6 of those, see:
> > > https://issues.apache.org/jira/browse/INCUBATOR-262
> > >
> > >> I want to make sure I'm picking the podling attribute you expect.
> > >
> > > The directory name under retired/ must be the same as the unqualified
> > > host name for the podling website.
> >
> > I’m not sure I’m doing what you expected:
> >
> > A file is created wit

Re: Redirecting retired podling websites

[sebb]

On Sun, 4 Apr 2021 at 13:04, sebb  wrote:
>
> On Sun, 4 Apr 2021 at 12:47, sebb  wrote:
> >
> > On Sun, 4 Apr 2021 at 01:31, Dave Fisher  wrote:
> > >
> > >
> > >
> > > > On Apr 3, 2021, at 4:49 PM, sebb  wrote:
> > > >
> > > > On Sat, 3 Apr 2021 at 23:43, Dave Fisher  wrote:
> > > >>
> > > >>
> > > >>
> > > >>> On Apr 3, 2021, at 3:38 PM, sebb  wrote:
> > > >>>
> > > >>> On Wed, 31 Mar 2021 at 22:28, sebb  wrote:
> > > >>>>
> > > >>>> On Wed, 31 Mar 2021 at 17:48, Dave Fisher  wrote:
> > > >>>>>
> > > >>>>> Hi Sebb,
> > > >>>>>
> > > >>>>> I noticed you did a lot of updates to .htaccess [1] - I have some 
> > > >>>>> inline questions.
> > > >>>>>
> > > >>>>>> On Mar 30, 2021, at 4:31 PM, Dave Fisher  wrote:
> > > >>>>>>
> > > >>>>>> Hi Sebb,
> > > >>>>>>
> > > >>>>>>> On Mar 30, 2021, at 4:22 PM, sebb  wrote:
> > > >>>>>>>
> > > >>>>>>> It's currently quite awkward fixing up retired podling websites 
> > > >>>>>>> so
> > > >>>>>>> they redirect to the status page.
> > > >>>>>>> There are currently about 6 such podlings, dating back to Nov 
> > > >>>>>>> 2013.
> > > >>>>>>>
> > > >>>>>>> [It's easy enough to do this for incubator sub-sites (e.g.
> > > >>>>>>> http://incubator.apache.org/wave), as these can use a single 
> > > >>>>>>> .htaccess
> > > >>>>>>> file; that is not the case for the above sites otherwise they 
> > > >>>>>>> would
> > > >>>>>>> have been fixed ages ago]
> > > >>>>>>>
> > > >>>>>>> Recent podlings use websites like http://ariatosca.apache.org/ 
> > > >>>>>>> and/or
> > > >>>>>>> http://ariatosca.incubator.apache.org/
> > > >>>>>>> The redirects need to be added in each website source.
> > > >>>>>>>
> > > >>>>>>> This can be difficult to do, see INFRA-21451 re Tamaya.
> > > >>>>>>> This was opened on Feb 21st and has yet to be completed.
> > > >>>>>>>
> > > >>>>>>> I have proposed an Infra PR which should make it much easier to 
> > > >>>>>>> set up
> > > >>>>>>> the redirect to the status file.
> > > >>>>>>>
> > > >>>>>>> The idea is to set up a special directory:
> > > >>>>>>> http://incubator.apache.org/retired/
> > > >>>>>>>
> > > >>>>>>> For each retired podling, create a marker directory, e.g.
> > > >>>>>>> tamaya/
> > > >>>>>>
> > > >>>>>> I can add a step in the clutch2.sh shell script to maintain these 
> > > >>>>>> placeholders.
> > > >>>>>
> > > >>>>> Do you still need retired/${podling} marker directories?
> > > >>>>
> > > >>>> Not yet.
> > > >>>>
> > > >>>> Infra have not yet applied the PR, so the marker directories won't
> > > >>>> have any effect yet.
> > > >>>
> > > >>> The PR has now been applied.
> > > >>
> > > >> So, please review https://incubator.apache.org/podlings_retired.txt
> > > >
> > > > No idea what that file has to do with this thread, or what you expect
> > > > me to review.
> > > >
> > > >> If create a retired/$col1 directory on the website the trouble will 
> > > >> resolve?
> > > >
> > > > Try creating retired/tamaya/ and see what happens to 
> > > > http://tamaya.apache.org/
> > > > It should redirect to http://incubator.apache.org/projects/tamaya.html
> > > >
> > > >

Re: [ANNOUNCE] Apache Pinot (incubating) 0.7.1 released

[sebb]

Well done releasing another version.

However, the announce email does not have an incubator disclaimer, nor
does the website.

As far as I am aware, such disclaimers are required for Incubating projects.

On Wed, 14 Apr 2021 at 09:13, Fu Xiang  wrote:
>
> Hello Community,
>
> We are pleased to announce that Apache Pinot (incubating) 0.7.1 is released!
>
> Apache Pinot (incubating) is a distributed columnar storage engine that can
> ingest data in real-time and serve analytical queries at low latency.
>
> The release can be downloaded at https://pinot.apache.org/download
>
> The release note is available at
> https://docs.pinot.apache.org/basics/releases/0.7.1
>
> Additional resources -
> Project website: https://pinot.apache.org
> Getting started: https://docs.pinot.apache.org/getting-started
> Pinot developer blogs: https://medium.com/apache-pinot-developer-blog
> Intro to Pinot Video: https://www.youtube.com/watch?v=T70jTTYhYyM
>
> Join Pinot Community -
> Twitter: https://twitter.com/ApachePinot
> Meetup: https://www.meetup.com/apache-pinot/
> Slack channel: https://communityinviter.com/apps/apache-pinot/apache-pinot
> Pinot Dev Mailing-list: d...@pinot.apache.org
> 
>
> Best Regards,
>
> Apache Pinot (incubating) Team

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

Re: [DISCUSS] YunionCloud Proposal

[sebb]

Although there are no matches for UnioneCloud, there is a match for UnionCloud.

Their owner might consider UnioneCloud to be confusingly similar.
And future searchers for UnioneCloud may be directed to UnionCloud.

S.

On Wed, 14 Apr 2021 at 13:22, Jian Qiu  wrote:
>
> Hi, Daniel,
>
> UnioneCloud = UniOneCloud, stands for  'Unify multiclouds into One Cloud'
>
>
> Daniel Gruno  于2021年4月14日周三 下午7:49写道：
>
> > On 14/04/2021 09.06, Jian Qiu wrote:
> > > Hi, Dave,
> > >
> > > When we decide to donate project to Apache Incubator, we consider several
> > > candidate names and make a vote in our community, the results are
> > > as follows:
> > >
> > > * YunionCloud - a cloud union of Clouds, 26 vote
> > > * UnioneCloud - to unify many clouds into One Cloud, 10 vote
> > > * OpenYunion -  open source Cloud Union, 5 vote
> > > * OpenMHCP - open source Multi/Hybrid Cloud Platform, 2 vote
> > >
> > > So we decided to choose YunionCloud as the new name. But we did not
> > > realize it conflicted with our company domain name.
> > >
> > > As you suggested, we would like to consider UnioneCloud as the project
> > name.
> > >
> > > Would you consider UnioneCloud an appropriate project name?
> >
> > What does the E in UnioneCloud signify? I must confess I find it
> > distracting that there is what appears to the average reader as a typo,
> > but if there is a reason you did not pick UnionCloud, I'd be happy to
> > hear it :)
> >
> > >
> > > Many thanks,
> > >
> > > Jian Qiu
> > >
> > > Willem Jiang  于2021年4月14日周三 上午9:47写道：
> > >
> > >> Hi Dave,
> > >>
> > >> I understand your concern. Actually,  I had a long discussion with the
> > >> team about the project name, but I missed that the company's domain
> > >> name has a close relationship with the project name.
> > >> Now the development team is working on finding a new name for it.  We
> > >> will come back with a new project name for this proposal.
> > >>
> > >> Regards,
> > >>
> > >> Willem Jiang
> > >>
> > >> Twitter: willemjiang
> > >> Weibo: 姜宁willem
> > >>
> > >> On Tue, Apr 13, 2021 at 1:26 PM Dave Fisher  wrote:
> > >>>
> > >>> This looks like an interesting project.
> > >>>
> > >>> My concern is that the donation comes from https://www.yunion.cn which
> > >> has a similar name to the podling and that might cause trademark
> > confusion.
> > >>>
> > >>> Regards,
> > >>> Dave
> > >>>
> >  On Apr 11, 2021, at 9:40 PM, Jian Qiu  wrote:
> > 
> >  Dear all,
> > 
> >  We would like to propose YunionCloud as a new Apache Incubator
> > project.
> > 
> >  YunionCloud is a unified multi-cloud/hybrid-cloud management platform.
> > >> It
> >  is an IaaS platform capable of managing on-premise resources,
> > including
> >  virtual machines and BareMetals. Further, it is extended to manage
> >  resources from other cloud platforms, including public and private
> > >> cloud
> >  providers. It provides consistent APIs and Web UI to access
> > >> heterogeneous
> >  resources from multi-cloud/hybrid-cloud. The platform is implemented
> > in
> >  Golang, portable and lightweight, and can be deployed in Kubernetes
> >  clusters.
> > 
> >  The proposal can be found at
> > 
> > >>
> > https://cwiki.apache.org/confluence/display/INCUBATOR/YunionCloud++Proposal
> > 
> >  The project has been open-sourced since March 2019 at GitHub
> >  https://github.com/yunionio/yunioncloud
> > 
> >  The project used to be called OneCloud, but we are in the process of
> >  changing the name to YunionCloud to avoid potential trademark
> > >> conflicts.
> > 
> >  Many thanks to Willem Jiang as our champion and mentor to guide us to
> > >> set
> >  up this proposal. We still need 2-3 mentors to set us on the track. If
> > >> you
> >  are interested, please kindly let me know. Besides, we are eager to
> > >> hear
> >  any of your thoughts on this project.
> > 
> >  Looking forward to your feedback and thank you for your time.
> > 
> >  Best regards,
> > 
> >  Jian Qiu, Co-found of YunionCloud
> >  sword...@gmail.com
> > >>>
> > >>>
> > >>> -
> > >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > >>> For additional commands, e-mail: general-h...@incubator.apache.org
> > >>>
> > >>
> > >> -
> > >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > >> For additional commands, e-mail: general-h...@incubator.apache.org
> > >>
> > >>
> > >
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For add

Re: [MENTORS] Old releases in release area

[sebb]

Also please ensure the podling release process documentation mentions
the need to remove old releases.

This is best done shortly after announcing a new release, as by then
the latest release should be on the mirrors.

See also
 http://www.apache.org/dev/release.html#when-to-archive

Thanks!

On Tue, 27 Apr 2021 at 06:46, Antoine Toulme  wrote:
>
> Very good point, thank you. I will make sure.
>
> > On Apr 26, 2021, at 10:45 PM, Justin Mclean  
> > wrote:
> >
> > Hi,
> >
> >> Sure, just delete the old bits? I will do that for Tuweni.
> >
> > You might want to double check that your projects download page isn’t 
> > linking to them. If it is you can change the links of old versions to point 
> > to the archive, but please keep the latest release going via the mirror 
> > system.
> >
> > Thanks,
> > Justin
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

What happened to TubeMQ?

[sebb]

TubeMQ decided to rename itself to InLong in mid April.

It looks like this took place on the private@ list only, which seems a bit odd.
I could find no mention on the dev@ list, nor on general@incubator

Also the Incubator resources have not been updated (podlings.xml and
the status file).

Sebb.

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

Re: What happened to TubeMQ?

[sebb]

On Thu, 13 May 2021 at 02:39, Goson zhang  wrote:
>
> Hi  Sebb:
>
> We are making adjustments to the renaming project, The new homepage is now
> online, next, we'll adjust the code content and related documents.

Note that Whimsy won't work properly until podlings.xml is fixed.
Ideally this should be done at the same time as the renames of LDAP groups etc.

> Thanks!
>
> Justin Mclean  于2021年5月13日周四 上午6:46写道：
>
> > Hi,
> >
> > > It looks like this took place on the private@ list only, which seems a
> > bit odd.
> > > I could find no mention on the dev@ list, nor on general@incubator
> >
> > There were long discussions on it in public on JIRA and trademarks were
> > involved.
> >
> > > Also the Incubator resources have not been updated (podlings.xml and
> > > the status file).
> >
> > They are still in the process of updating everything, renaming takes a lot
> > of work.
> >
> > Thanks,
> > Justin
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >

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

Re: What happened to TubeMQ?

[sebb]

The Git repo description can be changed in .asf.yaml

On Thu, 13 May 2021 at 14:17, John D. Ament  wrote:
>
> Hi Goson
>
> So there's a comment from Gav [1] about remaining steps you need to do (and 
> hence why I think we need a guide).  Your .asf.yml files need to be updated.  
> You (or one of your mentors) needs to update podlings.xml as well.  I would 
> also reach out to infra because your github repos still say Apache TubeMQ 
> instead of Apache InLong (in the description).
>
>
> [1]: 
> https://issues.apache.org/jira/browse/INFRA-21558?focusedCommentId=17318466&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17318466
>
> On Thu, May 13, 2021 at 8:18 AM Goson zhang  wrote:
>>
>> Hi John:
>>
>> We have already submitted the rename issue [1] before. Since the other 
>> modules of the project are still in the adjustment process and have not been 
>> prepared, we did not send out the rename notice email.
>>
>> We don’t know how wide the coverage is, so we can only submit a help request 
>> on the infra[2] once encounting one problem
>>
>> For this problem How to deal  it properly? Send an email to inform about the 
>> rename event, or submit an issue in the infra first?
>>
>> 1. 
>> https://issues.apache.org/jira/projects/INFRA/issues/INFRA-21558?filter=doneissues
>> 2. 
>> https://issues.apache.org/jira/projects/INFRA/issues/INFRA-21881?filter=allopenissues
>>
>> John D. Ament  于2021年5月13日周四 下午7:30写道：
>>>
>>>
>>>
>>> On Thu, May 13, 2021 at 07:12 Goson zhang  wrote:
>>>>
>>>> Hi Sebb
>>>>
>>>> How should we fix it?
>>>>
>>>> I did not pay attention to the issue, maybe we missed some items that must
>>>> be adjusted
>>>
>>>
>>>
>>>
>>> I might be missing official sources [1] but after you vote the name it 
>>> should be made aware to the IPMC (I would assume via general@) and then 
>>> request infra to rename your resources.  This would require you to rename 
>>> the podling in podlings.xml.
>>>
>>> It’s not often that we have this scenario but perhaps we should get it on 
>>> the guide.
>>>
>>> [1]:
>>> https://www.mail-archive.com/general@incubator.apache.org/msg73559.html
>>>
>>>>
>>>> Thanks!
>>>>
>>>> sebb  于2021年5月13日周四 下午7:05写道：
>>>>
>>>> > On Thu, 13 May 2021 at 02:39, Goson zhang  wrote:
>>>> > >
>>>> > > Hi  Sebb:
>>>> > >
>>>> > > We are making adjustments to the renaming project, The new homepage is
>>>> > now
>>>> > > online, next, we'll adjust the code content and related documents.
>>>> >
>>>> > Note that Whimsy won't work properly until podlings.xml is fixed.
>>>> > Ideally this should be done at the same time as the renames of LDAP 
>>>> > groups
>>>> > etc.
>>>> >
>>>> > > Thanks!
>>>> > >
>>>> > > Justin Mclean  于2021年5月13日周四 上午6:46写道：
>>>> > >
>>>> > > > Hi,
>>>> > > >
>>>> > > > > It looks like this took place on the private@ list only, which
>>>> > seems a
>>>> > > > bit odd.
>>>> > > > > I could find no mention on the dev@ list, nor on general@incubator
>>>> > > >
>>>> > > > There were long discussions on it in public on JIRA and trademarks 
>>>> > > > were
>>>> > > > involved.
>>>> > > >
>>>> > > > > Also the Incubator resources have not been updated (podlings.xml 
>>>> > > > > and
>>>> > > > > the status file).
>>>> > > >
>>>> > > > They are still in the process of updating everything, renaming takes 
>>>> > > > a
>>>> > lot
>>>> > > > of work.
>>>> > > >
>>>> > > > Thanks,
>>>> > > > Justin
>>>> > > > -
>>>> > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>>> > > > For additional commands, e-mail: general-h...@incubator.apache.org
>>>> > > >
>>>> > > >
>>>> >

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

Re: What happened to TubeMQ?

[sebb]

On Thu, 13 May 2021 at 12:30, John D. Ament  wrote:
>
> On Thu, May 13, 2021 at 07:12 Goson zhang  wrote:
>
> > Hi Sebb
> >
> > How should we fix it?
> >
> > I did not pay attention to the issue, maybe we missed some items that must
> > be adjusted
> >
>
>
>
> I might be missing official sources [1] but after you vote the name it
> should be made aware to the IPMC (I would assume via general@) and then
> request infra to rename your resources.  This would require you to rename
> the podling in podlings.xml.

As soon as the name change was agreed, I would have expected an email
to be sent to all the podling mailing lists.

Also for future reference: discussions and votes should be held on
public mailing lists.

Private mailing lists should only be used when it is essential.
For example, when discussing security issues and personnel (invites etc).

> It’s not often that we have this scenario but perhaps we should get it on
> the guide.
>
> [1]:
> https://www.mail-archive.com/general@incubator.apache.org/msg73559.html
>
>
> > Thanks!
> >
> > sebb  于2021年5月13日周四 下午7:05写道：
> >
> > > On Thu, 13 May 2021 at 02:39, Goson zhang  wrote:
> > > >
> > > > Hi  Sebb:
> > > >
> > > > We are making adjustments to the renaming project, The new homepage is
> > > now
> > > > online, next, we'll adjust the code content and related documents.
> > >
> > > Note that Whimsy won't work properly until podlings.xml is fixed.
> > > Ideally this should be done at the same time as the renames of LDAP
> > groups
> > > etc.
> > >
> > > > Thanks!
> > > >
> > > > Justin Mclean  于2021年5月13日周四 上午6:46写道：
> > > >
> > > > > Hi,
> > > > >
> > > > > > It looks like this took place on the private@ list only, which
> > > seems a
> > > > > bit odd.
> > > > > > I could find no mention on the dev@ list, nor on general@incubator
> > > > >
> > > > > There were long discussions on it in public on JIRA and trademarks
> > were
> > > > > involved.
> > > > >
> > > > > > Also the Incubator resources have not been updated (podlings.xml
> > and
> > > > > > the status file).
> > > > >
> > > > > They are still in the process of updating everything, renaming takes
> > a
> > > lot
> > > > > of work.
> > > > >
> > > > > Thanks,
> > > > > Justin
> > > > > -
> > > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > > For additional commands, e-mail: general-h...@incubator.apache.org
> > > > >
> > > > >
> > >
> >

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

Re: [MENTORS] Old releases in release area

[sebb]

On Mon, 3 May 2021 at 19:24, Nikita Ivanov  wrote:
>
> NLPCraft is cleaned up.

However the download page has not been updated, so the hash links are broken.
Please remove the outdated releases from the download page.
They can remain on the page if necessary, but it should be clear that
they are old releases, and the links must point to archive.apache.org.

> --
> On behalf of NLPCraft community,
> Nikita Ivanov
>
>
>
> On Sun, May 2, 2021 at 5:43 PM Justin Mclean 
> wrote:
>
> > Hi,
> >
> > Thanks to those who all responded and cleaned up their repo areas.
> >
> > Still to go are:
> > Crail [1]
> > DataLab [2]
> > Livy [3]
> > Milagro [4]
> > MXnet [5]
> > Nemo [6]
> > NLPCraft [7]
> > Pinot [8]
> >
> > Thanks,
> > Justin
> >
> >
> > 1. https://dist.apache.org/repos/dist/release/incubator/crail/ <
> > https://dist.apache.org/repos/dist/release/incubator/crail/>
> > 2. https://dist.apache.org/repos/dist/release/incubator/datalab/ <
> > https://dist.apache.org/repos/dist/release/incubator/datalab/>
> > 3. https://dist.apache.org/repos/dist/release/incubator/livy/ <
> > https://dist.apache.org/repos/dist/release/incubator/livy/>
> > 4. https://dist.apache.org/repos/dist/release/incubator/milagro/ <
> > https://dist.apache.org/repos/dist/release/incubator/milagro/>
> > 5. https://dist.apache.org/repos/dist/release/incubator/mxnet/ <
> > https://dist.apache.org/repos/dist/release/incubator/mxnet/>
> > 6 https://dist.apache.org/repos/dist/release/incubator/nemo/ <
> > https://dist.apache.org/repos/dist/release/incubator/nemo/>
> > 7. https://dist.apache.org/repos/dist/release/incubator/nlpcraft/nlpcraft/
> > 
> > 8. https://dist.apache.org/repos/dist/release/incubator/pinot/ <
> > https://dist.apache.org/repos/dist/release/incubator/pinot/>
> >
> >

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

Re: [MENTORS] Old releases in release area

[sebb]

On Tue, 25 May 2021 at 11:47, sebb  wrote:
>
> On Mon, 3 May 2021 at 19:24, Nikita Ivanov  wrote:
> >
> > NLPCraft is cleaned up.
>
> However the download page has not been updated, so the hash links are broken.
> Please remove the outdated releases from the download page.
> They can remain on the page if necessary, but it should be clear that
> they are old releases, and the links must point to archive.apache.org.
>

Also I just noticed that the link text does not quite agree with the
artifact file name.
For example, the link with the title:
apache-nlpcraft-0.7.5.zip
points to the artifact
apache-nlpcraft-incubating-0.7.5.zip

The text should be changed to agree with the artifact name to avoid
causing any confusion.

> > --
> > On behalf of NLPCraft community,
> > Nikita Ivanov
> >
> >
> >
> > On Sun, May 2, 2021 at 5:43 PM Justin Mclean 
> > wrote:
> >
> > > Hi,
> > >
> > > Thanks to those who all responded and cleaned up their repo areas.
> > >
> > > Still to go are:
> > > Crail [1]
> > > DataLab [2]
> > > Livy [3]
> > > Milagro [4]
> > > MXnet [5]
> > > Nemo [6]
> > > NLPCraft [7]
> > > Pinot [8]
> > >
> > > Thanks,
> > > Justin
> > >
> > >
> > > 1. https://dist.apache.org/repos/dist/release/incubator/crail/ <
> > > https://dist.apache.org/repos/dist/release/incubator/crail/>
> > > 2. https://dist.apache.org/repos/dist/release/incubator/datalab/ <
> > > https://dist.apache.org/repos/dist/release/incubator/datalab/>
> > > 3. https://dist.apache.org/repos/dist/release/incubator/livy/ <
> > > https://dist.apache.org/repos/dist/release/incubator/livy/>
> > > 4. https://dist.apache.org/repos/dist/release/incubator/milagro/ <
> > > https://dist.apache.org/repos/dist/release/incubator/milagro/>
> > > 5. https://dist.apache.org/repos/dist/release/incubator/mxnet/ <
> > > https://dist.apache.org/repos/dist/release/incubator/mxnet/>
> > > 6 https://dist.apache.org/repos/dist/release/incubator/nemo/ <
> > > https://dist.apache.org/repos/dist/release/incubator/nemo/>
> > > 7. https://dist.apache.org/repos/dist/release/incubator/nlpcraft/nlpcraft/
> > > <https://dist.apache.org/repos/dist/release/incubator/nlpcraft/nlpcraft/>
> > > 8. https://dist.apache.org/repos/dist/release/incubator/pinot/ <
> > > https://dist.apache.org/repos/dist/release/incubator/pinot/>
> > >
> > >

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

Retirement info does not mention LDAP

[sebb]

The retirement page [1] does not mention needing to ask Infra to
remove the LDAP project.


[1] http://incubator.apache.org/guides/retirement.html#steps_to_retirement

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

Re: Retirement info does not mention LDAP

[sebb]

Also, I think the bit about the .htaccess file is no longer accurate.

There's a new way to do this; not sure where (or if) it is documented.

On Thu, 3 Jun 2021 at 15:35, sebb  wrote:
>
> The retirement page [1] does not mention needing to ask Infra to
> remove the LDAP project.
>
>
> [1] http://incubator.apache.org/guides/retirement.html#steps_to_retirement

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

Re: Retirement info does not mention LDAP

[sebb]

Sorry, don't have time at present, otherwise I would have done so.

On Thu, 3 Jun 2021 at 15:50, Dave Fisher  wrote:
>
> Sebb,
>
> Please feel free to submit a PR, or suggested fix.
>
> Regards,
> Dave
>
> Sent from my iPhone
>
> > On Jun 3, 2021, at 7:40 AM, sebb  wrote:
> >
> > Also, I think the bit about the .htaccess file is no longer accurate.
> >
> > There's a new way to do this; not sure where (or if) it is documented.
> >
> >> On Thu, 3 Jun 2021 at 15:35, sebb  wrote:
> >>
> >> The retirement page [1] does not mention needing to ask Infra to
> >> remove the LDAP project.
> >>
> >>
> >> [1] http://incubator.apache.org/guides/retirement.html#steps_to_retirement
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

Re: Turn on GitHub Issues on apache/incubator

[sebb]

What about JIRA?

Will that still be kept?

If so, does it matter which issue reporting system is used?

Seems to me that if both are in use, that may cause confusion, and may
increase the workload.

On Thu, 3 Jun 2021 at 23:30, Christopher  wrote:
>
> Ideally, the GitHub traffic would go to a separate list... yes?
>
> On Thu, Jun 3, 2021 at 12:42 PM Julian Hyde  wrote:
> >
> > How much will this increase the email traffic?
> >
> > > On Jun 3, 2021, at 9:39 AM, Dave Fisher  wrote:
> > >
> > > Unless there is an objection I will turn on GitHub Issues on 
> > > https://github.com/apache/incubator next Monday.
> > >
> > > I’ll also set notifications so that PRs and issues are sent to 
> > > general@i.a.o
> > >
> > > See 
> > > https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features
> > >
> > > This will make it easier to track observations like sebb’s on the 
> > > retirement page.
> > >
> > > Regards,
> > > Dave
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

Re: Retirement info does not mention LDAP

[sebb]

On Sat, 5 Jun 2021 at 01:42, Willem Jiang  wrote:
>
> Hi sebb,
>
> I just want to know if we can still access the retired project website
> if the LDAP is removed.
> Currently I just found a bug in the retirement guide[1]
> If we put the repo into the archive, we cannot add the .htacess file
> into the archive repo any more.

You don't need to update the podling website any more.

That is another omission in the guide.

Just create the appropriate directory under
https://github.com/apache/incubator/tree/master/assets/retired
Remember to add an empty index.html file to it.

The web server that hosts all the podling websites checks for a
directory matching the host name, and redirects to the podling status
file if it is present.

> [1]https://issues.apache.org/jira/browse/INFRA-21960
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Thu, Jun 3, 2021 at 10:40 PM sebb  wrote:
> >
> > Also, I think the bit about the .htaccess file is no longer accurate.
> >
> > There's a new way to do this; not sure where (or if) it is documented.
> >
> > On Thu, 3 Jun 2021 at 15:35, sebb  wrote:
> > >
> > > The retirement page [1] does not mention needing to ask Infra to
> > > remove the LDAP project.
> > >
> > >
> > > [1] http://incubator.apache.org/guides/retirement.html#steps_to_retirement
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

Re: Weex project is retired

[sebb]

On Mon, 7 Jun 2021 at 10:31, Willem Jiang  wrote:
>
> Now the Infra options about the Weex retirement are all done.
> Please check out this issue[1] for more information.
> [1] https://issues.apache.org/jira/browse/INFRA-21917

However the weex LDAP project still exists [2]; it seems that step was
omitted from the JIRA issue.

[2] https://whimsy.apache.org/roster/other/

> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

Re: [ANNOUNCE] Release Apache Pegasus (incubating) 2.2.0

[sebb]

On Mon, 28 Jun 2021 at 09:02, Yingchun Lai  wrote:
>
> Hi, all,
>
> We are glad to announce the release of Apache Pegasus (incubating) 2.2.0.

Congrats on the release.

> Pegasus (https://pegasus.apache.org/en/) is a distributed key-value
> storage system that is designed to be simple, horizontally scalable,
> strongly consistent, and high-performance.
>
> The vote thread:
> https://lists.apache.org/thread.html/r5f045c9f82e67c01bc23504b66960fb07afdd72875b8e1c808a05e31%40%3Cdev.pegasus.apache.org%3EVote
> https://lists.apache.org/thread.html/r0202c80ef2ca2f7527cc95c7d783f9d8c75a78c377527f33cf4f0c72%40%3Cgeneral.incubator.apache.org%3E

IMO the VOTE threads are not appropriate for announce emails; they are
really only of interest to the developers producing the release.
I suggest they are dropped from future announce emails sent outside the project.

> The release can be downloaded at: 
> https://pegasus.apache.org/en/docs/downloads/

There are also some problems with the download page:
- no link to KEYS file
- no info on the need to verify downloads, nor how to do so.

Also download pages intended for the general public should not link
directly to the source code repo.
Such links should be reserved for developer pages.
Download pages must only link to source which has been formally released.

> The release note is available at:
> https://cwiki.apache.org/confluence/display/PEGASUS/Apache+Pegasus+2.2.0+Release+Notes
>
> Thanks to everyone involved!
>
> Apache Pegasus (incubating) community
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

Re: [ANNOUNCE] Release Apache EventMesh(incubating) 1.2.0

[sebb]

On Thu, 8 Jul 2021 at 13:49, mikexue  wrote:
>
> Hi all,
>
> The Apache EventMesh team would like to announce the release of Apache
> Mesh(incubating) 1.2.0.
>
> Brief features of this release:
> 1.Support rocketmq as store
> 2.Support Spi for extended implementation to accommodate a variety of 
> eventstore
> 3.Support http pub/sub ,heartbeat manage and subscribe manage
> 4.Support running eventmesh in docker
>
> More details regarding Apache EventMesh can be found at:
> https://eventmesh.apache.org/
>
> The release artifacts can be downloaded here:
> https://dist.apache.org/repos/dist/release/incubator/eventmesh/1.2.0

Sorry, but that is not suitable as a download location.
The dist.apache.org server is only intended for release publication,
not public downloads.

> The release notes can be found here:
> https://github.com/apache/incubator-eventmesh/releases/tag/v1.2.0
>
> Thanks,
> The Apache EventMesh Team
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

Re: [VOTE] Release Apache InLong 0.9.0-incubating RC1

[sebb]

The current release is 0.8.0, yet on the download page the links all
point to the archive server.

Current releases must use the ASF mirror system and the main ASF
server for the sigs and hashes.

This suggests that standard release practises are not being followed.

On Mon, 19 Jul 2021 at 03:50, Goson zhang  wrote:
>
> Hello Incubator Community,
>
> This is a call for a vote to release Apache InLong (Incubating) version
> 0.9.0-incubating RC1
>
> The Apache InLong community has voted on and approved a proposal to
> release
> Apache InLong (Incubating) version 0.9.0-incubating RC1
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> InLong community vote thread:
> •
> https://lists.apache.org/thread.html/r87faccf8c1ebe22c433bfcc43c17541fa81b7b7b6df9c393ed65460b%40%3Cdev.inlong.apache.org%3E
>
> Vote result thread:
> •
> https://lists.apache.org/thread.html/rb64923310d6d1a7ae0bbd4c89a4426ef032e936cc9330154526e72ad%40%3Cdev.inlong.apache.org%3E
>
> The release candidate:
> •
> https://dist.apache.org/repos/dist/dev/incubator/inlong/0.9.0-incubating-RC1
>
> Git tag for the release:
> • https://github.com/apache/incubator-inlong/tree/0.9.0-incubating-RC1
>
> Release notes:
> •
> https://github.com/apache/incubator-inlong/releases/tag/0.9.0-incubating-RC1
>
> The artifacts signed with PGP key
>  9B12C2228BDFF4F4CFE849445EF3A66D57EC647A, corresponding to
> gxch...@apache.org, that can be found in keys file:
> • https://dist.apache.org/repos/dist/dev/incubator/inlong/KEYS
>
> The vote will be open for at least 72 hours or until a necessary number
> of votes are reached.
>
> Please vote accordingly:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Thanks,
> On behalf of Apache InLong (Incubating) community

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

Re: [ANNOUNCE] Release Apache InLong(incubating) 0.9.0-incubating

[sebb]

On Fri, 23 Jul 2021 at 08:36, Goson zhang  wrote:
>
> Hi all,
>
> The Apache InLong(incubating) community is pleased to announce that Apache
> InLong(incubating) 0.9.0-incubating has been released!
>
> Apache InLong is a one-stop data streaming platform that provides
> automatic, secure,
> distributed, and efficient data publishing and subscription capabilities.
> This platform helps you easily build stream-based data applications.
>
> Download Links:
> https://downloads.apache.org/incubator/inlong/0.9.0-incubating/

Sorry, but that is not a valid download link.
Downloads must only be advertised from a page that contains links to
the KEYS, sigs and hashes, as well as the artifacts themselves.

The website already has a download page:
https://inlong.apache.org/en-us/docs/download/download.html
However that page is missing a link to the KEYS file, and does not
explain the need to verify downloads, nor how to do so.
Please fix the page ASAP, and use it in future announce emails.

Thanks.
>
> Release Notes:
> https://github.com/apache/incubator-inlong/blob/release-0.9.0/CHANGES.md
>
> Website: https://inlong.apache.org/
>
> InLong Resources:
> - Issue: https://issues.apache.org/jira/projects/INLONG/issues
> - Mailing-list: d...@inlong.apache.org
>
> Thanks
> On behalf of Apache InLong(Incubating) community

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

Re: [ANNOUNCE] Release Apache InLong(incubating) 0.9.0-incubating

[sebb]

On Fri, 23 Jul 2021 at 15:17, Goson zhang  wrote:
>
> Hi @sebb  :
>
> I just now modified the download page and added a reminder for the Release
> Integrity check [1];

That looks find now, thanks for the prompt attention to it.

However, the Chinese version of the page has the verification
instructions in English.
It would be better if it were translated.

> at the same time, I modified the notification template
> of the version release[2]. There should be no such problems later.
>
> If we have any other questions, please let me know
>
> thanks!!
>
> 1. https://inlong.apache.org/en-us/docs/download/download.html
> 2. https://inlong.apache.org/en-us/docs/development/how-to-release.html
>
> Goson zhang  于2021年7月23日周五 下午8:50写道：
>
> > Ok, will do that.
> >
> > Thanks, @sebb , You mentioned a few areas that need to
> > be dealt with in standardized rules. We will learn from the practices of
> > our peers and make adjustments.
> >
> > sebb  于2021年7月23日周五 下午7:24写道：
> >
> >> On Fri, 23 Jul 2021 at 08:36, Goson zhang  wrote:
> >> >
> >> > Hi all,
> >> >
> >> > The Apache InLong(incubating) community is pleased to announce that
> >> Apache
> >> > InLong(incubating) 0.9.0-incubating has been released!
> >> >
> >> > Apache InLong is a one-stop data streaming platform that provides
> >> > automatic, secure,
> >> > distributed, and efficient data publishing and subscription
> >> capabilities.
> >> > This platform helps you easily build stream-based data applications.
> >> >
> >> > Download Links:
> >> > https://downloads.apache.org/incubator/inlong/0.9.0-incubating/
> >>
> >> Sorry, but that is not a valid download link.
> >> Downloads must only be advertised from a page that contains links to
> >> the KEYS, sigs and hashes, as well as the artifacts themselves.
> >>
> >> The website already has a download page:
> >> https://inlong.apache.org/en-us/docs/download/download.html
> >> However that page is missing a link to the KEYS file, and does not
> >> explain the need to verify downloads, nor how to do so.
> >> Please fix the page ASAP, and use it in future announce emails.
> >>
> >> Thanks.
> >> >
> >> > Release Notes:
> >> >
> >> https://github.com/apache/incubator-inlong/blob/release-0.9.0/CHANGES.md
> >> >
> >> > Website: https://inlong.apache.org/
> >> >
> >> > InLong Resources:
> >> > - Issue: https://issues.apache.org/jira/projects/INLONG/issues
> >> > - Mailing-list: d...@inlong.apache.org
> >> >
> >> > Thanks
> >> > On behalf of Apache InLong(Incubating) community
> >>
> >

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

Re: [ANNOUNCE] Apache Annotator (incubating) 0.2.0 release

[sebb]

On Fri, 3 Sept 2021 at 13:43, Gerben  wrote:
>
> Dear community,
>
> The Apache Annotator (incubating) community is pleased to announce the
> release of Apache Annotator (incubating) 0.2.0.
>
> Apache Annotator (incubating) provides libraries to enable annotation
> related software, with an initial focus on identification of textual
> fragments in browser environments.
>
> These are the main changes since v0.1.0:
>
> - all code is converted to TypeScript
> - the API is documented
> - many tests have been added
> - npm package names changed from “@annotator/…” to “@apache-annotator/…”
> - a meta-package was added that includes all the others in one package
> - it now supports TextPositionSelector
> - it now supports CssSelector in both directions (match & describe)
> - steps were made to apply text matching algorithms to other environments 
> than the DOM
> - and many small fixes, tweaks and improvements
>
> Download links:
> https://annotator.apache.org/

The KEYS link is broken.

> The release tag:
> https://github.com/apache/incubator-annotator/releases/tag/v0.2.0
>
> With regards on behalf of the team,
>
> — Gerben
>

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

Re: [ANNOUNCE] Apache Annotator (incubating) 0.2.0 release

[sebb]

https://annotator.apache.org/www.apache.org/dist/incubator/annotator/KEYS
is not a valid keys link.

Looks like someone omitted the 'https://' prefix.

Please fix.
On Sun, 5 Sept 2021 at 13:57, sebb  wrote:
>
> On Fri, 3 Sept 2021 at 13:43, Gerben  wrote:
> >
> > Dear community,
> >
> > The Apache Annotator (incubating) community is pleased to announce the
> > release of Apache Annotator (incubating) 0.2.0.
> >
> > Apache Annotator (incubating) provides libraries to enable annotation
> > related software, with an initial focus on identification of textual
> > fragments in browser environments.
> >
> > These are the main changes since v0.1.0:
> >
> > - all code is converted to TypeScript
> > - the API is documented
> > - many tests have been added
> > - npm package names changed from “@annotator/…” to “@apache-annotator/…”
> > - a meta-package was added that includes all the others in one package
> > - it now supports TextPositionSelector
> > - it now supports CssSelector in both directions (match & describe)
> > - steps were made to apply text matching algorithms to other environments 
> > than the DOM
> > - and many small fixes, tweaks and improvements
> >
> > Download links:
> > https://annotator.apache.org/
>
> The KEYS link is broken.
>
> > The release tag:
> > https://github.com/apache/incubator-annotator/releases/tag/v0.2.0
> >
> > With regards on behalf of the team,
> >
> > — Gerben
> >

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