Apache Cassandra Contributor Meeting this week

This month's Apache Cassandra Contributor Meeting is coming up on Tuesday, 29 August @ 10am PT. You'll find more details about the Contributor Meetings and how to join the Zoom call here: https://cwiki.apache.org/confluence/display/CASSANDRA/Cassandra+Contributor+Meeting This wee

July Contributor Meeting: Topic change

Hi all, There has been a last minute change in topic for the July Contributor Meeting! Caleb Rackliffe will be talking about CEP-7: Storage Attached Index, rather than the previously advertised CEP-15. He'll talk through the history of CEP-7, look at the current work as it approaches merge

New Zoom link for this week's Contributor Meeting

Hi everyone, Due to unforeseen circumstances, the Zoom link for this week’s Apache Cassandra Contributor Meeting has changed. The calendar event and the Confluence page have been updated with the new link: https://us02web.zoom.us/j/81043384800?pwd=K240K2JSR0I4N05GTHN3cXRiVzMvZz09 - if you are

Re: Cassandra Contributor Meeting May 30

as it doesn't require deep expertise in Cassandra or Spark. On Tue, May 30, 2023 at 9:38 AM Melissa Logan wrote: > The Cassandra Contributor Meeting starts soon at 10am PT. Dinesh Joshi > will be discussing CEP-28: Reading and Writing Cassandra Data with Spark > Bulk Analytics. See yo

Re: Cassandra Contributor Meeting May 30

The Cassandra Contributor Meeting starts soon at 10am PT. Dinesh Joshi will be discussing CEP-28: Reading and Writing Cassandra Data with Spark Bulk Analytics. See you then! Details: https://cwiki.apache.org/confluence/display/CASSANDRA/Cassandra+Contributor+Meeting How to join: Join Zoom

Cassandra Contributor Meeting May 30

Hi folks, The Cassandra community will be hosting monthly Contributor Meetings the last Tuesday of each month at 10:00 PT / 13:00 ET / 17:00 UTC / 22:30 IST. The purpose of these meetings is to enable real-time collaboration for contributors to discuss CEPs and other issues, and ask questions

Re: [FOR REVIEW] Blog post: An interview with contributor, Aleksandr Sorokoumov

Thanks, Erick. All amends made, so closing review. This one heading through PR now for publication 14 April. On Mon, Apr 11, 2022 at 9:46 AM Erick Ramirez wrote: > I've posted a couple of minor formatting edits in the doc. Otherwise, it > looks good. Thanks, Alexandr! 🍻 > >>

Re: [FOR REVIEW] Blog post: An interview with contributor, Aleksandr Sorokoumov

I've posted a couple of minor formatting edits in the doc. Otherwise, it looks good. Thanks, Alexandr! 🍻 >

[FOR REVIEW] Blog post: An interview with contributor, Aleksandr Sorokoumov

The Contributor Q&A series continues with Aleksandr. Here's the Google Doc for 72-hour review, please add any edits or suggestions as comments, please: https://docs.google.com/document/d/1BK5M6crvyGfG_u4SLpTP1iHKFXlWrG9VzpoOZtl0B1E/edit This is due to be published next Thurs 14th April

Re: [FOR REVIEW] Blog post: An Interview with Project Contributor, Lorina Poland

pot them on Slack. > > We're currently mid-review for our first contributor Q&A which is with > Lorina Poland: > https://docs.google.com/document/d/1nnH4V1XvTcfTeeUdZ_mjSxlNlWTbSXFu_qKtJRQUFBk/edit. > Please add edits or suggests as comments. > > Thanks! > -- >

Re: [FOR REVIEW] Blog post: An Interview with Project Contributor, Lorina Poland

+1 Kind Regards, Brandon On Tue, Mar 15, 2022 at 4:17 PM Chris Thornett wrote: > > As requested, I'm posting content contributions for community review on the > ML for those that might not spot them on Slack. > > We're currently mid-review for our first contributor

Re: [FOR REVIEW] Blog post: An Interview with Project Contributor, Lorina Poland

.apache.org >> *Subject: *Re: [FOR REVIEW] Blog post: An Interview with Project >> Contributor, Lorina Poland >> >> Looks good to me! 🍻 >> >> >> >> On Wed, 16 Mar 2022 at 08:17, Chris Thornett wrote: >> >> As requested, I'm posting conten

Re: [FOR REVIEW] Blog post: An Interview with Project Contributor, Lorina Poland

+1 On Wed, 16 Mar 2022 at 21:58, bened...@apache.org wrote: > +1 > > > > *From: *Erick Ramirez > *Date: *Tuesday, 15 March 2022 at 22:08 > *To: *dev@cassandra.apache.org > *Subject: *Re: [FOR REVIEW] Blog post: An Interview with Project > Contributor, Lorina Pola

Re: [FOR REVIEW] Blog post: An Interview with Project Contributor, Lorina Poland

+1 From: Erick Ramirez Date: Tuesday, 15 March 2022 at 22:08 To: dev@cassandra.apache.org Subject: Re: [FOR REVIEW] Blog post: An Interview with Project Contributor, Lorina Poland Looks good to me! 🍻 On Wed, 16 Mar 2022 at 08:17, Chris Thornett mailto:ch...@constantia.io>> wro

Re: [FOR REVIEW] Blog post: An Interview with Project Contributor, Lorina Poland

Looks good to me! 🍻 On Wed, 16 Mar 2022 at 08:17, Chris Thornett wrote: > As requested, I'm posting content contributions for community review on > the ML for those that might not spot them on Slack. > > We're currently mid-review for our first contributor Q&A whi

[FOR REVIEW] Blog post: An Interview with Project Contributor, Lorina Poland

As requested, I'm posting content contributions for community review on the ML for those that might not spot them on Slack. We're currently mid-review for our first contributor Q&A which is with Lorina Poland: https://docs.google.com/document/d/1nnH4V1XvTcfTeeUdZ_mjSxlNlWTbSXFu_q

Re: Contributor Q&A interview program

Thanks to Lorina for offering to be the first contributor to not only offer to do a Q&A but submit her answers on the same day! Who's next? This is a chance to encourage others to get involved and see the folks behind all the hard work. Chris Thornett > senior content strategist, C

Contributor Q&A interview program

As part of the 'Inside Cassandra' content theme, we're inviting project contributors to answer a simple list of questions that will be posted on the official Cassandra blog as a Q&A interview. This is a chance to highlight all the great people involved in the project and encourage others to join u

Re: [INTRODUCTIONS] New Non Coding Contributor

Hi Mick Long time no see!  And great to re-connect with you here on list. I'm here with my contributor hat on so it's really nice to actually start getting involved with a project again. Thanks very much the update and also including all the details around the website. (BTW the

Re: [INTRODUCTIONS] New Non Coding Contributor

Hi Benjamin Thanks very much for the warm welcome and also the suggestion. I will take a look! Thanks Sharan On 2021-11-23 10:46, Benjamin Lerer wrote: Hi Sharan, Welcome to our community! We have a cassandra-website slack channel dedicated to the website and the documentation. It is proba

Re: [INTRODUCTIONS] New Non Coding Contributor

irector reach out! The project is ramping up on a number of non-coding fronts: website, documentation, social media, events, and project governance (from CEPs to voting to methods for contributor recognition…) Repeating Benjamin, with 4.0 we landed a new website and documentation. An immense am

Re: [INTRODUCTIONS] New Non Coding Contributor

Hi Sharan, Welcome to our community! We have a cassandra-website slack channel dedicated to the website and the documentation. It is probably the best place to ask website and documentation questions. Happy to have you with us 😀 Le mar. 23 nov. 2021 à 10:29, sharanf a écrit : > Hi Everyone >

[INTRODUCTIONS] New Non Coding Contributor

Hi Everyone My name is Sharan Foga and I am new to the Apache Cassandra community. I would like to contribute to the project but am not a developer so am looking for ways to contribute that are not coding related (e.g helping out with things like community building, documentation, events, meet

Re: Code Contributor stats: patches, reviews, and relationships

Thanks for the script Mick. I found it really useful to have a better view of people's contributions. Le lun. 9 août 2021 à 16:18, Mick Semb Wever a écrit : > > > > The following metrics provide top lists of contributors for different > time > > periods. Listing patches, reviews, and who has wor

Re: Code Contributor stats: patches, reviews, and relationships

> > The following metrics provide top lists of contributors for different time > periods. Listing patches, reviews, and who has worked with who. > It's intended to give insight into (and to praise) the people who are > contributing code to the project. > https://nightlies.apache.org/cassandra/devbr

Code Contributor stats: patches, reviews, and relationships

The following metrics provide top lists of contributors for different time periods. Listing patches, reviews, and who has worked with who. It's intended to give insight into (and to praise) the people who are contributing code to the project. https://nightlies.apache.org/cassandra/devbranch/misc/

2020-09-29 Contributor Meeting

Hi everyone, I have the meeting video and transcripts uploaded: https://cwiki.apache.org/confluence/display/CASSANDRA/2020-09-29+Apache+Cassandra+Contributor+Meeting+-+4.0+push+edition Takeaways from today's meeting - Shephards, shepherds shepherds. Quite a few places that no longer h

Re: Cassandra Contributor Meeting to focus on outstanding 4.0 issues

> Isn't this hi-jacking the meaning (and value) of the "4.0-beta" and "4.0-rc" fixVersion placeholders? Makes sense, I hadn't thought of this. I retract my suggestion. > Kinda agree with Josh here on what the epics should focus on. Personally, because that better isolates and highlights what's mi

Re: Cassandra Contributor Meeting to focus on outstanding 4.0 issues

> I personally prefer to track fail/flaky tests as sub-issue of the 4.0 epic > (CASSANDRA-15536) so we can track 4.0 completion status in a single place. Strongly recommend against this approach. If we have hundreds of failing upgrade tests (or even dozens) then we end up with a wild mix of scop

Re: Cassandra Contributor Meeting to focus on outstanding 4.0 issues

I personally prefer to track fail/flaky tests as sub-issue of the 4.0 epic > (CASSANDRA-15536) so we can track 4.0 completion status in a single place. > > The way I see it is: > * CASSANDRA-15536 epic: track everything that needs to be done to wrap-up > 4.0 per macro component. > Isn't this hi-j

Re: Cassandra Contributor Meeting to focus on outstanding 4.0 issues

addendum: I understand the original way CASSANDRA-15536 was proposed is not the way I'm describing, but it could be easily adaptable to that so we can have a single place to track all tasks related to 4.0 quality and address some of the visibility points raised by Mick. Em ter., 29 de set. de 2020

Re: Cassandra Contributor Meeting to focus on outstanding 4.0 issues

I personally prefer to track fail/flaky tests as sub-issue of the 4.0 epic (CASSANDRA-15536) so we can track 4.0 completion status in a single place. The way I see it is: * CASSANDRA-15536 epic: track everything that needs to be done to wrap-up 4.0 per macro component. * Kanban board: a different

Re: Cassandra Contributor Meeting to focus on outstanding 4.0 issues

Not that I know of. Perhaps we should add a new ticket to the quality epic to track flakey and failing tests? (@cc Josh/Jordan) Either a separate epic or a ticket w/sub-tasks either work well in terms of organization. There's value in having one place to go to cleanly pull that kind of work so I h

Re: Cassandra Contributor Meeting to focus on outstanding 4.0 issues

Thanks for bringing up these valuable points, Mick! In fact we focused on the quality epic so far but there is a lot more stuff unaddressed. I commented some of the points you brought up below: > How will we ensure this QA persists, so it's not a manual checklist every release? This is a great q

Re: Cassandra Contributor Meeting to focus on outstanding 4.0 issues

> On 29 Sep 2020, at 09:50, Mick Semb Wever wrote: > >> Regarding the proposed agenda of going through the unassigned issues to >> improve visibility on what needs to be done to ship 4.0 GA I think this is >> a great start but only covers part of the problem. >> >> I think we have 3 outstandi

Re: Cassandra Contributor Meeting to focus on outstanding 4.0 issues

> Regarding the proposed agenda of going through the unassigned issues to > improve visibility on what needs to be done to ship 4.0 GA I think this is > a great start but only covers part of the problem. > > I think we have 3 outstanding issues that are hampering visibility of 4.0 > progress: > a)

Re: Cassandra Contributor Meeting to focus on outstanding 4.0 issues

Mailing List - Official record of discussions and decisions Slack - Fast > > discussions with searchable text > > Video Call - High bandwidth discussions and presentations. Transactional > > in nature with an agenda. > > > > Having 25 people on a call to make a decision

Re: Cassandra Contributor Meeting to focus on outstanding 4.0 issues

I posted as an example, the agenda is a discussion > focused on the three unassigned Jiras. I expect we will have a few people > that can directly speak about them and everyone else is a spectator or > commenting in chat. The intent is to drive some activity on Jira. > > The timezone

Re: Cassandra Contributor Meeting to focus on outstanding 4.0 issues

> Using this meeting I posted as an example, the agenda is a discussion > focused on the three unassigned Jiras. I expect we will have a few people > that can directly speak about them and everyone else is a spectator or > commenting in chat. The intent is to drive some activity on Jira. &

Re: Cassandra Contributor Meeting to focus on outstanding 4.0 issues

roposal as we formed the contributor meetings was to rotate the time to accommodate European timezones to Australia. The Kubernetes SIG had tried the 2 meetings in different halves of the world. Eventually consistent discussions don't work well. I don't want to go all Mandelorian and say

Re: Cassandra Contributor Meeting to focus on outstanding 4.0 issues

gt; There is an epic that was discussed in slack: > > https://issues.apache.org/jira/browse/CASSANDRA-15536 > > > > There are 17 separate jiras as dependencies, of which only 2 are marked > as > > completed. 3 have no assigned owner. I have put a Zoom call on the >

Re: Cassandra Contributor Meeting to focus on outstanding 4.0 issues

Thanks for the initiative, Patrick! I wonder if videochat is the most inclusive method of discussion, not only due to time zone differences, as mentioned by Alex, but also because it makes it harder for introverts from voicing their opinions. In my experience video calls with more than 5 participa

Re: Cassandra Contributor Meeting to focus on outstanding 4.0 issues

Very well said, Patrick! I'm not part of the inner circle of contributors so I'm a bit of an outsider. But as an advocate for Cassandra and the community, I'm optimistic that we will collectively get past this bump on the road, get 4.0 GA in 2020 and do bigger things in 2021. Cheers!

Re: Cassandra Contributor Meeting to focus on outstanding 4.0 issues

=355&quickFilter=1661 > > There is an epic that was discussed in slack: > https://issues.apache.org/jira/browse/CASSANDRA-15536 > > There are 17 separate jiras as dependencies, of which only 2 are marked as > completed. 3 have no assigned owner. I have put a Zoom call on the

Cassandra Contributor Meeting to focus on outstanding 4.0 issues

ere are 17 separate jiras as dependencies, of which only 2 are marked as completed. 3 have no assigned owner. I have put a Zoom call on the contributor meeting calendar to discuss those three first. I had to weave it between ApacheCon sessions but hopefully this will help in velocity. Agenda posted,

Contributor meeting canceled today

Hi everyone, I realized I missed a huge action item for today's meeting. Jordan West created some discussion last meeting about how to get more discussion items brought forward. I will get back with him on that idea and email the dev list on some new proposals. After which, I can reschedule. Cong

Contributor Meeting 2020-06-23

Yes! That is tomorrow at 10AM PST. Zoom: https://datastax.zoom.us/j/390839037 Add any agenda items here: https://cwiki.apache.org/confluence/display/CASSANDRA/2020-06-23+Apache+Cassandra+Contributor+Meeting I think it would be great to get an update on the governance doc under vote right now

2020-05-19 Contributor Meeting notes and recording

Hi everyone, Meeting notes and recording up here: https://cwiki.apache.org/confluence/display/CASSANDRA/2020-05-19+Apache+Cassandra+Contributor+Meeting Patrick

Re: Reminder - 2020-05-19 Apache Cassandra Contributor Meeting

Tue, 19 May 2020 at 02:53, Patrick McFadin wrote: > > > > Hi everyone, > > > > Reminder that tomorrow at 1PM PST we'll be having a contributor meeting. > I > > gave Jitsi a try for the Kubernetes SIG but ran into a lot of trouble > with > > browser compat

Re: Reminder - 2020-05-19 Apache Cassandra Contributor Meeting

ow at 1PM PST we'll be having a contributor meeting. I > gave Jitsi a try for the Kubernetes SIG but ran into a lot of trouble with > browser compatibility and recording. I'll just stick with using Zoom to > keep it working consistently. > > https://datastax.zoom.us/j/390839037 &

Reminder - 2020-05-19 Apache Cassandra Contributor Meeting

Hi everyone, Reminder that tomorrow at 1PM PST we'll be having a contributor meeting. I gave Jitsi a try for the Kubernetes SIG but ran into a lot of trouble with browser compatibility and recording. I'll just stick with using Zoom to keep it working consistently. https://datastax

2020-03-24 Apache Cassandra Contributor Meeting

Hi everyone, It's easy to loose track of thing given how quickly things have changed in the past couple of weeks. I missed sending a reminder last week but we have a contributor meeting tomorrow at 11AM PST. Please post any agenda items to the cwiki page below. If you don't have e

Apache Cassandra Contributor Meeting 2020-02-18

Hi everyone, A page has been setup for the Apache Cassandra Contributor Meeting on February 18. The time in the rotation will be 10AM PST You can add your agenda items here. https://cwiki.apache.org/confluence/display/CASSANDRA/2020-02-18+Apache+Cassandra+Contributor+Meeting The Zoom link for

Re: Feedback from the last Apache Cassandra Contributor Meeting

, I would appreciate your feedback. I'll keep it open until > tomorrow > >> and then send results. > >> > >> Patrick > >> > >>> On Mon, Feb 3, 2020 at 4:21 PM Patrick McFadin > wrote: > >>> > >>> Hi everyone, > >>

Re: Feedback from the last Apache Cassandra Contributor Meeting

r on the survey link I sent. I got a few responses >> but could use a few more to give us some decent N. If you have < 5minutes >> today, I would appreciate your feedback. I'll keep it open until tomorrow >> and then send results. >> >> Patrick >> &

Re: Feedback from the last Apache Cassandra Contributor Meeting

il tomorrow > and then send results. > > Patrick > > On Mon, Feb 3, 2020 at 4:21 PM Patrick McFadin wrote: > >> Hi everyone, >> >> One action item I took from our first contributor meeting was gather >> feedback for the next meetings. I've created a sh

Re: Feedback from the last Apache Cassandra Contributor Meeting

Patrick McFadin wrote: > Hi everyone, > > One action item I took from our first contributor meeting was gather > feedback for the next meetings. I've created a short survey if you would > like to offer feedback. I'll let it run for the week and report back on the > results

Feedback from the last Apache Cassandra Contributor Meeting

Hi everyone, One action item I took from our first contributor meeting was gather feedback for the next meetings. I've created a short survey if you would like to offer feedback. I'll let it run for the week and report back on the results. https://www.surveymonkey.com/r/C95B7ZP Thanks, Patrick

Re: Apache Cassandra Contributor Meeting

luence/display/CASSANDRA/Apache+Cassandra+Contributor+Meeting > > Here's a direct link: > https://www.youtube.com/watch?v=DprX7Y5v30M&feature=emb_logo > > Thanks, Patrick! > > > From: Scott Andreas > Sent: Tuesday, January 21

Contributor Meeting summary for 2020-01-21

nk to recorded video can be found here: https://cwiki.apache.org/confluence/display/CASSANDRA/Apache+Cassandra+Contributor+Meeting *Meeting Notes:* The community and contributors remain focussed on the 4.0 release. There was broad consensus that we want to keep working towards the 4.0 QA Test

Re: Apache Cassandra Contributor Meeting

Patrick's added the recording and linked it via the wiki: https://cwiki.apache.org/confluence/display/CASSANDRA/Apache+Cassandra+Contributor+Meeting Here's a direct link: https://www.youtube.com/watch?v=DprX7Y5v30M&feature=emb_logo Thanks, Patrick! ___

Re: Apache Cassandra Contributor Meeting

_ >> From: Jordan West >> Sent: Monday, January 20, 2020 7:27 PM >> To: dev@cassandra.apache.org >> Subject: Re: Apache Cassandra Contributor Meeting >> >> Thanks Patrick. Looking forward to tomorrow’s meeting. I added an agenda &

Re: Apache Cassandra Contributor Meeting

ality tracks that need an owner > – 3.0 / 3.11 branch status > > > From: Jordan West > Sent: Monday, January 20, 2020 7:27 PM > To: dev@cassandra.apache.org > Subject: Re: Apache Cassandra Contributor Meeting > > Thanks Patrick. L

Re: Apache Cassandra Contributor Meeting

Cassandra Contributor Meeting Thanks Patrick. Looking forward to tomorrow’s meeting. I added an agenda item around 4.0 — it’s not my intention to lead that section necessarily but I think a check in / progress update / follow up on Josh’s email will be good to cover. Jordan On Mon, Jan 13, 2020 at 6

Re: Apache Cassandra Contributor Meeting

as taken so long. I saw some of the examples mentioned in > > the original thread for other open source projects and I "borrowed" > heavily > > from them. > > > > I created a page in the Cassandra Confluence page to hopefully centralize > > both logistics and r

Re: Apache Cassandra Contributor Meeting

ly > from them. > > I created a page in the Cassandra Confluence page to hopefully centralize > both logistics and records of each call. You can fine it here: > https://cwiki.apache.org/confluence/display/CASSANDRA/Apache+Cassandra+Contributor+Meeting > > The meetings are on Zoom

Apache Cassandra Contributor Meeting

projects and I "borrowed" heavily from them. I created a page in the Cassandra Confluence page to hopefully centralize both logistics and records of each call. You can fine it here: https://cwiki.apache.org/confluence/display/CASSANDRA/Apache+Cassandra+Contributor+Meeting The meetings

[JIRA Epic] Removing Contributor Role

filed, (and perhaps those that have been assigned to you, but this would require limiting who may assign issues). This would limit the possible corruption to transitioning tickets, or spamming comments (the latter of which is already open to them). All other contributor rights could be conferred

Re: Wiki Contributor

try now On 11/22/2016 06:38 PM, Thomas Brown wrote: Hi, Could I please be added as a Wiki Contributor Username: Thomas Brown Thank you!

Wiki Contributor

Hi, Could I please be added as a Wiki Contributor Username: Thomas Brown Thank you! -- *Thomas Brown* *Digital Marketing Associate * m: +61427864972 <http://goog_172086/> <https://www.instaclustr.com/> MANAGED. <https://www.instaclustr.com/managed/> SUPPORT. <https:

Re: Wiki contributor

you should be added On 06/01/2016 05:03 PM, Mahdi Mohammadi wrote: Hi, Would someone please add me to the Wiki contributors? Username: MahdiMohammadi Best Regards

Wiki contributor

Hi, Would someone please add me to the Wiki contributors? Username: MahdiMohammadi Best Regards

Re: Contributor

Happy to add you, we just need your wiki username. On Thu, Mar 31, 2016 at 5:02 PM, Megan Smith wrote: > Hi there, > > I work for Instaclustr, and on your third party support page our company > logo does not appear correctly. I am just wondering if i could please be > added as a

Contributor

Hi there, I work for Instaclustr, and on your third party support page our company logo does not appear correctly. I am just wondering if i could please be added as a contributor to edit the page so i can then fix this issue? Thank you! Megan Smith Digital Marketing Coordinator