Ok, thanks Daniel!
Daniel Widdis 于2021年2月11日周四 下午2:10写道：
> To continue to provide clarity:
>
> The current version (7.5.11) still has AL2.0 licensing; I just downloaded
> it to confirm. Any version from 7.3.7 and newer (at this point in time) is
> an acceptable dependency.
>
> If Oracle choos
The project looks dead since a while
+1 for retirement (non-binding)
—Alex
Sent from my iPhone
> On 11. Feb 2021, at 06:27, Liu Ted wrote:
>
> +1 for retirement.
>
> Ted
>
> 在 2021 年 2月 月 11 日週四，時間：13:13 ， Ralph Goers
> 寫道： I don’t really see anything to discuss.
>
> Ralph
>
>> O
To continue to provide clarity:
The current version (7.5.11) still has AL2.0 licensing; I just downloaded it to
confirm. Any version from 7.3.7 and newer (at this point in time) is an
acceptable dependency.
If Oracle chooses to change the license again for future releases that could
pose a pr
Yes, restricting the use of its version number in the project is still a
relatively passive solution: if we want to upgrade the version, but the
corresponding version authorization is adjusted, our project still has
restrictions.
The biggest dependency of replacing this component lies in the
activ
Hi,
> 1. Can we meet the requirements of this open source agreement by
> restricting the version of this component to 7.X.Y?
> For Berkeley DB JE (Java Edition), this component itself is TubeMQ to store
> metadata and switch between active and standby. It is not very deep, but it
> need to take so
I believe that as long as you are using 7.3.7 or newer (such as the current
7.5.11 version) of the Java Edition you are fine to include this as a
dependency.
I will defer to more experienced people on this list on the most appropriate
language to indicate this minimum version and the JE spec
+1 for retirement.
Ted
在 2021 年 2月 月 11 日週四，時間：13:13 ， Ralph Goers 寫道：
I don’t really see anything to discuss.
Ralph
> On Feb 10, 2021, at 7:22 PM, Justin Mclean wrote:
>
> Hi,
>
> My message to the Samoa asking them to consider retirement got no response
> [1] so I this think it
Hi Daniel && Justin && all:
What should we do in this situation?
When we open sourced the project, we did a LICENSE analysis for all
dependent packages, and adjusted to exclude unfriendly protocol components;
for Berkeley DB JE (Java Edition), as Daniel said, the Berkeley DB JE (Java
Edition) LIC
I don’t really see anything to discuss.
Ralph
> On Feb 10, 2021, at 7:22 PM, Justin Mclean wrote:
>
> Hi,
>
> My message to the Samoa asking them to consider retirement got no response
> [1] so I this think it time to discuss their retirement. Are there any
> objections to returning the pro
Fair enough ;) No objection from my side.
Regards
JB
> Le 11 févr. 2021 à 05:57, jus...@classsoftware.com a écrit :
>
> Hi,
>
> Sorry I meant to say "Are there any objections to retiring the project?”
>
> Justin
> -
> To unsub
Hi,
Sorry I meant to say "Are there any objections to retiring the project?”
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
Agree to discuss the retirement.
Regards
JB
> Le 11 févr. 2021 à 03:22, Justin Mclean a écrit :
>
> Hi,
>
> My message to the Samoa asking them to consider retirement got no response
> [1] so I this think it time to discuss their retirement. Are there any
> objections to returning the proje
I believe there may be some confusion between Berkeley DB which is indeed GNU
AGPL v3, and Berkeley DB JE (Java Edition) which was previously GNU AGPL v3 but
switched to Apache License 2.0 with the 7.3.7 release.
Current Berkeley DB JE license is at [3]
3. https://www.oracle.com/downloads/licen
Hi,
> We should have discussed this issue [1], and in August 2020, I sent an
> email to berkeleydb-info...@oracle.com in accordance with the requirements
> of [2] to clarify my question, but it not responded to me. And the LICENSE
> of we choosed 7.3.7 berkeleydb, is licensed under Apache V2 lice
Hi Goson & Xiangdong
If you are going to deliver convenient binary(s), you definitely need
licenses to describe what libs you are included in.
I can see you have a LICENSE file in the binary, if this license includes
all license of your dependencies in the runtime, then it is fine.
Sheng Wu 吴晟
Tw
Hi @Justin Mclean and all:
Regarding the LICENSE issue of berkeleydb binary package:
In this case, can we choose to use it in accordance with the Apache V2
protocol?
We should have discussed this issue [1], and in August 2020, I sent an
email to berkeleydb-info...@oracle.com in accordance with
Hi @Justin Mclean :
Regarding the version of berkeleydb, see if the LICENSE description is OK
[1]?
Oracle mentioned in the Oracle Berkeley DB Licensing Information that the
dual license agreement adopted by their components.
We choose to use this component under Apache V2 protocol, at the same
Hi,
-1 (binding) I have not checked dates release but teh vote thread shows only
one PPMC (and no mentors) vote. Committer votes are not binding on release
votes. I would suggest you continue with the vote on your dev listuntill you
have enough PPMC votes and then bright it back here again.
Th
Hi,
My message to the Samoa asking them to consider retirement got no response [1]
so I this think it time to discuss their retirement. Are there any objections
to returning the project?
Thanks,
Justin
1.
https://lists.apache.org/thread.html/rb513f7ba5cc5dd1ba9adbf9fe8dbbb52db40066f04a9fed9f
Hi Xiangdong:
This place is indeed worth exploring: why do some software carry a binary
license, and some do not, what are the considerations for this? I mainly
refer to the components of Kafka, Pulsar, and Kylin.
It would be great if anyone can answer!
This berkeleydb-je is quite special: we us
+1 binding
1. Compiling passed
2. Rat passed
3. ASC checked
4. sha512 exist.
5. LICENSE, NOTICE, and DISCLAIMER exist.
Good luck and happy Chinese New Year.
Sheng Wu 吴晟
Twitter, wusheng1108
Kris Calvin 于2021年2月11日周四 上午9:32写道：
> Hello IPMC and DolphinScheduler Community,
>
> This is a call fo
Hello IPMC and DolphinScheduler Community,
This is a call for vote to release Apache DolphinScheduler (Incubating)
version 1.3.5
We now kindly request the Incubator IPMC members review and vote on this
incubator release.
Dolphin Scheduler is a distributed and easy-to-expand visual DAG workflow
s
Dear community,
This is a call for a releasing Apache MXNet (incubating) 2.0.0.alpha, release
candidate 2. Note that this is an Alpha release, which represents our first
project milestone on the road to MXNet 2 and is intended for bleeding-edge
developers working outside the project. [1]
Apache M
+1 non-binding. Congrats!
---
Xiangdong Huang
School of Software, Tsinghua University
Willem Jiang 于2021年2月9日周二 上午8:07写道：
> +1 (binding). It's good to see DolphinScheduler made this great
> improvement.
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
+ 1 non-binding
On Wed, Feb 10, 2021 at 8:10 AM Kevin Ratnasekera
wrote:
> +1 ( binding )
>
> On Wed, Feb 10, 2021 at 6:38 PM Adina Crainiceanu
> wrote:
>
> > +1 (non-binding)
> >
> > Adina
> >
> > On Wed, Feb 10, 2021 at 3:17 AM Christofer Dutz <
> christofer.d...@c-ware.de
> > >
> > wrote:
>
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-INCUBAT
+1 ( binding )
On Wed, Feb 10, 2021 at 6:03 PM kezhenxu94@apache
wrote:
> +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 gradu
+1 ( binding )
On Wed, Feb 10, 2021 at 6:38 PM Adina Crainiceanu wrote:
> +1 (non-binding)
>
> Adina
>
> On Wed, Feb 10, 2021 at 3:17 AM Christofer Dutz >
> wrote:
>
> > +1 (binding)
> >
> > Chris
> >
> > -Ursprüngliche Nachricht-
> > Von: Dave Fisher
> > Gesendet: Mittwoch, 10. Februa
+1 (non-binding)
Adina
On Wed, Feb 10, 2021 at 3:17 AM Christofer Dutz
wrote:
> +1 (binding)
>
> Chris
>
> -Ursprüngliche Nachricht-
> Von: Dave Fisher
> Gesendet: Mittwoch, 10. Februar 2021 01:01
> An: general@incubator.apache.org
> Betreff: Re: [VOTE] Graduate Apache Daffodil to a to
+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 proc
Hi,
+1 from me (binding).
I checked:
- Incubating in name
- DISCLAIMER-WIP exists
- LICENSE is fine
- NOTICE has incorrect year
- No unexpected binary files
- Checked PGP signatures
- Checked checksums
- Code compiles and tests successfully run
PS: DISCLAIMER-WIP/LICENSE should be fixed as Just
+1 (binding)
Chris
-Ursprüngliche Nachricht-
Von: Dave Fisher
Gesendet: Mittwoch, 10. Februar 2021 01:01
An: general@incubator.apache.org
Betreff: Re: [VOTE] Graduate Apache Daffodil to a top-level project
+1 (binding)
Regards,
Dave
Sent from my iPhone
> On Feb 9, 2021, at 2:03 PM,
32 matches
Mail list logo
