I agree with Ben - why can other Apache communities navigate this issue,
and Apache Cassandra cannot?
I think that we grow the community when we make people aware of how
Cassandra is used. Why make new users to Cassandra search for things that
we all know exist? Help them to discover!
I would
I would be sad to see us drop this just because it's a hard discussion with
a few different opinions. My apologies if this discussion is making folks
feel excluded.
Whilst I don't have a problem with a strict approach and it does improve
user clarity. I can understand how it might feel
>
> And I'm thinking of anyone that has to update this list and reason through
> all of the complex rulesets of why or why not, It's really not fair to
> them.
My proposal is that we completely drop the Cassandra Cloud Offereing
> section.
> Given that criteria, Professional Support and Education
gt; for the consequences of utilising an endorsement or other facility, not
> > as
> > > a communicative act indicating a lack of actual endorsement.
> > >
> > > Besides which, many here have communicated reasons they believe it is
> > > wrong to promote t
is a weaker
> criteria
> > than endorsement.
> >
> >
> > From: Paulo Motta
> > Date: Tuesday, 29 June 2021 at 19:14
> > To: Cassandra DEV
> > Subject: Re: Additions to Cassandra ecosystem page?
> > > Listing a product on our website implicitly endo
> From: Paulo Motta
> Date: Tuesday, 29 June 2021 at 19:14
> To: Cassandra DEV
> Subject: Re: Additions to Cassandra ecosystem page?
> > Listing a product on our website implicitly endorses that offering, and
> we should absolutely be restrictive about what we endorse. I’m
t; >
> > I don’t think this website is going to drive a lot of traffic to any of
> > these businesses, so I doubt any of them should be upset at any loss of
> > revenue. The question is simply one of principle for us as a project.
> >
> >
> >
> > From:
gt;
> > I don’t think this website is going to drive a lot of traffic to any of
> > these businesses, so I doubt any of them should be upset at any loss of
> > revenue. The question is simply one of principle for us as a project.
> >
> >
> >
> > From: Benjamin Le
for us as a project.
>
>
>
> From: Benjamin Lerer
> Date: Tuesday, 29 June 2021 at 08:10
> To: dev@cassandra.apache.org
> Subject: Re: Additions to Cassandra ecosystem page?
> I feel that we are going into a too restrictive direction. I believe that
> we have more to win by
for us as a project.
From: Benjamin Lerer
Date: Tuesday, 29 June 2021 at 08:10
To: dev@cassandra.apache.org
Subject: Re: Additions to Cassandra ecosystem page?
I feel that we are going into a too restrictive direction. I believe that
we have more to win by being open and welcoming.
-1
I feel that we are going into a too restrictive direction. I believe that
we have more to win by being open and welcoming.
-1 for the strict approach and for the licences.
Le mar. 29 juin 2021 à 00:40, Ben Bromhead a écrit :
> On Thu, Jun 24, 2021 at 2:38 AM Joshua McKenzie
> wrote:
>
> >
> >
On Thu, Jun 24, 2021 at 2: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
>
> I'm also comfortable with a strict approach where we just list actual
> Apache Cassandra offerings, that also provides good solid clarity to
> users.
That sounds like a reasonable proposal. I just do not know how we can do
that in practice. What is a actual Apache Cassandra offering and how
I'm a huge +1 to the sentiments here.
I have to confess that I've been responsible for publishing the updates for
several months now with Mick's mentoring. I publish the content I was
requested to push to the site but as far as review is concerned, the only
review I do is mostly around grammar
t;>
>>>> 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
>>>&
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.o
.@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
> >
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 sec
+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
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
y 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 cert
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@cassand
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
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..
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.apach
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
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
27 matches
Mail list logo
