Re: Unapproved Sharding Sphere releases

[Justin Mclean]

HI,

> This was done. The issue is that the "3.0.0 outside Apache" release should 
> not be associated with Apache but with the previous project.

They also made a 3.1.0 release as well and it was on the Apache github site 
(both 3.0 and 3.1 have now been removed from there).

> It looks like the original repositories have been changed to redirect to 
> Apache. I'd suggest restoring the original 
> https://github.com/sharding-sphere/ 
> * repositories so 
> they don't automatically redirect to the Apache podling git repositories. 

I’m not so sure that's OK. It’s probably not right for a PPMC to be releasing 
software anywhere advertised to the general public that hasn’t been approved 
for release. Could a 3rd party do it sure, could they call it Sharding Sphere 
probably not.

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

Re: Unapproved Sharding Sphere releases

[Craig Russell]

Sorry I have not been following this as closely as I should have.

It was decided after ShardingSphere was accepted into the incubator that the 
project would make a final release outside the incubator and then bring the 
code into Apache. The release 4.0.0 would be an Apache release.

This was done. The issue is that the "3.0.0 outside Apache" release should not 
be associated with Apache but with the previous project.

So, there are not yet any Apache ShardingSphere releases. But there is no 
reason to disallow the 3.0.0 release to be published from its previous home.

It looks like the original repositories have been changed to redirect to 
Apache. I'd suggest restoring the original https://github.com/sharding-sphere/ 
* repositories so they 
don't automatically redirect to the Apache podling git repositories. 

There are two projects now and they should remain separate. At some point, 
people will migrate from the previous project to Apache. But that time has not 
come.

WDYT?

Craig


> On Feb 1, 2019, at 6:56 AM, zhangli...@apache.org wrote:
> 
> I updated wiki for remove unapproved releases.
> 
> --
> 
> Liang Zhang (John)
> Apache ShardingSphere & Dubbo
> 
> 
> 吴晟 Sheng Wu  于2019年2月1日周五 下午10:51写道：
> 
>> Hi
>> 
>> 
>> By following the Apache policy, besides the suggestions I gave and done.
>> Just a moment ago, I deleted the recent two unapproved releases, 3.1.0.m1
>> and 3.1.0 at GitHub release page[1].
>> 
>> 
>> In further, I will help the shardingsphere community to follow the policy.
>> 
>> 
>> 
>> 
>> [1] https://github.com/apache/incubator-shardingsphere/releases
>> 
>> Sheng Wu
>> Apache SkyWalking, ShardingSphere, Zipkin
>> 
>> From Wu Sheng 's phone.
>> 
>> 
>> -- Original --
>> From: 吴晟 Sheng Wu 
>> Date: Wed,Jan 30,2019 5:54 PM
>> To: dev , dev <
>> d...@shardingsphere.apache.org>
>> Cc: Justin Mclean , jmclean 
>> Subject: Re: Unapproved Sharding Sphere releases
>> 
>> 
>> 
>> Hi
>> 
>> 
>> I think I agree the Justin's points.
>> No matter the release happens in Apache org repo or not, it still happened
>> after you asked and accepted by Incubator. So, it is not encouraged and not
>> following the Apache way.
>> 
>> 
>> I propose these adjustments
>> 1. Add statement in GitHub release versions. Saying these are not Apache
>> release.
>> 2. Add statement in you website home, document and download pages, saying
>> all available releases are not Apache releases
>> 3. After the first approved release, you only says before this
>> version(4.0.0 maybe) are not Apachre releases.
>> 4. Add statement in GitHub project readme.md for the same thing.
>> 
>> 
>> Especially for document pages, this needs to be tagged in clear way.
>> I know, those releases in maven central repo are hard to release, and not
>> good for the existing community. So, I hope my proposals are good enough.
>> 
>> 
>> 
>> Sheng Wu
>> Apache SkyWalking, ShardingSphere, Zipkin
>> 
>> From Wu Sheng 's phone.
>> 
>> 
>> -- Original --
>> From: zhangli...@apache.org 
>> Date: Wed,Jan 30,2019 0:03 PM
>> To: dev 
>> Cc: Justin Mclean , jmclean 
>> Subject: Re: Unapproved Sharding Sphere releases
>> 
>> 
>> 
>> Hello Justin,
>> 
>> Thanks for your advice.
>> This is a legacy release, which we have discussed on the dev mail list[1]
>> before.
>> This release is done before the transfer to ASF repo and package rename.
>> We are now preparing apache release which begins with new version(4.0.0).
>> We will not release non-Apache version any more in the future.
>> Any suggestion to identify versions like these kind of releases?
>> 
>> 
>> [1]
>> 
>> https://lists.apache.org/thread.html/a3bba7e53bfed6d18924b592ecf0533aebc8d307f8c7e399a7fec2cf@%3Cdev.shardingsphere.apache.org%3E
>> 
>> --
>> 
>> Liang Zhang (John)
>> Apache ShardingSphere & Dubbo
>> 
>> 
>> Justin Mclean  于2019年1月30日周三 上午6:23写道：
>> 
>>> Hi,
>>> 
>>> Looking at [1] there seems to have been releases made after you have
>>> entered incubation. All releases must be approved by the PPMC and the
>> IPMC
>>> (usually by voting). Can you please remove these releases and include in
>>> your upcoming incubator report what you will do to stop this happening
>>> going forward.
>>> 
>>> Thanks,
>>> Justin
>>> 
>>> P.S please CC me on any replies as I'm not subscribed to this list
>>> 
>>> 1.https://github.com/apache/incubator-shardingsphere/releases
>>> 
>>> 

Craig L Russell
Secretary, Apache Software Foundation
c...@apache.org  http://db.apache.org/jdo 

Re: Tying Dockerhub into development and release management

[Justin Mclean]

Hi,

> AFAIK everyone releasing binary convenience to dockerhub believed they were 
> authorized.

I didn't have a problem with them if they are based on actual released 
software, although it seem it’s now not clear that in line with policy or not, 
lets alone if a PPMC can  release tagged nightly or snapshots there.

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 Fisher]

Hey - not everyone agrees with Justin’s and Henry’s conclusions.

I don’t have time to argue every point.

AFAIK everyone releasing binary convenience to dockerhub believed they were 
authorized.

Pulsar had ONE release that was current for a short time that mistakenly kept 
an RC in the name. It was a valid release. Please review the vote thread.

Please stop these allegations and work to clarify the policy!

Until tomorrow.

Regards,
Dave

Sent from my iPhone

> On Feb 6, 2019, at 4:10 PM, Dave  wrote:
> 
> Seems like some well established projects need some schooling from The
> Incubator :-)
> 
> 
> On Wed, Feb 6, 2019 at 6:41 PM Justin Mclean 
> wrote:
> 
>> Hi,
>> 
>>> If projects want to make convenience binaries available for installation
>>> via Docker and DockerHub, then it seems like we need an official Apache
>>> DockerHub repository. Do we have one of those, or are folks just
>> publishing
>>> to personal repos?
>> 
>> A quick look shows HTTP, Maven, Tomcat, Casandra, Solr, Groovy and a
>> number of other Apache TLP using docker hub. Well they may be it’s hard to
>> know who is publishing them.
>> 
>> All are using Apache branding and most are marked as "Docker Official
>> Images” [1]
>> 
>> None seem to be publishing nightly there but there are binary versions of
>> released source code in all these projects.
>> 
>> I can also see ignite [2] published under an apache ignite account and
>> pulsar [2] under an apache pulsar account and nutch [3] published under an
>> apache account.
>> 
>> Pulsar is publishing RCs and looks like it was doing so during incubation
>> :-(
>> 
>> There are more project published under an apache named account here. [6]
>> That account would look official to an outsider from its given details.
>> 
>> A couple seem to be / may be pointing to master [7] or latest [9] and
>> others are releasing snapshots.[8] No wonder podlings get confused.
>> 
>> Thanks,
>> Justin
>> 
>> 1. https://hub.docker.com/search?q=Apache=image
>> 2. https://hub.docker.com/r/apacheignite/ignite
>> 3. https://hub.docker.com/r/apacheignite/ignite
>> 4. https://hub.docker.com/r/apachepulsar/pulsar
>> 5. https://hub.docker.com/r/apache/nutch
>> 6. https://hub.docker.com/u/apache
>> 7. https://hub.docker.com/r/apache/yetus/tags
>> 8. https://hub.docker.com/r/apache/syncope/tags
>> 9. https://hub.docker.com/r/apache/airflow/tags
>> -
>> 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: Tying Dockerhub into development and release management

[Hen]

On Wed, Feb 6, 2019 at 8:34 PM Justin Mclean 
wrote:

> HI,
>
> > 2. The PPMC should not publish software outside of Apache controlled
> > locations.
>
> We have TLP / PMCs doing that already
>
> > 3. Third parties may publish software based on Apache's, but they must
> not
> > cause user confusion (i.e. respect trademarks).
>
> And we have this as well (see docker links).
>
> All a bit of a mess really.
>
> Justin



Agreed :)

I think PMCs are trying to do the right thing for the public and we need to
come up with structure for how PMCs should publish installables on 3p
locations.

Hen

>

Re: Tying Dockerhub into development and release management

[Justin Mclean]

HI,

> 2. The PPMC should not publish software outside of Apache controlled
> locations.

We have TLP / PMCs doing that already

> 3. Third parties may publish software based on Apache's, but they must not
> cause user confusion (i.e. respect trademarks).

And we have this as well (see docker links).

All a bit of a mess really.

Justin

Re: Tying Dockerhub into development and release management

[Dave]

Seems like some well established projects need some schooling from The
Incubator :-)


On Wed, Feb 6, 2019 at 6:41 PM Justin Mclean 
wrote:

> Hi,
>
> > If projects want to make convenience binaries available for installation
> > via Docker and DockerHub, then it seems like we need an official Apache
> > DockerHub repository. Do we have one of those, or are folks just
> publishing
> > to personal repos?
>
> A quick look shows HTTP, Maven, Tomcat, Casandra, Solr, Groovy and a
> number of other Apache TLP using docker hub. Well they may be it’s hard to
> know who is publishing them.
>
> All are using Apache branding and most are marked as "Docker Official
> Images” [1]
>
> None seem to be publishing nightly there but there are binary versions of
> released source code in all these projects.
>
> I can also see ignite [2] published under an apache ignite account and
> pulsar [2] under an apache pulsar account and nutch [3] published under an
> apache account.
>
> Pulsar is publishing RCs and looks like it was doing so during incubation
> :-(
>
> There are more project published under an apache named account here. [6]
> That account would look official to an outsider from its given details.
>
>  A couple seem to be / may be pointing to master [7] or latest [9] and
> others are releasing snapshots.[8] No wonder podlings get confused.
>
> Thanks,
> Justin
>
> 1. https://hub.docker.com/search?q=Apache=image
> 2. https://hub.docker.com/r/apacheignite/ignite
> 3. https://hub.docker.com/r/apacheignite/ignite
> 4. https://hub.docker.com/r/apachepulsar/pulsar
> 5. https://hub.docker.com/r/apache/nutch
> 6. https://hub.docker.com/u/apache
> 7. https://hub.docker.com/r/apache/yetus/tags
> 8. https://hub.docker.com/r/apache/syncope/tags
> 9. https://hub.docker.com/r/apache/airflow/tags
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Apache ODF Toolkit (retired) migration to TDF

[Thorsten Behrens]

Hi Dave,

Dave Fisher wrote:
> Created https://issues.apache.org/jira/browse/INFRA-17810
> 
Thx a lot, seems the transfer is in flight.

> > 2. adding a pointer from the ASF website
> >   https://incubator.apache.org/projects/odftoolkit.html to the new
> >   TDF website for the project, such that people looking for it still
> >   find the active project:
> 
> Where do you want the link to point? Is it
> https://github.com/tdf/odftoolkit ? Please confirm and I’ll make the
> change.
>
I think we'd prefer a link to http://odftoolkit.org on that page,
since it's of more generic nature.

> > 4. adding a pointer on the github repository
> >   https://github.com/apache/odftoolkit to point to the new git
> >   repository at https://github.com/tdf/odftoolkit (if not removed
> >   anyway at some stage)
> 
> We can probably make the same README changes as to the svn repos.
> 
Thx a lot - and yeah from within the code repos, a link to
https://github.com/tdf/odftoolkit would be ideal.

All the best,

-- Thorsten


signature.asc
Description: PGP signature

Re: Tying Dockerhub into development and release management

[Justin Mclean]

Hi,

> If projects want to make convenience binaries available for installation
> via Docker and DockerHub, then it seems like we need an official Apache
> DockerHub repository. Do we have one of those, or are folks just publishing
> to personal repos?

A quick look shows HTTP, Maven, Tomcat, Casandra, Solr, Groovy and a number of 
other Apache TLP using docker hub. Well they may be it’s hard to know who is 
publishing them.

All are using Apache branding and most are marked as "Docker Official Images” 
[1]

None seem to be publishing nightly there but there are binary versions of 
released source code in all these projects.

I can also see ignite [2] published under an apache ignite account and pulsar 
[2] under an apache pulsar account and nutch [3] published under an apache 
account.

Pulsar is publishing RCs and looks like it was doing so during incubation :-(

There are more project published under an apache named account here. [6] That 
account would look official to an outsider from its given details.

 A couple seem to be / may be pointing to master [7] or latest [9] and others 
are releasing snapshots.[8] No wonder podlings get confused.

Thanks,
Justin

1. https://hub.docker.com/search?q=Apache=image
2. https://hub.docker.com/r/apacheignite/ignite
3. https://hub.docker.com/r/apacheignite/ignite
4. https://hub.docker.com/r/apachepulsar/pulsar
5. https://hub.docker.com/r/apache/nutch
6. https://hub.docker.com/u/apache
7. https://hub.docker.com/r/apache/yetus/tags
8. https://hub.docker.com/r/apache/syncope/tags
9. https://hub.docker.com/r/apache/airflow/tags
-
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]

Thanks, Hen. Seems like the "Apache controlled locations" bit is important
here.

If projects want to make convenience binaries available for installation
via Docker and DockerHub, then it seems like we need an official Apache
DockerHub repository. Do we have one of those, or are folks just publishing
to personal repos?

I recently made a Docker image available for the unreleased Apache Roller
6.0.0-SNAPSHOT on my personal DockerHub account, which I believe is kosher,
but where should the Roller project publish the convenience binary/Docker
image for the official 6.0.0 release?

Thanks,
Dave


On Wed, Feb 6, 2019 at 4:22 PM Roman Shaposhnik 
wrote:

> On Wed, Feb 6, 2019 at 10:12 PM Hen  wrote:
>
> > On Tue, Feb 5, 2019 at 6:45 AM Roman Shaposhnik 
> > wrote:
> >
> > > 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.
> > >
> > >
> > I remain confused on this topic.
> >
>
> We're not talking about "official" release binaries (whatever that means at
> ASF).
> We're talking about snapshot binaries that need to be available for
> developers.
> I don't think the rest of your reasoning applies *to this* particular
> discussion.
>
>
> >
> > The legal-discuss thread leads me to think the current state is:
> >
> > 1. The PPMC release some source code. They may release convenience
> binaries
> > on the Apache distribution urls, or in Maven Central (via Infra's
> support),
> > and those binaries must be built from the release soruce.
> > 2. The PPMC should not publish software outside of Apache controlled
> > locations.
> > 3. Third parties may publish software based on Apache's, but they must
> not
> > cause user confusion (i.e. respect trademarks).
> > 4. The PPMC may link to the software (including binaries) published by a
> > third party, but they should flag that it does not come from Apache and
> > should not treat it as the default user experience.
> >
> > All of which means PPMCs must not use PyPI, NuGet, NPM, DockerHub, etc.
> > unless Infra actively support a mechanism of doing so (which they
> > definitely do for Maven).
> >
> > (Though I'm confused as to whether #2 is a must not, should not, or can
> if
> > they wish to)
> >
> > Hen
> >
>

Mentor sign-off due next Tuesday (February 12th)

[Justin Mclean]

Hi,

Mentor sign-off of the podling reports is due next Tuesday.

So far these projects don’t have any sign-offs:
- BRPC (missing report)
- Doris
- ECharts
- Heron
- Pinot
- ShardingSphere
- Tamaya

Congratulations to SDAP where all mentors have signed off the report.

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

[VOTE] Release Apache MXNet (incubating) version 1.4.0.rc2

[Steffen Rochel]

Dear community,

This is a call for releasing Apache MXNet (incubating) 1.4.0, release
candidate 2

Apache MXNet (incubating) community has voted and approved the release.

Vote thread:

https://lists.apache.org/thread.html/4b445460d36d098be1c1e60e29869cf243e2bc37bd2b84ca7b1daab3@%3Cdev.mxnet.apache.org%3E


Result thread:

https://lists.apache.org/thread.html/60e3272326cf93100370fa5b01a54a4b2f18f95462553b5a1acfd456@%3Cdev.mxnet.apache.org%3E

The community raised the following issues which are not considered as
release stopper:

1. NOTICE year is wrong (2018): Not considered a stopping issue as release
was started in 2018.
2. TVM NOTICE missing - TVM NOTICE file was added post the commit ID used
in MXNet v1.4.0.rc2 release, not considered a stopping issue
3. build with make passes, but build with cmake failed in
3rdparty/dmlc-core/test/unittest
4. Recent MKLDNN upgrade prevents us from offering binary distribution for
earlier versions before OSX 10.13.


The source tarball, including signatures, digests, etc. can be found at:

https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.4.0.rc2/

The tag to be voted upon:
https://github.com/apache/incubator-mxnet/releases/tag/1.4.0.rc2

The release hash is e999a46

:

https://github.com/apache/incubator-mxnet/commit/e999a46a8ca1383e78a9178dc65fa91e6e656c26

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/Apache+MXNet+%28incubating%29+1.4.0+Release+Notes

The vote will be open at least 72 hours (Sunday February 10th 4pm PST) and
until sufficient votes are received.

[ ] +1 release this package as 1.4.0
[ ] +0 no opinion
[ ] -1 do not release this package because...

Best regards,
Steffen

Re: Tying Dockerhub into development and release management

[Roman Shaposhnik]

On Wed, Feb 6, 2019 at 10:12 PM Hen  wrote:

> On Tue, Feb 5, 2019 at 6:45 AM Roman Shaposhnik 
> wrote:
>
> > 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.
> >
> >
> I remain confused on this topic.
>

We're not talking about "official" release binaries (whatever that means at
ASF).
We're talking about snapshot binaries that need to be available for
developers.
I don't think the rest of your reasoning applies *to this* particular
discussion.


>
> The legal-discuss thread leads me to think the current state is:
>
> 1. The PPMC release some source code. They may release convenience binaries
> on the Apache distribution urls, or in Maven Central (via Infra's support),
> and those binaries must be built from the release soruce.
> 2. The PPMC should not publish software outside of Apache controlled
> locations.
> 3. Third parties may publish software based on Apache's, but they must not
> cause user confusion (i.e. respect trademarks).
> 4. The PPMC may link to the software (including binaries) published by a
> third party, but they should flag that it does not come from Apache and
> should not treat it as the default user experience.
>
> All of which means PPMCs must not use PyPI, NuGet, NPM, DockerHub, etc.
> unless Infra actively support a mechanism of doing so (which they
> definitely do for Maven).
>
> (Though I'm confused as to whether #2 is a must not, should not, or can if
> they wish to)
>
> Hen
>

Re: Tying Dockerhub into development and release management

[Hen]

On Tue, Feb 5, 2019 at 6:45 AM Roman Shaposhnik 
wrote:

> 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.
>
>
I remain confused on this topic.

The legal-discuss thread leads me to think the current state is:

1. The PPMC release some source code. They may release convenience binaries
on the Apache distribution urls, or in Maven Central (via Infra's support),
and those binaries must be built from the release soruce.
2. The PPMC should not publish software outside of Apache controlled
locations.
3. Third parties may publish software based on Apache's, but they must not
cause user confusion (i.e. respect trademarks).
4. The PPMC may link to the software (including binaries) published by a
third party, but they should flag that it does not come from Apache and
should not treat it as the default user experience.

All of which means PPMCs must not use PyPI, NuGet, NPM, DockerHub, etc.
unless Infra actively support a mechanism of doing so (which they
definitely do for Maven).

(Though I'm confused as to whether #2 is a must not, should not, or can if
they wish to)

Hen

Re: [PROPOSAL] New blockchain project: Cava

[Antoine Toulme]

Thanks Furkan, I’ll list you as a mentor too.

> On Feb 6, 2019, at 10:18 AM, Furkan KAMACI  wrote:
> 
> Hi Antonie,
> 
> Thanks for the proposal! Feel free to ask any questions about it. By the
> way, right along with being an initial committer, I would like to help as a
> mentor too.
> 
> Kind Regards,
> Furkan KAMACI
> 
> On Wed, Feb 6, 2019 at 9:10 PM Antoine Toulme  wrote:
> 
>> All, thank you for your expressions of interest.
>> 
>> I have listed all names reported here and a few more colleagues and
>> contributors in the page:
>> 
>> https://wiki.apache.org/incubator/CavaProposal <
>> https://wiki.apache.org/incubator/CavaProposal>
>> 
>> In particular, thank you for the folks stepping forward to volunteer to
>> mentor this project. I have listed you all on the page for now.
>> 
>> There is still a couple of TBD points on the proposal. I will address them
>> in a new thread.
>> I will also leave this proposal open until Monday next week, so we can
>> guarantee maximum public participation. I will engage with the incubator
>> early next week on next steps.
>> 
>> Cheers,
>> 
>> Antoine
>> 
>>> On Feb 6, 2019, at 5:02 AM, Pierre Smits  wrote:
>>> 
>>> Hi Antoine,
>>> 
>>> Thank you for bringing this proposal to the Apache Incubator. So I gladly
>>> give my +1.
>>> 
>>> Having a background in accounting and being one of the Apache OFBiz
>>> contributors I am very interested in blockchain technology, while being
>>> very interested in applying its functionalities in an ERP setting like
>>> Apache OFBiz is.
>>> 
>>> While the Apache Trafodion project was in incubation I was very much
>>> involved in helping (mentoring) that project towards graduation, which it
>>> has successively done. I would like to help out as one of the mentors,
>> and
>>> as a contributor/committer (of the other kind).
>>> 
>>> Best regards,
>>> 
>>> Pierre Smits
>>> 
>>> *Apache Trafodion , Vice President & PMC
>>> Chair*
>>> *Apache Directory , PMC Member*
>>> Apache Incubator , committer
>>> *Apache OFBiz , contributor (without
>> privileges)
>>> since 2008*
>>> Apache Steve , committer
>>> 
>>> 
>>> On Tue, Feb 5, 2019 at 11: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 

Re: [PROPOSAL] New blockchain project: Cava

[Antoine Toulme]

> On Feb 6, 2019, at 10:11 AM, Greg Stein  wrote:
> 
> On Wed, Feb 6, 2019 at 10:48 AM Dave Fisher  wrote:
> 
>>> On Feb 6, 2019, at 6:16 AM, Greg Stein  wrote:
>>> 
 On Tue, Feb 5, 2019 at 6: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]
 
>>> 
>>> I read it as: it seems they are more (rightly) concerned that the
>>> derivation of the name includes a corporate name. Not that it interferes
>>> with other existing names.
>> 
>> It is not unusual for an Apache project name to be a brand and domain in
>> another field of use.
>> 
>> Try these:
>> Tomcat.com -> baited rodent traps
>> Spark.com -> dating site
>> Camel.com -> tobacco
>> Geronimo.com -> help for non-profits
>> Sling.com -> live tv streaming
>> Jackrabbit.com -> athletic apparel
>> 
> 
> I understand that, and how trademarks are area-specific.
> 
> The proposal specifically states: *Cava is a contraction of "ConsenSys
> Java"*
> 
> Thus, I read the community requesting a to-do for a new name that is not
> based on a company name.
> 
> -g

Yes, I think it will help adoption if the community owns the name.

-
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

[Furkan KAMACI]

Hi Antonie,

Thanks for the proposal! Feel free to ask any questions about it. By the
way, right along with being an initial committer, I would like to help as a
mentor too.

Kind Regards,
Furkan KAMACI

On Wed, Feb 6, 2019 at 9:10 PM Antoine Toulme  wrote:

> All, thank you for your expressions of interest.
>
> I have listed all names reported here and a few more colleagues and
> contributors in the page:
>
> https://wiki.apache.org/incubator/CavaProposal <
> https://wiki.apache.org/incubator/CavaProposal>
>
> In particular, thank you for the folks stepping forward to volunteer to
> mentor this project. I have listed you all on the page for now.
>
> There is still a couple of TBD points on the proposal. I will address them
> in a new thread.
> I will also leave this proposal open until Monday next week, so we can
> guarantee maximum public participation. I will engage with the incubator
> early next week on next steps.
>
> Cheers,
>
> Antoine
>
> > On Feb 6, 2019, at 5:02 AM, Pierre Smits  wrote:
> >
> > Hi Antoine,
> >
> > Thank you for bringing this proposal to the Apache Incubator. So I gladly
> > give my +1.
> >
> > Having a background in accounting and being one of the Apache OFBiz
> > contributors I am very interested in blockchain technology, while being
> > very interested in applying its functionalities in an ERP setting like
> > Apache OFBiz is.
> >
> > While the Apache Trafodion project was in incubation I was very much
> > involved in helping (mentoring) that project towards graduation, which it
> > has successively done. I would like to help out as one of the mentors,
> and
> > as a contributor/committer (of the other kind).
> >
> > Best regards,
> >
> > Pierre Smits
> >
> > *Apache Trafodion , Vice President & PMC
> > Chair*
> > *Apache Directory , PMC Member*
> > Apache Incubator , committer
> > *Apache OFBiz , contributor (without
> privileges)
> > since 2008*
> > Apache Steve , committer
> >
> >
> > On Tue, Feb 5, 2019 at 11: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 

Re: [PROPOSAL] New blockchain project: Cava

[Greg Stein]

On Wed, Feb 6, 2019 at 10:48 AM Dave Fisher  wrote:

> > On Feb 6, 2019, at 6:16 AM, Greg Stein  wrote:
> >
> >> On Tue, Feb 5, 2019 at 6: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]
> >>
> >
> > I read it as: it seems they are more (rightly) concerned that the
> > derivation of the name includes a corporate name. Not that it interferes
> > with other existing names.
>
> It is not unusual for an Apache project name to be a brand and domain in
> another field of use.
>
> Try these:
> Tomcat.com -> baited rodent traps
> Spark.com -> dating site
> Camel.com -> tobacco
> Geronimo.com -> help for non-profits
> Sling.com -> live tv streaming
> Jackrabbit.com -> athletic apparel
>

I understand that, and how trademarks are area-specific.

The proposal specifically states: *Cava is a contraction of "ConsenSys
Java"*

Thus, I read the community requesting a to-do for a new name that is not
based on a company name.

-g

Re: [PROPOSAL] New blockchain project: Cava

[Antoine Toulme]

All, thank you for your expressions of interest.

I have listed all names reported here and a few more colleagues and 
contributors in the page:

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


In particular, thank you for the folks stepping forward to volunteer to mentor 
this project. I have listed you all on the page for now.

There is still a couple of TBD points on the proposal. I will address them in a 
new thread.
I will also leave this proposal open until Monday next week, so we can 
guarantee maximum public participation. I will engage with the incubator early 
next week on next steps.

Cheers,

Antoine

> On Feb 6, 2019, at 5:02 AM, Pierre Smits  wrote:
> 
> Hi Antoine,
> 
> Thank you for bringing this proposal to the Apache Incubator. So I gladly
> give my +1.
> 
> Having a background in accounting and being one of the Apache OFBiz
> contributors I am very interested in blockchain technology, while being
> very interested in applying its functionalities in an ERP setting like
> Apache OFBiz is.
> 
> While the Apache Trafodion project was in incubation I was very much
> involved in helping (mentoring) that project towards graduation, which it
> has successively done. I would like to help out as one of the mentors, and
> as a contributor/committer (of the other kind).
> 
> Best regards,
> 
> Pierre Smits
> 
> *Apache Trafodion , Vice President & PMC
> Chair*
> *Apache Directory , PMC Member*
> Apache Incubator , committer
> *Apache OFBiz , contributor (without privileges)
> since 2008*
> Apache Steve , committer
> 
> 
> On Tue, Feb 5, 2019 at 11: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.
>> 
>> 

Re: [PROPOSAL] New blockchain project: Cava

[Zak Cole]

Count me in.

On 2019/02/05 22:42:31, 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:'''> 
> 

Re: [PROPOSAL] New blockchain project: Cava

[Dave Fisher]

Sent from my iPhone

> On Feb 6, 2019, at 6:16 AM, Greg Stein  wrote:
> 
>> On Tue, Feb 5, 2019 at 6: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]
>> 
> 
> I read it as: it seems they are more (rightly) concerned that the
> derivation of the name includes a corporate name. Not that it interferes
> with other existing names.

It is not unusual for an Apache project name to be a brand and domain in 
another field of use.

Try these:
Tomcat.com -> baited rodent traps
Spark.com -> dating site
Camel.com -> tobacco
Geronimo.com -> help for non-profits
Sling.com -> live tv streaming
Jackrabbit.com -> athletic apparel

Best Regards,
Dave


> 
> Cheers,
> -g


-
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

[Greg Stein]

On Tue, Feb 5, 2019 at 6: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]
>

I read it as: it seems they are more (rightly) concerned that the
derivation of the name includes a corporate name. Not that it interferes
with other existing names.

Cheers,
-g

Re: [PROPOSAL] New blockchain project: Cava

[Vinayakumar B]

+1,

Interesting proposal.

I would be happy to be part of the project in any way possible..
(Contributor/Reviewer/Mentor/Committer)

-Vinay

On Wed, 6 Feb 2019, 6:32 pm Pierre Smits  Hi Antoine,
>
> Thank you for bringing this proposal to the Apache Incubator. So I gladly
> give my +1.
>
> Having a background in accounting and being one of the Apache OFBiz
> contributors I am very interested in blockchain technology, while being
> very interested in applying its functionalities in an ERP setting like
> Apache OFBiz is.
>
> While the Apache Trafodion project was in incubation I was very much
> involved in helping (mentoring) that project towards graduation, which it
> has successively done. I would like to help out as one of the mentors, and
> as a contributor/committer (of the other kind).
>
> Best regards,
>
> Pierre Smits
>
> *Apache Trafodion , Vice President & PMC
> Chair*
> *Apache Directory , PMC Member*
> Apache Incubator , committer
> *Apache OFBiz , contributor (without privileges)
> since 2008*
> Apache Steve , committer
>
>
> On Tue, Feb 5, 2019 at 11: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 

Re: [PROPOSAL] New blockchain project: Cava

[Pierre Smits]

Hi Antoine,

Thank you for bringing this proposal to the Apache Incubator. So I gladly
give my +1.

Having a background in accounting and being one of the Apache OFBiz
contributors I am very interested in blockchain technology, while being
very interested in applying its functionalities in an ERP setting like
Apache OFBiz is.

While the Apache Trafodion project was in incubation I was very much
involved in helping (mentoring) that project towards graduation, which it
has successively done. I would like to help out as one of the mentors, and
as a contributor/committer (of the other kind).

Best regards,

Pierre Smits

*Apache Trafodion , Vice President & PMC
Chair*
*Apache Directory , PMC Member*
Apache Incubator , committer
*Apache OFBiz , contributor (without privileges)
since 2008*
Apache Steve , committer


On Tue, Feb 5, 2019 at 11: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 

Re: [PROPOSAL] New blockchain project: Cava

[Jean-Baptiste Onofré]

Hi Antoine,

as said in my other e-mail, I would like to help. Especially, it seems
now you have a set of blockchain library, but not yet a runtime.
I would like to help on the runtime part (if it's planned to be part of
the project), especially around Karaf, Camel, Kafka, whatever.

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 

Re: [PROPOSAL] New blockchain project: Cava

[Charith Elvitigala]

+1

On Wed, 6 Feb 2019 at 13:04, Furkan KAMACI  wrote:

> 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