Re: [DISCUSS] Requirement to document features before releasing them

That page does not look great, but the link “Documentation” in the middle of it takes you to the actual page on contributing https://cassandra.apache.org/_/development/documentation.html On May 1, 2025 at 4:19:15 PM, Jon Haddad wrote: > Oh, well then, that’s perfect. I looked at our contributin

Re: [DISCUSS] Requirement to document features before releasing them

Oh, well then, that’s perfect. I looked at our contributing to the docs page and found it empty: https://cassandra.apache.org/_/docdev/index.html Will merge in my UCS changes tomorrow. Jon On Thu, May 1, 2025 at 1:41 PM Brandon Williams wrote: > The governanceays "Correcting typos, docs, webs

Re: [DISCUSS] Requirement to document features before releasing them

The governance https://cwiki.apache.org/confluence/display/CASSANDRA/Cassandra+Project+Governance says "Correcting typos, docs, website, and comments etc operate a “Commit Then Review ” policy" Kind Regards, Brandon On Thu, May 1,

Re: [VOTE][IP CLEARANCE] easy-cass-stress

+1 On Thu, May 1, 2025 at 4:27 PM Dave Herrington wrote: > +1 (nb) > > -Dave > > On Wed, Apr 30, 2025 at 8:16 AM Jordan West wrote: > >> (general@incubator cc'd) >> >> Please vote on the acceptance of the easy-cass-stress (to be renamed >> cassandra-stress) and its IP Clearance: >> >> https://i

Re: [VOTE][IP CLEARANCE] easy-cass-stress

+1 (nb) -Dave On Wed, Apr 30, 2025 at 8:16 AM Jordan West wrote: > (general@incubator cc'd) > > Please vote on the acceptance of the easy-cass-stress (to be renamed > cassandra-stress) and its IP Clearance: > > https://incubator.apache.org/ip-clearance/cassandra-easy-cass-stress.html > > All co

Re: [DISCUSS] Requirement to document features before releasing them

I propose we encourage committers commit docs without review or a JIRA. On Thu, May 1, 2025 at 8:06 AM Jon Haddad wrote: > Stefan, > > Any feature developed for Cassandra is a collaborative effort. The public > branches of accord have been available for months. Have you contributed to > the a

Re: Welcome Jaydeepkumar Chovatia as Cassandra committer

Thank you, everyone! Jaydeep On Thu, May 1, 2025 at 5:27 AM Marouan REJEB wrote: > Congratulations ! > > On Thu, May 1, 2025 at 1:22 PM Aaron Ploetz wrote: > >> Congratulations Jaydeep! >> >> >> > On Apr 30, 2025, at 8:18 AM, Paulo Motta wrote: >> > >> > Congratulations Jaydeep! >> >

Re: [VOTE][IP CLEARANCE] easy-cass-stress

+1 On Wed, Apr 30, 2025 at 8:17 AM Jordan West wrote: > (general@incubator cc'd) > > Please vote on the acceptance of the easy-cass-stress (to be renamed > cassandra-stress) and its IP Clearance: > > https://incubator.apache.org/ip-clearance/cassandra-easy-cass-stress.html > > All consent from o

Re: [DISCUSS] Requirement to document features before releasing them

Stefan, Any feature developed for Cassandra is a collaborative effort. The public branches of accord have been available for months. Have you contributed to the accord docs? You've had plenty of opportunity. It looks like you're turning your own thread into an airing of grievances. It's not pa

Re: [DISCUSS] Requirement to document features before releasing them

Yeah, no surprise, I was thinking the dicussion will go this direction. I am not completely sure who we are developing this for then. I see the statements like this and I am pretty disappointed: "The project obviously aims to serve end users, but the developer community is the actual project an

Re: [DISCUSS] Requirement to document features before releasing them

I love the idea of having great docs, but blocking at this point probably hurts the project more than it helps. How about we see if we can find people that are actually interested in working on them? Figuring that out needs to happen regardless. I suspect not many of us want to, or have time to.

Re: [DISCUSS] Requirement to document features before releasing them

My view from the "balcony" here: I think, some documentation is better that no documentation. If I would have to start in Cassandra right now, I would have a massive challenge. The project evolved a lot, documentation is not great, and the community is not the 20/30ish people of the past that w

Re: [DISCUSS] Requirement to document features before releasing them

On Thu, May 1, 2025 at 7:37 AM Benedict wrote: > I am opposed to this. There’s too much imprecision in the “rule” while > simultaneously being much too rigid, and it will be improperly enforced (we > already have lots of rule breaking around modifying public APIs, that > should have discuss threa

Re: A Roadmap to Cassandra Analytics 1.0

Patrick, Thanks for the clarification - makes sense. I can put the contents here up on Confluence and we can work together to tweak it if necessary. > On Apr 30, 2025, at 11:15 AM, Patrick McFadin wrote: > > I'm not thinking that the Confluence page would be a status page or try to > get too

Re: [DISCUSS] Requirement to document features before releasing them

Stefan, I agree with you, that's a pretty terrible way to go about writing docs, and I'm not sure if you're being hyperbolic. I really don't think it's what Patrick is suggesting. LLMs are great at taking some notes and examples and turning it into docs. You don't need to have it write everything,

Re: [DISCUSS] Requirement to document features before releasing them

I am opposed to this. There’s too much imprecision in the “rule” while simultaneously being much too rigid, and it will be improperly enforced (we already have lots of rule breaking around modifying public APIs, that should have discuss threads and do not, for instance). This kind of arbitrary rule

Re: Welcome Jaydeepkumar Chovatia as Cassandra committer

Congratulations ! On Thu, May 1, 2025 at 1:22 PM Aaron Ploetz wrote: > Congratulations Jaydeep! > > > > On Apr 30, 2025, at 8:18 AM, Paulo Motta wrote: > > > > Congratulations Jaydeep! >

Re: [DISCUSS] Requirement to document features before releasing them

I am not completely sure LLMs are the way to go here. Sure, to have something to further refine ... why not. But to just generate something via LLM and commit that, that would be a no-no from me. These things can go hallucinate quite quickly, then what? Who is going to proof-read technical stuff

Re: Welcome Jaydeepkumar Chovatia as Cassandra committer

Congratulations Jaydeep! > On Apr 30, 2025, at 8:18 AM, Paulo Motta wrote: > > Congratulations Jaydeep!

Re: [DISCUSS] Requirement to document features before releasing them

I am bit out of the loop on how/if this would extend to driver sub-projects. Because this makes 100% sense, and in the driver space as well. Looking into Java driver docs and making others similar would be a great. Patrich that LLM suggestion might be a life saver, let me try that! _