en but it doesn't excuse not writing docs, even if it
>> becomes a PMC type rule for committers to commit Docs for new features like
>> they should be committing unit tests. At least it improves what is shipped
>> with the Apache project in question.
I’m investigating something a few ASF members contacted
me about and pointed out, so I’m hoping you can help
guide me here as a community. I have heard that a company,
DataStax, whose marketing material mentions it as the only
Cassandra vendor, “controls” the Java Driver for Apache
Thanks Jonathan. I’m starting to get a clearer idea of what’s
going on here. Do you think it was a walled garden in terms of
making reviews for incoming driver patches when you did have
them in the tree? What you are talking about in the first paragraph
is precisely the reason that your community
here at the ASF.
>> I’m happy to be corrected that that is the case, and/or that
>> I’ve missed something, but the first reply to questions like
>> this from newbies shouldn’t be to point to an external website.
>> the diversity and health issues of the project, and also some
>> ideas about potential strategies for mitigation.
>> I appreciate the open and honest conversation thus far. Let’s
>> keep it up.
part of Cassandra is hosted
>Chris Mattmann, Ph.D.
>Instrument Software and Science Data Systems Section (398)
>NASA Jet Propulsion Laboratory Pasadena,
>it was only done via developers who most likely won't document or do a poor
>job at documentation).
>Having some documentation is much better for the community than the
>alternative that "the code is the documentation".
>Nothing is free.
>On Jun 6, 2016,
Dev discussion about the project should ideally be on the dev list.
Further, all *decisions* must be on the dev list for the project.
JIRA has the negative impact that it is lost in many people’s email
filters and hard to parse the signal from the noise.
I would consider some well formed emails
Yeah this is something that hopefully folks at DataStax can work to
update in its marketing material..
On 8/6/16, 2:54 PM, "James Carman" wrote:
>I don't see any reference to the fact that it's "Apache Cassandra" here...
>-- Forwarded message -
Carman and others bring up about
marketing material from DataStax
4. PMC composition and overall approach to PMC and committers
Discussion belongs on the dev list. Putting discussion in JIRA, is fine, but
there is a lot of noise in that signal and people may or may not be watching
the JIRA list. In fact, I don’t see JIRA sent to the dev list at all so you are
forking the conversation to a high noise
essary if we simply use JIRA.
> So, I'm +1 to just post JIRA link to dev list.
> On Mon, Aug 15, 2016 at 12:35 PM, Chris Mattmann <mattm...@apache.org>
> > This is a good outward flow of info to the dev list. However, the
> On Aug 15, 2016, at 12:22 PM, Chris Mattmann <mattm...@apache.org> wrote:
> Discussion belongs on the dev list. Putting discussion in JIRA, is fine,
> there is a lot of noise in that signal and people may or may no
s reference-able in the changes.txt and other things.
I think the approach proposed by Jonathan is a nice way to keep dev list
followers informed but keeping ticket details focused.
> On Aug 15, 2016, at 1:12 PM, Chris Mattmann <mattm...@apache.org> wrote:
How is it harder to point someone to mail?
Have you seen lists.apache.org?
On 8/15/16, 10:08 AM, "Jeremiah D Jordan" wrote:
I like keeping things in JIRA because then everything is in
We aren’t doing it currently, but we could, and probably should.
On 15 August 2016 at 18:22:36, Chris Mattmann (mattm...@apache.org) wrote:
Discussion belongs on the dev list. Putting discussion in JIRA, is fine,
there is a lot of noise in that signa
e good for broad discussion or bringing specific issues to
the attention of the broader community. It should never be the source of truth.
Sent from my iPhone
On Aug 15, 2016, at 2:57 PM, Chris Mattmann
So then what was the point of Ellis’s proposal, and this discussion, if
there was never a choice in the matter in the first place?
On 8/15/16, 2:03 PM, "Chris Mattmann" <mattm...@apache.org> wrote:
I’m sorry but you are massively confused if y
> >> Chris,
> >> Yes, I would like to be added, and here sis the ticket I filed:
> >> https://issues.apache.org/jira/browse/INFRA-12858.
> >> Thanks,
> >> -Jason
rmation to make a sound decision in that
> All I ask if for some common professionalism and courtesy, nothing
> On 11/4/16, 4:46 PM, "Chris Mattmann" <mattm...@apache.org>
of their community
leaders becoming “ASF members”,
and that Cassandra MVPs are great – but secondary – to the responsibilities of
the PMC to move towards ensuring
its community understands the Apache Way.”
On 11/6/16, 6:53 AM, "Chris Mattmann" <mattm...@apac
Thank you for sending this. I am not going to reply in depth now, but will do
so to Kelly and
others over the weekend, but this is *precisely* the reason that I have been so
about trying to get the PMC to see the road they have already gone done and the
has already set sail.
Kelly Sommers sent a message to dev@cassandra and I'm trying to figure out if
it's in moderation.
Can the moderators speak up?
at same conversation could be had on list. If you are ok with that
> > continuing to happen then great but I am not. Can someone please moderate
> > the message through?
> > Sent from my iPhone
> > > On Nov 4, 2016, at 8:54 AM, Mark Thomas <ma...@apache.o
oject? Or is Twitter the
official list now? Go ahead, I'll wait.
> On 4 November 2016 at 16:44, Chris Mattmann <mattm...@apache.org> wrote:
> > So seriously, we're going to send now 4 emails talking about what a user
> > of Apache Cassandra and possible community m
> > Sorry, it's a chore to begin with and I've been traveling this week.
> > Gary.
> > On Fri, Nov 4, 2016 at 3:47 PM, Chris Mattmann <mattm...@apache.org>
> > wrote:
> > > Hi Folks,
> > >
e help lead by example and reply to Kelly's questions in her email?
> I don't enjoy watching a community I care about continue to explode in front
> of my eyes â¹ï¸
> Sent from my iPhone
> > On Nov 4, 2016, at 10:10 AM, C
Mail list logo