Re: Tying Dockerhub into development and release management

[Justin Mclean]

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 unapproved code to the general public, this mandated 
by ASF release policy and has been previous discussed here [1].

"It is appropriate to distribute official releases through downstream channels, 
but inappropriate to distribute unreleased materials through them.”

Docker images MUST be built from our official source releases.

Put it this way if a PPMC could just publish what they wanted  to docker at any 
time why bother with official release at all.

Thanks,
Justin

1. https://issues.apache.org/jira/browse/LEGAL-270
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Draft incubator report

[Justin Mclean]

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/legal/release-policy.html#what

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

Re: Draft incubator report

[Myrle Krantz]

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 draft of alternative language which you rejected.
I humbly request that you propose an alternative.

Best Regards,
Myrle

On Tue, Feb 5, 2019 at 11:24 AM 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 fine. [1]
>
> Thanks,
> Justin
>
> 1. http://www.apache.org/legal/release-policy.html#what
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Draft incubator report

[Justin Mclean]

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 
unreleased code and the risk is all theirs.
 
> 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 allready offered an alternative to how projects can do this in this 
thread. The exact details how to do this is going to vary by distribution 
method but all platforms that I know of have a way of doing this.

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

Re: Draft incubator report

[Mark Thomas]

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 fine. [1]

s/available/advertised/

The pre-release artifacts are nearly always available to the general
public (i.e. they can download them if they wish). What matters is that
they are not advertised to the general public.

To put it another way:

Linking to snapshots on the public download page - not allowed.
Linking to snapshots on a page targeted at developers - allowed.

Mark

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

Re: Draft incubator report

[Justin Mclean]

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 when you do a "docker pull” or 
appear on github release pages or appear as a release on PyPi etc. etc.

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

Re: Tying Dockerhub into development and release management

[Dave]

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 source release; I'd don't agree with that point of view.

I'm curious what "built from the official source releases". Does that mean
that you must create Docker images by downloading the official source
release, verifying it's hash and then building image?  Or, are you allowed
to build your Docker images from the same SCM tag as was used to create the
source release?

Dave

On Tue, Feb 5, 2019 at 5:23 AM Justin Mclean 
wrote:

> 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 unapproved code to the general public, this
> mandated by ASF release policy and has been previous discussed here [1].
>
> "It is appropriate to distribute official releases through downstream
> channels, but inappropriate to distribute unreleased materials through
> them.”
>
> Docker images MUST be built from our official source releases.
>
> Put it this way if a PPMC could just publish what they wanted  to docker
> at any time why bother with official release at all.
>
> Thanks,
> Justin
>
> 1. https://issues.apache.org/jira/browse/LEGAL-270
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Tying Dockerhub into development and release management

[Roman Shaposhnik]

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 various ASF members that the only official release is
> the source release; I'd don't agree with that point of view.
>
> I'm curious what "built from the official source releases". Does that mean
> that you must create Docker images by downloading the official source
> release, verifying it's hash and then building image?  Or, are you allowed
> to build your Docker images from the same SCM tag as was used to create the
> source release?
>

I think an acceptable solution could be:
   * make sure that your :latest tag either points to a Docker scratch
container
 or a container that simply prints Incubator disclaimer and exists
   * introduce a tagging scheme for nightly builds (personally I'm quite
fond
 of tagging nightly docker builds with SHAs from your git tree from
which
 you build the image)
   * introduce :snapshot tag that points at the latest tag from previous
item

I feel that this could be passable for IPMC.

Thanks,
Roman.

Re: Draft incubator report

[Kevin A. McGrail]

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.


Thanks Justin.  The advertised vs available was a big concern for me
when I read that this morning.


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

Re: Draft incubator report

[Dave Fisher]

> 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 artefact 
>> is available to the general public if and when they discover it.
> 
> 
> Thanks Justin.  The advertised vs available was a big concern for me
> when I read that this morning.

Yes, that is better, but here is the next challenge. For distribution channels 
like Maven, NPM, etc which some projects use to stage prospective releases how 
do we recommend that projects stay within the available, but not advertised 
rule? I think somewhere some guidance is needed. Recently on legal-discuss 
there is a long thread [1] which discusses binary channels. Perhaps some 
guidance can be pulled from that thread.

Regards,
Dave

[1] 
https://lists.apache.org/thread.html/d578819f1afa6b8fb697ea72083e0fb05e43938a23d6e7bb804069b8@%3Clegal-discuss.apache.org%3E
 

 


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

Re: Draft incubator report

[Myrle Krantz]

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 and
IPMC. This includes docker, githubb, PyPi, npm and any other platform for
publishing releases, and also covers release candidates. If in doubt please
ask your mentors or on the incubator general list."

To this:

"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.
Nightly builds for project-internal use clearly marked as "snapshot" or
"prerelease" (or similar) can be made available to project contributors. If
in doubt please ask your mentors or on the incubator general list."

Objections?

Best Regards,
Myrle


On Tue, Feb 5, 2019 at 7:34 PM Dave Fisher  wrote:

>
>
> > 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
> artefact is available to the general public if and when they discover it.
> >
> >
> > Thanks Justin.  The advertised vs available was a big concern for me
> > when I read that this morning.
>
> Yes, that is better, but here is the next challenge. For distribution
> channels like Maven, NPM, etc which some projects use to stage prospective
> releases how do we recommend that projects stay within the available, but
> not advertised rule? I think somewhere some guidance is needed. Recently on
> legal-discuss there is a long thread [1] which discusses binary channels.
> Perhaps some guidance can be pulled from that thread.
>
> Regards,
> Dave
>
> [1]
> https://lists.apache.org/thread.html/d578819f1afa6b8fb697ea72083e0fb05e43938a23d6e7bb804069b8@%3Clegal-discuss.apache.org%3E
> <
> https://lists.apache.org/thread.html/d578819f1afa6b8fb697ea72083e0fb05e43938a23d6e7bb804069b8@%3Clegal-discuss.apache.org%3E>
>
>
>
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
>

Re: Draft incubator report

[Justin Mclean]

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.
> Nightly builds for project-internal use clearly marked as "snapshot" or
> "prerelease" (or similar) can be made available to project contributors. If
> in doubt please ask your mentors or on the incubator general list."
> 
> Objections?

None from me. I’ll make the change.

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

Missing podling reports (due Wednesday 6th)

[Justin Mclean]

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 
miss a couple in a row the board may need to be involved.

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

Re: Missing podling reports (due Wednesday 6th)

[Dave Fisher]

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 listed in the report 
> and asked to report next month. While missing one is not a big deal, if you 
> miss a couple in a row the board may need to be involved.

We as the IPMC are responsible. If we need to take action the Board long ago 
has empowered us to do so.

Put another way, why are you threatening podlings with Board action?

Regards,
Dave


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


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

Re: Missing podling reports (due Wednesday 6th)

[Justin Mclean]

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 likely to be a 
friendly email asking why several reports have been missed.

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

[PROPOSAL] New blockchain project: Cava

[Antoine Toulme]

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 champion, Jim Jagielski (thanks Jim), and would like to 
recruit additional developers and mentors.

We have deliberately left room on the project charter to engage openly with the 
community. That said, we would start the project with code coming from 
ConsenSys, and we will recruit developers from there and elsewhere actively.

The goal of this thread is engage with the community and gather interest for 
participation in the project. Please let us know what you think!

Cheers,

Antoine Toulme

== Abstract ==
Cava is a set of libraries and other tools to aid development of blockchain and 
other decentralized software in Java and other JVM languages.

Please note: Cava is a contraction of "ConsenSys Java". The community should 
consider an alternate name.

= Proposal =

Cava is a set of libraries and other tools to aid development of blockchain and 
other decentralized software in Java and other JVM languages.
It includes a low-level bytes library, serialization and deserialization codecs 
(e.g. RLP), various cryptography functions and primatives, and lots of other 
helpful utilities.
Cava is developed for JDK 1.8 or higher, and depends on various other FOSS 
libraries.

=== Background ===

Cava was built as an open source project from the grounds up to accelerate the 
maturation of the blockchain ecosystem, particularly in relation with 
enterprise products predominantly built in Java.
Cava is used by several products today: Orion, Pantheon, and Artemis from 
Pegasys.

Cava libraries are also used in various experiments regarding scalability, such 
as Canto.

Several other community members would want to leverage Cava and would benefit 
from working directly on the project outside of the influence of the original 
corporate sponsor, ConsenSys.

=== Rationale ===

Cava is organized as set of libraries that form the basis of most blockchain, 
distributed ledgers or cryptography work.

Most of the work built for Cava was meant for Ethereum, but can be reused 
across other blockchain technologies.

There is a need for blockchain implementors to use well trusted, 
production-ready software to bootstrap their efforts.

=== Initial Goals ===

The goal is to form a community of developers and adopters who will be able to 
collaborate openly around blockchain technologies and mature frameworks 
to reduce risk when implementing blockain-related projects.

=== Current Status ===

The project is well established and counts 2 active committers. Some 
contributions were made from the community.

The project has made several releases, distributed through Maven Central, with 
GPG signatures and proper Maven metadata published.

'''Meritocracy:'''

Active discussions on github issues and PRs has helped identify new possible 
commiters.

Our main goal, moving to Apache is to promote our project as a meritocracy 
under the guideline of the Apache Way to help foster a community around our 
efforts.

 * '''Community:'''

Blockchain protocol developers organize well in communities, and some lively 
discussions take place over Twitter, Gitter, Telegram.

We would like to create a community for dedicated Java developers to contribute 
to the blockchain space.

We currently have a little activity through the channels mentioned above, but 
no channel dedicated specifically to Cava is seeing a lot of traction.

 * '''Core Developers:'''

Cava was built by two developers with a long experience in open source work. 
Both lead separate open source projects.
One of the developers is the PMC Chair for Apache Buildr and a committer for 
Apache ODE.

 * '''Alignment:'''

We believe there isn't a blockchain TLP for Java at Apache at this time and 
would like to participate in establishing a presence in that domain of 
expertise.

We would rely and integrate closely with a number of projects hosted by the ASF 
such as Apache Camel.

'''Known Risks'''

 * '''Orphaned products''':

The contributors are committed to the development of the blockchain space and 
are employed by a leading vendor in blockchain.

The source code is used in a production setting by critical projects.

However, the number of initial developers and contributors is small, and we 
will need to ramp up our recruitment efforts.

 * '''Inexperience with Open Source:'''

The project was started from scratch as an open source project. All committers 
have experience with open source projects.

We did not make the effort of creating a detailed roadmap and organizing a 
collaborative approach to reaching to the community for feedback.
We aim to rely on the ASF infrastructure, especially Jira, to help create more 
visibility in this regard.

 * '''Length of Incubation:'''

 We will rema

Re: [PROPOSAL] New blockchain project: Cava

[Selvamohan Neethiraj]

+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 available here, and reproduced below: 
> https://wiki.apache.org/incubator/CavaProposal 
> 
> 
> At this time, we have a champion, Jim Jagielski (thanks Jim), and would like 
> to recruit additional developers and mentors.
> 
> We have deliberately left room on the project charter to engage openly with 
> the community. That said, we would start the project with code coming from 
> ConsenSys, and we will recruit developers from there and elsewhere actively.
> 
> The goal of this thread is engage with the community and gather interest for 
> participation in the project. Please let us know what you think!
> 
> Cheers,
> 
> Antoine Toulme
> 
> == Abstract ==
> Cava is a set of libraries and other tools to aid development of blockchain 
> and other decentralized software in Java and other JVM languages.
> 
> Please note: Cava is a contraction of "ConsenSys Java". The community should 
> consider an alternate name.
> 
> = Proposal =
> 
> Cava is a set of libraries and other tools to aid development of blockchain 
> and other decentralized software in Java and other JVM languages.
> It includes a low-level bytes library, serialization and deserialization 
> codecs (e.g. RLP), various cryptography functions and primatives, and lots of 
> other helpful utilities.
> Cava is developed for JDK 1.8 or higher, and depends on various other FOSS 
> libraries.
> 
> === Background ===
> 
> Cava was built as an open source project from the grounds up to accelerate 
> the maturation of the blockchain ecosystem, particularly in relation with 
> enterprise products predominantly built in Java.
> Cava is used by several products today: Orion, Pantheon, and Artemis from 
> Pegasys.
> 
> Cava libraries are also used in various experiments regarding scalability, 
> such as Canto.
> 
> Several other community members would want to leverage Cava and would benefit 
> from working directly on the project outside of the influence of the original 
> corporate sponsor, ConsenSys.
> 
> === Rationale ===
> 
> Cava is organized as set of libraries that form the basis of most blockchain, 
> distributed ledgers or cryptography work.
> 
> Most of the work built for Cava was meant for Ethereum, but can be reused 
> across other blockchain technologies.
> 
> There is a need for blockchain implementors to use well trusted, 
> production-ready software to bootstrap their efforts.
> 
> === Initial Goals ===
> 
> The goal is to form a community of developers and adopters who will be able 
> to collaborate openly around blockchain technologies and mature frameworks 
> to reduce risk when implementing blockain-related projects.
> 
> === Current Status ===
> 
> The project is well established and counts 2 active committers. Some 
> contributions were made from the community.
> 
> The project has made several releases, distributed through Maven Central, 
> with GPG signatures and proper Maven metadata published.
> 
> '''Meritocracy:'''
> 
> Active discussions on github issues and PRs has helped identify new possible 
> commiters.
> 
> Our main goal, moving to Apache is to promote our project as a meritocracy 
> under the guideline of the Apache Way to help foster a community around our 
> efforts.
> 
> * '''Community:'''
> 
> Blockchain protocol developers organize well in communities, and some lively 
> discussions take place over Twitter, Gitter, Telegram.
> 
> We would like to create a community for dedicated Java developers to 
> contribute to the blockchain space.
> 
> We currently have a little activity through the channels mentioned above, but 
> no channel dedicated specifically to Cava is seeing a lot of traction.
> 
> * '''Core Developers:'''
> 
> Cava was built by two developers with a long experience in open source work. 
> Both lead separate open source projects.
> One of the developers is the PMC Chair for Apache Buildr and a committer for 
> Apache ODE.
> 
> * '''Alignment:'''
> 
> We believe there isn't a blockchain TLP for Java at Apache at this time and 
> would like to participate in establishing a presence in that domain of 
> expertise.
> 
> We would rely and integrate closely with a number of projects hosted by the 
> ASF such as Apache Camel.
> 
> '''Known Risks'''
> 
> * '''Orphaned products''':
> 
> The contributors are committed to the development of the blockchain space and 
> are employed by a leading vendor in blockchain.
> 
> The source code is used in a production setting by critical projects.
> 
> However, the number of initial developers and contributors is small, and we 
> will need to ramp up our recruitment efforts.
> 
> * '''Inexperience with Open Source:'''
> 
> The project 

Re: [PROPOSAL] New blockchain project: Cava

[larry mccay]

+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 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 available here, and reproduced below:
> https://wiki.apache.org/incubator/CavaProposal <
> https://wiki.apache.org/incubator/CavaProposal>
> >
> > At this time, we have a champion, Jim Jagielski (thanks Jim), and would
> like to recruit additional developers and mentors.
> >
> > We have deliberately left room on the project charter to engage openly
> with the community. That said, we would start the project with code coming
> from ConsenSys, and we will recruit developers from there and elsewhere
> actively.
> >
> > The goal of this thread is engage with the community and gather interest
> for participation in the project. Please let us know what you think!
> >
> > Cheers,
> >
> > Antoine Toulme
> >
> > == Abstract ==
> > Cava is a set of libraries and other tools to aid development of
> blockchain and other decentralized software in Java and other JVM languages.
> >
> > Please note: Cava is a contraction of "ConsenSys Java". The community
> should consider an alternate name.
> >
> > = Proposal =
> >
> > Cava is a set of libraries and other tools to aid development of
> blockchain and other decentralized software in Java and other JVM languages.
> > It includes a low-level bytes library, serialization and deserialization
> codecs (e.g. RLP), various cryptography functions and primatives, and lots
> of other helpful utilities.
> > Cava is developed for JDK 1.8 or higher, and depends on various other
> FOSS libraries.
> >
> > === Background ===
> >
> > Cava was built as an open source project from the grounds up to
> accelerate the maturation of the blockchain ecosystem, particularly in
> relation with enterprise products predominantly built in Java.
> > Cava is used by several products today: Orion, Pantheon, and Artemis
> from Pegasys.
> >
> > Cava libraries are also used in various experiments regarding
> scalability, such as Canto.
> >
> > Several other community members would want to leverage Cava and would
> benefit from working directly on the project outside of the influence of
> the original corporate sponsor, ConsenSys.
> >
> > === Rationale ===
> >
> > Cava is organized as set of libraries that form the basis of most
> blockchain, distributed ledgers or cryptography work.
> >
> > Most of the work built for Cava was meant for Ethereum, but can be
> reused across other blockchain technologies.
> >
> > There is a need for blockchain implementors to use well trusted,
> production-ready software to bootstrap their efforts.
> >
> > === Initial Goals ===
> >
> > The goal is to form a community of developers and adopters who will be
> able to collaborate openly around blockchain technologies and mature
> frameworks
> > to reduce risk when implementing blockain-related projects.
> >
> > === Current Status ===
> >
> > The project is well established and counts 2 active committers. Some
> contributions were made from the community.
> >
> > The project has made several releases, distributed through Maven
> Central, with GPG signatures and proper Maven metadata published.
> >
> > '''Meritocracy:'''
> >
> > Active discussions on github issues and PRs has helped identify new
> possible commiters.
> >
> > Our main goal, moving to Apache is to promote our project as a
> meritocracy under the guideline of the Apache Way to help foster a
> community around our efforts.
> >
> > * '''Community:'''
> >
> > Blockchain protocol developers organize well in communities, and some
> lively discussions take place over Twitter, Gitter, Telegram.
> >
> > We would like to create a community for dedicated Java developers to
> contribute to the blockchain space.
> >
> > We currently have a little activity through the channels mentioned
> above, but no channel dedicated specifically to Cava is seeing a lot of
> traction.
> >
> > * '''Core Developers:'''
> >
> > Cava was built by two developers with a long experience in open source
> work. Both lead separate open source projects.
> > One of the developers is the PMC Chair for Apache Buildr and a committer
> for Apache ODE.
> >
> > * '''Alignment:'''
> >
> > We believe there isn't a blockchain TLP for Java at Apache at this time
> and would like to participate in establishing a presence in that domain of
> expertise.
> >
> > We would rely and integrate closely with a number of projects hosted by
> the ASF such as Apache Camel.
> >
> > '''Known Risks'''
> >
> > * '''Orphaned products''':
> >
> > The contributors are committed to the development of the blockchain
> space and are employed 

Re: [PROPOSAL] New blockchain project: Cava

[Justin Mclean]

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 see for example Apache 
PLC4X.

> Blockchain protocol developers organize well in communities, and some lively 
> discussions take place over Twitter, Gitter, Telegram.

At the ASF all decisions need to be made on the mailing list not on any 
external platform mentioned above. Would the project be OK with moving 
discussions to a mailing list and having them in an asynchronous manner?

> We will remain in incubation for a period of no less than a year so we can 
> properly invest and build a community of users, contributors and committers 
> around our goals.

Most projects take more than a year to graduate, two years is usual but some 
projects do take longer. Is the project OK with that and will your mentors stay 
around for that long?

> '''Initial Committers'''
> 
> Antoine Toulme (toulmean at apache dot org) *

Seem odd to only list one initial committer, all initial committer s are on the 
PPMC and you would need a minimum of 3 active people. The IPMC generally likes 
to see 5.

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

Re: [PROPOSAL] New blockchain project: Cava

[Kenneth Knowles]

+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 that small may be a concern, the ASF prefers project with a
> community around them, but it’s not always a barrier to entry see for
> example Apache PLC4X.
>
> > Blockchain protocol developers organize well in communities, and some
> lively discussions take place over Twitter, Gitter, Telegram.
>
> At the ASF all decisions need to be made on the mailing list not on any
> external platform mentioned above. Would the project be OK with moving
> discussions to a mailing list and having them in an asynchronous manner?
>
> > We will remain in incubation for a period of no less than a year so we
> can properly invest and build a community of users, contributors and
> committers around our goals.
>
> Most projects take more than a year to graduate, two years is usual but
> some projects do take longer. Is the project OK with that and will your
> mentors stay around for that long?
>
> > '''Initial Committers'''
> >
> > Antoine Toulme (toulmean at apache dot org) *
>
> Seem odd to only list one initial committer, all initial committer s are
> on the PPMC and you would need a minimum of 3 active people. The IPMC
> generally likes to see 5.
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [PROPOSAL] New blockchain project: Cava

[Dave Fisher]

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 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 see for
>> example Apache PLC4X.
>> 
>>> Blockchain protocol developers organize well in communities, and some
>> lively discussions take place over Twitter, Gitter, Telegram.
>> 
>> At the ASF all decisions need to be made on the mailing list not on any
>> external platform mentioned above. Would the project be OK with moving
>> discussions to a mailing list and having them in an asynchronous manner?
>> 
>>> We will remain in incubation for a period of no less than a year so we
>> can properly invest and build a community of users, contributors and
>> committers around our goals.
>> 
>> Most projects take more than a year to graduate, two years is usual but
>> some projects do take longer. Is the project OK with that and will your
>> mentors stay around for that long?
>> 
>>> '''Initial Committers'''
>>> 
>>> Antoine Toulme (toulmean at apache dot org) *
>> 
>> Seem odd to only list one initial committer, all initial committer s are
>> on the PPMC and you would need a minimum of 3 active people. The IPMC
>> generally likes to see 5.
>> 
>> Thanks,
>> Justin
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
>> 


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

Re: [PROPOSAL] New blockchain project: Cava

[Debo Dutta (dedutta)]

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
> 
> 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 that small may be a concern, the ASF prefers project with a
>> community around them, but it’s not always a barrier to entry see for
>> example Apache PLC4X.
>> 
>>> Blockchain protocol developers organize well in communities, and some
>> lively discussions take place over Twitter, Gitter, Telegram.
>> 
>> At the ASF all decisions need to be made on the mailing list not on any
>> external platform mentioned above. Would the project be OK with moving
>> discussions to a mailing list and having them in an asynchronous manner?
>> 
>>> We will remain in incubation for a period of no less than a year so we
>> can properly invest and build a community of users, contributors and
>> committers around our goals.
>> 
>> Most projects take more than a year to graduate, two years is usual but
>> some projects do take longer. Is the project OK with that and will your
>> mentors stay around for that long?
>> 
>>> '''Initial Committers'''
>>> 
>>> Antoine Toulme (toulmean at apache dot org) *
>> 
>> Seem odd to only list one initial committer, all initial committer s are
>> on the PPMC and you would need a minimum of 3 active people. The IPMC
>> generally likes to see 5.
>> 
>> Thanks,
>> Justin
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
>> 


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




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

Re: [PROPOSAL] New blockchain project: Cava

[Michael Wall]

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  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
> >
> > 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 that small may be a concern, the ASF prefers project with a
> >> community around them, but it’s not always a barrier to entry see for
> >> example Apache PLC4X.
> >>
> >>> Blockchain protocol developers organize well in communities, and some
> >> lively discussions take place over Twitter, Gitter, Telegram.
> >>
> >> At the ASF all decisions need to be made on the mailing list not on any
> >> external platform mentioned above. Would the project be OK with moving
> >> discussions to a mailing list and having them in an asynchronous manner?
> >>
> >>> We will remain in incubation for a period of no less than a year so we
> >> can properly invest and build a community of users, contributors and
> >> committers around our goals.
> >>
> >> Most projects take more than a year to graduate, two years is usual but
> >> some projects do take longer. Is the project OK with that and will your
> >> mentors stay around for that long?
> >>
> >>> '''Initial Committers'''
> >>>
> >>> Antoine Toulme (toulmean at apache dot org) *
> >>
> >> Seem odd to only list one initial committer, all initial committer s are
> >> on the PPMC and you would need a minimum of 3 active people. The IPMC
> >> generally likes to see 5.
> >>
> >> Thanks,
> >> Justin
> >> -
> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> For additional commands, e-mail: general-h...@incubator.apache.org
> >>
> >>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [PROPOSAL] New blockchain project: Cava

[Antoine Toulme]

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 concern, the ASF prefers project with a community 
> around them, but it’s not always a barrier to entry see for example Apache 
> PLC4X.
We actually have more interest and contributors, and making this proposal is 
going to help me engage them in the open.

I’d like to leverage this proposal process as much as possible to build the 
community.

> 
>> Blockchain protocol developers organize well in communities, and some lively 
>> discussions take place over Twitter, Gitter, Telegram.
> 
> At the ASF all decisions need to be made on the mailing list not on any 
> external platform mentioned above. Would the project be OK with moving 
> discussions to a mailing list and having them in an asynchronous manner?
This is absolutely fine, yes.

If that wasn’t clear, I lament the state of the communication channels of 
blockchain development communities. I believe proper mailing lists will help. 
And I think the culture of ASF will help us stick to that.

> 
>> We will remain in incubation for a period of no less than a year so we can 
>> properly invest and build a community of users, contributors and committers 
>> around our goals.
> 
> Most projects take more than a year to graduate, two years is usual but some 
> projects do take longer. Is the project OK with that and will your mentors 
> stay around for that long?
I’m OK with this. Will update.
> 
>> '''Initial Committers'''
>> 
>> Antoine Toulme (toulmean at apache dot org) *
> 
> Seem odd to only list one initial committer, all initial committer s are on 
> the PPMC and you would need a minimum of 3 active people. The IPMC generally 
> likes to see 5.
See above. I’m now collecting motions of support and will push for more people.
> 
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


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

Re: [PROPOSAL] New blockchain project: Cava

[Antoine Toulme]

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 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  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
>>> 
>>> 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 that small may be a concern, the ASF prefers project with a
 community around them, but it’s not always a barrier to entry see for
 example Apache PLC4X.
 
> Blockchain protocol developers organize well in communities, and some
 lively discussions take place over Twitter, Gitter, Telegram.
 
 At the ASF all decisions need to be made on the mailing list not on any
 external platform mentioned above. Would the project be OK with moving
 discussions to a mailing list and having them in an asynchronous manner?
 
> We will remain in incubation for a period of no less than a year so we
 can properly invest and build a community of users, contributors and
 committers around our goals.
 
 Most projects take more than a year to graduate, two years is usual but
 some projects do take longer. Is the project OK with that and will your
 mentors stay around for that long?
 
> '''Initial Committers'''
> 
> Antoine Toulme (toulmean at apache dot org) *
 
 Seem odd to only list one initial committer, all initial committer s are
 on the PPMC and you would need a minimum of 3 active people. The IPMC
 generally likes to see 5.
 
 Thanks,
 Justin
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 
 
>> 
>> 
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
>> 


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

Re: [PROPOSAL] New blockchain project: Cava

[Dave Fisher]

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, 2019, at 4:01 PM, Antoine Toulme  wrote:
> 
> 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 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  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
 
 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 that small may be a concern, the ASF prefers project with a
> community around them, but it’s not always a barrier to entry see for
> example Apache PLC4X.
> 
>> Blockchain protocol developers organize well in communities, and some
> lively discussions take place over Twitter, Gitter, Telegram.
> 
> At the ASF all decisions need to be made on the mailing list not on any
> external platform mentioned above. Would the project be OK with moving
> discussions to a mailing list and having them in an asynchronous manner?
> 
>> We will remain in incubation for a period of no less than a year so we
> can properly invest and build a community of users, contributors and
> committers around our goals.
> 
> Most projects take more than a year to graduate, two years is usual but
> some projects do take longer. Is the project OK with that and will your
> mentors stay around for that long?
> 
>> '''Initial Committers'''
>> 
>> Antoine Toulme (toulmean at apache dot org) *
> 
> Seem odd to only list one initial committer, all initial committer s are
> on the PPMC and you would need a minimum of 3 active people. The IPMC
> generally likes to see 5.
> 
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 
> 
>>> 
>>> 
>>> -
>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>> 
>>> 
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


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

Re: [PROPOSAL] New blockchain project: Cava

[Antoine Toulme]

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 5, 2019, at 4:06 PM, Dave Fisher  wrote:
> 
> 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, 2019, at 4:01 PM, Antoine Toulme  wrote:
>> 
>> 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 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  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
> 
> 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 that small may be a concern, the ASF prefers project with a
>> community around them, but it’s not always a barrier to entry see for
>> example Apache PLC4X.
>> 
>>> Blockchain protocol developers organize well in communities, and some
>> lively discussions take place over Twitter, Gitter, Telegram.
>> 
>> At the ASF all decisions need to be made on the mailing list not on any
>> external platform mentioned above. Would the project be OK with moving
>> discussions to a mailing list and having them in an asynchronous manner?
>> 
>>> We will remain in incubation for a period of no less than a year so we
>> can properly invest and build a community of users, contributors and
>> committers around our goals.
>> 
>> Most projects take more than a year to graduate, two years is usual but
>> some projects do take longer. Is the project OK with that and will your
>> mentors stay around for that long?
>> 
>>> '''Initial Committers'''
>>> 
>>> Antoine Toulme (toulmean at apache dot org) *
>> 
>> Seem odd to only list one initial committer, all initial committer s are
>> on the PPMC and you would need a minimum of 3 active people. The IPMC
>> generally likes to see 5.
>> 
>> Thanks,
>> Justin
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
>> 
 
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 
 
>> 
>> 
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 

Re: [PROPOSAL] New blockchain project: Cava

[Jean-Baptiste Onofré]

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 available here, and reproduced below: 
> https://wiki.apache.org/incubator/CavaProposal 
> 
> 
> At this time, we have a champion, Jim Jagielski (thanks Jim), and would like 
> to recruit additional developers and mentors.
> 
> We have deliberately left room on the project charter to engage openly with 
> the community. That said, we would start the project with code coming from 
> ConsenSys, and we will recruit developers from there and elsewhere actively.
> 
> The goal of this thread is engage with the community and gather interest for 
> participation in the project. Please let us know what you think!
> 
> Cheers,
> 
> Antoine Toulme
> 
> == Abstract ==
> Cava is a set of libraries and other tools to aid development of blockchain 
> and other decentralized software in Java and other JVM languages.
> 
> Please note: Cava is a contraction of "ConsenSys Java". The community should 
> consider an alternate name.
> 
> = Proposal =
> 
> Cava is a set of libraries and other tools to aid development of blockchain 
> and other decentralized software in Java and other JVM languages.
> It includes a low-level bytes library, serialization and deserialization 
> codecs (e.g. RLP), various cryptography functions and primatives, and lots of 
> other helpful utilities.
> Cava is developed for JDK 1.8 or higher, and depends on various other FOSS 
> libraries.
> 
> === Background ===
> 
> Cava was built as an open source project from the grounds up to accelerate 
> the maturation of the blockchain ecosystem, particularly in relation with 
> enterprise products predominantly built in Java.
> Cava is used by several products today: Orion, Pantheon, and Artemis from 
> Pegasys.
> 
> Cava libraries are also used in various experiments regarding scalability, 
> such as Canto.
> 
> Several other community members would want to leverage Cava and would benefit 
> from working directly on the project outside of the influence of the original 
> corporate sponsor, ConsenSys.
> 
> === Rationale ===
> 
> Cava is organized as set of libraries that form the basis of most blockchain, 
> distributed ledgers or cryptography work.
> 
> Most of the work built for Cava was meant for Ethereum, but can be reused 
> across other blockchain technologies.
> 
> There is a need for blockchain implementors to use well trusted, 
> production-ready software to bootstrap their efforts.
> 
> === Initial Goals ===
> 
> The goal is to form a community of developers and adopters who will be able 
> to collaborate openly around blockchain technologies and mature frameworks 
> to reduce risk when implementing blockain-related projects.
> 
> === Current Status ===
> 
> The project is well established and counts 2 active committers. Some 
> contributions were made from the community.
> 
> The project has made several releases, distributed through Maven Central, 
> with GPG signatures and proper Maven metadata published.
> 
> '''Meritocracy:'''
> 
> Active discussions on github issues and PRs has helped identify new possible 
> commiters.
> 
> Our main goal, moving to Apache is to promote our project as a meritocracy 
> under the guideline of the Apache Way to help foster a community around our 
> efforts.
> 
>  * '''Community:'''
> 
> Blockchain protocol developers organize well in communities, and some lively 
> discussions take place over Twitter, Gitter, Telegram.
> 
> We would like to create a community for dedicated Java developers to 
> contribute to the blockchain space.
> 
> We currently have a little activity through the channels mentioned above, but 
> no channel dedicated specifically to Cava is seeing a lot of traction.
> 
>  * '''Core Developers:'''
> 
> Cava was built by two developers with a long experience in open source work. 
> Both lead separate open source projects.
> One of the developers is the PMC Chair for Apache Buildr and a committer for 
> Apache ODE.
> 
>  * '''Alignment:'''
> 
> We believe there isn't a blockchain TLP for Java at Apache at this time and 
> would like to participate in establishing a presence in that domain of 
> expertise.
> 
> We would rely and integrate closely with a number of projects hosted by the 
> ASF such as Apache Camel.
> 
> '''Known Risks'''
> 
>  * '''Orphaned products''':
> 
> The contributors are committed to the development of the blockchain space and 
> are employed by a leading vendor in blockchain.
> 
> The source code is used in a production setting by critical projects.
> 
> However, the number of initial developers and contributors is small, and we 
> will need to ramp up our recruitment efforts.
> 
>  * '''Inexperience with Open Source:'''
> 
> The projec

Re: [PROPOSAL] New blockchain project: Cava

[Furkan KAMACI]

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 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 available here, and reproduced below:
> https://wiki.apache.org/incubator/CavaProposal <
> https://wiki.apache.org/incubator/CavaProposal>
> >
> > At this time, we have a champion, Jim Jagielski (thanks Jim), and would
> like to recruit additional developers and mentors.
> >
> > We have deliberately left room on the project charter to engage openly
> with the community. That said, we would start the project with code coming
> from ConsenSys, and we will recruit developers from there and elsewhere
> actively.
> >
> > The goal of this thread is engage with the community and gather interest
> for participation in the project. Please let us know what you think!
> >
> > Cheers,
> >
> > Antoine Toulme
> >
> > == Abstract ==
> > Cava is a set of libraries and other tools to aid development of
> blockchain and other decentralized software in Java and other JVM languages.
> >
> > Please note: Cava is a contraction of "ConsenSys Java". The community
> should consider an alternate name.
> >
> > = Proposal =
> >
> > Cava is a set of libraries and other tools to aid development of
> blockchain and other decentralized software in Java and other JVM languages.
> > It includes a low-level bytes library, serialization and deserialization
> codecs (e.g. RLP), various cryptography functions and primatives, and lots
> of other helpful utilities.
> > Cava is developed for JDK 1.8 or higher, and depends on various other
> FOSS libraries.
> >
> > === Background ===
> >
> > Cava was built as an open source project from the grounds up to
> accelerate the maturation of the blockchain ecosystem, particularly in
> relation with enterprise products predominantly built in Java.
> > Cava is used by several products today: Orion, Pantheon, and Artemis
> from Pegasys.
> >
> > Cava libraries are also used in various experiments regarding
> scalability, such as Canto.
> >
> > Several other community members would want to leverage Cava and would
> benefit from working directly on the project outside of the influence of
> the original corporate sponsor, ConsenSys.
> >
> > === Rationale ===
> >
> > Cava is organized as set of libraries that form the basis of most
> blockchain, distributed ledgers or cryptography work.
> >
> > Most of the work built for Cava was meant for Ethereum, but can be
> reused across other blockchain technologies.
> >
> > There is a need for blockchain implementors to use well trusted,
> production-ready software to bootstrap their efforts.
> >
> > === Initial Goals ===
> >
> > The goal is to form a community of developers and adopters who will be
> able to collaborate openly around blockchain technologies and mature
> frameworks
> > to reduce risk when implementing blockain-related projects.
> >
> > === Current Status ===
> >
> > The project is well established and counts 2 active committers. Some
> contributions were made from the community.
> >
> > The project has made several releases, distributed through Maven
> Central, with GPG signatures and proper Maven metadata published.
> >
> > '''Meritocracy:'''
> >
> > Active discussions on github issues and PRs has helped identify new
> possible commiters.
> >
> > Our main goal, moving to Apache is to promote our project as a
> meritocracy under the guideline of the Apache Way to help foster a
> community around our efforts.
> >
> >  * '''Community:'''
> >
> > Blockchain protocol developers organize well in communities, and some
> lively discussions take place over Twitter, Gitter, Telegram.
> >
> > We would like to create a community for dedicated Java developers to
> contribute to the blockchain space.
> >
> > We currently have a little activity through the channels mentioned
> above, but no channel dedicated specifically to Cava is seeing a lot of
> traction.
> >
> >  * '''Core Developers:'''
> >
> > Cava was built by two developers with a long experience in open source
> work. Both lead separate open source projects.
> > One of the developers is the PMC Chair for Apache Buildr and a committer
> for Apache ODE.
> >
> >  * '''Alignment:'''
> >
> > We believe there isn't a blockchain TLP for Java at Apache at this time
> and would like to participate in establishing a presence in that domain of
> expertise.
> >
> > We would rely and integrate closely with a number of projects hosted by
> the ASF such as Apache Camel.
> >
> > '''Known Risks'''
> >
> >  * '''Orphaned products''':
> >
> > The contributors are committed to the develo