Google Season of Docs
Sadly, I am informing the community that our grant application to GSoD was unsuccessful. If you would like to see the list of winning projects, check out https://developers.google.com/season-of-docs/docs/participants.LorinaSent from my Verizon, Samsung Galaxy smartphone
Re: Push TCM (CEP-21) and Accord (CEP-15) to 5.1 (and cut an immediate 5.1-alpha1)
I'm certainly a fan of docker images as a dev tool! LorinaSent from my Verizon, Samsung Galaxy smartphone Original message From: Patrick McFadin Date: 10/24/23 13:31 (GMT-08:00) To: dev@cassandra.apache.org Subject: Re: Push TCM (CEP-21) and Accord (CEP-15) to 5.1 (and cut an immediate 5.1-alpha1) Let me make that really easy. Hell yesNot everybody runs CCM, I've tried but I've met resistance. Compiling your own version usually involves me saying the words "Yes, ant realclean exists. I'm not trolling you" docker pull works on every OS and curates a single node experience. On Tue, Oct 24, 2023 at 12:37 PM Josh McKenzie wrote:In order for the project to advertise the release outside the dev@ list it needs to be a formal release.That's my reading as well:https://www.apache.org/legal/release-policy.html#release-definitionI wonder if there'd be value in us having a cronned job that'd do nightly docker container builds on trunk + feature branches, archived for N days, and we make that generally known to the dev@ list here so folks that want to poke at the current state of trunk or other branches could do so with very low friction. We'd probably see more engagement on feature branches if it was turn-key easy for other C* devs to spin the up and check them out.For what you're talking about here Patrick (a docker image for folks outside the dev@ audience and more user-facing), we'd want to vote on it and go through the formal process.On Tue, Oct 24, 2023, at 3:10 PM, Jeremiah Jordan wrote:In order for the project to advertise the release outside the dev@ list it needs to be a formal release. That just means that there was a release vote and at least 3 PMC members +1’ed it, and there are more +1 than there are -1, and we follow all the normal release rules. The ASF release process doesn’t care what branch you cut the artifacts from or what version you call it.So the project can cut artifacts for and release a 5.1-alpha1, 5.1-dev-preview1, what ever we want to version this thing, from trunk or any other branch name we want.-JeremiahOn Oct 24, 2023 at 2:03:41 PM, Patrick McFadin wrote:I would like to have something for developers to use ASAP to try the Accord syntax. Very few people have seen it, and I think there's a learning curve we can start earlier.It's my understanding that ASF policy is that it needs to be a project release to create a docker image.On Tue, Oct 24, 2023 at 11:54 AM Jeremiah Jordan wrote:If we decide to go the route of not merging TCM to the 5.0 branch. Do we actually need to immediately cut a 5.1 branch? Can we work on stabilizing things while it is in trunk and cut the 5.1 branch when we actually think we are near releasing? I don’t see any reason we can not cut “preview” artifacts from trunk?-JeremiahOn Oct 24, 2023 at 11:54:25 AM, Jon Haddad wrote:I guess at the end of the day, shipping a release with a bunch of awesome features is better than holding it back. If there's 2 big releases in 6 months the community isn't any worse off. We either ship something, or nothing, and something is probably better.JonOn 2023/10/24 16:27:04 Patrick McFadin wrote:+1 to what you are saying, Josh. Based on the last survey, yes, everyonewas excited about Accord, but SAI and UCS were pretty high on the list.Benedict and I had a good conversation last night, and now I understandmore essential details for this conversation. TCM is taking far more workthan initially scoped, and Accord depends on a stable TCM. TCM is monthsbehind and that's a critical fact, and one I personally just learned of. Ithought things were wrapping up this month, and we were in the testingphase. I get why that's a topic we are dancing around. Nobody wants to sayship dates are slipping because that's part of our culture. It'sdisappointing and, if new information, an unwelcome surprise, but none ofus should be angry or in a blamey mood because I guarantee every one of ushas shipped the code late. My reaction yesterday was based on an incorrectassumption. Now that I have a better picture, my point of view is changing.Josh's point about what's best for users is crucial. Users deserve stablecode with a regular cadence of features that make their lives easier. If weput 5.0 on hold for TCM + Accord, users will get neither for a very longtime. And I mentioned a disaster yesterday. A bigger disaster would beshipping Accord with a major bug that causes data loss, eroding communitytrust. Accord has to be the most bulletproof of all bulletproof features.The pressure to ship is only going to increase and that's fertile groundfor that sort of bug.So, taking a step back and with a clearer picture, I support the 5.0 + 5.1plan mainly because I don't think 5.1 is (or should be) a fast follow.For the user community, the communication should be straightforward. TCM +Accord are turning out to be much more complicated than was originallyscoped, and for good reasons
RE: Cassandra PMC Chair Rotation, 2024 Edition
Congrats, Dinesh!Sent from my Verizon, Samsung Galaxy smartphone Original message From: Josh McKenzie Date: 6/20/24 08:51 (GMT-08:00) To: dev Subject: Cassandra PMC Chair Rotation, 2024 Edition Another PMC Chair baton pass incoming! On behalf of the Apache Cassandra Project Management Committee (PMC) I would like to welcome and congratulate our next PMC Chair Dinesh Joshi (djoshi).Dinesh has been a member of the PMC for a few years now and many of you likely know him from his thoughtful, measured presence on many of our collective discussions as we've grown and evolved over the past few years.I appreciate the project trusting me as liaison with the board over the past year and look forward to supporting Dinesh in the role in the future.Repeating Mick (repeating Paulo's) words from last year: The chair is an administrative position that interfaces with the Apache Software Foundation Board, by submitting regular reports about project status and health. Read more about the PMC chair role on Apache projects:- https://www.apache.org/foundation/how-it-works.html#pmc- https://www.apache.org/foundation/how-it-works.html#pmc-chair- https://www.apache.org/foundation/faq.html#why-are-PMC-chairs-officersThe PMC as a whole is the entity that oversees and leads the project and any PMC member can be approached as a representative of the committee. A list of Apache Cassandra PMC members can be found on: https://cassandra.apache.org/_/community.html
Re: Adding RSS feed to the Apache Cassandra website.
I'm sure that someone has an rss feed Javascript that can just be added to the antora-ui-docs, as Anthony is suggesting. Sent from my Verizon, Samsung Galaxy smartphone Original message From: Ekaterina Dimitrova Date: 5/31/22 09:37 (GMT-08:00) To: dev@cassandra.apache.org Subject: Re: Adding RSS feed to the Apache Cassandra website. +1 for option 2On Tue, 31 May 2022 at 12:21, Patrick McFadin wrote:+1 on option 2. Anything that eliminates a human step is how it stays up to date. On Tue, May 31, 2022 at 5:25 AM Brandon Williams wrote:+1 to Anthony, that seems like the best path to me too.On Tue, May 31, 2022, 7:15 AM Anthony Grasso wrote:This is a good idea!I think option 2 is the best way to go. Currently, there are manual steps involved to publish a post to the blog. I would like to avoid adding more manual work.We could implement option 2 either by:Bolting on JavaScript for Anotra to use to generate the RSS XMLAdding a Python script that gets called (probably after the HTML is generated) to generate the RSS XMLThe Python script would be the easiest to implement and maintain.Regards,On Tue, 31 May 2022 at 10:12, Erick Ramirez wrote:Thanks for coordinating this. I'm happy to incorporate the manual process (option 1) in my workflow when reviewing/publishing blog PRs immediately as a quick solution if our intention is to go with option 2.FWIW by "workflow" I mean step 6 of the Pipeline Overview documented in the wiki here -- https://cwiki.apache.org/confluence/x/-6rkCw. Cheers!
RE: Welcome Jacek Lewandowski as Cassandra committer
Congratulations and welcome, Jacek!Sent from my Verizon, Samsung Galaxy smartphone Original message From: Benjamin Lerer Date: 7/6/22 05:01 (GMT-08:00) To: dev@cassandra.apache.org Subject: Welcome Jacek Lewandowski as Cassandra committer The PMC members are pleased to announce that Jacek Lewandowski has accepted the invitation to become committer. Thanks a lot, Jacek, for everything you have done!Congratulations and welcomeThe Apache Cassandra PMC members
RE: Thanks to Nate for his service as PMC Chair
Thank you Nate, and congratulations Mick!Sent from my Verizon, Samsung Galaxy smartphone Original message From: Paulo Motta Date: 7/11/22 05:54 (GMT-08:00) To: Cassandra DEV Subject: Thanks to Nate for his service as PMC Chair Hi,I wanted to announce on behalf of the Apache Cassandra Project Management Committee (PMC) that Nate McCall (zznate) has stepped down from the PMC chair role. Thank you Nate for all the work you did as the PMC chair!The Apache Cassandra PMC has nominated Mick Semb Wever (mck) as the new PMC chair. Congratulations and good luck on the new role Mick!The chair is an administrative position that interfaces with the Apache Software Foundation Board, by submitting regular reports about project status and health. Read more about the PMC chair role on Apache projects:- https://www.apache.org/foundation/how-it-works.html#pmc- https://www.apache.org/foundation/how-it-works.html#pmc-chair- https://www.apache.org/foundation/faq.html#why-are-PMC-chairs-officersThe PMC as a whole is the entity that oversees and leads the project and any PMC member can be approached as a representative of the committee. A list of Apache Cassandra PMC members can be found on: https://cassandra.apache.org/_/community.htmlKind regards,Paulo
