Re: possible interest in forming a community fork of akka

[Apache]

No, fixes most definitely cannot be back ported. But someone can look at the 
code fix and describe in very general terms what the fix was and then someone 
else can implement it. But you cannot copy code and I wouldn’t even create 
psuedo code as doing that would almost certainly be copyright infringement.

Yes, it would be a lot of work, which is why I think it is important to ensure 
there is a strong community around doing this before doing much more of 
anything at the ASF.

Ralph

> On Sep 26, 2022, at 6:30 PM, Willem Jiang  wrote:
> 
> After going through the FAQ of the Akka license,   it looks like we
> cannot backport the BSL codes to the Apache License branch.
> 
>> If there is a newer version of the software under BSL, can I backport any of 
>> the code to an older, Open Source, version of Akka?
> 
>> No. In this circumstance, you would either violate Lightbend’s copyright by 
>> re-releasing the code under Open Source, or you would violate the earlier 
>> Akka version’s Apache license by introducing incompatible BSL code (i.e., 
>> code subject to a use limitation not allowed by the Open Source Apache 2.0 
>> license).
> 
> It will cause us a lot of effort to maintain the code, even if we just
> want to backport some critical bug fixes.
> 
> [1]https://www.lightbend.com/akka/license-faq
> 
> Willem Jiang
> 
> Twitter: willemjiang
> Weibo: 姜宁willem
> 
>> On Tue, Sep 27, 2022 at 6:25 AM Ralph Goers  
>> wrote:
>> 
>> Before going too far with this I would be interested to know:
>> 1. Who the initial committers/PMC members would be.
>> 2. How much familiarity the proposed people already have with the code base.
>> 3. How diverse the community is from an employment point of view.
>> 
>> In other words, I would be concerned if this is pushed by just 3 or 4 people,
>> none of which have ever spent much time in the code, and who all work for
>> the same employer.
>> 
>> Ralph
>> 
>>>> On Sep 26, 2022, at 11:11 AM, PJ Fanning  wrote:
>>> 
>>> Hi everyone,
>>> 
>>> Apologies if this is not the right mailing list. If it is not, please
>>> let me know and I'll switch the thread to the right list.
>>> 
>>> Lighbend [1], the company that maintains the popular open source
>>> framework, Akka [2], recently announced they are moving Akka to a
>>> non-OSS commercial license [3].
>>> 
>>> There is interest in the OSS community in forking Akka under a new
>>> name and maintaining it as an ASF project [4].
>>> 
>>> It is early days yet but there is some discussion online [5].
>>> 
>>> Reading the incubator cookbook, a new podling would need to have
>>> champions and mentors from within the Incubator PMC [6].
>>> 
>>> I would like to put my name forward for such a role, as an existing
>>> ASF member [7].
>>> 
>>> If anyone else in the Incubator PMC would like to get involved, that
>>> would be great.
>>> 
>>> Regards,
>>> PJ
>>> 
>>> [1] https://www.lightbend.com/
>>> [2] https://akka.io/
>>> [3] https://www.lightbend.com/akka/license-faq
>>> [4] https://github.com/mdedetrich/akka-apache-project
>>> [5] https://github.com/mdedetrich/akka-apache-project/discussions/9
>>> [6] 
>>> https://incubator.apache.org/cookbook/#does_our_project_fit_the_apache_incubator
>>> [7] https://whimsy.apache.org/roster/committer/fanningpj
>>> 
>>> -
>>> 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

Chunjun Proposal

[Apache]

Dear Apache Incubator Community, 
We propose to contribute Chunjun as an Apache Incubator project.
We are still looking for possible Champion and Mentors if anyone would like to 
volunteer. Thanks a lot.
Best Regards, 
Real-time computing engine team of DTStack.

#Chunjun Proposal

##Abstract
Chunjun is a distributed ETL tool and distributed data integration tool. 
Currently Chunjun is based on Apache Flink. It was initially known as FlinkX 
and renamed Chunjun on February 22, 2022.
- Chunjun codebase: https://github.com/DTStack/chunjun

##Proposal
We propose to contribute the Chunjun codebase to the Apache Software Foundation 
with the intent of forming a productive, meritocratic and open community around 
Chunjun’s continued development, according to the 'Apache Way'. The Chunjun's 
source code is already under the Apache License Version 2.0.

##Background
We developed Chunjun in DTStack company in 2017, when we needed a low-code 
development and high-performance data integration tool. It has been an 
open-source project on GitHub since April 2018. Chunjun is running in DTStack 
production environment all the time. Chunjun has also been widely used by 
companies in China, including DTStack (https://www.dtstack.com/), 
Qihu360(https://www.360.cn/), Iflytek (https://www.iflytek.com/), XPeng Motors 
(https://en.xiaopeng.com/), WeBank (https://www.webank.com/), 
Asiainfo(https://asiainfo.com/), Guazi(https://www.guazi.com/), Hello Inc 
(https://www.hello-inc.com/), etc.  Nowadays, Chunjun has a strong community in 
China. 

##Rationale
High-performance of Chunjun is based on Apache Flink, and Chunjun can integrate 
data from different data source. Users only need to configure a JSON file to 
complete the data reading, transformer, and writing. Users can implement new 
reader/writer plugins to meet their requirements. Chunjun have implemented 
plugins that can capture data change for MySQL to restore data for Apache Doris.
Chunjun has the following feature: 
real-time and offline integrate data from different data sources. 
change data capture(CDC) to merge restore data.
resume from broken-point.
capture and collect dirty data.
limit data transferring rate.
thoughput metrics.
capture and restore schema evolution. (TODO)

##Current Status###Meritocracy
Since Chunjun was open-sourced, many enterprises have adopted Chunjun to build 
up their data integration system. In return, we have received many issue 
reports or enhancements from them simultaneously. The codebase is now mainly 
managed by the development team inside DTStack who's responsible for building 
internal data integration system too.###Community
Chunjun has been building a community around contributors and users to this 
framework for the last five years. We organized one meetup in 2020. Currently, 
we communicate in Github issues and in chinese DingTalk group. There are about 
3000 people in this group. And we believe that we can get a lot of help from 
the Apache Flink community too. We will organize a meetup again in 2022.###Core 
Developers
(In alphabetical order) 
Chao Xu (https://github.com/zoudaokoulife)
Gongjiang Tang, (https://github.com/kyo-tom)
Huai Yang, (https://github.com/yanghuaiGit)
Jiangbo Li, (https://github.com/lijiangbo)
Luning Wong, (https://github.com/deadwind4)
Luo Li, (https://github.com/kanata163)
Sishu Yang, (https://github.com/yangsishu) 
Tianzhu Wen, (https://github.com/WTZ468071157)
Weiliang Hao, (https://github.com/xiuzhu9527)
Wenqiang Liu, (https://github.com/meng1222)
Xing Liu, (https://github.com/simenliuxing)
Yang Lan, (https://github.com/HiLany)
Yanquan Lv, (https://github.com/lvyanquan)
Yifan Hu, (https://github.com/demotto)
Zaiyue Yu, (https://github.com/tonybobam)
Zhangwan Zhao, (https://github.com/jiemotongxue)
Zhiqiang Li, (https://github.com/ChestnutQiang) 
They are almost working in real-time computing engine team of DTStack. Only 
Yifan Hu working for CaoCao Tech. Most of them are Apache Flink contributor.

##Known Risks###Project Name
The name of the project is Chunjun. Chunjun comes from mandarin chinese Pinyin 
"Chun Jun", and it is one of the top ten famous swords in China.###Orphaned 
products
More than 20 contributors and thousands of forks and star further show that 
Chunjun is actively supported, and we seek to further prosper the community 
with the aid of Apache. As a consequence, Chunjun is unlikely to be reduced to 
an orphaned project.###Inexperience with Open Source
Many of the Chunjun committers have experience working on open source projects. 
They are also active contributors to other Apache projects.
###Homogenous Developers 
The most of core developers are from DTStack, and Chunjun received some bug 
fixes and enhancements from other developers not working at DTStack. 
###Reliance on Salaried Developers
Currently, most of core developers are paid to work on Chunjun project by 
DTStack. We look forward to attracting more people outside DTStack to join this 
project.###Rel

Re: [VOTE] Retire BlueMarlin

[kezhenxu94@apache]

+1, I saw we have had several discussion threads and they have had several 
chances without positive outcome.

> On Feb 16, 2022, at 07:20, Dave Fisher  wrote:
> 
> Please vote to retire BlueMarlin. This is a group that has made no progress 
> as an Apache podling. There is no interest in developing a community. They’ve 
> had multiple chances.
> 
> [ ] +1 Retire BlueMarlin
> [ ] -1 Keep BlueMarlin and I’m willing to join to make it an Apache Community.
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 

— 
Zhenxu Ke (柯振旭)
GitHub @kezhenxu94


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

Re: [IMPORTANT] Linkis, Doris, Shenyu, MXNet. Website branding issue

[kezhenxu94@apache]

Hi Mingyu, yes, Kafka’s website looks to be a good practice in terms of the 
user wall.

> On Dec 13, 2021, at 10:12, 陈明雨  wrote:
> 
> Hi Zhenxu:
> Thanks for your advice.
> And maybe the Kafka website[1] is one of best practice we can refer to?
> That is to move our "user wall" or "user cases" to a submenu like "Powered 
> by".
> 
> 
> 
> 
> [1] https://kafka.apache.org/powered-by
> 
> --
> 
> 此致！Best Regards
> 陈明雨 Mingyu Chen
> 
> Email:
> chenmin...@apache.org
> 
> 
> 
> 
> 
> At 2021-12-12 23:18:45, "kezhenxu94@apache"  wrote:
>> Hi the PPMC of 
>> 
>> - Linkis
>> - Doris
>> - Shenyu
>> - MXNet
>> 
>> (And maybe more...)
>> 
>> I notice that your website violates the best practice of “thanks pages” / 
>> “Trusted By” / “User Wall” [1] and needs some changes to the homepage. The 
>> "TL;DR;” version is not to list your users in the homepage, you can move 
>> them to a submenu like “Users” or similar, but not list them in homepage. 
>> For more rationale please read [1].
>> 
>> Please do not ignore this request and adjust the homepage ideally within 30 
>> days.
>> 
>> [1] https://apache.org/foundation/marks/linking#projectthanks
>> 
>> — 
>> Zhenxu Ke (柯振旭)
>> GitHub @kezhenxu94
>> Apache Incubator PMC
>> 
>> 
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org

— 
Zhenxu Ke (柯振旭)
GitHub @kezhenxu94


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

[IMPORTANT] Linkis, Doris, Shenyu, MXNet. Website branding issue

[kezhenxu94@apache]

Hi the PPMC of 

- Linkis
- Doris
- Shenyu
- MXNet

(And maybe more...)

I notice that your website violates the best practice of “thanks pages” / 
“Trusted By” / “User Wall” [1] and needs some changes to the homepage. The 
"TL;DR;” version is not to list your users in the homepage, you can move them 
to a submenu like “Users” or similar, but not list them in homepage. For more 
rationale please read [1].

Please do not ignore this request and adjust the homepage ideally within 30 
days.

[1] https://apache.org/foundation/marks/linking#projectthanks

— 
Zhenxu Ke (柯振旭)
GitHub @kezhenxu94
Apache Incubator PMC


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

Re: [VOTE] Release Apache MXNet (incubating) version 1.9.0.rc8 (corrected vote)

[kezhenxu94@apache]

Carry my +1 (binding) from dev@ list

— 
Zhenxu Ke (柯振旭)
GitHub @kezhenxu94

> On Dec 6, 2021, at 12:05, Serge Panev  wrote:
> 
> Dear community,
> 
> This is a call for a releasing Apache MXNet (incubating) 1.9.0, release
> candidate 8.
> 
> Apache MXNet (incubating) community has voted and approved the release.
> 
> Vote thread:
> https://lists.apache.org/thread/cb8xjt38s7j78htzd174hyd0yogcwpr8
> 
> Result thread:
> https://lists.apache.org/thread/rwpk1rzdyxmb6vv18d3lb96gqz4nvkdx
> 
> The source tarball, including signatures, digests, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.9.0.rc8/
> 
> The tag to be voted upon is 1.9.0.rc8:
> https://github.com/apache/incubator-mxnet/releases/tag/1.9.0.rc8
> 
> The release hash is 8173b858dd1bff6be465bca2e2bbfc4eabd189b4:
> https://github.com/apache/incubator-mxnet/commit/8173b858dd1bff6be465bca2e2bbfc4eabd189b4
> 
> KEYS file available:
> https://downloads.apache.org/incubator/mxnet/KEYS
> 
> For information about the contents of this release, see:
> https://cwiki.apache.org/confluence/display/MXNET/1.9.0+Release+Notes
> 
> This vote follows the previous vote 
> https://lists.apache.org/thread/63noybmypw0mh0qdp5covbp6yzqo85ly
> but with a corrected KEYS file location.
> 
> The vote will be open for 7 days.
> 
> [ ] +1 release this package as 1.9.0.rc8
> [ ] +0 no opinion
> [ ] -1 do not release this package because...
> 
> Best regards,
> Serge Panev
> 


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

Re: [VOTE] Accept SeaTunnel into the Apache Incubator

[kezhenxu94@apache]

+1 binding to bring SeaTunnel into the incubator

> On Dec 3, 2021, at 21:56, Willem Jiang  wrote:
> 
> Hi all,
> 
> Following up the [DISCUSS] thread on SeaTunnel [1] I would like to call a
> VOTE to accept into the Apache Incubator.
> 
> Please cast your vote:
> 
>  [ ] +1, bring  into the Incubator
>  [ ] +0, I don't care either way
>  [ ] -1, do not bring SeaTunnel into the Incubator, because...
> 
> The vote will open at least for 72 hours and only votes from the
> Incubator PMC are binding, but votes from everyone are welcome.
> 
> Please check out the SeaTunnel Proposal from the incubator wiki[2].
> 
> [1]https://lists.apache.org/thread/nvp0sxnl0b69wgylxsvmdshfd70om1gk
> [2]https://cwiki.apache.org/confluence/display/INCUBATOR/SeaTunnelProposal
> 
> Regards,
> 
> 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
> 

— 
Zhenxu Ke (柯振旭)
GitHub @kezhenxu94


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

Re: [VOTE] Release Apache MXNet (incubating) version 1.9.0.rc7

[kezhenxu94@apache]

Oh yes, the problem is that `3rdparty/ctc_include` should be listed under 
`BSD-3` section instead of `Apache-2.0` section in the `./LICENSE` file.

> On Sep 13, 2021, at 20:28, Xun Liu  wrote:
> 
> hi, zhenxu
> 
> It is stated in the `./LICENSE`[1] file that 3rdparty/ctc_include is
> `Apache-2.0 license`,
> but the file in ctc_include is `NVIDIA CORPORATION` [2].
> I'm not sure if this will be a problem?
> 
> 
> [1] https://github.com/apache/incubator-mxnet/blob/master/LICENSE#L221
> [2]
> https://github.com/apache/incubator-mxnet/blob/v1.9.x/3rdparty/ctc_include/contrib/moderngpu/include/mgpudevice.cuh#L2
> 
> 
> Xun Liu
> Best regards,
> 
> 
> 
> On Mon, Sep 13, 2021 at 7:56 PM kezhenxu94@apache 
> wrote:
> 
>>> I checked the mxnet project again,
>>> and I found that all the files in the third-party submodule
>>> ./3rdparty/ctc_include did not include ASF headers.
>> 
>> Hi Xun, those files are from third-party, and is listed in LICENSE
>> 
>> —
>> Zhenxu Ke (柯振旭)
>> GitHub @kezhenxu94
>> 
>> 
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
>> 

— 
Zhenxu Ke (柯振旭)
GitHub @kezhenxu94


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

Re: [VOTE] Release Apache MXNet (incubating) version 1.9.0.rc7

[kezhenxu94@apache]

> I checked the mxnet project again,
> and I found that all the files in the third-party submodule
> ./3rdparty/ctc_include did not include ASF headers.

Hi Xun, those files are from third-party, and is listed in LICENSE

— 
Zhenxu Ke (柯振旭)
GitHub @kezhenxu94


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

Re: [VOTE] Release Apache Kyuubi(Incubating) v1.3.0-incubating RC7

[kezhenxu94@apache]

Hi, +1 (binding), but please take a look at (3), (4).

1. sha sum is OK. 
  But prefer to use relative path instead of absolute path to generate the sha 
sum, for the sake of convenience when verifying.
  For example, prefer `sha -a 512 kyuubi-1.3.0-incubating-bin.tgz` instead of 
`sha -a 512 
/Users/chengpan/Projects/apache-kyuubi/work/release/kyuubi-1.3.0-incubating-bin.tgz`

2. tar balls are signed by  correctly.
3. “incubating” is in file names but “apache-“ is not, prefer to use 
apache-kyuubi-1.3.0-incubating-bin.tgz.
4. “Incubating” is not in NOTICE file.
5. Source files have license header when necessary.
6. Compile from source successfully. `mvn clean install -DskipTests 
-Pkyuubi-extension-spark-3-1,spark-provided`
7. Bundled licenses are listed correctly.

> On Sep 2, 2021, at 17:26, Cheng Pan  wrote:
> 
> Hello Incubator Community,
> 
> The Apache Kyuubi community has voted on and approved a proposal to release
> Apache Kyuubi(Incubating) version v1.3.0-incubating RC7.
> 
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
> 
> Kyuubi community vote thread:
> https://www.mail-archive.com/dev@kyuubi.apache.org/msg00754.html
> 
> Vote result thread:
> https://www.mail-archive.com/dev@kyuubi.apache.org/msg00802.html
> 
> [ ] +1 Release this package as Apache Kyuubi v1.3.0-incubating
> [ ] +0
> [ ] -1 Do not release this package because ...
> 
> To learn more about Apache Kyuubi (Incubating), please see
> https://kyuubi.apache.org/
> 
> The tag to be voted on is v1.3.0-incubating-rc7 (commit f1319e5):
> https://github.com/apache/incubator-kyuubi/tree/v1.3.0-incubating-rc7
> 
> The release files, including signatures, digests, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/kyuubi/v1.3.0-incubating-rc7/
> 
> Signatures used for Kyuubi RCs can be found in this file:
> https://dist.apache.org/repos/dist/dev/incubator/kyuubi/KEYS
> 
> The staging repository for this release can be found at:
> https://repository.apache.org/content/repositories/orgapachekyuubi-1007/
> 
> 
> Thanks,
> Cheng Pan

— 
Zhenxu Ke (柯振旭)
GitHub @kezhenxu94


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

Re: [VOTE] Release Apache brpc (Incubating) 1.0.0-rc02

[kezhenxu94@apache]

+1 binding

- [OK] .sha512 is correct.
- [OK] .asc is signed by lorin...@apache.org.
- [OK] Source files have license header when needed.
- [OK] No unexpected binary files in source tar.
- [OK] LICENSE and NOTICE and DISCLAIMER exist.

> On Aug 31, 2021, at 20:52, Lorin Lee  wrote:
> 
> Hello IPMC,
> 
> 
> 
> The Apache brpc community has voted and approved the release of Apache
> 
> brpc (Incubating) 1.0.0-rc02. We now kindly request the IPMC members
> 
> review and vote for this release.
> 
> 
> 
> brpc is an industrial-grade RPC framework with extremely high performance,
> and it supports multiple protocols, full rpc features, and has many
> convenient tools. The current release provides the first official and
> stable package, resolves all of the license issues, and fixes many bugs.
> 
> 
> 
> brpc community vote thread:
> 
> https://lists.apache.org/thread.html/rcdf94f507621ac72226b848e3c2ff7c1e1509e37f4926011398a7a2b%40%3Cdev.brpc.apache.org%3E
> 
> 
> 
> Vote result thread:
> 
> https://lists.apache.org/thread.html/r04525259b2044b7118d71418c065cf6173e85c149c0125bb99795c8e%40%3Cdev.brpc.apache.org%3E
> 
> 
> 
> The release candidate:
> 
> https://dist.apache.org/repos/dist/dev/incubator/brpc/1.0.0-rc02/
> 
> 
> 
> This release has been signed with a PGP available here:
> 
> https://dist.apache.org/repos/dist/dev/incubator/brpc/KEYS
> 
> 
> 
> Git tag for the release:
> 
> https://github.com/apache/incubator-brpc/releases/tag/1.0.0-rc02
> 
> 
> 
> Build guide and get started instructions can be found at:
> 
> https://github.com/apache/incubator-brpc/blob/master/docs/en/getting_started.md
> 
> 
> 
> The vote will be open for at least 72 hours or until the necessary number
> 
> of votes is reached.
> 
> 
> 
> Please vote accordingly:
> 
> [ ] +1 Approve the release of Apache brpc (Incubating) 1.0.0-rc02
> 
> [ ] +0
> 
> [ ] -1 Do not approve (please specify the reason)
> 
> 
> 
> Regards,
> 
> Lorin Lee
> 
> Apache brpc (Incubating)



— 
Zhenxu Ke (柯振旭)
GitHub @kezhenxu94


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

Re: [VOTE] Release Apache MXNet (incubating) version 1.9.0.rc7

[kezhenxu94@apache]

Carry my +1 from dev@

> On Aug 30, 2021, at 07:10, Serge Panev  wrote:
> 
> Dear community,
> 
> This is a call for a releasing Apache MXNet (incubating) 1.9.0, release
> candidate 7.
> 
> Apache MXNet (incubating) community has voted and approved the release.
> 
> Vote thread:
> https://lists.apache.org/thread.html/r7da1068178bb5f860cd0b20788c5510f31eaf0595f8f44cf42c09393%40%3Cdev.mxnet.apache.org%3E
> 
> Result thread:
> https://lists.apache.org/thread.html/rc03c1e94bd91b2fb5bfabc72f3eb79af3204779fe53bd4da72202027%40%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.9.0.rc7/
> 
> The tag to be voted upon is 1.9.0.rc7:
> https://github.com/apache/incubator-mxnet/releases/tag/1.9.0.rc7
> 
> The release hash is b5e9ae89bb5a4232875cd354ffe9a091b43bba69:
> https://github.com/apache/incubator-mxnet/commit/b5e9ae89bb5a4232875cd354ffe9a091b43bba69
> 
> KEYS file available:
> https://dist.apache.org/repos/dist/dev/incubator/mxnet/KEYS
> 
> For information about the contents of this release, see:
> https://cwiki.apache.org/confluence/display/MXNET/1.9.0+Release+Notes
> 
> The vote will be open for 7 days.
> 
> [ ] +1 release this package as 1.9.0.rc7
> [ ] +0 no opinion
> [ ] -1 do not release this package because...
> 
> Best regards,
> Serge Panev

— 
Zhenxu Ke (柯振旭)
GitHub @kezhenxu94


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

Re: [VOTE]: Release Apache DataLab (incubating) 2.5.0

[kezhenxu94@apache]

+1 (binding)

- .sha is correct.
- tar is signed by ura.kin...@gmail.com.
- “incubating” in tar name but not in doc.
- source files contain license header if needed.
- LICENSE and NOTICE exist.

The following are not blocker of the release but you might want to fix them in 
the next release.

- it’s better to put “Apache" and "(incubating)" in the README.md at least for 
the first time DataLab occurs, ex. Apache DataLab (Incubating).
- there is a hidden binary file in the source tar "doc/.DS_Store”, consider 
removing it in the next release.

> On Aug 3, 2021, at 15:03, Yurii Kinash  wrote:
> 
> Hello Incubator Community,
> 
> The Apache DataLab community has voted on and approved a proposal to release 
> Apache DataLab (incubating) version 2.5.0.
> 
> We now kindly request the Incubator PMC members review and vote in this 
> release.
> 
> DataLab is a platform for creating self-service, exploratory data science 
> environments in the cloud using best-of-breed data science tools.
> DataLab includes a self-service web console, used to create and manage 
> exploratory environments. It allows teams to spin up analytical environments 
> with just a single click of a mouse.
> Once established, the environment can be managed by an analytical team 
> itself, leveraging simple and easy-to-use web-based interface.
> 
> DataLab community vote thread:
> •https://lists.apache.org/thread.html/rc7f3e1a7e3f46e27ed7f05d6763a8fb162a0b1572cf4bbf0f0afbd5a%40%3Cdev.datalab.apache.org%3E
> 
> Vote result thread:
> •https://lists.apache.org/thread.html/r9657e8a5f5fdfb29b1df1dc9e291fd291765211e0ff6335bac6f755e%40%3Cdev.datalab.apache.org%3E
> 
> The release candidate:
> • https://dist.apache.org/repos/dist/dev/incubator/datalab/2.5.0/
> 
> Git tag for the release:
> • https://github.com/apache/incubator-datalab/releases/tag/2.5.0
> 
> Release notes:
> • https://github.com/apache/incubator-datalab/releases/tag/2.5.0
> 
> This has been signed with PGP key CB4730CE3EA35480 corresponding to 
> ura.kin...@gmail.com.
> KEYS file is available here:
> 
>  *   https://dist.apache.org/repos/dist/dev/incubator/datalab/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,
> The Apache DataLab (Incubating) Team
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 

— 
Zhenxu Ke (柯振旭)
GitHub @kezhenxu94


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

Re: [VOTE] Release Apache ShenYu (incubating) 2.4.0

[kezhenxu94@apache]

Hi, -1 (binding)

1. the commit ID claimed in this thread doesn’t match the release tag v2.4.0 
(https://github.com/apache/incubator-shenyu/commit/dc841a2720ea0b5a6ca71f1b9c1aa7958d241f16).

> Release Commit ID: 
> https://github.com/apache/incubator-shenyu/commit/c75a273a8a9118411ed367e743b574e7fe0a5a87

2. the maven staging repository can not be found (404 NOT FOUND) or you had 
recreated the staging repo.

> Maven 2 staging repository: 
> https://repository.apache.org/content/repositories/orgapacheshenyu-1012/org/apache/shenyu/

3. https://dist.apache.org/repos/dist/dev/incubator/shenyu/2.4.0/ has new 
changes since the voting thread is started.

If you think the release candidate is not good enough or need some fixes, 
please cancel the voting thread as soon as possible
instead of changing it silently when the voting thread is still open, so that 
people don’t waste time in voting a changing candidate.

> On Jul 27, 2021, at 10:57, Zhang Yonglun  wrote:
> 
> Hello Incubator Community,
> 
> This is a call for vote to release Apache ShenYu (incubating) version 2.4.0.
> 
> The Apache ShenYu community has voted on and approved a proposal to release
> Apache ShenYu (incubating) version 2.4.0.
> 
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
> 
> ShenYu community vote thread:
> https://lists.apache.org/thread.html/r8164d5840fda82b2d8bce5a7075ea874d247f2c0abf9203821a13cbb%40%3Cdev.shenyu.apache.org%3E
> 
> Vote result thread:
> https://lists.apache.org/thread.html/re7b26cf370707cdb54a5404e317167fde643d3669e9783e335bf3b5e%40%3Cdev.shenyu.apache.org%3E
> 
> Release notes:
> https://github.com/apache/incubator-shenyu/blob/master/RELEASE-NOTES.md
> 
> The release candidates:
> https://dist.apache.org/repos/dist/dev/incubator/shenyu/2.4.0/
> 
> Maven 2 staging repository:
> https://repository.apache.org/content/repositories/orgapacheshenyu-1012/org/apache/shenyu/
> 
> Git tag for the release:
> https://github.com/apache/incubator-shenyu/tree/v2.4.0/
> 
> Release Commit ID:
> https://github.com/apache/incubator-shenyu/commit/c75a273a8a9118411ed367e743b574e7fe0a5a87
> 
> Keys to verify the Release Candidate:
> https://dist.apache.org/repos/dist/dev/incubator/shenyu/KEYS
> 
> Look at here for how to verify this release candidate:
> https://shenyu.apache.org/community/release/#check-release
> 
> GPG user ID:
> zhangyonglun
> 
> 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
> 
> Checklist for reference:
> 
> [ ] Download links are valid.
> 
> [ ] Checksums and PGP signatures are valid.
> 
> [ ] Source code distributions have correct names matching the current
> release.
> 
> [ ] LICENSE and NOTICE files are correct for each ShenYu repo.
> 
> [ ] All files have license headers if necessary.
> 
> [ ] No compiled archives bundled in source archive.
> 
> --
> 
> Zhang Yonglun
> Apache ShenYu (Incubating)
> Apache ShardingSphere



— 
Zhenxu Ke (柯振旭)
GitHub @kezhenxu94


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

Re: [VOTE] Release Apache MXNet (incubating) version 1.9.0.rc3

[kezhenxu94@apache]

Hi, my +1 binding only due to DISCLAIMER-WIP

- SIL Open Font License is included in source tar [1].
- Some files are not listed in LICENSE [2].
- Some files are not recognized as ASF license header nor listed in LICENSE, 
hence I’m not sure what they are licensed [3].

[1] docs/python_docs/themes/mx-theme/mxtheme/static/webfonts/ 
[2] 3rdparty/googletest/ci , include/mkldnn
[3] docs/static_site/src/_includes/disqus_comments.html, and all files under 
docs/static_site/***

I also checked

- .asc, .sha512 are correct.
- commit sha and tag are correct.
- license headers are correct if needed.
- LICENSE, NOTICE and DISCLAIMER-WIP are correct.
- “Incubator” is in src tar name and docs.
- 

> On Jun 11, 2021, at 11:39, Serge Panev  wrote:
> 
> Dear community,
> 
> This is a call for a releasing Apache MXNet (incubating) 1.9.0, release
> candidate 3.
> 
> Apache MXNet (incubating) community has voted and approved the release.
> 
> Vote thread:
> https://lists.apache.org/thread.html/r1849016d251dad390312c8a788e9debd36abbf31e1ef15284582b41a%40%3Cdev.mxnet.apache.org%3E
> 
> Result thread:
> https://lists.apache.org/thread.html/r23fe1a469edde8036845d3efb49ac1a69b68277a7275c0270fc9427e%40%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.9.0.rc3/
> 
> The tag to be voted upon is 1.9.0.rc3:
> https://github.com/apache/incubator-mxnet/releases/tag/1.9.0.rc3
> 
> The release hash is 579a631c44c97de838379b138858277999754b94:
> 
> https://github.com/apache/incubator-mxnet/commit/579a631c44c97de838379b138858277999754b94
> 
> KEYS file available:
> https://dist.apache.org/repos/dist/dev/incubator/mxnet/KEYS
> 
> For information about the contents of this release, see:
> 
> https://cwiki.apache.org/confluence/display/MXNET/1.9.0+Release+Notes
> 
> 
> The vote will be open for 7 days.
> 
> [ ] +1 release this package as 1.9.0.rc3
> [ ] +0 no opinion
> [ ] -1 do not release this package because...
> 
> Best regards,
> 
> Serge Panev



— 
Zhenxu Ke (柯振旭)
GitHub @kezhenxu94


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

Re: [VOTE] Release Apache Doris 0.14.0-incubating-rc06

[kezhenxu94@apache]

+1 (binding)

- .asc, .sha512 are correct.
- no unexpected binary files in src.
- “incubating” in src name and doc.
- files have license header if needed.
- LICENSE and NOTICE exist.
- didn’t compile b/c OS not supported.

> On May 17, 2021, at 11:18, 寒江雪  wrote:
> 
> Hi all,
> 
> Please review and vote on Apache Doris 0.14.0-incubating-rc06 release.
> 
> Apache Doris is an MPP-based interactive SQL data warehousing for reporting
> and analysis.
> 
> The Apache Doris community has voted on and approved this release:
> https://lists.apache.org/thread.html/r1fd266598796a7b18ac00c7a23f8ad23ebcd0e6a64d83277f25c8150%40%3Cdev.doris.apache.org%3E
> 
> The vote result email thread:
> https://lists.apache.org/thread.html/r4d34c37304efe41b6999d4475b962b0923e39356cd200dbef045312f%40%3Cdev.doris.apache.org%3E
> 
> The release candidate has been tagged in GitHub as 0.14.0-rc06, available
> here:
> https://github.com/apache/incubator-doris/releases/tag/0.14.0-rc06
> 
> Thanks to everyone who has contributed to this release, and there is a
> simple release notes can be found here:
> https://github.com/apache/incubator-doris/issues/5374
> 
> The artifacts (source, signature and checksum) corresponding to this release
> candidate can be found here:
> https://dist.apache.org/repos/dist/dev/incubator/doris/0.14/0.14.0-rc06
> 
> This has been signed with PGP key 59F2ACED, corresponding to
> yang...@apache.org.
> KEYS file is available here:
> https://dist.apache.org/repos/dist/dev/incubator/doris/KEYS
> It is also listed here:
> https://people.apache.org/keys/committer/yangzhg.asc
> 
> The vote will be open for at least 72 hours.
> [ ] +1 Approve the release
> [ ] +0 No opinion
> [ ] -1 Do not release this package because ...
> 
> To verify and build, you can refer to the following wiki:
> https://github.com/apache/incubator-doris/wiki/How-to-verify-Apache-Release
> https://wiki.apache.org/incubator/Incubator+Release+Checklist
> 
> You can also refer to instruction:
> 
> Firstly, you must install and start docker service, and then you could
> build Doris as the following steps:
> 
> Step1: Pull the docker image with Doris building environment
> $ docker pull apachedoris/doris-dev:build-env-1.2
> You can check it by listing images, its IMAGE ID is d854b488afaf
> 
> Step2: Run the Docker image
> You can run the image directly:
> $ docker run -it apachedoris/doris-dev:build-env1.2
> 
> Step3: Download Doris source
> Now you should in the docker environment, and you can download the Doris
> source package.
> (If you have downloaded the source, and it is not in the image, you can map
> its path to the image in Step2.)
> $ wget
> https://dist.apache.org/repos/dist/dev/incubator/doris/0.14/0.14.0-rc06/apache-doris-0.14.0-incubating-src.tar.gz
> 
> Step4: Build Doris
> Now you can decompress and enter Doris source path and build Doris.
> $ tar -zxvf apache-doris-0.14.0-incubating-src.tar.gz
> $ cd apache-doris-0.14.0-incubating-src
> $ sh build.sh
> 
> Best Regards,
> Yang Zhengguo

— 
Zhenxu Ke (柯振旭)
GitHub @kezhenxu94


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

Re: [VOTE] Release Apache NLPCraft (incubating) 0.7.5

[kezhenxu94@apache]

+1 (binding), some minor issues are expected to fixed in next release.

- Source tar is signed by aradzin...@datalingvo.com, it’s better to sign with 
your @apache.org account.
- Sha shum is correct.
- LICENSE, NOTICE, and DISCLAIMER exist.
- License headers exist in files where applicable, except for generated files 
and 3rd-party files declared in LICENSE.
- No unexpected binary files in source tar.
- “Incubating” exists in distributed file names, but not in the documentations 
(README.md).
- Compile from source codes successfully.

> On May 14, 2021, at 01:42, Aaron Radzinski  wrote:
> 
> Hello all,
> This is a call for a vote to release Apache NLPCraft (incubating)
> version 0.7.5. Apache NLPCraft is a library for adding a natural language
> interface to any application.
> 
> The Apache NLPCraft community has voted on and approved a proposal to
> release Apache NLPCraft (Incubating) version 0.7.5. We would like to
> request the Incubator PMC members review and vote on this incubator release.
> 
> Release information:
> 1. PPMC vote result thread:
> https://mail-archives.apache.org/mod_mbox/nlpcraft-dev/202105.mbox/%3cCALV17Qp_roGvs6jvR09zdXX0x99=mtefuax1bhtnw5cbsvk...@mail.gmail.com%3e
> 2. Release location:
> https://dist.apache.org/repos/dist/dev/incubator/nlpcraft/nlpcraft/0.7.5/
> 3. Git tag: https://github.com/apache/incubator-nlpcraft/tree/v0.7.5
> 4. JIRA issues fixed in release:
> https://issues.apache.org/jira/projects/NLPCRAFT/versions/12349604
> 5. KEYS file: https://dist.apache.org/repos/dist/release/incubator/nlpcraft
> /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
> 
> Aaron,
> ---
> Thank you,
> On behalf of NLPCraft community

— 
Zhenxu Ke (柯振旭)
GitHub @kezhenxu94


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

Re: [VOTE] Retirement of Weex

[kezhenxu94@apache]

+1 binding

> On May 9, 2021, at 18:06, Willem Jiang  wrote:
> 
> Hi,
> 
> According to the retirement guide[1] of incubator, we started the
> public discussion in the weex dev mailing list and got the
> conclusion[2] to go to the retirement process.
> 
> Now we just start a LAZY consensus vote in the IPMC.
> 
> [ ] +1 Support to retire Weex from Apache Incubator
> [ ] -1  Do not Support to retire Weex from Apache Incubator (please
> provide specific comments)
> 
> This vote will be open for at least 72 hours.
> 
> [1]https://incubator.apache.org/guides/retirement.html
> [2]https://lists.apache.org/thread.html/rcaf67836a77ad3bebcafffc9e853bcd043a844e123e06ac8e71c9f4d%40%3Cdev.weex.apache.org%3E
> 
> 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
> 

— 
Zhenxu Ke (柯振旭)
GitHub @kezhenxu94


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

Re: [DISCUSS] Incubating Proposal of Shenyu

[kezhenxu94@apache]

In addition to Sheng’s list, I’ll also suggest the community to reconsider
the project name “ShenYu”, because from a quick search, there are several
potential branding / trademark conflicts, such as [1], [2], and [3].

Note that there is no official Chinese names for ASF Projects so you won’t
have “神禹” officially to distinguish yourself from others with the same pinyin 
“ShenYu”.

You may not want to change the name again later b/c that's a lot of work
and can be disruptive to your community, as you’ve already changed once.

[1] SHENYU Official Store <https://www.aliexpress.com/store/2792168>
[2] Shenyu <http://www.shenyu-group.com/en/>
[3] 神鱼（SHENYU）京东自营旗舰店 https://shenyu.jd.com

> On Apr 19, 2021, at 21:24, Sheng Wu  wrote:
> 
> Hi Shenyu community
> 
> IPMC has an internal discussion these 2 days. My concerns have been
> resolved.
> Some IPMC members want to give the following suggestions to the Shenyu's
> team
> - The incubating evaluation process only runs some checks on project
> branding, IP clearance, and community-related issues.
> - There is no endorsement of the project's technology from Apache or the
> mentor side even if the project is accepted by Apache Incubator.
> - Company affiliations of potential committers shouldn't matter. Anyone can
> become a committer not matter who they work for.
> - Code and no of commits is not the only activity that result in
> committership.
> - It is best to keep the committer bar low.
> - Dictators / leaders, friendly or other wise are not welcome. The code and
> management of that must be given over to the community.
> - Don't play the number game. The Apache counts on the real community
> activities. A TLP could be a big or small community, but need to be real.
> 
> These are going to be very important with other Apache cultures you need to
> learn and follow.
> If you are willing to learn and follow from your experienced mentors and
> IPMC, I am welcome you to join the incubator journey.
> 
> And this kind of argument is normal, you will experience more and must have
> to face -1 one day, at least when releasing, which would not be pleasant
> always and also normal cases. :)
> Once you get the idea and baseline, it would not be that hard.
> 
> Work closely with your community and mentors, have good luck.
> I am looking forward to your new proposal.
> 
> Sheng Wu 吴晟
> Twitter, wusheng1108
> 
> 
> Sheng Wu 吴晟
> Twitter, wusheng1108
> 
> 
> Sheng Wu  于2021年4月18日周日 下午2:41写道：
> 
>> Thanks, Duo.
>> Look forward to a better version of their proposal.
>> 
>> Sheng Wu 吴晟
>> Twitter, wusheng1108
>> 
>> 张铎(Duo Zhang)  于2021年4月18日周日 下午12:11写道：
>>> 
>>> Thanks Willem for clarifying.
>>> 
>>> As long as the community status is not important when joining incubtor(it
>>> is important when graduating), and there are some concerns, let's remove
>>> the sensitive words such as 'diverse' in the proposal, just mention that
>>> the project is already open sourced and has an initial community, so we
>> do
>>> not need to argue on this any more.
>>> And lack of English skill is a problem. Talking with the project leaders,
>>> they need to use google translate a lot when the topic is not about tech,
>>> so it is easy for them to be misunderstood.
>>> 
>>> So let's focus on the problems which must be solved before joining the
>>> incubator. I think the initial committer candidate is a problem and I saw
>>> the project leaders have already started to solve it.
>>> 
>>> And also, I agree with Willem that, joining incubator does not mean
>>> endorsement from ASF and the mentors about technology. We just want to
>> help
>>> the project to build the community in Apache way in the future.
>>> 
>>> Thanks.
>>> 
>>> Willem Jiang  于2021年4月17日周六 下午11:08写道：
>>> 
>>>> After having some talk with the project leaders, we will start a
>>>> discussion in the dromara community to make a clear initial committer
>>>> choosing standard.
>>>> Then we will update the initial committer list by asking the selected
>>>> committer if they want to join as the initial committer.
>>>> 
>>>> BTW, to be more clear,  the incubating evaluation process only runs
>>>> some checks on project branding, IP clearance and community related
>>>> issues.
>>>> There is no endorsement of the project's technology from Apache or the
>>>> mentor side if the project is accepted by Apache Incubator.
>>>> 
>>>> Willem Jiang
>>>> 
>>>>

Re: Release Helm chart as a derived downstream software artifact

[kezhenxu94@apache]

Hi

> I would like the first release of this package to be an official Apache 
> release. I am therefore of the mindset that it should be treated as any other 
> official Apache source code release.

Right, it should follow the Apache release policy and release source tar to be 
an official Apache release.
So there is no exception IMO to release the Helm Chart source tar.

While at the same time, Apache also allows (not requires) binary releases or 
distributions to third-party platforms, such as Pypi,  Docker Hub, npmjs.com, 
etc.

You may be interested in the distribution guide [1] (for incubating projects 
though)

[1] 
https://cwiki.apache.org/confluence/display/INCUBATOR/Distribution+Guidelines

> Can someone point me to a precedent or policy pertaining to the publication 
> of derived downstream software artifacts such as containers, Helm charts, etc.

There are also some TLPs [2] that did Helm Chart releases just for your 
reference.

[2] https://artifacthub.io/packages/helm/apache-solr/solr-operator 
(https://github.com/apache/solr-operator)
https://artifacthub.io/packages/helm/apache/pulsar 
(https://github.com/apache/pulsar-helm-chart)
https://github.com/apache/skywalking-kubernetes

> Thank you
> lewismc
> 
> [0] https://github.com/apache/tika-helm
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 



— 
Zhenxu Ke (柯振旭)
GitHub @kezhenxu94


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

Re: [DISCUSS] Incubating Proposal of Shenyu

[Apache DolphinScheduler]

+1 (no binding)


Best Regards
---
DolphinScheduler PMC
Lidong Dai
dailidon...@gmail.com
---


On Tue, Apr 13, 2021 at 5:28 PM Goson zhang  wrote:

> +1 (no binding)
>
> Good luck!!
>
> jincheng sun  于2021年4月13日周二 上午10:32写道：
>
> > +1 (binding)
> >
> > Best,
> > Jincheng
> >
> >
> > Juan Pan  于2021年4月12日周一 下午7:55写道：
> >
> > > Welcome, looks many people are interested in this project.
> > >
> > >
> > >
> > >
> > > ----
> > >Juan Pan (Trista)
> > >
> > > Senior DBA & PMC of Apache ShardingSphere
> > > E-mail: panj...@apache.org
> > >
> > >
> > >
> > >
> > > On 04/12/2021 10:46，Liu Ted wrote：
> > > +1 (binding)
> > >
> > > Ted Liu
> > >
> > > 在 2021 年 4月 月 12 日週一，時間：9:14 ， Kevin A. McGrail 
> > > 寫道：   +1 binding and good luck!
> > >
> > > On Sun, Apr 11, 2021, 21:08 Zhang Yonglun 
> > wrote:
> > >
> > > Thanks. I had also invited Justin Mclean to be our mentor. Now he's in
> > the
> > > Mentors list.
> > >
> > > --
> > >
> > > Zhang Yonglun
> > > Apache ShardingSphere
> > >
> > >
> > > Sheng Wu  于2021年4月11日周日 下午11:26写道：
> > >
> > > Good to see you are ready for this proposal.
> > > Good luck!!
> > >
> > > Sheng Wu 吴晟
> > > Twitter, wusheng1108
> > >
> > >
> > > Willem Jiang  于2021年4月11日周日 下午10:42写道：
> > >
> > > Hi Atric
> > >
> > > Thanks for the kindly offer.
> > > I just added you to the mentor list.
> > >
> > > Willem Jiang
> > >
> > > Twitter: willemjiang
> > > Weibo: 姜宁willem
> > >
> > > On Sun, Apr 11, 2021 at 9:24 PM Atri Sharma  wrote:
> > >
> > > Please include me in mentors list if required.
> > >
> > > On Sun, 11 Apr 2021, 18:42 Kevin Ratnasekera, <
> > > djkevincr1...@gmail.com
> > >
> > > wrote:
> > >
> > > +1 (binding) Please count me in if you consider adding further
> > > mentors.
> > >
> > > On Sun, Apr 11, 2021 at 6:20 PM Willem Jiang <
> > > willem.ji...@gmail.com
> > >
> > > wrote:
> > >
> > > Hi,
> > >
> > > ShenYu (神禹) project is developed by the Dromara[1] community.
> > > ShenYu
> > > is a high performance Microservices API gateway in the Java
> > > ecosystem,
> > > compatible with a variety of mainstream framework systems,
> > > supports
> > > hot plug extenstion. Users can write their own plugin to meet the
> > > current requirement and future needs in a variety of scenarios,
> > > especially in large-scale scenes.
> > > Recently the Dromara community decided to donate the project
> > > Apache
> > > Software Foundation[2].
> > >
> > > As the Champion of ShenYu, I'd like to bring your attention to
> > > the
> > > proposal of ShenYu [3] for Incubation in the Apache Software
> > > Foundation.
> > >
> > > Please note that the Shenyu project was named Soul before, but we
> > > decided to rename the project because of the trademark issue. You
> > > can
> > > find the original project web page here[4].
> > >
> > > [1]https://github.com/dromara/
> > > [2]https://github.com/dromara/soul/issues/1247
> > > [3]
> > > https://cwiki.apache.org/confluence/display/INCUBATOR/ShenyuProposal
> > > [4]https://dromara.org/projects/soul/overview/
> > >
> > > 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: [VOTE] Release Apache Doris 0.14.0-incubating-rc04

[kezhenxu94@apache]

> On Apr 12, 2021, at 09:47, 寒江雪  wrote:
> 
> Hi
> Doris 0.14.7 is a rolling version maintained internally by baidu. We will
> regularly select committs from the community to the internal version and
> release the version number.  0.14.7 has nothing to do with the community’s
> 0.14 release.

If 0.14.7 has nothing to do with the community, please don’t publish the blog 
[1] under the account named ApacheDoris [2], which I believe is under your 
(PPMC members) control.

[1] https://blog.csdn.net/ucanuup_/article/details/115548997
[2] https://blog.csdn.net/ucanuup_

> 
> Ming Wen  于2021年4月12日周一 上午9:27写道：
> 
>> Hello,
>> When I searched for `Doris 0.14` on Google, I found an article[1]
>> mentioning that Doris 0.14.7 has been released.
>> But I checked the historical release[2] and did not have this version.
>> In my understanding, 0.14.0 has not been released. Why does 0.14.7 exist?
>> 
>> [1] https://www.modb.pro/db/49638
>> [2] https://doris.apache.org/master/en/downloads/downloads.html
>> 
>> Thanks,
>> Ming Wen, Apache APISIX PMC Chair
>> Twitter: _WenMing
>> 
>> 
>> Xun Liu  于2021年4月11日周日 下午11:05写道：
>> 
>>> +1 (non-binding)
>>> 
>>> I checked:
>>> [√] Download links are valid.
>>> [√] Checksums and PGP signatures are valid.
>>> [√] LICENSE, NOTICE and DISCLAIMER files exist.
>>> [√] All files have license headers if necessary.
>>> 
>>> Thanks,
>>> Xun Liu
>>> 
>>> On Sun, Apr 11, 2021 at 10:13 PM Willem Jiang 
>>> wrote:
>>> 
>>>> I’m +1, I checked
>>>> 
>>>> - LICENSE, DISCLAIM and NOTICE files exist;
>>>> - Release candidate tar is signed, the Shasum.
>>>> - “incubating” exists in tar file name and documentation;
>>>> - License headers exist in files if necessary.
>>>> 
>>>> Willem Jiang
>>>> 
>>>> Twitter: willemjiang
>>>> Weibo: 姜宁willem
>>>> 
>>>> On Wed, Apr 7, 2021 at 1:37 PM 寒江雪  wrote:
>>>>> 
>>>>> Hi all,
>>>>> 
>>>>> Please review and vote on Apache Doris 0.14.0-incubating-rc04
>> release.
>>>>> 
>>>>> Apache Doris is an MPP-based interactive SQL data warehousing for
>>>> reporting
>>>>> and analysis.
>>>>> 
>>>>> The Apache Doris community has voted on and approved this release:
>>>>> 
>>>> 
>>> 
>> https://lists.apache.org/thread.html/rc95a58e64b926dc89b61e747fd11f8cb7bb173d95395fa26d02d2c00%40%3Cdev.doris.apache.org%3E
>>>>> 
>>>>> The vote result email thread:
>>>>> 
>>>> 
>>> 
>> https://lists.apache.org/thread.html/r14fc4ffeb31046343570a226dd7870ca74b0f15fbad492b09f0bb69f%40%3Cdev.doris.apache.org%3E
>>>>> 
>>>>> The release candidate has been tagged in GitHub as 0.14.0-rc04,
>>> available
>>>>> here:
>>>>> https://github.com/apache/incubator-doris/releases/tag/0.14.0-rc04
>>>>> 
>>>>> Thanks to everyone who has contributed to this release, and there is
>> a
>>>>> simple release notes can be found here:
>>>>> https://github.com/apache/incubator-doris/issues/5374
>>>>> 
>>>>> The artifacts (source, signature and checksum) corresponding to this
>>>> release
>>>>> candidate can be found here:
>>>>> 
>>> https://dist.apache.org/repos/dist/dev/incubator/doris/0.14/0.14.0-rc04/
>>>>> 
>>>>> This has been signed with PGP key 59F2ACED, corresponding to
>>>>> yang...@apache.org.
>>>>> KEYS file is available here:
>>>>> https://dist.apache.org/repos/dist/dev/incubator/doris/KEYS
>>>>> It is also listed here:
>>>>> https://people.apache.org/keys/committer/yangzhg.asc
>>>>> 
>>>>> The vote will be open for at least 72 hours.
>>>>> [ ] +1 Approve the release
>>>>> [ ] +0 No opinion
>>>>> [ ] -1 Do not release this package because ...
>>>>> 
>>>>> To verify and build, you can refer to the following wiki:
>>>>> 
>>>> 
>>> 
>> https://github.com/apache/incubator-doris/wiki/How-to-verify-Apache-Release
>>>>> https://wiki.apache.org/incubator/Incubator+Release+Checklist
>>>>> 
>>>>> You can

Re: [VOTE] Release Apache Doris 0.14.0-incubating-rc04

[kezhenxu94@apache]

> On Apr 12, 2021, at 09:33, 寒江雪  wrote:
> 
> Hi Zhenxu Ke:
> Thanks for voting. The following files are not from 3rd-party, they are
> written by ourselves:
> 1. be/src/olap/rowset/alpha_rowset_writer.h
> 2. be/src/olap/rowset/segment_v2/empty_segment_iterator.cpp

If that’s the case, the license header in file 
be/src/olap/rowset/segment_v2/empty_segment_iterator.cpp is not complete, 
please check and compare with other files, add the missing lines into it.

> I will fix the wrong path of
> "fe/fe-common/src/main/java/org/apache/doris/common/jmockit"  in LICENSE.txt
> 
> kezhenxu94@apache  于2021年4月11日周日 下午9:47写道：
> 
>> Hi, I’m +1, here are my check list
>> 
>> - LICENSE, DISCLAIM and NOTICE files exist;
>> - Release candidate tar is signed correctly, by "yang...@apache.org”;
>> - Shasum of the tar is correct;
>> - “incubating” exists in tar file name and documentation;
>> - License headers exist in files if necessary.
>> 
>> However, I found
>> 
>>  - the following files from 3rd-party are not listed in LICENSE.txt:
>>1. be/src/olap/rowset/alpha_rowset_writer.h
>>2. be/src/olap/rowset/segment_v2/empty_segment_iterator.cpp
>> 
>>  - the following files are listed (IMO) but with wrong file path:
>>1. Should be
>> "fe/fe-common/src/main/java/org/apache/doris/common/jmockit”, but was
>> listed as "fe/fe-common/src/test/java/org/apache/doris/common/jmockit” in
>> LICENSE.txt
>> 
>> The missing 3rd-party files in LICENSE.txt is not a blocker IMO because
>> there are files from the same owner ("be/src/olap/lru_cache.h”,
>> “be/src/olap/lru_cache.cpp”, "be/src/olap/skiplist.h”) which are listed.
>> 
>> And the wrong file path is easily fixed in mind so I think you can proceed
>> but remember to fix in the next release.
>> 
>> 
>>> On Apr 7, 2021, at 13:36, 寒江雪  wrote:
>>> 
>>> Hi all,
>>> 
>>> Please review and vote on Apache Doris 0.14.0-incubating-rc04 release.
>>> 
>>> Apache Doris is an MPP-based interactive SQL data warehousing for
>> reporting
>>> and analysis.
>>> 
>>> The Apache Doris community has voted on and approved this release:
>>> 
>> https://lists.apache.org/thread.html/rc95a58e64b926dc89b61e747fd11f8cb7bb173d95395fa26d02d2c00%40%3Cdev.doris.apache.org%3E
>>> 
>>> The vote result email thread:
>>> 
>> https://lists.apache.org/thread.html/r14fc4ffeb31046343570a226dd7870ca74b0f15fbad492b09f0bb69f%40%3Cdev.doris.apache.org%3E
>>> 
>>> The release candidate has been tagged in GitHub as 0.14.0-rc04, available
>>> here:
>>> https://github.com/apache/incubator-doris/releases/tag/0.14.0-rc04
>>> 
>>> Thanks to everyone who has contributed to this release, and there is a
>>> simple release notes can be found here:
>>> https://github.com/apache/incubator-doris/issues/5374
>>> 
>>> The artifacts (source, signature and checksum) corresponding to this
>> release
>>> candidate can be found here:
>>> https://dist.apache.org/repos/dist/dev/incubator/doris/0.14/0.14.0-rc04/
>>> 
>>> This has been signed with PGP key 59F2ACED, corresponding to
>>> yang...@apache.org.
>>> KEYS file is available here:
>>> https://dist.apache.org/repos/dist/dev/incubator/doris/KEYS
>>> It is also listed here:
>>> https://people.apache.org/keys/committer/yangzhg.asc
>>> 
>>> The vote will be open for at least 72 hours.
>>> [ ] +1 Approve the release
>>> [ ] +0 No opinion
>>> [ ] -1 Do not release this package because ...
>>> 
>>> To verify and build, you can refer to the following wiki:
>>> 
>> https://github.com/apache/incubator-doris/wiki/How-to-verify-Apache-Release
>>> https://wiki.apache.org/incubator/Incubator+Release+Checklist
>>> 
>>> You can also refer to instruction:
>>> 
>>> Firstly, you must install and start docker service, and then you could
>>> build Doris as the following steps:
>>> 
>>> Step1: Pull the docker image with Doris building environment
>>> $ docker pull apachedoris/doris-dev:build-env-1.2
>>> You can check it by listing images, its IMAGE ID is d854b488afaf
>>> 
>>> Step2: Run the Docker image
>>> You can run the image directly:
>>> $ docker run -it apachedoris/doris-dev:build-env1.2
>>> 
>>> Step3: Download Doris source
>>> Now you should in the docker environment, and you can download the Doris
>>> sourc

Re: [VOTE] Release Apache Doris 0.14.0-incubating-rc04

[kezhenxu94@apache]

Hi, I’m +1, here are my check list

- LICENSE, DISCLAIM and NOTICE files exist;
- Release candidate tar is signed correctly, by "yang...@apache.org”;
- Shasum of the tar is correct;
- “incubating” exists in tar file name and documentation;
- License headers exist in files if necessary.

However, I found

  - the following files from 3rd-party are not listed in LICENSE.txt:
1. be/src/olap/rowset/alpha_rowset_writer.h
2. be/src/olap/rowset/segment_v2/empty_segment_iterator.cpp

  - the following files are listed (IMO) but with wrong file path:
1. Should be "fe/fe-common/src/main/java/org/apache/doris/common/jmockit”, 
but was listed as "fe/fe-common/src/test/java/org/apache/doris/common/jmockit” 
in LICENSE.txt

The missing 3rd-party files in LICENSE.txt is not a blocker IMO because there 
are files from the same owner ("be/src/olap/lru_cache.h”, 
“be/src/olap/lru_cache.cpp”, "be/src/olap/skiplist.h”) which are listed.

And the wrong file path is easily fixed in mind so I think you can proceed but 
remember to fix in the next release.


> On Apr 7, 2021, at 13:36, 寒江雪  wrote:
> 
> Hi all,
> 
> Please review and vote on Apache Doris 0.14.0-incubating-rc04 release.
> 
> Apache Doris is an MPP-based interactive SQL data warehousing for reporting
> and analysis.
> 
> The Apache Doris community has voted on and approved this release:
> https://lists.apache.org/thread.html/rc95a58e64b926dc89b61e747fd11f8cb7bb173d95395fa26d02d2c00%40%3Cdev.doris.apache.org%3E
> 
> The vote result email thread:
> https://lists.apache.org/thread.html/r14fc4ffeb31046343570a226dd7870ca74b0f15fbad492b09f0bb69f%40%3Cdev.doris.apache.org%3E
> 
> The release candidate has been tagged in GitHub as 0.14.0-rc04, available
> here:
> https://github.com/apache/incubator-doris/releases/tag/0.14.0-rc04
> 
> Thanks to everyone who has contributed to this release, and there is a
> simple release notes can be found here:
> https://github.com/apache/incubator-doris/issues/5374
> 
> The artifacts (source, signature and checksum) corresponding to this release
> candidate can be found here:
> https://dist.apache.org/repos/dist/dev/incubator/doris/0.14/0.14.0-rc04/
> 
> This has been signed with PGP key 59F2ACED, corresponding to
> yang...@apache.org.
> KEYS file is available here:
> https://dist.apache.org/repos/dist/dev/incubator/doris/KEYS
> It is also listed here:
> https://people.apache.org/keys/committer/yangzhg.asc
> 
> The vote will be open for at least 72 hours.
> [ ] +1 Approve the release
> [ ] +0 No opinion
> [ ] -1 Do not release this package because ...
> 
> To verify and build, you can refer to the following wiki:
> https://github.com/apache/incubator-doris/wiki/How-to-verify-Apache-Release
> https://wiki.apache.org/incubator/Incubator+Release+Checklist
> 
> You can also refer to instruction:
> 
> Firstly, you must install and start docker service, and then you could
> build Doris as the following steps:
> 
> Step1: Pull the docker image with Doris building environment
> $ docker pull apachedoris/doris-dev:build-env-1.2
> You can check it by listing images, its IMAGE ID is d854b488afaf
> 
> Step2: Run the Docker image
> You can run the image directly:
> $ docker run -it apachedoris/doris-dev:build-env1.2
> 
> Step3: Download Doris source
> Now you should in the docker environment, and you can download the Doris
> source package.
> (If you have downloaded the source and it is not in image, you can map its
> path to image in Step2.)
> $ wget
> https://dist.apache.org/repos/dist/dev/incubator/doris/0.14/0.14.0-rc04/apache-doris-0.14.0-incubating-src.tar.gz
> 
> Step4: Build Doris
> Now you can decompress and enter Doris source path and build Doris.
> $ tar -zxvf apache-doris-0.14.0-incubating-src.tar.gz
> $ cd apache-doris-0.14.0-incubating-src
> $ sh build.sh
> 
> Best Regards,
> Yang Zhengguo



— 
Zhenxu Ke (柯振旭)
GitHub @kezhenxu94


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

Re: [VOTE] Release Apache Hop (incubating) 0.70-rc1

[kezhenxu94@apache]

Hi, my +1, I’ve checked

- Sha sum is OK
- GPG signature verified.
- RC matches the git tag / branch.
- LICENSE, NOTICE, DISCLAIMER-WIP files exist.
- Docs, release names include “Incubating”.

However the following issue is not a blocker of the release and can be fixed in 
the following releasees,
but I found the headers in these files are not the one ASF specified.
Note that there is dedicated license header for ASF projects, see this link [1]


- 
plugins/databases/clickhouse/src/main/java/org/apache/hop/databases/clickhouse/ClickhouseDatabaseMeta.java
- 
plugins/databases/clickhouse/src/test/java/org/apache/hop/databases/clickhouse/ClickhouseDatabaseMetaTest.java
- 
plugins/databases/snowflake/src/main/java/org/apache/hop/databases/snowflake/SnowflakeDatabaseMeta.java
- 
plugins/databases/snowflake/src/test/java/org/apache/hop/databases/snowflake/SnowflakeDatabaseMetaTest.java
- 
plugins/misc/git/src/main/java/org/apache/hop/git/DrawDiffOnActionExtensionPoint.java
- 
plugins/misc/git/src/main/java/org/apache/hop/git/DrawDiffOnActionExtensionPoint.java
- 
plugins/misc/git/src/main/java/org/apache/hop/git/DrawDiffOnPipelineHopExtensionPoint.java
- 
plugins/misc/git/src/main/java/org/apache/hop/git/DrawDiffOnTransformExtensionPoint.java
- 
plugins/misc/git/src/main/java/org/apache/hop/git/DrawDiffOnWorkflowHopExtensionPoint.java
- plugins/misc/git/src/main/java/org/apache/hop/git/HopDiff.java
- 
plugins/misc/git/src/main/java/org/apache/hop/git/dialog/DeleteBranchDialog.java
- 
plugins/misc/git/src/main/java/org/apache/hop/git/dialog/MergeBranchDialog.java
- 
plugins/misc/git/src/main/java/org/apache/hop/git/dialog/UsernamePasswordDialog.java
- plugins/misc/git/src/main/java/org/apache/hop/git/model/UIFile.java
- plugins/misc/git/src/main/java/org/apache/hop/git/model/UIGit.java
- 
plugins/misc/git/src/main/java/org/apache/hop/git/model/revision/GitObjectRevision.java
- plugins/misc/git/src/test/java/org/apache/hop/git/HopDiffTest.java
- plugins/misc/git/src/test/java/org/apache/hop/git/model/UIGitTest.java
- core/src/main/java/org/apache/hop/core/util/StorageUnitConverter.java

[1] https://www.apache.org/legal/src-headers.html#headers

> On Mar 30, 2021, at 22:43, Hans Van Akelyen  
> wrote:
> 
> Hi Incubator team,
> 
> We are proud to announce that we have a new release candidate ready for
> release and would like your review and vote.
> 
> Build instructions can be found in the README included.
> 
> Hop community vote and result threads:
> Vote:
> 
> https://lists.apache.org/thread.html/r24f1435c891c11d87d20d87d832b5de2613a37cda5e92c3587f058d1%40%3Cdev.hop.apache.org%3E
> Result:
> 
> https://lists.apache.org/thread.html/red37c2870bd3c366426579ffdd1c33c845eaf13801fd81bc0bd74539%40%3Cdev.hop.apache.org%3E
> 
> The tag to be voted on is 0.70-rc1 (commit
> f16b78f1a16feac5021f4556b30ee0a9609dbc1a)
> https://github.com/apache/incubator-hop/tree/0.70-rc1
> 
> The release files, including signatures, digests, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/hop/apache-hop-0.70-incubating-rc1/
> 
> The SHA512 Checksum for these artifacts is:
> bbf9357801d9bdd0560a6788c7e51d469777d9dbf483be10d67e674552da28848edfba8533bab280afb97949ec55454ec5e147b73ce733010efa57af1997ef3d
> 
> Release artifacts are signed with the following key:
> https://keyserver.ubuntu.com/pks/lookup?op=get=0x9a8a628dd4f4aa1e
> 
> For more information about the contents of this release, see:
> https://issues.apache.org/jira/projects/HOP/versions/12349578
> 
> Please vote on releasing this package as Apache Hop (incubating) 0.70!
> 
> The vote is open for 72 hours and passes if
> a majority of at least 3 +1 PMC votes are cast.
> 
> [ ] +1 Release this package as Apache Hop (incubating) 0.70
> [ ] +0 No opinion
> [ ] -1 Do not release this package because ...
> 
> Best Regards,
> Hans



— 
Zhenxu Ke (柯振旭)
GitHub @kezhenxu94


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

Re: [VOTE] Release Apache Doris 0.14.0-incubating-rc03

[kezhenxu94@apache]

Sorry my -1, I saw there are binary files in the source tar, although they’re 
test tools, but this is not allowed in the source release.

./fe/fe-core/src/test/resources/plugin_test/plugin_test.jar
./fe/fe-core/src/test/resources/plugin_test/test_local_plugin/auditdemo.jar

> On Mar 26, 2021, at 12:36, 寒江雪  wrote:
> 
> Hi all,
> 
> Please review and vote on Apache Doris 0.14.0-incubating-rc03 release.
> 
> Apache Doris is an MPP-based interactive SQL data warehousing for reporting
> and analysis.
> 
> The Apache Doris community has voted on and approved this release:
> https://lists.apache.org/thread.html/r1d3728b02b4f7b56413d3bf334b94fbc9c8406bf2d78aa01fea60a77%40%3Cdev.doris.apache.org%3E
> 
> The vote result email thread:
> https://lists.apache.org/thread.html/re1eb419d0eb4689d77e82727811facef08f3c2498f64ad2ea812d42a%40%3Cdev.doris.apache.org%3E
> 
> The release candidate has been tagged in GitHub as 0.14.0-rc03, available
> here:
> https://github.com/apache/incubator-doris/releases/tag/0.14.0-rc03
> 
> Thanks to everyone who has contributed to this release, and there is a
> simple release notes can be found here:
> https://github.com/apache/incubator-doris/issues/5374
> 
> The artifacts (source, signature and checksum) corresponding to this release
> candidate can be found here:
> https://dist.apache.org/repos/dist/dev/incubator/doris/0.14/0.14.0-rc03/
> 
> This has been signed with PGP key 59F2ACED, corresponding to
> yang...@apache.org.
> KEYS file is available here:
> https://dist.apache.org/repos/dist/dev/incubator/doris/KEYS
> It is also listed here:
> https://people.apache.org/keys/committer/yangzhg.asc
> 
> The vote will be open for at least 72 hours.
> [ ] +1 Approve the release
> [ ] +0 No opinion
> [ ] -1 Do not release this package because ...
> 
> To verify and build, you can refer to following wiki:
> https://github.com/apache/incubator-doris/wiki/How-to-verify-Apache-Release
> https://wiki.apache.org/incubator/Incubator+Release+Checklist
> 
> You can also refer to instruction:
> 
> Firstly, you must be install and start docker service, and then you could
> build Doris as following steps:
> 
> Step1: Pull the docker image with Doris building environment
> $ docker pull apachedoris/doris-dev:build-env-1.2
> You can check it by listing images, its IMAGE ID is d854b488afaf
> 
> Step2: Run the Docker image
> You can run image directly:
> $ docker run -it apachedoris/doris-dev:build-env1.2
> 
> Step3: Download Doris source
> Now you should in the docker environment, and you can download the Doris
> source package.
> (If you have downloaded the source and it is not in image, you can map its
> path to image in Step2.)
> $ wget
> https://dist.apache.org/repos/dist/dev/incubator/doris/0.14/0.14.0-rc03/apache-doris-0.14.0-incubating-src.tar.gz
> 
> Step4: Build Doris
> Now you can decompress and enter Doris source path and build Doris.
> $ tar zxvf apache-doris-0.14.0-incubating-src.tar.gz
> $ cd apache-doris-0.14.0-incubating-src
> $ sh build.sh
> 
> Best Regards,
> Yang Zhengguo



— 
Zhenxu Ke (柯振旭)
GitHub @kezhenxu94


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

Re: [VOTE] Apache Pinot (incubating) 0.7.0 RC1

[kezhenxu94@apache]

Hey, I found some of the files lack the license headers, 
though some of which are for testing only, but since you have
included them in the source tar, it’d be better to have license headers for 
them.

pinot-clients/pinot-jdbc-client/src/main/resources/java.sql.Driver
pinot-connectors/pinot-spark-connector/src/main/resources/META-INF/services/org.apache.spark.sql.sources.DataSourceRegister
pinot-core/src/test/resources/conf/pinot-broker.properties
pinot-core/src/test/resources/conf/query-executor.properties
pinot-core/src/test/resources/generate-test-data.py
pinot-integration-tests/src/test/resources/compat-tests/kafka/topic1.cfg
pinot-integration-tests/src/test/resources/index.html
pinot-tools/src/main/resources/conf/sample_filesystem_benchmark.conf


Also, I found that this file `docs/Makefile` originated from 3-rd party [1] and
is modified in the release, but not mentioned in the LICENSE file.

[1] https://github.com/apache/incubator-pinot/blob/release-0.7.0-rc/LICENSE


> On Mar 23, 2021, at 00:25, Yupeng Fu  wrote:
> 
> Felix and others,
> 
> The git hash on the git tag is now the same as the one sent out in the
> vote. Please check again
> https://github.com/apache/incubator-pinot/commits/release-0.7.0
> 
> Sorry for the inconvenience and thanks for checking.
> 
> Best,
> 
> On Fri, Mar 19, 2021 at 3:45 PM Felix Cheung  wrote:
> 
>> For some reason the git hash has changed in release git tag
>> 
>> https://github.com/apache/incubator-pinot/commits/release-0.7.0
>> 
>> 
>> https://github.com/apache/incubator-pinot/commit/de0236c25727ffc2408c5bf55836bbfecf40499c
>> 
>> 
>> 
>> 
>> On Fri, Mar 19, 2021 at 11:00 AM kishore g  wrote:
>> 
>>> Jim/Felix and others
>>> 
>>> Do we have your +1 to go ahead with the release.
>>> 
>>> Thanks
>>> Kishore G
>>> 
>>> On Thu, Mar 18, 2021 at 9:32 PM kishore g  wrote:
>>> 
>>>> That would be great. We will update the release runbook to make sure
>> this
>>>> doesn't happen again.
>>>> 
>>>> Here is my +1
>>>> 
>>>> 
>>>> 
>>>> On Thu, Mar 18, 2021 at 11:03 AM Jim Jagielski 
>> wrote:
>>>> 
>>>>> I propose that we run the vote anyway, thus ensuring IPMC oversight
>> and
>>>>> (post)approval, and then update the release runbook to make sure this
>>>>> doesn't happen again. Make sense?
>>>>> 
>>>>>> On Mar 17, 2021, at 11:35 PM, Felix Cheung 
>>>>> wrote:
>>>>>> 
>>>>>> It is unclear the guidance on this but since it is impossible remove
>>>>> from
>>>>>> maven
>>>>>> 
>>>>>> https://repository.apache.org/#nexus-search;classname~Pinot
>>>>>> 
>>>>>> Once it is published, I’d suggest we update all the links and git
>> hash
>>>>> and
>>>>>> still proceed to vote on this. If there is any issue we should vote
>> on
>>>>>> another release with fix ASAP. Otherwise hopefully IPMC can continue
>>> to
>>>>>> sign off on this release.
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> On Wed, Mar 17, 2021 at 3:09 PM kishore g 
>>> wrote:
>>>>>> 
>>>>>>> Apologies for the mistake. We have done multiple releases until now
>>> and
>>>>>>> this is the first time we missed the step to get the approval from
>>>>> IPMC was
>>>>>>> missed before making the release.
>>>>>>> 
>>>>>>> What is the right thing to do at this point? Should we cut another
>>>>> release
>>>>>>> or can we go ahead with this and ensure that this does not happen
>>>>> again.
>>>>>>> 
>>>>>>> thanks,
>>>>>>> Kishore G
>>>>>>> 
>>>>>>> On Wed, Mar 17, 2021 at 10:59 AM Felix Cheung <
>>> felixche...@apache.org>
>>>>>>> wrote:
>>>>>>> 
>>>>>>>> Unfortunately this isn’t the right process for a podling release.
>>>>>>>> 
>>>>>>>> As the mentor, I am sorry to see the release is not up to the
>>> standard
>>>>>>>> upheld by previous releases.
>>>>>>>> 
>>>>>>>> 
>>>>>>>> On Wed, Mar 17, 20

Re: [VOTE] Apache Pinot (incubating) 0.7.0 RC1

[kezhenxu94@apache]

I think this release violates the Apache release policy because it didn’t get 
the approvals from IPMC but was released actually (in both dist.a.o and GitHub).

— 
Zhenxu Ke (柯振旭)
GitHub @kezhenxu94

> On Mar 17, 2021, at 06:14, Yupeng Fu  wrote:
> 
> Hi all,
> 
> This is a call for vote to the release Apache Pinot (incubating) version
> 0.7.0.
> 
> Apache Pinot (incubating) is a distributed columnar storage engine that can
> ingest data in realtime and serve analytical queries at low latency.
> 
> Pinot community has voted and approved this release.
> 
> Vote thread:
> https://lists.apache.org/thread.html/r850cee1e6fc23804d161a31d465e30d5d12b7a4e1cc8035264ea91d6%40%3Cdev.pinot.apache.org%3E
> 
> 
> Result thread:
> https://lists.apache.org/thread.html/r80672ac39a6a6eb7f63c7dbbf595de2f7350cf75d2a7a598601da638%40%3Cdev.pinot.apache.org%3E
> 
> The release candidate:
> https://dist.apache.org/repos/dist/dev/incubator/pinot/apache-pinot-incubating-0.7.0-rc1/
> 
> 
> Git tag for this release:
> <https://github.com/apache/incubator-pinot/tree/release-0.7.0-rc0>
> https://github.com/apache/incubator-pinot/tree/release-0.7.0-rc1
> 
> Git hash for this release:
> 695ca390a8080409b3b76f250f2315b81b86b362
> 
> The artifacts have been signed with key: F41AB2B856C6C29D, which can be
> found in the following KEYS file.
> https://dist.apache.org/repos/dist/release/incubator/pinot/KEYS
> 
> Release notes:
> https://github.com/apache/incubator-pinot/releases/tag/release-0.7.0-rc1
> 
> Staging repository:
> <https://repository.apache.org/content/repositories/orgapachepinot-1023>
> https://repository.apache.org/content/repositories/orgapachepinot-1024
> 
> Documentation on verifying a release candidate:
> https://cwiki.apache.org/confluence/display/PINOT/Validating+a+release+candidate
> 
> 
> The vote will be open for at least 72 hours or until the necessary number of
> votes are reached.
> 
> Please vote accordingly,
> 
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
> 
> Thanks,
> Apache Pinot (incubating) team



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

Re: [VOTE] Release Apache Doris 0.14.0-incubating-rc02

[kezhenxu94@apache]

You have to include a DISCLAIMER file in the release because Doris is still in 
incubator.

If you have license issues, you can have DISCLAIMER-WIP so that IPMC members 
won’t -1 when voting a release (WIP indicates that you’re resolving the 
problem), but if you have resolved the license issues, you MUST have a 
DISCLAIMER file in it, at this time, IPMC members will vote -1 when they find 
license issues.

> On Mar 17, 2021, at 21:22, 陈明雨  wrote:
> 
> Hi Juan, Williem and Zhiyuan:
> 
> 
> Thank for your review.
> 
> 
> 
> But why do we still need to keep DISCLAIMER-WIP in the code base?
> 
> We had some LICENSE issues in version 0.12, so we declared these issues in 
> DISCLAIMER-WIP.
> 
> These license issues have been resolved in version 0.13, so we have removed 
> DISCLAIMER-WIP in version 0.13.
> 
> 
> 
> 
> --
> 
> 此致！Best Regards
> 陈明雨 Mingyu Chen
> 
> 
> 
> Email:
> chenmin...@apache.org
> 
> 
> 
> 
> 
> 在 2021-03-17 09:18:37，"Zhiyuan Ju"  写道：
>> Please check the necessary files :)
>> 
>> Willem Jiang 于2021年3月16日 周二下午11:19写道：
>> 
>>> We need to keep the DISCLAIMER-WIP into the release kit file.
>>> Please add it back.
>>> 
>>> Willem Jiang
>>> 
>>> Twitter: willemjiang
>>> Weibo: 姜宁willem
>>> 
>>> On Tue, Mar 16, 2021 at 1:36 PM Juan Pan  wrote:
>>>> 
>>>> Hi,
>>>> Sorry for my -1 (non-binding)
>>>> Same as Kris Calvin.
>>>> Just my curiosity, DISCLAIMER-WIP existed in incubator-doris-0.12.0 but
>>> disappears from this candidate one?
>>>> 
>>>> 
>>>> Cheers,
>>>> Trista
>>>> 
>>>> 
>>>> 
>>>>   Juan Pan (Trista)
>>>> 
>>>> Senior DBA & PMC of Apache ShardingSphere
>>>> E-mail: panj...@apache.org
>>>> 
>>>> 
>>>> 
>>>> 
>>>> On 03/15/2021 10:56，寒江雪 wrote：
>>>> Hi all,
>>>> 
>>>> Please review and vote on Apache Doris 0.14.0-incubating-rc02 release.
>>>> 
>>>> Apache Doris is an MPP-based interactive SQL data warehousing for
>>> reporting
>>>> and analysis.
>>>> 
>>>> The Apache Doris community has voted on and approved this release:
>>>> 
>>> https://lists.apache.org/thread.html/r0dd10dc04af92f262f74a67092c1d927e79c939d62396e2d6284b647%40%3Cdev.doris.apache.org%3E
>>>> 
>>>> The vote result email thread:
>>>> 
>>> https://lists.apache.org/thread.html/r18b7960ac02836cf1285d2139ecb951156d43e94b9d81ba86c67%40%3Cdev.doris.apache.org%3E
>>>> 
>>>> The release candidate has been tagged in GitHub as 0.14.0-rc02, available
>>>> here:
>>>> https://github.com/apache/incubator-doris/releases/tag/0.14.0-rc02
>>>> 
>>>> Thanks to everyone who has contributed to this release, and there is a
>>>> simple release notes can be found here:
>>>> https://github.com/apache/incubator-doris/issues/5374
>>>> 
>>>> The artifacts (source, signature and checksum) corresponding to this
>>> release
>>>> candidate can be found here:
>>>> https://dist.apache.org/repos/dist/dev/incubator/doris/0.14/0.14.0-rc02/
>>>> 
>>>> This has been signed with PGP key 59F2ACED, corresponding to
>>>> yang...@apache.org.
>>>> KEYS file is available here:
>>>> https://dist.apache.org/repos/dist/dev/incubator/doris/KEYS
>>>> It is also listed here:
>>>> https://people.apache.org/keys/committer/yangzhg.asc
>>>> 
>>>> The vote will be open for at least 72 hours.
>>>> [ ] +1 Approve the release
>>>> [ ] +0 No opinion
>>>> [ ] -1 Do not release this package because ...
>>>> 
>>>> To verify and build, you can refer to following wiki:
>>>> 
>>> https://github.com/apache/incubator-doris/wiki/How-to-verify-Apache-Release
>>>> https://wiki.apache.org/incubator/Incubator+Release+Checklist
>>>> 
>>>> You can also refer to instruction:
>>>> 
>>>> Firstly, you must be install and start docker service, and then you could
>>>> build Doris as following steps:
>>>> 
>>>> Step1: Pull the docker image with Doris building environment
>>>> $ docker pull apachedoris/doris-dev:build-env-1.2
>>>> You can che

Re: [VOTE] Apache Pinot (incubating) 0.7.0 RC1

[kezhenxu94@apache]

Hey, most of the links in this email are invalid (404) [1], it seems because 
you have moved the candidate into the release directory [2] already, which 
should be done after incubator votes’ result (this thread).

Also, I found this tag [3] on GitHub but the commit hash doesn’t match the one 
in this thread.

[1]
- 
https://dist.apache.org/repos/dist/dev/incubator/pinot/apache-pinot-incubating-0.7.0-rc1/
- https://github.com/apache/incubator-pinot/tree/release-0.7.0-rc1
- https://repository.apache.org/content/repositories/orgapachepinot-1023
- https://repository.apache.org/content/repositories/orgapachepinot-1024
- https://github.com/apache/incubator-pinot/releases/tag/release-0.7.0-rc1

[2] 
https://dist.apache.org/repos/dist/release/incubator/pinot/apache-pinot-incubating-0.7.0/
[3] https://github.com/apache/incubator-pinot/tree/release-0.7.0

> On Mar 17, 2021, at 06:14, Yupeng Fu  wrote:
> 
> Hi all,
> 
> This is a call for vote to the release Apache Pinot (incubating) version
> 0.7.0.
> 
> Apache Pinot (incubating) is a distributed columnar storage engine that can
> ingest data in realtime and serve analytical queries at low latency.
> 
> Pinot community has voted and approved this release.
> 
> Vote thread:
> https://lists.apache.org/thread.html/r850cee1e6fc23804d161a31d465e30d5d12b7a4e1cc8035264ea91d6%40%3Cdev.pinot.apache.org%3E
> 
> 
> Result thread:
> https://lists.apache.org/thread.html/r80672ac39a6a6eb7f63c7dbbf595de2f7350cf75d2a7a598601da638%40%3Cdev.pinot.apache.org%3E
> 
> The release candidate:
> https://dist.apache.org/repos/dist/dev/incubator/pinot/apache-pinot-incubating-0.7.0-rc1/
> 
> 
> Git tag for this release:
> <https://github.com/apache/incubator-pinot/tree/release-0.7.0-rc0>
> https://github.com/apache/incubator-pinot/tree/release-0.7.0-rc1
> 
> Git hash for this release:
> 695ca390a8080409b3b76f250f2315b81b86b362
> 
> The artifacts have been signed with key: F41AB2B856C6C29D, which can be
> found in the following KEYS file.
> https://dist.apache.org/repos/dist/release/incubator/pinot/KEYS
> 
> Release notes:
> https://github.com/apache/incubator-pinot/releases/tag/release-0.7.0-rc1
> 
> Staging repository:
> <https://repository.apache.org/content/repositories/orgapachepinot-1023>
> https://repository.apache.org/content/repositories/orgapachepinot-1024
> 
> Documentation on verifying a release candidate:
> https://cwiki.apache.org/confluence/display/PINOT/Validating+a+release+candidate
> 
> 
> The vote will be open for at least 72 hours or until the necessary number of
> votes are reached.
> 
> Please vote accordingly,
> 
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
> 
> Thanks,
> Apache Pinot (incubating) team



— 
Zhenxu Ke (柯振旭)
GitHub @kezhenxu94


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

Re: [VOTE] Release Apache Doris 0.14.0-incubating-rc02

[kezhenxu94@apache]

-1 (non-binding) because I cannot see a DISCLAIMER file in the release tar, 
neither in the GitHub repository.

> On Mar 15, 2021, at 10:56, 寒江雪  wrote:
> 
> Hi all,
> 
> Please review and vote on Apache Doris 0.14.0-incubating-rc02 release.
> 
> Apache Doris is an MPP-based interactive SQL data warehousing for reporting
> and analysis.
> 
> The Apache Doris community has voted on and approved this release:
> https://lists.apache.org/thread.html/r0dd10dc04af92f262f74a67092c1d927e79c939d62396e2d6284b647%40%3Cdev.doris.apache.org%3E
> 
> The vote result email thread:
> https://lists.apache.org/thread.html/r18b7960ac02836cf1285d2139ecb951156d43e94b9d81ba86c67%40%3Cdev.doris.apache.org%3E
> 
> The release candidate has been tagged in GitHub as 0.14.0-rc02, available
> here:
> https://github.com/apache/incubator-doris/releases/tag/0.14.0-rc02
> 
> Thanks to everyone who has contributed to this release, and there is a
> simple release notes can be found here:
> https://github.com/apache/incubator-doris/issues/5374
> 
> The artifacts (source, signature and checksum) corresponding to this release
> candidate can be found here:
> https://dist.apache.org/repos/dist/dev/incubator/doris/0.14/0.14.0-rc02/
> 
> This has been signed with PGP key 59F2ACED, corresponding to
> yang...@apache.org.
> KEYS file is available here:
> https://dist.apache.org/repos/dist/dev/incubator/doris/KEYS
> It is also listed here:
> https://people.apache.org/keys/committer/yangzhg.asc
> 
> The vote will be open for at least 72 hours.
> [ ] +1 Approve the release
> [ ] +0 No opinion
> [ ] -1 Do not release this package because ...
> 
> To verify and build, you can refer to following wiki:
> https://github.com/apache/incubator-doris/wiki/How-to-verify-Apache-Release
> https://wiki.apache.org/incubator/Incubator+Release+Checklist
> 
> You can also refer to instruction:
> 
> Firstly, you must be install and start docker service, and then you could
> build Doris as following steps:
> 
> Step1: Pull the docker image with Doris building environment
> $ docker pull apachedoris/doris-dev:build-env-1.2
> You can check it by listing images, its IMAGE ID is 686ed7f45a02
> 
> Step2: Run the Docker image
> You can run image directly:
> $ docker run -it apachedoris/doris-dev:build-env1.2
> 
> Step3: Download Doris source
> Now you should in docker environment, and you can download Doris source
> package.
> (If you have downloaded source and it is not in image, you can map its path
> to image in Step2.)
> $ wget
> https://dist.apache.org/repos/dist/dev/incubator/doris/0.14/0.14.0-rc02/apache-doris-0.14.0-incubating-src.tar.gz
> 
> Step4: Build Doris
> Now you can decompress and enter Doris source path and build Doris.
> $ tar zxvf apache-doris-0.14.0-incubating-src.tar.gz
> $ cd apache-doris-0.14.0-incubating-src
> $ sh build.sh
> 
> Best Regards,
> Yang Zhengguo

— 
Zhenxu Ke (柯振旭)
GitHub @kezhenxu94


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

Re: [VOTE] Release Apache Liminal (incubating) 0.0.1rc5-INCUBATING

[kezhenxu94@apache]

Hi, there is a dedicated license header for ASF projects [1], while I saw you 
are still using a common license header [2].

Also, I cannot verify the checksum via `shasum -a 512 -c 
apache-liminal-0.0.1rc5-INCUBATING-source.tar.gz.sha512`, error message is 
`shasum: apache-liminal-0.0.1rc5-INCUBATING-source.tar.gz.sha512: no properly 
formatted SHA checksum lines found`, although the checksum is correct, I have 
to generate the checksum and compare myself, so if you could save your checksum 
via `shasum -a 512 apache-liminal-0.0.1rc5-INCUBATING-source.tar.gz > 
apache-liminal-0.0.1rc5-INCUBATING-source.tar.gz.sha512` so that others can 
verify it easily with `shasum -a 512 -c 
apache-liminal-0.0.1rc5-INCUBATING-source.tar.gz.sha512`.

Third, there is no “incubating” in the README.md file [1].

I’ve checked

- LICENSE and NOTICE files are in src tar ball and .whl
- .asc, .sha512 checked
- DISCLAIMER file exists

[1] https://www.apache.org/legal/src-headers.html#headers
[2] http://apache.org/foundation/license-faq.html#Apply-My-Software
[3] https://github.com/apache/incubator-liminal

— 
Zhenxu Ke (柯振旭)
GitHub @kezhenxu94

> On Feb 3, 2021, at 20:12, Lior Schachter  wrote:
> 
> Hi All,
> We would like to have a third round of vote for the first release of
> Apache Liminal (Incubating), after fixing the issues identified at the
> previous round.
> 
> This release enables seamless Liminal installation in Local mode and
> in AWS cloud to execute machine-learning pipelines.
> 
> Liminal community vote and result threads:
> Vote:
> https://lists.apache.org/thread.html/r536fafe3328b23b6b37bd7f9dbd1e2e107b4e1435972bd807696781f%40%3Cdev.liminal.apache.org%3E
> 
> Result:
> https://lists.apache.org/thread.html/r12ad1e9729e385cf9dcdf2eb9f09aace64c1e100634b40a1c2393a78%40%3Cdev.liminal.apache.org%3E
> 
> Installation and testing instructions can be found in the README included.
> 
> The release files, including signatures, digests, etc. can be found at:
> 
> https://dist.apache.org/repos/dist/dev/incubator/liminal/0.0.1rc5-INCUBATING/
> 
> The tag to be voted on:
> 
> https://github.com/apache/incubator-liminal/releases/tag/0.0.1rc5-INCUBATING
> 
> The SHA512 Checksum for these artifacts is:
> 
> apache-liminal-0.0.1rc5-INCUBATING-source.tar.gz:
> BF86B430 D431E433 DB1E6D8E 9917F1B3 AF7BF11A B734ED8C 5AE2C2B4
> 606F7891 F8F65225 C3DAD172 DB0FDE0F 8AE68DA8 E67994AB 306726D4
> 6FED5CF6 A1666CED
> 
> Release artifacts are signed with the following key:
> 
> https://dist.apache.org/repos/dist/dev/incubator/liminal/KEYS
> 
> For more information about the contents of this release,
> see:https://issues.apache.org/jira/projects/LIMINAL/versions/12349599
> 
> Please vote on releasing this package as Apache Liminal
> 0.0.1rc5-INCUBATING. A majority of at least 3 +1 PMC votes are cast.
> 
> [ ] +1 Release this package as Apache Liminal 0.0.1rc5
> [ ] +0 No opinion
> [ ] -1 Do not release this package because ...
> 
> Regards,
> Lior Schachter



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

Re: [VOTE] Graduate Apache Ratis as TLP Project

[kezhenxu94@apache]

+1 non-binding. Good luck!

— 
Zhenxu Ke (柯振旭)
GitHub @kezhenxu94

> On Jan 30, 2021, at 04:32, Uma gangumalla  wrote:
> 
> Dear Incubator Community,
> 
> We have discussed Apache Ratis Podling graduation in the incubator general
> DISCUSS thread[1] and We did not see any objections to proceed for voting.
> Here is the official vote for graduating Apache Ratis project as TLP.
> 
> Please provide your in the following options:
> [ ] +1 - Recommend graduation of Apache Ratis as a TLP
> [ ]  0 - I don't feel strongly about it, but don't object
> [ ] -1 - Do not recommend graduation of Apache Ratis because...
> 
> The VOTE will open for at least 72 hours.
> 
> Just to summarize again:
> Apache Ratis project is a very active project and the community has grown
> well by following the Apache way in the process. It produced several
> releases by having diverse people as release managers. I and the community
> strongly believe that it's ready for graduation.
> 
> The Apache Ratis project has been an Apache incubator project for nearly 3
> year. Since then the community has grown and followed Apache Way. Some
> highlights include:
> * 7 releases given ( including 1.0.0 and 0.0.1 alpha ) by having
> different people as release managers
> * 50 contributors ( from report)
> * 28 committers
> * More than 1161 Jiras created, 905 resolved or closed
> * > 293 pull requests in github
> * One of the biggest positives for this community is that most of the
> members in this community have a lot of experience in other Apache projects
> already.
> 
> Some additional note about the resolution below:
> The current PPMC will be transitioned to the PMC. We have invited some of
> the mentors in the current PPMC who like to stay involved.
> We are also adding Siddharth and Jie Wang into PMC as we believe they are
> committed to the project and a good addition to PMC.
> 
> We have already voted for Ratis TLP in the Ratis Podling community. Please
> find the voting threads for reference. Ratis PPMC DISCUSS thread: [2],
> Ratis PPMC Vote: [3] and Ratis Community: [4]
> 
> To make easy for you to review, here is the *resolution text*[5] copied:
> ==
> Establish the Apache Ratis 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 java implementation for RAFT consensus protocol.
> 
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Ratis Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
> 
> RESOLVED, that the Apache Ratis Project be and hereby is responsible for
> the creation and maintenance of software related to A java
> implementation for RAFT consensus protocol; and be it further
> 
> RESOLVED, that the office of "Vice President, Apache Ratis" 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 Ratis
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache Ratis 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 Ratis Project:
> 
> * Anu Engineer  [Hadoop, Ozone PMC,
> Incubator Committer]
> * Arpit Agarwal [ ASF Member, Hadoop, Ozone,
> Incubator PMC]
> * Enis Soztutar [ASF Member, Hadoop, HBase,
> Incubator PMC and also PMC in curator, gora, phoenix]
> * Hanisha Koneru[Hadoop, Ozone PMC,
> Incubator Committer]
> * Jie Wang  [Incubator, Ozone Committer]
> * Jing Zhao [Hadoop PMC, Incubator Committer]
> * Jitendra Nath Pandey   [ASF Member, Hadoop, Ozone,
> Incubator PMC and also PMC in ambari, atlas, tez]
> * Josh Elser [ASF Member, HBase, Incubator
> PMC, and also PMC in accumulo, calcite, fluo, phoenix, rya]
> * Lokesh Jain   [Hadoop, Ozone PMC, Incubator
> Committer]
> * Marton Elek[Hadoop, Ozone PMC, Incubator
> Committer]
> * Mingliang Liu  [Hadoop PMC, Incubator
> Committer]
> * Mukul Kumar Singh  [Hadoop, Ozone PMC, Incubator
> Committer]
> * Shashikant Banerjee   [Hadoop, Ozone PMC,
> Incubator Committer]
> * Siddharth Wagle[Ambari, Ozone PMC, Hadoop,
> Incubator Committer]
> * Tsz-wo

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

[kezhenxu94@apache]

+1 non-binding

ECharts is one of my favorite visualization projects :)

— 
Zhenxu Ke (柯振旭)
GitHub @kezhenxu94

> On Nov 23, 2020, at 4:28 PM, Ovilia  wrote:
> 
> Hi everyone,
> 
> After discussion with the community [1], and a positive vote result [2] and
> the
> discussion under general mailing list [6], we believe
> ECharts is ready for graduation to a TLP, and we'd like to call on the vote
> to
> graduate Apache ECharts as TPL.
> 
> This is a formal voting thread about Apache ECharts's graduation, please
> Vote:
> [ ] +1 - Recommend graduation of Apache ECharts as a TLP
> [ ]  0 - I don't feel strongly about it, but don't object
> [ ] -1 - Do not recommend graduation of Apache ECharts because...
> 
> The VOTE will open for at least 72 hours.
> <https://www.timeanddate.com/countdown/vote?iso=20201126T1435=237=%5BVOTE%5D+Graduate+Apache+ECharts+as+TLP=serif=1>
> https://www.timeanddate.com/countdown/vote?iso=20201126T1635=237=Graduate+Apache+ECharts+as+TLP=serif=1
> 
> -----
> 
> X. Establish the Apache ECharts 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 charting and data visualization
> library written in JavaScript.
> 
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> Committee (PMC), to be known as the "Apache ECharts Project",
> be and hereby is established pursuant to Bylaws of the
> Foundation; and be it further
> 
> RESOLVED, that the Apache ECharts Project be and hereby is
> responsible for the creation and maintenance of software
> related to a charting and data visualization
> library written in JavaScript; and be it further
> 
> RESOLVED, that the office of "Vice President, Apache ECharts" 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 ECharts Project, and to have primary responsibility
> for management of the projects within the scope of
> responsibility of the Apache ECharts 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 ECharts Project:
> 
>* Houjin Huang  
>* Deqing Li 
>* Dong Rui  
>* Kener Linfeng 
>* Kevin A. McGrail  
>* Wenli Zhang   
>* Shen Yi   
>* Shuang Su 
>* Siwen Su  
>* Junting Wang      
>* Zhongxiang Wang   
>* Dave Fisher   
>* Sheng Wu  
>* Zak Wu
> 
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Wenli Zhang
> be appointed to the office of Vice President, Apache ECharts, 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 initial Apache ECharts PMC be and hereby is
> tasked with the creation of a set of bylaws intended to
> encourage open development and increased participation in the
> Apache ECharts Project; and be it further
> 
> RESOLVED, that the Apache ECharts Project be and hereby
> is tasked with the migration and rationalization of the Apache
> Incubator ECharts podling; and be it further
> 
> RESOLVED, that all responsibilities pertaining to the Apache
> Incubator ECharts podling encumbered upon the Apache Incubator
> Project are hereafter discharged.
> 
> --
> 
> A few points to assist in the discussion:
> 
> - Released 9 official Apache releases by 3 release managers [3]
> - Voted in 9 committers including 3 PPMC members
> - Achieved 43556 stars (and counting) on GitHub
> - Apache suitable name search has been approved [4]
> - Completed the Podling Maturity Assessment, all items are passed [5]
> - Our PPMC is diverse and consists of members from 9 organizations
> - There have been 143 contributors to the codebase, 82 of whom contributed
> during incubation
> - Closed 11033+ issues
> - Merged 603+ pull requests
> 
> We've resolved all branding issues which include Logo, GitHub repo,
> documentation, website, and others.
> 
> Thank you!
> 
> *Ovilia*
> 
> [1]
> https://lists.apache.org/thread.html/rf05e9dfa1aec1ac072c71c9cba882a59c9c57f4f89723da68e96de01%40%3Cdev.echarts.apache.org%3E
> [2]
> https:/

Re: Re: [VOTE] Release Apache Doris 0.13.0-incubating-rc03

[apache]

+1 (non-binding)


I checked:
[x] Download links are valid.
[x] Checksums and PGP signatures are valid.
[x] Source code artifacts have correct names matching the current release.
[x] LICENSE and NOTICE files are correct for the repository[1].


From: ling miao 
Sent: Wednesday, October 21, 2020 14:29
To: general@incubator.apache.org 
Subject: Re: Re: [VOTE] Release Apache Doris 0.13.0-incubating-rc03

The vote on Apache Doris (incubating) version 0.13 has been opened.
Looking forward your votes ^0^

Ling Miao

陈明雨  于2020年10月16日周五 下午9:03写道：

> +1 (non-binding)
>
>
> I checked:
> [x] Download links are valid.
> [x] Checksums and PGP signatures are valid.
> [x] Source code artifacts have correct names matching the current release.
> [x] LICENSE and NOTICE files are correct for the repository[1].
> [x] All files have license headers if necessary[2].
> [x] No compiled archives bundled in source archive.
> [x] Building is OK
>
>
> [1] The content about MySQL and LZO in thirdparty/LICENSE need to be
> modified. And it has been modified in PR:
> https://github.com/apache/incubator-doris/pull/4740
> [2] Some of files does not contain license header, those are some test
> files, or the licenses are statemented in LICENSE.txt. So they looks good
> to me.
>
>
>
> --
>
> 此致！Best Regards
> 陈明雨 Mingyu Chen
>
> Email:
> chenmin...@apache.org
>
>
>
>
>
> 在 2020-10-16 10:57:40，"ling miao"  写道：
> >The vote on Apache Doris (incubating) version 0.13 has been opened.
> >Welcome to vote ^0^
> >
> >Ling Miao
> >
> >ling miao  于2020年10月14日周三 下午7:22写道：
> >
> >> Thanks for voting.
> >> Regarding the license file in third party, we have changed the
> description
> >> in this pr [https://github.com/apache/incubator-doris/pull/4740]
> >>
> >> Ling Miao
> >>
> >> ling miao  于2020年10月12日周一 下午4:28写道：
> >>
> >>> The vote has been opened. Welcome to vote ^0^
> >>>
> >>> Ling Miao
> >>>
> >>> ling miao  于2020年10月9日周五 上午11:50写道：
> >>>
> >>>> Hi all,
> >>>>
> >>>> Please review and vote on Apache Doris 0.13.0-incubating-rc03 release.
> >>>>
> >>>> Apache Doris is an MPP-based interactive SQL data warehousing for
> >>>> reporting and analysis.
> >>>>
> >>>> The Apache Doris community has voted on and approved this release:
> >>>>
> >>>>
> https://lists.apache.org/thread.html/rcaa6e8926c6f9ed11743c3d3b9265f78a5b2f2e1b61c3964e0718c8c%40%3Cdev.doris.apache.org%3E
> >>>>
> >>>> The vote result email thread:
> >>>>
> >>>>
> https://lists.apache.org/thread.html/rceaf95cdfc3a2ec5a39ad8964cd19319d0f65d51a3e979ac973a5c0e%40%3Cdev.doris.apache.org%3E
> >>>>
> >>>> The release candidate has been tagged in GitHub as 0.13.0-rc03,
> >>>> available here:
> >>>> https://github.com/apache/incubator-doris/releases/tag/0.13.0-rc03
> >>>>
> >>>> Thanks to everyone who has contributed to this release, and there is a
> >>>> simple release notes can be found here:
> >>>> https://github.com/apache/incubator-doris/issues/4370
> >>>>
> >>>> The artifacts (source, signature and checksum) corresponding to this
> >>>> release candidate can be found here:
> >>>>
> https://dist.apache.org/repos/dist/dev/incubator/doris/0.13/0.13.0-rc3/
> >>>>
> >>>> This has been signed with PGP key 517E5B28, corresponding to
> >>>> lingm...@apache.org.
> >>>> KEYS file is available here:
> >>>> https://dist.apache.org/repos/dist/dev/incubator/doris/KEYS
> >>>> It is also listed here:
> >>>> https://people.apache.org/keys/committer/lingmiao.asc
> >>>>
> >>>> The vote will be open for at least 72 hours.
> >>>> [ ] +1 Approve the release
> >>>> [ ] +0 No opinion
> >>>> [ ] -1 Do not release this package because ...
> >>>>
> >>>> To verify and build, you can refer to following instruction:
> >>>>
> >>>> Firstly, you must be install and start docker service, and then you
> >>>> could build Doris as following steps:
> >>>>
> >>>> Step1: Pull the docker image with Doris building environment
> >>>> $ docker pull apachedoris/doris-dev:build-env-1.2
> >>>> You can check it by listing images, its size is about 3.2 GB.
> >>>>
> >>>> Step2: Run the Docker image
> >>>> You can run image directly:
> >>>> $ docker run -it apachedoris/doris-dev:build-env-1.2
> >>>>
> >>>> Step3: Download Doris source
> >>>> Now you should in docker environment, and you can download Doris
> source
> >>>> package.
> >>>> (If you have downloaded source and it is not in image, you can map its
> >>>> path to image in Step2.)
> >>>> $ wget
> >>>>
> https://dist.apache.org/repos/dist/dev/incubator/doris/0.13/0.13.0-rc3
> >>>> /apache-doris-0.13.0-incubating-src.tar.gz
> >>>>
> >>>> Step4: Build Doris
> >>>> Now you can decompress and enter Doris source path and build Doris.
> >>>> $ tar zxvf apache-doris-0.13.0-incubating-src.tar.gz
> >>>> $ cd apache-doris-0.13.0-incubating-src
> >>>> $ sh build.sh
> >>>>
> >>>> Best Regards,
> >>>> Ling Miao
> >>>>
> >>>
>

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

[john@apache]

+1

On Thu, Nov 1, 2018 at 6:03 PM Jean-Baptiste Onofré  wrote:

> +1 (binding)
>
> Regards
> JB
>
> Le 1 nov. 2018 à 14:03, à 14:03, Willem Jiang  a
> écrit:
> >+1 binding.
> >It's good to see griffin is ready to graduate.
> >
> >Willem Jiang
> >
> >Twitter: willemjiang
> >Weibo: 姜宁willem
> >
> >On Thu, Nov 1, 2018 at 3:31 PM William Guo  wrote:
> >>
> >> +dev
> >>
> >> -- Forwarded message -
> >> From: William Guo 
> >> Date: Thu, Nov 1, 2018 at 11:21 AM
> >> Subject: [VOTE] Graduate Apache Griffin (incubating) as a TLP
> >> To: 
> >>
> >>
> >> Hi all,
> >>
> >> Given that we've got positive feedback on the DISCUSS
> >> thread, after we had made some changes based on DISCUSS feedback.
> >> I'd like to start an official VOTE thread now.
> >>
> >>
> >> Please vote on the resolution pasted below to graduate
> >> Apache Griffin from the incubator to the top level project.
> >>
> >> [ ] +1 Graduate Apache Griffin from the Incubator.
> >> [ ] +0 Don't care.
> >> [ ] -1 Don't graduate Apache Griffin from the Incubator because...
> >>
> >> This vote will be open for at least 72 hours.
> >>
> >>
> >> Many thanks to our mentors and everyone else for their support,
> >>
> >> William Guo (on behalf of the Apache Griffin PPMC).
> >>
> >>
> >> ## Resolution to create a TLP from graduating Incubator podling
> >>
> >> X. Establish the Apache Griffin 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 data quality solution for big data, including both
> >streaming
> >> and batch mode.
> >>
> >>
> >> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> >> (PMC), to be known as the "Apache Griffin Project", be and hereby is
> >> established pursuant to Bylaws of the Foundation; and be it further
> >>
> >> RESOLVED, that the Apache Griffin Project be and hereby is
> >> responsible for the creation and maintenance of software related to
> >> a data quality solution for big data, including both streaming and
> >batch
> >> mode;
> >> and be it further
> >>
> >> RESOLVED, that the office of "Vice President, Apache Griffin" 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
> >> Griffin Project, and to have primary responsibility for management
> >> of the projects within the scope of responsibility of the Apache
> >> Griffin 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 Griffin
> >Project:
> >>
> >> * Alex Lv 
> >> * Deyi Yao 
> >> * Eugene Liu 
> >> * Grant Guo 
> >> * He Wang 
> >> * Henry Saputra 
> >> * Jason Liao 
> >> * John Liu 
> >> * Juan Li 
> >> * Liang Shao 
> >> * Lionel Liu 
> >> * Luciano Resende 
> >> * Nick Sokolov 
> >> * Shawn Sha 
> >> * Vincent Zhao 
> >> * William Guo 
> >> * Yuqin Xuan 
> >>
> >> NOW, THEREFORE, BE IT FURTHER RESOLVED, that William Guo be
> >> appointed to the office of Vice President, Apache Griffin, 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 Griffin Project be and hereby is tasked
> >> with the migration and rationalization of the Apache Incubator
> >> Griffin podling; and be it further
> >>
> >> RESOLVED, that all responsibilities pertaining to the Apache
> >Incubator
> >> Griffin podling encumbered upon the Apache Incubator PMC are
> >> here after discharged.
> >
> >-
> >To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >For additional commands, e-mail: general-h...@incubator.apache.org
>

Re: [VOTE] Resolution to graduate Apache FreeMarker to TLP

[Apache]

+1 (binding)

Ralph

> On Feb 19, 2018, at 3:45 AM, Jacopo Cappellato <jaco...@apache.org> wrote:
> 
> Hi all,
> 
> The FreeMarker community has discussed [1] and voted [2] positively on
> graduating to a top level project (TLP). The resolution for the graduation
> has been proposed and discussed in this list [3].
> Information about FreeMarker can be found in the status page [4],
> in the project maturity model [5] and in the website [6].
> 
> I am now calling a VOTE to ask the IPMC to recommend the resolution to the
> ASF Board:
> the proposed resolution can be found at the bottom of this email.
> The vote will be open for 72 hours.
> 
> [ ] +1 recommend to the Board the resolution to graduate Apache FreeMarker
> to a TLP
> [ ] +0 no opinion
> [ ] -1 don't graduate Apache FreeMarker to a TLP (please specify a reason)
> 
> Thanks,
> Jacopo Cappellato
> 
> References:
> [1] Community graduation discussion: https://s.apache.org/gYMw
> [2] Community graduation vote: https://s.apache.org/MNdd
> [3] Incubator resolution discussion: https://s.apache.org/xdI3
> [4] Project status page:
> http://incubator.apache.org/projects/freemarker.html
> [5] Project maturity model: https://s.apache.org/ixlR
> [6] Freemarker website: https://freemarker.apache.org/
> 
> The proposed Resolution of the Apache FreeMarker project:
> 
> --
> 
> Establish the Apache FreeMarker 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 template engine.
> 
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> Committee (PMC), to be known as the "Apache FreeMarker Project",
> be and hereby is established pursuant to Bylaws of the
> Foundation; and be it further
> 
> RESOLVED, that the Apache FreeMarker Project be and hereby is
> responsible for the creation and maintenance of software
> related to a template engine, and be it further
> 
> RESOLVED, that the office of "Vice President, Apache FreeMarker" 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 FreeMarker Project, and to have primary responsibility
> for management of the projects within the scope of
> responsibility of the Apache FreeMarker 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 FreeMarker Project:
> 
>  * Dániel Dékány   <ddek...@apache.org>
>  * David E. Jones<jone...@apache.org>
>  * Jacopo Cappellato   <jaco...@apache.org>
>  * Jacques Le Roux <jler...@apache.org>
>  * Nan Lei     <nan...@apache.org>
>  * Sergio Fernández<wik...@apache.org>
>  * Woonsan Ko  <woon...@apache.org>
> 
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Dániel Dékány
> be appointed to the office of Vice President, Apache FreeMarker,
> 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 FreeMarker Project be and hereby
> is tasked with the migration and rationalization of the Apache
> Incubator FreeMarker podling; and be it further
> 
> RESOLVED, that all responsibilities pertaining to the Apache
> Incubator FreeMarker podling encumbered upon the Apache Incubator
> Project are hereafter discharged.
> 
> --



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

Re: [VOTE] Drop incubating requirement of Maven artifacts

[Apache]

-1

Ralph

> On Jan 2, 2017, at 10:22 AM, John D. Ament  wrote:
> 
> All,
> 
> I'm calling to vote on a proposed policy change.  Current guide at [1]
> indicates that maven artifacts should include incubator (or incubating) in
> the version string of maven artifacts.  Its labeled as a best practice, not
> a requirement and is not a policy followed on other repository management
> tools (e.g. PyPi).
> 
> I therefore push forward that the incubator will cease expecting java-based
> projects to publish artifacts with "-incubating" in the version string,
> with the understanding that:
> 
> - Incubating is a term used to refer to a project's stability, not a
> release's stability.  It is generally understood that incubating projects
> are not necessarily immature, but may have a potential of failing to become
> a TLP.
> - Podling releases are endorsed, the podling itself is not endorsed.  We
> will not approve releases that are blatantly against ASF policies.
> 
> 
> [ ] +1 Drop the -incubator/-incubating expectation of maven projects
> [ ] +/0
> [ ] -1 Don't drop because
> 
> 
> [1]:
> http://incubator.apache.org/guides/release-java.html#best-practice-maven



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

Re: Request to join Apache Streams (Incubating) as Mentor

[apache]

+1 (non-binding)

On September 23, 2016 at 12:51:30 PM, Suneel Marthi (smar...@apache.org) wrote:
 

Re: [VOTE] Retire Apache Streams to the attic

[apache]

On September 22, 2016 at 5:05:39 PM, Ate Douma (a...@douma.nu) wrote:
On 2016-09-21 18:28, apache wrote:  
> I remain committed to building and sharing open-source software for social 
> web  
> data interoperability. Participating in the incubator process has taught me a 
>  
> lot, and I would like the keep the project operating at Apache, but as Ate  
> points out the community around this podling has never been healthy and has 
> all  
> but disappeared in 2016.  
>  
> I would very much welcome anyone interested in this problem to volunteer as a 
>  
> mentor or contributor. With even a few new committed active participants I 
> can  
> envision the project graduating to TLP. Without fresh initiative, it should 
> be  
> retired. Perhaps some of the codebase will be useful elsewhere.  
>  
Hi Steve,  

Although the retirement for Apache Streams hasn't been formally decided, as  
there hasn't been any further signal for support or initiative, it does look  
like we'll have to draw that conclusion soon.  

You really tried your best in making Apache Streams a success, and with the  
openness and focus fitting for the Apache Software Foundation.  
That it didn't work out as anticipated and hoped for is of course  
disappointing, but sometimes that's just the way things goes.  


Thanks for saying so.  There has been a lot of good work from the committers 
involved but not all efforts ultimately succeed.  

I definitely hope you will stick to it and at the ASF, contributing to and  
joining other projects because you clearly demonstrated to be an fine Apache  
committer. And not just because you are a nice and really smart guy, but also  
as a great advocate of the Apache Way, at ApacheCons and other places!  


Thanks for saying so.  I’m not going anywhere.  #bigdata is what I do and ASF 
is where it happens.

> I’ll be submitting a (potentially final) release candidate later today. 

I'll take a look and review the release candidate over the weekend, which if OK 
and when receiving +3 from the IPMC, indeed might become a final incubating 
release for Apache Stream.
Thanks.



I'll follow up later on the VOTE thread for the release candidate on 
d...@streams.incubator.apache.org 

Kind regards, Ate 

> 
> Steve Blackmon 
> sblack...@apache.org 
> 
> On September 19, 2016 at 10:25:16 AM, Ate Douma (a...@douma.nu 
> <mailto:a...@douma.nu>) wrote: 
> 
>> On 2016-09-19 17:09, Suneel Marthi wrote: 
>> > I am sorry to be reading this, but I was at Steve Blackmon's talk last 
>> > week 
>> > in Berlin at Flink forward about using Streams + Flink. 
>> > 
>> > It was a very interesting talk and I chatted with Steve briefly about the 
>> > Streams project. 
>> 
>> Good to hear that! 
>> I wasn't aware Steve was presenting about Streams in Berlin. 
>> 
>> > 
>> > Is there absolutely no chance of reviving this project or giving the 
>> > project some more time before calling the attic ? 
>> 
>> Sure there is a chance, but for that the project needs active community 
>> involvement. Which has been lacking for quite a while now. 
>> Community building and involvement really is the primary problem for the 
>> project with only a single active member, which is not sustainable. 
>> However, if you are willing and able to get actively involved, and rally 
>> some 
>> additional community involvement as well, then I'd be happy to 
>> postpone/cancel 
>> the retirement VOTE for now. 
>> 
>> I suggest to head over to d...@streams.incubator.apache.org, let us know 
>> what you can and will do for the project, and see how that works out. 
>> 
>> Regards, Ate 
>> 
>> > 
>> > 
>> > 
>> > 
>> > On Mon, Sep 19, 2016 at 4:58 PM, Ate Douma <a...@douma.nu> wrote: 
>> > 
>> >> On 2016-09-19 16:33, Ate Douma wrote: 
>> >> 
>> >>> On 2016-09-19 15:44, John D. Ament wrote: 
>> >>> 
>> >>>> Ate, 
>> >>>> 
>> >>>> Please also note the instructions from the incubator's retirement 
>> >>>> guide. 
>> >>>> 
>> >>>> http://incubator.apache.org/guides/retirement.html 
>> >>>> 
>> >>> 
>> >>> Right. 
>> >>> Thanks for pointing this out John. 
>> >>> 
>> >>> I've never before had to handle a podling retirement and overlooked this 
>> >>> requires different handling from a TLP retirement. 
>> >>> And with slightly different consequences, e.g. website will be taken 
>> >>> down, 
>> >>> instead

Re: [VOTE] Retire Apache Streams to the attic

[apache]

I remain committed to building and sharing open-source software for social web 
data interoperability.  Participating in the incubator process has taught me a 
lot, and I would like the keep the project operating at Apache, but as Ate 
points out the community around this podling has never been healthy and has all 
but disappeared in 2016. 

I would very much welcome anyone interested in this problem to volunteer as a 
mentor or contributor.  With even a few new committed active participants I can 
envision the project graduating to TLP.  Without fresh initiative, it should be 
retired.  Perhaps some of the codebase will be useful elsewhere.

I’ll be submitting a (potentially final) release candidate later today.

Steve Blackmon
sblack...@apache.org
On September 19, 2016 at 10:25:16 AM, Ate Douma (a...@douma.nu) wrote:

On 2016-09-19 17:09, Suneel Marthi wrote:  
> I am sorry to be reading this, but I was at Steve Blackmon's talk last week  
> in Berlin at Flink forward about using Streams + Flink.  
>  
> It was a very interesting talk and I chatted with Steve briefly about the  
> Streams project.  

Good to hear that!  
I wasn't aware Steve was presenting about Streams in Berlin.  

>  
> Is there absolutely no chance of reviving this project or giving the  
> project some more time before calling the attic ?  

Sure there is a chance, but for that the project needs active community  
involvement. Which has been lacking for quite a while now.  
Community building and involvement really is the primary problem for the  
project with only a single active member, which is not sustainable.  
However, if you are willing and able to get actively involved, and rally some  
additional community involvement as well, then I'd be happy to postpone/cancel  
the retirement VOTE for now.  

I suggest to head over to d...@streams.incubator.apache.org, let us know  
what you can and will do for the project, and see how that works out.  

Regards, Ate  

>  
>  
>  
>  
> On Mon, Sep 19, 2016 at 4:58 PM, Ate Douma <a...@douma.nu> wrote:  
>  
>> On 2016-09-19 16:33, Ate Douma wrote:  
>>  
>>> On 2016-09-19 15:44, John D. Ament wrote:  
>>>  
>>>> Ate,  
>>>>  
>>>> Please also note the instructions from the incubator's retirement guide.  
>>>>  
>>>> http://incubator.apache.org/guides/retirement.html  
>>>>  
>>>  
>>> Right.  
>>> Thanks for pointing this out John.  
>>>  
>>> I've never before had to handle a podling retirement and overlooked this  
>>> requires different handling from a TLP retirement.  
>>> And with slightly different consequences, e.g. website will be taken down,  
>>> instead of flagged as being retired.  
>>>  
>>> So, to do this proper, I'll first cancel the vote thread on dev@streams  
>>> and open a new [FINAL][DISCUSS] thread for retirement again, this  
>>> time also pointing to the podling retirement page.  
>>> This way at least everyone on that list will have a proper notice what  
>>> the retirement entails.  
>>> (not that I expect a different outcome, but there is no rush either)  
>>>  
>>  
>> Reading the podling retirement guide a bit more thoroughly, I think I it is  
>> sufficient to restart the [VOTE] thread for retirement on dev@streams  
>> with the  
>> link to the podling retirement guide.  
>>  
>>  
>>  
>>> And after that I'll open the final [VOTE] for retirement here on general@  
>>>  
>>> Ate  
>>>  
>>>  
>>>> John  
>>>>  
>>>> On Mon, Sep 19, 2016 at 6:37 AM Ate Douma <a...@douma.nu> wrote:  
>>>>  
>>>> FYI, I've started below vote to retire Apache Streams, after I first  
>>>>> initiated a  
>>>>> [discuss] thread more than a week ago, which resulted in zero feedback.  
>>>>>  
>>>>> Ate  
>>>>> (Streams mentor)  
>>>>>  
>>>>>  Forwarded Message   
>>>>> Subject: [VOTE] Retire Apache Streams to the attic  
>>>>> Date: Sun, 18 Sep 2016 23:27:11 +0200  
>>>>> From: Ate Douma <a...@douma.nu>  
>>>>> To: d...@streams.incubator.apache.org <d...@streams.incubator.apache.org> 
>>>>>  
>>>>>  
>>>>> As a final follow up on the earlier [discuss] thread, lets formally  
>>>>> vote on  
>>>>> retiring Apache Streams and move it to the attic.  
>>>>>  
>>>>> The process is described at http://attic.apache.org/process.html  
>>>>>  
>>>>> [ ] +1 Move Streams to the Attic  
>>>>> [ ] ±0 Proceed according to the majority  
>>>>> [ ] -1 Do not move Streams to the Attic, because... [please add  
>>>>> justification]  
>>>>>  
>>>>> Ate  
>>>>>  
>>>>>  
>>>>>  
>>>>> -  
>>>>> 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  
>>  
>>  
>  

[ANNOUNCE] Apache Johnzon 0.1-incubating released

[Hendrik Saly (apache)]

The Apache Johnzon team is happy to announce the first release of
Apache Johnzon - version 0.1-incubating.

Apache Johnzon is an implementation of JSR-353 (JavaTM API for JSON
Processing) and provides additionally a set of useful extension for
this specification like an object mapper and some JAX-RS providers.

For more details please refer to:

http://incubator.apache.org/projects/johnzon.html

You can download our source distribution from an Apache mirror site:

http://www.apache.org/dyn/closer.cgi/incubator/johnzon

Distribution artifacts are available using the Maven coordinates listed here:


https://repository.apache.org/content/repositories/releases/org/apache/johnzon


Kind regards,

The Apache Johnzon Team

-- 
Hendrik Saly
@hendrikdev22
PGP: 0x22D7F6EC

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

[ANNOUNCEMENT] Apache Flex 4.8.0-incubating Released

[Carol Frampton at Apache]

The Apache Flex community is pleased to announce the release of Apache
Flex 4.8.0-incubating!

Apache Flex is an application framework for easily building Flash
Platform-based applications for mobile devices, the browser and desktop.

This is the first release under the Incubator of the Apache Software
Foundation and represents the initial donation of Adobe Flex 4.6 by
Adobe System Inc.  Note that because Apache Flex is under incubation,
Apache Flex is not an official Apache Project, and this is not an
official Apache release.  For more information see the DISCLAIMER file
in the release.

This release marks the start of a new era for Flex. The future of Flex
is now driven by the community instead of a corporation.  Users can
have important bugs fixed or new features added by contributing the
code themselves.

Apache Flex is available in source form from the following download page:

 http://incubator.apache.org/flex/download.html

When downloading from a mirror site, please remember to verify the
downloads using signatures found on the Apache site:

 http://www.apache.org/dist/incubator/flex/KEYS

Apache Flex release packages are different from Adobe release packages.
For information on how to use Apache Flex with existing IDEs, see:

 http://incubator.apache.org/flex/packager.html

For more information on Apache Flex, visit the project home page:

 http://incubator.apache.org/flex/

Thank you for using Apache Flex,
The Apache Flex Community.





signature.asc
Description: OpenPGP digital signature

London Java Community Unconference

[Apache]

I just wanted to let you know about a ConCom approved event in London,  
UK this month. There will be an Apache Way talk and a few ASF projects  
will be there. Maybe your projects should be too?


As you may already have seen the London Java Community (LJC) are  
running their June Unconference is association with the ASF.  The LJC  
represent about 1000 Java developers from the London (UK) area, LJC  
members have various levels of understanding of open source and recent  
LJC events suggest that they are keen to learn more.


Apache is such a major player in the open source world but (incredible  
though it may seem) some people in the Java world still equate Apache  
with the http server project and have no understanding of the breadth,  
scope and culture of the ASF. In suggesting the unconference  
partnership the organisers goal is provide Apache committers with a  
platform and a different audience to the ones that already attend  
things like ApacheCon and to provide LJC members with an opportunity  
to gain a much broader understanding of the ASF.


The unconference organisers would be delighted to welcome anyone who  
can talk about any aspect of the ASF on June the 26th The sign up  
details are here:


http://skillsmatter.com/event/java-jee/london-java-community-unconference-02/zx-548

Ross

Sent from my mobile device.

Re: [commons-ssl] - incubator / been a long time

[Filip at Apache]

nanoTime, like this one?

http://java.sun.com/j2se/1.5.0/docs/api/java/lang/System.html#nanoTime()

is there a difference?

Filip

Julius Davies wrote:

Hi, Commons Developers, Incubator,


I've been too busy over the last year to spend much time on incubating
not-yet-commons-ssl, but I just wanted to let you know that I will get
back into it this weekend.  I'll update the proposal (from a year ago
- blush!), and then find out who would still like to be involved.


[untouched for 1 year -- eek!]
http://wiki.apache.org/incubator/CommonsSSLProposal


I hope that Martin van den Bemt can still be the champion after all
this time.  Henri Yandell recently volunteered to be the mentor.


* * *


Now, totally OT, and unrelated  would you like better timestamps
on java, say microsecond or nanosecond?  I'm cooking something up.
The people at JSR 310 also know about this:


http://juliusdavies.ca/nanotime/



If you're interested, try downloading the zip file, building it, and
running the little test method, like so:

unzip nanotime.zip
cd nanotime
ant
java -jar build/nanotime.jar


It should print out something like this:

libjnano.so loaded!
2008-05-09/14:11:14.54500/PDT JavaTime
2008-05-09/14:11:14.545567057/PDT NativeTime1
2008-05-09/14:11:14.545606890/PDT NativeTime2



It's rough around the edges, and the code contains very few comments.
You may need to hack the build file a bit to get it to build properly
on your platform.  So far I've succeeded on building/running on the
following platforms without any fiddling:

Windows XP 32bit
Windows Vista 32bit
Linux 2.6 ppc 32bit
Linux 2.6 x86 64bit
Linux 2.6 x86 32bit
Linux 2.4 x86 32bit
Mac 10.5 x86 32bit
Solaris 10 sparc (64bit? not sure)

It builds and runs against Java4, Java5, and Java6 with no problems.


Some Notes:
--

* Ant is using exec to call gcc.

* The windows platforms need cygwin/mingw to build, but the jar file
created on any platform will run on win32, because I've stored a
pre-built win32 DLL in the zip.

* In other words, no matter what platform you build on, the jar file
will run on 32bit windows.

* The jar file will not run on non-windows unless you build from
source just for your platform.

* The native code is stored in the jar file.  On startup, Clock.java
copies the native code to ~/.nanotime/libjnano.so, and then loads it.

* Every time it starts up it deletes ~/.nanotime/libjnano.so, and
replaces it with the copy from the jar file.  This way a newer jar
file will (usually) overwrite the older native file.







  



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [DISCUSS] Re-election of podling committers before graduation

[Filip at Apache]

Bertrand Delacretaz wrote:

On Feb 3, 2008 7:36 AM, William A. Rowe, Jr. [EMAIL PROTECTED] wrote:

  

...Craig has a good point - maybe that 'pruning' process, to the
extent it's appropriate, should happen before they start the actual
graduation process?

The question is how, and it's something no established project has
ever figured out, nevermind our podlings :)...



Hence the suggestion that some of us discussed in December:
re-electing podling committers is a no-brainer for active people, and
gives others a chance to step out.
  
Make it part of the graduation for the contributors in the podling to 
decide if they want to continue or not. the folks who have made the 
podling successful enough to graduate should not have to be re-elected. 
In the other ASF projects, if a committer has not been active, (s)he 
gets a chance to decide if (s)he wants to step out, one does not start a 
process of re-electing active one. That seems so backwards.


Filip

-Bertrand

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



  



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [DISCUSS] Re-election of podling committers before graduation

[Filip at Apache]

I'd vote -1, if a project graduates, it does so cause the committer 
community is healthy and works well together, and all the other factors.
I don't see any reason why a community should have to be re-elected. It 
just doesn't make sense. Graduation out of incubator should not be a 
popularity contest, if the project can graduate, they have already 
proven themselves at that point


Filip

Bertrand Delacretaz wrote:

Hi,

Following up (finally) on the community diversity discussion of last
December [1], I propose to re-elect podling committers before a
project graduates.

If we agree, I'll start a vote to add the following text after the
Graduation Process title at
http://incubator.apache.org/guides/graduation.html#process :

*** Podling committers graduation ***
Once a podling is ready to graduate, its committers are re-elected,
according to the ASF's usual meritocracy rules.

The goal is to ensure that all Apache committers have gone through the
meritocracy filter, which does not apply to people included in a
podling's initial committers list, for obvious reasons.

The suggested process is to have podling committers (and mentors if
they want) self-nominate themselves, indicating why they believe they
should be included in the list of graduated committers. People who
were on the initial list of podling committers, but did not actively
contribute, are expected to step down at this point.

The PPMC votes to accept the nominations, subject to the usual voting
rules for committers.

The podling's mentors lead this process, usually with no involement of the IPMC.

The results of the committers graduation votes are include in the
podling's graduation request.
***

I think this reflects our discussions at [1], but let me know if I
forgot something!

-Bertrand

[1] http://markmail.org/message/xy57ghwdezq4w4pi

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



  



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Fwd: [VOTE] Erik Bengtson for Imperius committer

[Filip at Apache]

My vote, fhanik



For information, I'm blind copying incubator private alias.

[X] +1 offer Erik commit privileges in Imperius
[ ] -1 don't (why?)

Here's my enthusiastic +1

Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:[EMAIL PROTECTED]
P.S. A good JDO? O, Gasp!



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Proposal Draft]BlueSky-Wish to ADD

[Filip at Apache]

Yoav Shapira wrote:

Hi,
Cool proposal!  I have a couple of questions, just out of curiosity.

On 10/24/07, Ting Peng [EMAIL PROTECTED] wrote:
  

in China.  More than 40,000 students has benefited from it.  Our developing
website  is http://202.117.16.176/ , source code is also available.
All source code of this project is written by ourselves, no third
part components are included.



I could only see the source code for CWPlayer.  I download it, and it
seems to be written in Pascal.  Is that true?  (I have nothing for or
against Pascal, just hadn't seen anything written in Pascal in a few
years, so I wanted to ask) ;)
  

I believe it's written using Borland Delphi, Pascal on steroids.
I wonder if there is a compiler for this, it would suck to have open 
source code that you can't compile cause there is no compiler available :)
I know borland has a delphi explorer for free, with a compiler, but that 
not all extensions are available.

think it might be worth looking into

Filip

  

Currently, all developers of Blue Sky Distance Collaboration System
are not native speaker of  English.  But  we don't have any obstacles to
communicate in English on technical topics. We want to share our work
with people who is interested in it around the world. We want new
volunteers to make our team more diverse, active and creative.



I'm sure we'll be fine with respect to communications ;)

  

For this is our first candidate project to Apache Foundation. We are
grateful for your ideas!



As you know IBM has contributed a bunch of stuff to Apache in the past
(and present).  Are you part of IBM?  Do you need their (IBM legal
department) approval for this, and if so, have you already gotten
their approval?

Yoav

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



  



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Incubator Proposal: SPL

[Filip at Apache]

Brian McCallister wrote:


On Sep 17, 2007, at 5:57 AM, David L Kaminsky wrote:

Tomcat
-

We're open to suggestions regarding the order in which we add 
bindings to

APIs, and doing such bindings isn't terribly hard.  If Tomcat is
particularly critical as an early demonstration, we can add that to the
proposal.  And, of course, the code is (suppose to be) modular, so 
others

could at it at any time.


Lot more people deploy and manage large number of Tomcat instances 
than Geronimo instances.
just ping me fhanik at apache dot org when you wish to do Tomcat 
integration, I sometimes have a hard time follow all the general 
incubator threads.


Filip


-Brian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Incubator Proposal: SPL

[Filip at Apache]

Noel J. Bergman wrote:

We proposed to develop a policy-based management infrastructure that
automates administrative tasks by executing policies



Sounds good.  I will be curious to see the reaction from the HTTP Server
folks, but this sort of thing is very much needed in real-world deployments
of app servers.

  

The initial goals are to develop an SPL evaluation engine and
bindings to the APIs for [...]



What about Tomcat?
  
I'd be happy to help out with this piece, should the vote to incubation 
go through


Filip
  

Nominated Mentors
-Bill Stoddard([EMAIL PROTECTED])



Glad to see that Bill will have cycles for this.  :-)

Would you please take a look at lokahi (http://incubator.apache.org/lokahi)
and comment on any synergies that you see?

--- Noel



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



  




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Jini : Separate Governance and Implementation Projects

[Filip at Apache]

Sanjiva Weerawarana wrote:

On Tue, 2006-08-15 at 17:36 -0400, Jim Hurley wrote:
  

I'm not going to try and pull a Bill Clinton with it depends what the
definition of is is but I'd answer that I believe the Jini  
Community

views the project as *the* Jini implementation.

But *the* as in:  the main, the original, the most prominent,  
(what will be)
  the Community's implementation, and the one you'd recommend a  
developer

go grab to get going with Jini. But not *the* as in the only.



If the resulting code is in org.jini.* then I have no problem with this.

However, the current structure appears to be org.jini.* for APIs and
com.sun.something.* for implementation. Clearly that structure says
there can be multiple implementations - and in that case I'm against
putting the two parts together.
  
doesn't make sense, let me give you two examples, the latter being 
extremely obvious
1. in Tomcat we have javax.servlet.*, org.apache.catalina.*, 
org.apache.coyote.*, org.apache.jasper.*, javax.mail.*, javax.annotation.*
2. Harmony, are we saying that harmony couldn't implement 
java.lang.String and org.apache.harmony.strings.StringImpl?


Clearly harmony is a project for both spec and implementation, and yes, 
there are more than one implementation available, but that doesn't mean 
harmony doesn't create their own java.* library.


Filip



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


  



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Jini : Separate Governance and Implementation Projects

[Filip at Apache]

Bob Scheifler wrote:

Geir Magnusson Jr wrote:
  

We have a tradition, for good reason, for not giving our projects
technology domain ownership for implementations.  I'd never support
Apache EMail or Apache Web.



It would help me if you could explain how these existing TLP names
are different/OK: DB, Directory, Logging, Web Services, XML.
  

jini is a trademark
http://tess2.uspto.gov/bin/showfield?f=docstate=v6g57o.2.9

directory isn't

and although, there is an individual that has trademarked XML, I doubt 
that it is actually legally a thread to the acronym XML


Filip


- Bob

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


  



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Jini : Separate Governance and Implementation Projects

[Filip at Apache]

Noel J. Bergman wrote:

Craig.Russell wrote:

  

It would appear then that the Apache Jini podling would be the
[spec project], and the to be named podling the [implementation
project]. Fortunately, the incubator should be warmed up for a
naming discussion.



Apache JINI and Apache JINN?  Deliberate play on words, and related
sounds.
  

Apache Genie

rub my tummy for good luck!

--- Noel
  



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]