Re: Tying Dockerhub into development and release management

Hi, > My understanding is that only source-code releases are official releases. > Binaries are just a convenience and not official, so I don't think you have > to worry about making images available via DockerHub, even if that is the > primary way most people install. -1 the PMC can’t release un

Re: Draft incubator report

Hi, > We need a formulation which enables pre-release QA by non-coding > contributors. I've given my attempt at formulating it. Please give your > take on how to accomplish this. As long as these are not available to the general public all is fine. [1] Thanks, Justin 1. http://www.apache.org/

Re: Draft incubator report

That statement would also forbid maven snapshots. Something which many projects (TLPS too) offer. Is that the intention? It’s important to me that when we forbid something that projects are doing for valid reasons that we offer an alternative within the same statement. I’ve offered a potential dra

Re: Draft incubator report

Hi, > That statement would also forbid maven snapshots. Something which many > projects (TLPS too) offer. Is that the intention? They are fine as you need to explicitly do something to use them, i.e. they are not the default and the user understands that by using snapshots they are using unrele

Re: Draft incubator report

On 05/02/2019 10:23, Justin Mclean wrote: > Hi, > >> We need a formulation which enables pre-release QA by non-coding >> contributors. I've given my attempt at formulating it. Please give your >> take on how to accomplish this. > > As long as these are not available to the general public all is

Re: Draft incubator report

Hi, >> As long as these are not available to the general public all is fine. [1] > > s/available/advertised/ Thanks that’s a better way of putting it. Obviously any published artefact is available to the general public if and when they discover it. What’s important is that it’s not the default

Re: Tying Dockerhub into development and release management

I totally agree with you that Docker images should be built from official source releases, unless they are clearly marked as unofficial SNAPSHOT releases and intended for testing. I'm just repeating what I've heard over and over again from various ASF members that the only official release is the s

Re: Tying Dockerhub into development and release management

On Tue, Feb 5, 2019 at 2:48 PM Dave wrote: > I totally agree with you that Docker images should be built from official > source releases, unless they are clearly marked as unofficial SNAPSHOT > releases and intended for testing. I'm just repeating what I've heard over > and over again from variou

Re: Draft incubator report

On 2/5/2019 6:27 AM, Justin Mclean wrote: > Hi, > >>> As long as these are not available to the general public all is fine. [1] >> s/available/advertised/ > Thanks that’s a better way of putting it. Obviously any published artefact is > available to the general public if and when they discover it.

Re: Draft incubator report

> On Feb 5, 2019, at 10:27 AM, Kevin A. McGrail wrote: > > On 2/5/2019 6:27 AM, Justin Mclean wrote: >> Hi, >> As long as these are not available to the general public all is fine. [1] >>> s/available/advertised/ >> Thanks that’s a better way of putting it. Obviously any published artefac

Re: Draft incubator report

Cool. I think we've generated some consensus, even if we haven't answered every question. To summarize, I'd like to change this paragraph of the report: "Again a reminder to all incubating projects and mentors that all releases made available to the general public need to be approved by the PPMC

Re: Draft incubator report

HI, > "A reminder to all incubating projects and mentors that all releases > and distributions advertised to the general public need to be approved by > the PPMC and IPMC. This includes docker, github, PyPi, npm and any > other platform for publishing releases, and also covers release candidates.

Missing podling reports (due Wednesday 6th)

Hi, There’s less than a day to get you podling report in. Currently these podlings have failed to report: - BRPC - Iceberg - Ratis - SDAP Any podling that fails to report by the deadline will be listed in the report and asked to report next month. While missing one is not a big deal, if you

Re: Missing podling reports (due Wednesday 6th)

Hi - Sent from my iPhone > On Feb 5, 2019, at 1:07 PM, Justin Mclean wrote: > > Hi, > > There’s less than a day to get you podling report in. Currently these > podlings have failed to report: > - BRPC > - Iceberg > - Ratis > - SDAP > > Any podling that fails to report by the deadline will be

Re: Missing podling reports (due Wednesday 6th)

Hi, > Put another way, why are you threatening podlings with Board action? There’s no threat there, note the “may”. The board needs to know that a podling has oversight, if it doesn’t they might do something about it. The IPMC would probably do something before that happens. Any action is likel

[PROPOSAL] New blockchain project: Cava

Hi all, We’d like to start a conversation around a new proposal for a set of Java-based blockchain project. I have written a proposal available here, and reproduced below: https://wiki.apache.org/incubator/CavaProposal At this time, we have a c

Re: [PROPOSAL] New blockchain project: Cava

+1 Love to be part of this incubation project ….. Thanks, Selva- Apache Ranger, PMC Chair > On Feb 5, 2019, at 5:42 PM, Antoine Toulme wrote: > > Hi all, > > We’d like to start a conversation around a new proposal for a set of > Java-based blockchain project. > > I have written a proposal

Re: [PROPOSAL] New blockchain project: Cava

+1 I would also be interested in being involved as an initial committer for this. thanks, --larry Apache Knox, PMC Chair On Tue, Feb 5, 2019 at 5:47 PM Selvamohan Neethiraj wrote: > +1 > > Love to be part of this incubation project ….. > > Thanks, > Selva- > Apache Ranger, PMC Chair > > > On

Re: [PROPOSAL] New blockchain project: Cava

Hi, Nice proposal. Just a couple of comments. > The project is well established and counts 2 active committers. Some > contributions were made from the community. Being that small may be a concern, the ASF prefers project with a community around them, but it’s not always a barrier to entry se

Re: [PROPOSAL] New blockchain project: Cava

+1 I would like to volunteer as an additional mentor. Kenn On Tue, Feb 5, 2019 at 2:57 PM Justin Mclean wrote: > Hi, > > Nice proposal. Just a couple of comments. > > > The project is well established and counts 2 active committers. Some > contributions were made from the community. > > Being

Re: [PROPOSAL] New blockchain project: Cava

Hi - I would also be happy to volunteer as a Mentor to this podling. Regards, Dave > On Feb 5, 2019, at 3:28 PM, Kenneth Knowles wrote: > > +1 > > I would like to volunteer as an additional mentor. > > Kenn > > On Tue, Feb 5, 2019 at 2:57 PM Justin Mclean > wrote: > >> Hi, >> >> Nice pro

Re: [PROPOSAL] New blockchain project: Cava

I would love to be contribute in some way. thx debo On 2/5/19, 3:36 PM, "Dave Fisher" wrote: Hi - I would also be happy to volunteer as a Mentor to this podling. Regards, Dave > On Feb 5, 2019, at 3:28 PM, Kenneth Knowles wrote: > > +1 > >

Re: [PROPOSAL] New blockchain project: Cava

Interesting proposal. I would be interested in helping. Seems like you don't need anymore mentors so I can volunteer in any capacity you need. I think you are going to have trouble with the name though as https://cava.com/ is a great restaurant. Mike On Tue, Feb 5, 2019 at 6:36 PM Dave Fisher

Re: [PROPOSAL] New blockchain project: Cava

Thanks. I am replying inline: > On Feb 5, 2019, at 2:57 PM, Justin Mclean wrote: > > Hi, > > Nice proposal. Just a couple of comments. > >> The project is well established and counts 2 active committers. Some >> contributions were made from the community. > > Being that small may be a conce

Re: [PROPOSAL] New blockchain project: Cava

Thanks for your interest, all. Yes, the name of the project will very likely change. > On Feb 5, 2019, at 3:52 PM, Michael Wall wrote: > > Interesting proposal. I would be interested in helping. Seems like you > don't need anymore mentors so I can volunteer in any capacity you need. > > I th

Re: [PROPOSAL] New blockchain project: Cava

Hey just because there is a restaurant chain called Cava does not mean that a software project called Cava is not suitable. BTW Cava is Spanish Sparkling Wine - it is like Champagne but made with Spanish varietals. [1] Regards, Dave [1] https://winefolly.com/hidden/what-is-cava/ > On Feb 5, 2

Re: [PROPOSAL] New blockchain project: Cava

Indeed, our logo on bintray is a bottle of wine :) All, thanks for your enthusiastic replies. Please keep feedback coming! I have added all the responses to the wiki page: https://wiki.apache.org/incubator/CavaProposal Cheers, Antoine > On Feb

Re: [PROPOSAL] New blockchain project: Cava

Hi Antoine, I would be happy to help (as mentor, or as committer, or both, up to you ;)). Regards JB On 05/02/2019 23:42, Antoine Toulme wrote: > Hi all, > > We’d like to start a conversation around a new proposal for a set of > Java-based blockchain project. > > I have written a proposal ava

Re: [PROPOSAL] New blockchain project: Cava

Hi, I have Blockchain development experience with my Blockchain startup and would like to be added as an initial committer for this proposal. Kind Regards, Furkan KAMACI On Wed, Feb 6, 2019 at 9:45 AM Jean-Baptiste Onofré wrote: > Hi Antoine, > > I would be happy to help (as mentor, or as comm