Re: Additions to Cassandra ecosystem page?

[Jeff Jirsa]

This would be my preference.


On Wed, Jun 23, 2021 at 2:22 PM Ben Bromhead  wrote:

> I'm also comfortable with a strict approach where we just list actual
> Apache Cassandra offerings, that also provides good solid clarity to users.
>
> On Thu, Jun 24, 2021 at 3:06 AM bened...@apache.org 
> wrote:
>
> > +1
> >
> > From: Brandon Williams 
> > Date: Wednesday, 23 June 2021 at 15:44
> > To: dev@cassandra.apache.org 
> > Subject: Re: Additions to Cassandra ecosystem page?
> > On Wed, Jun 23, 2021 at 9:38 AM Joshua McKenzie 
> > wrote:
> > >
> > > The obvious core responsibility of the website should be to ASLv2
> > > permissively licensed Apache Cassandra and secondarily to CQL as a
> > protocol
> > > IMO. I don't think we as a project should be tracking derivative works,
> > > forks, or other things built on top of the code-base and certainly not
> > > things with wildly varied licensing (AGPL, proprietary closed, etc).
> >
> > I agree.  I don't see how it makes sense for us to promote less
> > compatible derivatives with more restrictive licensing.  Imitation may
> > be flattery but as you pointed out, we don't need to be the ones
> > advertising it.
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> > For additional commands, e-mail: dev-h...@cassandra.apache.org
> >
>
>
> --
>
> Ben Bromhead
>
> Instaclustr | www.instaclustr.com | @instaclustr
>  | +64 27 383 8975
>

Re: Additions to Cassandra ecosystem page?

[Ben Bromhead]

I'm also comfortable with a strict approach where we just list actual
Apache Cassandra offerings, that also provides good solid clarity to users.

On Thu, Jun 24, 2021 at 3:06 AM bened...@apache.org 
wrote:

> +1
>
> From: Brandon Williams 
> Date: Wednesday, 23 June 2021 at 15:44
> To: dev@cassandra.apache.org 
> Subject: Re: Additions to Cassandra ecosystem page?
> On Wed, Jun 23, 2021 at 9:38 AM Joshua McKenzie 
> wrote:
> >
> > The obvious core responsibility of the website should be to ASLv2
> > permissively licensed Apache Cassandra and secondarily to CQL as a
> protocol
> > IMO. I don't think we as a project should be tracking derivative works,
> > forks, or other things built on top of the code-base and certainly not
> > things with wildly varied licensing (AGPL, proprietary closed, etc).
>
> I agree.  I don't see how it makes sense for us to promote less
> compatible derivatives with more restrictive licensing.  Imitation may
> be flattery but as you pointed out, we don't need to be the ones
> advertising it.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
>


-- 

Ben Bromhead

Instaclustr | www.instaclustr.com | @instaclustr
 | +64 27 383 8975

Re: Additions to Cassandra ecosystem page?

[bened...@apache.org]

+1

From: Brandon Williams 
Date: Wednesday, 23 June 2021 at 15:44
To: dev@cassandra.apache.org 
Subject: Re: Additions to Cassandra ecosystem page?
On Wed, Jun 23, 2021 at 9:38 AM Joshua McKenzie  wrote:
>
> The obvious core responsibility of the website should be to ASLv2
> permissively licensed Apache Cassandra and secondarily to CQL as a protocol
> IMO. I don't think we as a project should be tracking derivative works,
> forks, or other things built on top of the code-base and certainly not
> things with wildly varied licensing (AGPL, proprietary closed, etc).

I agree.  I don't see how it makes sense for us to promote less
compatible derivatives with more restrictive licensing.  Imitation may
be flattery but as you pointed out, we don't need to be the ones
advertising it.

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

Re: Additions to Cassandra ecosystem page?

[Brandon Williams]

On Wed, Jun 23, 2021 at 9:38 AM Joshua McKenzie  wrote:
>
> The obvious core responsibility of the website should be to ASLv2
> permissively licensed Apache Cassandra and secondarily to CQL as a protocol
> IMO. I don't think we as a project should be tracking derivative works,
> forks, or other things built on top of the code-base and certainly not
> things with wildly varied licensing (AGPL, proprietary closed, etc).

I agree.  I don't see how it makes sense for us to promote less
compatible derivatives with more restrictive licensing.  Imitation may
be flattery but as you pointed out, we don't need to be the ones
advertising it.

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

Re: Additions to Cassandra ecosystem page?

[Joshua McKenzie]

>
> With it we could simply organize the offers by level of CQL compatibility.

I would suggest another category along the lines of "Cassandra Protocol
> compatible offerings"

The obvious core responsibility of the website should be to ASLv2
permissively licensed Apache Cassandra and secondarily to CQL as a protocol
IMO. I don't think we as a project should be tracking derivative works,
forks, or other things built on top of the code-base and certainly not
things with wildly varied licensing (AGPL, proprietary closed, etc).

To go that route we either become fully inclusive of everything or become
Kingmakers, and either way there's the consequence of inconsistent levels
of vetting, maintenance, and dilution of what it means to "be Cassandra".
There's plenty of other websites for other projects and everyone has access
to search engines.


On Wed, Jun 23, 2021 at 5:39 AM Benjamin Lerer  wrote:

> Brian Houser proposed to build a tool for the next release to validate the
> level of CQL compatibility. With it we could simply organize the offers by
> level of CQL compatibility.
>
> Le mer. 23 juin 2021 à 10:24, bened...@apache.org <
> pub...@belliottsmith.com>
> a écrit :
>
> > If we are going to include copycats, let’s (in all seriousness) at least
> > be fun about it and put them under the heading “Copycats”
> >
> > We should also include a disclaimer that they may not be feature
> > compatible. Since due diligence on this is hard even for subject matter
> > experts, it would be nicer still if we put a bit of detail explaining
> some
> > of the differences before putting them on the website, but I doubt anyone
> > has the time for that (so I still slightly prefer we don’t include them).
> >
> >
> > 
> > From: Ben Bromhead 
> > Sent: Wednesday, June 23, 2021 4:56:34 AM
> > To: Cassandra DEV 
> > Subject: Re: Additions to Cassandra ecosystem page?
> >
> > There is certainly a lack of clarity in the grouping, as a number of
> those
> > services are not offering Apache Cassandra. I would suggest another
> > category along the lines of "Cassandra Protocol compatible offerings".
> >
> > That way users can easily distinguish between ecosystem offerings where
> > "the driver works, but certain features might not", vs an actual Apache
> > Cassandra offering.
> >
> > We could then also add things like Yugabyte and Scylla into that
> category.
> >
> > On Wed, Jun 23, 2021 at 11:15 AM Jonathan Koppenhofer <
> j...@koppedomain.com
> > >
> > wrote:
> >
> > > No major opinion on the "cloud offerings" piece, but I agree people
> > should
> > > know what they are getting into, and be able to make an informed
> > decision.
> > > However, if someone is going down that path, I would hope they do the
> > > due-diligence to make sure it fits their requirements.
> > >
> > > 1 small update I would suggest. It seems like Datastax Spring Boot
> entry
> > > would go in development frameworks as opposed to the sidecar section.
> > >
> > > On Tue, Jun 22, 2021, 5:39 PM bened...@apache.org  >
> > > wrote:
> > >
> > > > Under Cloud Offerings, are we comfortable implicitly endorsing “API
> > > > compatible” offerings that aren’t actually Cassandra, and also don’t
> > (as
> > > > far as I am aware) fully support Cassandra functionality? Should we
> at
> > > > least mention that this is the case?
> > > >
> > > >
> > > > From: Melissa Logan 
> > > > Date: Tuesday, 22 June 2021 at 21:39
> > > > To: u...@cassandra.apache.org ,
> > > > dev@cassandra.apache.org 
> > > > Subject: Additions to Cassandra ecosystem page?
> > > > Hi all,
> > > >
> > > > The Cassandra community recently updated its website and has added
> > > several
> > > > new entries to the Ecosystem page:
> > > https://cassandra.apache.org/ecosystem/
> > > > .
> > > >
> > > > If you have edits or know of other third-party Cassandra projects,
> > tools,
> > > > products, etc that may be useful to others -- please get in touch and
> > > we'll
> > > > add to the next round of site updates in July.
> > > >
> > > > Thanks!
> > > >
> > > > Melissa
> > > > Apache Cassandra Contributor
> > > >
> > >
> >
> >
> > --
> >
> > Ben Bromhead
> >
> > Instaclustr | www.instaclustr.com |
> > @instaclustr
> >  | +64 27 383 8975
> >
>

Re: Additions to Cassandra ecosystem page?

[Benjamin Lerer]

Brian Houser proposed to build a tool for the next release to validate the
level of CQL compatibility. With it we could simply organize the offers by
level of CQL compatibility.

Le mer. 23 juin 2021 à 10:24, bened...@apache.org 
a écrit :

> If we are going to include copycats, let’s (in all seriousness) at least
> be fun about it and put them under the heading “Copycats”
>
> We should also include a disclaimer that they may not be feature
> compatible. Since due diligence on this is hard even for subject matter
> experts, it would be nicer still if we put a bit of detail explaining some
> of the differences before putting them on the website, but I doubt anyone
> has the time for that (so I still slightly prefer we don’t include them).
>
>
> 
> From: Ben Bromhead 
> Sent: Wednesday, June 23, 2021 4:56:34 AM
> To: Cassandra DEV 
> Subject: Re: Additions to Cassandra ecosystem page?
>
> There is certainly a lack of clarity in the grouping, as a number of those
> services are not offering Apache Cassandra. I would suggest another
> category along the lines of "Cassandra Protocol compatible offerings".
>
> That way users can easily distinguish between ecosystem offerings where
> "the driver works, but certain features might not", vs an actual Apache
> Cassandra offering.
>
> We could then also add things like Yugabyte and Scylla into that category.
>
> On Wed, Jun 23, 2021 at 11:15 AM Jonathan Koppenhofer  >
> wrote:
>
> > No major opinion on the "cloud offerings" piece, but I agree people
> should
> > know what they are getting into, and be able to make an informed
> decision.
> > However, if someone is going down that path, I would hope they do the
> > due-diligence to make sure it fits their requirements.
> >
> > 1 small update I would suggest. It seems like Datastax Spring Boot entry
> > would go in development frameworks as opposed to the sidecar section.
> >
> > On Tue, Jun 22, 2021, 5:39 PM bened...@apache.org 
> > wrote:
> >
> > > Under Cloud Offerings, are we comfortable implicitly endorsing “API
> > > compatible” offerings that aren’t actually Cassandra, and also don’t
> (as
> > > far as I am aware) fully support Cassandra functionality? Should we at
> > > least mention that this is the case?
> > >
> > >
> > > From: Melissa Logan 
> > > Date: Tuesday, 22 June 2021 at 21:39
> > > To: u...@cassandra.apache.org ,
> > > dev@cassandra.apache.org 
> > > Subject: Additions to Cassandra ecosystem page?
> > > Hi all,
> > >
> > > The Cassandra community recently updated its website and has added
> > several
> > > new entries to the Ecosystem page:
> > https://cassandra.apache.org/ecosystem/
> > > .
> > >
> > > If you have edits or know of other third-party Cassandra projects,
> tools,
> > > products, etc that may be useful to others -- please get in touch and
> > we'll
> > > add to the next round of site updates in July.
> > >
> > > Thanks!
> > >
> > > Melissa
> > > Apache Cassandra Contributor
> > >
> >
>
>
> --
>
> Ben Bromhead
>
> Instaclustr | www.instaclustr.com |
> @instaclustr
>  | +64 27 383 8975
>

Re: Additions to Cassandra ecosystem page?

[bened...@apache.org]

If we are going to include copycats, let’s (in all seriousness) at least be fun 
about it and put them under the heading “Copycats”

We should also include a disclaimer that they may not be feature compatible. 
Since due diligence on this is hard even for subject matter experts, it would 
be nicer still if we put a bit of detail explaining some of the differences 
before putting them on the website, but I doubt anyone has the time for that 
(so I still slightly prefer we don’t include them).



From: Ben Bromhead 
Sent: Wednesday, June 23, 2021 4:56:34 AM
To: Cassandra DEV 
Subject: Re: Additions to Cassandra ecosystem page?

There is certainly a lack of clarity in the grouping, as a number of those
services are not offering Apache Cassandra. I would suggest another
category along the lines of "Cassandra Protocol compatible offerings".

That way users can easily distinguish between ecosystem offerings where
"the driver works, but certain features might not", vs an actual Apache
Cassandra offering.

We could then also add things like Yugabyte and Scylla into that category.

On Wed, Jun 23, 2021 at 11:15 AM Jonathan Koppenhofer 
wrote:

> No major opinion on the "cloud offerings" piece, but I agree people should
> know what they are getting into, and be able to make an informed decision.
> However, if someone is going down that path, I would hope they do the
> due-diligence to make sure it fits their requirements.
>
> 1 small update I would suggest. It seems like Datastax Spring Boot entry
> would go in development frameworks as opposed to the sidecar section.
>
> On Tue, Jun 22, 2021, 5:39 PM bened...@apache.org 
> wrote:
>
> > Under Cloud Offerings, are we comfortable implicitly endorsing “API
> > compatible” offerings that aren’t actually Cassandra, and also don’t (as
> > far as I am aware) fully support Cassandra functionality? Should we at
> > least mention that this is the case?
> >
> >
> > From: Melissa Logan 
> > Date: Tuesday, 22 June 2021 at 21:39
> > To: u...@cassandra.apache.org ,
> > dev@cassandra.apache.org 
> > Subject: Additions to Cassandra ecosystem page?
> > Hi all,
> >
> > The Cassandra community recently updated its website and has added
> several
> > new entries to the Ecosystem page:
> https://cassandra.apache.org/ecosystem/
> > .
> >
> > If you have edits or know of other third-party Cassandra projects, tools,
> > products, etc that may be useful to others -- please get in touch and
> we'll
> > add to the next round of site updates in July.
> >
> > Thanks!
> >
> > Melissa
> > Apache Cassandra Contributor
> >
>


--

Ben Bromhead

Instaclustr | www.instaclustr.com | @instaclustr
 | +64 27 383 8975