Re: Call for help to promote the project

[Sharan Foga]

Hi All

I can help here and have access to some blog post style content. How do you 
want to organise it? I can get a list and then you can take a look through and 
decide on the ones you want. Will that work?

Thanks
Sharan

On 2021/11/23 10:26:13 Benjamin Lerer wrote:
> Hi everybody,
> 
> With Chris, Diogenese, Erick, Mick and Ekaterina we are working on making
> the Apache Cassandra project more visible to the rest of the world and we
> need your help for that.
> 
> We need some blog posts to explain: existing features, internals, new
> developments, how your organization uses Cassandra ...
> 
> That type of contribution is extremely valuable for the project as it helps
> us to attract more users and contributors. We would love to have more.
> 
> We also try to post more on twitter than we used to do.  Our goal is to
> expose more broadly what is happening on the project and reach some persons
> that we would not have reached otherwise. Our reach grows exponentially
> with each retweet so if you like our tweets do not hesitate to help us
> reach more people by liking or retweeting them :-)
> 
> Thanks a lot for your help,
> 
> PS: There is some interest in the community for blog posts on Performance
> aspects & troubleshooting as well as on the various metrics and how to use
> them. So if anybody is motivated to write a blog post on one of those
> subjects, he will make some people happy ;-)
> 

-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

Re: [DISCUSS] Non Coding Committers

[Sharan Foga]

Hi All

Thanks very much to everyone who took the time to provide feedback and share 
their views on this topic. It seems to me like there is a general consensus 
around it and it's great to hear that the PMC is aware and actively working on 
it.

A community is an evolving thing and so adapting to change is part of the 
journey. I am really happy to see this open dialogue happening and even though 
some current problems have been highlighted - the focus is on resolving them! 

Happy to be involved and part of this community :-)

Thanks
Sharan

On 2022/02/09 09:12:56 Benjamin Lerer wrote:
> Thanks a lot Sharan, Patrick and Lorina.
> It is a perfectly valid point that the PMC members have recognized for some
> time already and are actively working on.
> 😊
> 
> Le mar. 8 févr. 2022 à 23:07, Lorina Poland  a écrit :
> 
> > +1 to this conversation, from a Docs wonk. :-)
> >
> > On Tue, Feb 8, 2022 at 1:40 PM Patrick McFadin  wrote:
> >
> >> Sharan has done a good job shining a spotlight on something that has
> >> created a weird bottleneck in the project. Docs and the Cassandra website
> >> are all in-tree, but it takes somebody who probably isn't even working on
> >> those things to commit any changes. Dinesh nailed it. It's silly. I'm sure
> >> the PMC can come up with a reasonable solution that can be done quickly.
> >> There are a lot of us that love this project that contribute in ways that
> >> don't get compiled into a jar file. This is something that needs to be
> >> solved for the sake of project velocity.
> >>
> >> Patrick
> >>
> >> On Sun, Feb 6, 2022 at 10:28 PM Mick Semb Wever  wrote:
> >>
> >>>
> >>> Thank you Sharan for sharing.
> >>>
> >>>
>  So here in Apache Cassandra I see there is a whole lot of activity
>  happening around the website, marketing, project promotion, blogs, social
>  media - these activities are all contributions to the project. If there 
>  are
>  contributions happening in the project that need a committer to action,
>  then it could make sense to consider having committers that are focussed
>  around the 'non coding' parts.
> 
> 
> 
> >>>
> >>> This is so true for us. We are spending a lot of extra time getting
> >>> these non-code contributions across the finish line. The context switching
> >>> and wait time involved in just one more handover, and often across time
> >>> zones, is hurting. And regardless, totally agree we should be formally
> >>> recognising the ongoing work that goes into these non-coding 
> >>> contributions.
> >>>
> >>>
> 

Re: Welcome Anthony Grasso, Erick Ramirez and Lorina Poland as Cassandra committers

[Sharan Foga]

Congratulations Lorina, Erick and Anthony! Well done

And also kudos to the PMC for making this happen!

Thanks
Sharan

On 2022/02/15 18:12:46 Benjamin Lerer wrote:
>  The PMC members are pleased to announce that Anthony Grasso, Erick Ramirez
> and Lorina Poland have accepted the invitation to become committers.
> 
> Thanks a lot, Anthony, Erick and Lorina for all the work you have done on
> the website and documentation.
> 
> Congratulations and welcome
> 
> The Apache Cassandra PMC members
> 

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

[Sharan Foga]

Hi Chris

+1

This looks really good. I added a few comments and suggestions so feel free to 
use what you think.

Thanks
Sharan

On 2022/03/15 21:16:34 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 which is with
> Lorina Poland:
> https://docs.google.com/document/d/1nnH4V1XvTcfTeeUdZ_mjSxlNlWTbSXFu_qKtJRQUFBk/edit.
> Please add edits or suggests as comments.
> 
> Thanks!
> -- 
> 
> Chris Thornett
> senior content strategist, Constantia.io
> ch...@constantia.io
> 

Re: Performance Engineering Track at ApacheCon NA?

[Sharan Foga]

Hi Paulo

Thanks for the feedback. If we do get the track accepted then we will 
definitely be needing help reviewing the submissions - so may take you up on 
your offer :-)

Thanks
Sharan

On 2022/03/14 16:32:23 Paulo Motta wrote:
> This Apachecon track sounds fun! I hope someone from the Cassandra
> community steps up to help on this track.
> 
> I would be happy to help on reviews but not organize the event per se as I
> will likely not attend the event.
> 
> Em sex., 11 de mar. de 2022 às 09:26, sharanf  escreveu:
> 
> > Hi All
> >
> > The call for tracks for ApacheCon NA is open. There is a suggestion to
> > try and run a Performance Engineering track at ApacheCon this year. At
> > the end of the message I have included some details including a
> > definition of what we mean by it and some reasoning about why it could
> > be good to run. We have a list of projects that have something to do
> > with performance engineering and if you take a look -  you will see that
> > this project is on the list!
> >
> > So what I need is a some feedback as to whether the community thinks
> > that this could be an interesting track topic to run at ApacheCon..and
> > more importantly would the community be willing to submit talks for it
> > or attend ApacheCon to see it.
> >
> > Like I say - this is just an idea at this stage. If the Performance
> > Engineering track does get approval to be included at ApacheCon  - do we
> > have any volunteers willing to help with managing and promoting the
> > track on behalf of the project?
> >
> > Thanks
> > Sharan
> >
> > -
> >
> > *Performance Engineering*  is the science and practice of engineering
> > software with the required performance and scalability characteristics.
> > Many Apache projects focus on solving hard Big Data performance and
> > scalability challenges, while others provide tools for performance
> > engineering - but there are few projects that don’t care about some
> > aspect of software performance.
> >
> > This track will enable Apache projects members to share their
> > experiences of performance engineering best practices, tools,
> > techniques, and results, from their own communities, with the benefits
> > of cross-fertilization between projects. Performance Engineering in the
> > wider open source community is pervasive and includes methods and tools
> > (including automation and agile approaches) for performance:
> > architecting and design, benchmarking, monitoring, tracing, analysis,
> > prediction, modeling and simulation, testing and reporting, regression
> > testing, and source code analysis and instrumentation techniques.
> >
> > Performance Engineering also has wider applicability to DevOps, the
> > operation of cloud platforms by managed service providers (hence some
> > overlap with SRE - Site Reliability Engineering), and customer
> > application performance and tuning.  This track would therefore be
> > applicable to the wider open source community.
> >
> > *SUPPORTING DETAILS*
> >
> > *Google Searches*
> > Google “Open source performance engineering” has 4,180,000,000 results
> > Google “site:apache.org  performance” has 147,000
> > results
> >
> > *Apache Projects *which may have some interest in, or focus on,
> > performance (just the top results):
> > JMeter, Cassandra, Storm, Spark, Samza, Pulsar, Kafka, Log4J, SystemML,
> > Drill, HTTP Server, Cayenne, ActiveMQ, Impala, Geode, Flink, Ignite,
> > Impala, Lucene, TVM, Tika, YuniKorn, Solr, Iceberg, Dubbo, Hudi,
> > Accumulo, Xerces, MXNet, Zookeeper
> >
> > *Incubator projects *which may have some interest in, or focus on,
> > performance**(again just top results):
> > Crail, Eagle, Nemo, Skywalking, MXnet, HAWQ, Mnemonic, CarbonData,
> > Drill, ShenYu, Tephra, Sedona
> >
> > *References *(randomly selected to show the range of open-source
> > performance engineering topics available, rather than the quality of
> > articles):
> >
> >   1. Performance Engineering for Apache Spark and Databricks Runtime
> >  ETHZ, Big Data HS19
> >  <
> > https://archive-systems.ethz.ch/sites/default/files/courses/2019-fall/bigdata/Databricks%20ETHZ%20Big%20Data%20HS19.pdf
> > >
> >   2. Real time insights into LinkedIn's performance using Apache Samza
> >  <
> > https://engineering.linkedin.com/samza/real-time-insights-linkedins-performance-using-apache-samza
> > >
> >   3. A day in the life of an open source performance engineering team
> >  
> >   4. Locating Performance Regression Root Causes in the Field Operations
> >  ofWeb-based Systems:
> >  An Experience Report Published in: IEEE Transactions on Software
> >  Engineering (Early Access)
> >  
> >   5. How to Detect Performance Changes in Software History: Performance
> >  Analysis of Software System Versions
> >   

Re: Podcast Interviews for Feathercast

[Sharan Foga]

Hi All

A quick update - I am working with someone on a potential first Cassandra 
related podcast. We are just looking at the questions and interview format etc 
to see how that could work.

Thanks
Sharan

On 2022/04/02 11:43:32 Mick Semb Wever wrote:
> >
> >
> > For those who are not familiar with FeatherCast
> >  -  its the ASF's podcast channel that
> > we generally use to help promote projects.
> >
> > Looking through the list of published content I see that there are a few
> > interviews about Cassandra 
> > but they are a few years old - so if anyone is interested in being
> > interviewed then please let me know and we can set something up.
> >
> >
> 
> This is an awesome opportunity. I recommend any and all committers to take
> advantage of it.
> 
> Chris / Melissa, when we do an 'inside cassandra … interview' for the
> website, we should offer the contributor the opportunity to follow it up
> with one of these podcasts.
> 

Re: Performance Engineering Track at ApacheCon NA?

[Sharan Foga]

Hi Paulo 

We have great news - the Performance Engineering track has been accepted so we 
will be looking to encourage and promote CFP submissions for it. We are also 
looking for reviewers to help us rate the submissions---if you are still 
interested in doing that. ;-)

Thanks
Sharan

On 2022/03/16 15:36:04 Sharan Foga wrote:
> Hi Paulo
> 
> Thanks for the feedback. If we do get the track accepted then we will 
> definitely be needing help reviewing the submissions - so may take you up on 
> your offer :-)
> 
> Thanks
> Sharan
> 
> On 2022/03/14 16:32:23 Paulo Motta wrote:
> > This Apachecon track sounds fun! I hope someone from the Cassandra
> > community steps up to help on this track.
> > 
> > I would be happy to help on reviews but not organize the event per se as I
> > will likely not attend the event.
> > 
> > Em sex., 11 de mar. de 2022 às 09:26, sharanf  escreveu:
> > 
> > > Hi All
> > >
> > > The call for tracks for ApacheCon NA is open. There is a suggestion to
> > > try and run a Performance Engineering track at ApacheCon this year. At
> > > the end of the message I have included some details including a
> > > definition of what we mean by it and some reasoning about why it could
> > > be good to run. We have a list of projects that have something to do
> > > with performance engineering and if you take a look -  you will see that
> > > this project is on the list!
> > >
> > > So what I need is a some feedback as to whether the community thinks
> > > that this could be an interesting track topic to run at ApacheCon..and
> > > more importantly would the community be willing to submit talks for it
> > > or attend ApacheCon to see it.
> > >
> > > Like I say - this is just an idea at this stage. If the Performance
> > > Engineering track does get approval to be included at ApacheCon  - do we
> > > have any volunteers willing to help with managing and promoting the
> > > track on behalf of the project?
> > >
> > > Thanks
> > > Sharan
> > >
> > > -
> > >
> > > *Performance Engineering*  is the science and practice of engineering
> > > software with the required performance and scalability characteristics.
> > > Many Apache projects focus on solving hard Big Data performance and
> > > scalability challenges, while others provide tools for performance
> > > engineering - but there are few projects that don’t care about some
> > > aspect of software performance.
> > >
> > > This track will enable Apache projects members to share their
> > > experiences of performance engineering best practices, tools,
> > > techniques, and results, from their own communities, with the benefits
> > > of cross-fertilization between projects. Performance Engineering in the
> > > wider open source community is pervasive and includes methods and tools
> > > (including automation and agile approaches) for performance:
> > > architecting and design, benchmarking, monitoring, tracing, analysis,
> > > prediction, modeling and simulation, testing and reporting, regression
> > > testing, and source code analysis and instrumentation techniques.
> > >
> > > Performance Engineering also has wider applicability to DevOps, the
> > > operation of cloud platforms by managed service providers (hence some
> > > overlap with SRE - Site Reliability Engineering), and customer
> > > application performance and tuning.  This track would therefore be
> > > applicable to the wider open source community.
> > >
> > > *SUPPORTING DETAILS*
> > >
> > > *Google Searches*
> > > Google “Open source performance engineering” has 4,180,000,000 results
> > > Google “site:apache.org<http://apache.org>  performance” has 147,000
> > > results
> > >
> > > *Apache Projects *which may have some interest in, or focus on,
> > > performance (just the top results):
> > > JMeter, Cassandra, Storm, Spark, Samza, Pulsar, Kafka, Log4J, SystemML,
> > > Drill, HTTP Server, Cayenne, ActiveMQ, Impala, Geode, Flink, Ignite,
> > > Impala, Lucene, TVM, Tika, YuniKorn, Solr, Iceberg, Dubbo, Hudi,
> > > Accumulo, Xerces, MXNet, Zookeeper
> > >
> > > *Incubator projects *which may have some interest in, or focus on,
> > > performance**(again just top results):
> > > Crail, Eagle, Nemo, Skywalking, MXnet, HAWQ, Mnemonic, CarbonData,
> > > Drill, ShenYu, Tephra, Sedona
> > &

Re: Performance Engineering Track at ApacheCon NA?

[Sharan Foga]

Hi Dinesh

Thanks for volunteering to help us review the submissions for the Performance 
Engineering track. One thing we are currently asking of the track reviewers is 
that they are not planning to make a submission to the track they are 
reviewing. Will that be OK for you? If so then please let me know so I can 
contact you about getting setup.

Thanks
Sharan

On 2022/04/06 17:21:52 Dinesh Joshi wrote:
> That’s great to hear. I would also be available to help review submissions.
> 
> > On Apr 6, 2022, at 8:14 AM, Sharan Foga  wrote:
> > 
> > Hi Paulo 
> > 
> > We have great news - the Performance Engineering track has been accepted so 
> > we will be looking to encourage and promote CFP submissions for it. We are 
> > also looking for reviewers to help us rate the submissions---if you are 
> > still interested in doing that. ;-)
> > 
> > Thanks
> > Sharan
> > 
> >> On 2022/03/16 15:36:04 Sharan Foga wrote:
> >> Hi Paulo
> >> 
> >> Thanks for the feedback. If we do get the track accepted then we will 
> >> definitely be needing help reviewing the submissions - so may take you up 
> >> on your offer :-)
> >> 
> >> Thanks
> >> Sharan
> >> 
> >>> On 2022/03/14 16:32:23 Paulo Motta wrote:
> >>> This Apachecon track sounds fun! I hope someone from the Cassandra
> >>> community steps up to help on this track.
> >>> 
> >>> I would be happy to help on reviews but not organize the event per se as I
> >>> will likely not attend the event.
> >>> 
> >>>> Em sex., 11 de mar. de 2022 às 09:26, sharanf  
> >>>> escreveu:
> >>> 
> >>>> Hi All
> >>>> 
> >>>> The call for tracks for ApacheCon NA is open. There is a suggestion to
> >>>> try and run a Performance Engineering track at ApacheCon this year. At
> >>>> the end of the message I have included some details including a
> >>>> definition of what we mean by it and some reasoning about why it could
> >>>> be good to run. We have a list of projects that have something to do
> >>>> with performance engineering and if you take a look -  you will see that
> >>>> this project is on the list!
> >>>> 
> >>>> So what I need is a some feedback as to whether the community thinks
> >>>> that this could be an interesting track topic to run at ApacheCon..and
> >>>> more importantly would the community be willing to submit talks for it
> >>>> or attend ApacheCon to see it.
> >>>> 
> >>>> Like I say - this is just an idea at this stage. If the Performance
> >>>> Engineering track does get approval to be included at ApacheCon  - do we
> >>>> have any volunteers willing to help with managing and promoting the
> >>>> track on behalf of the project?
> >>>> 
> >>>> Thanks
> >>>> Sharan
> >>>> 
> >>>> -
> >>>> 
> >>>> *Performance Engineering*  is the science and practice of engineering
> >>>> software with the required performance and scalability characteristics.
> >>>> Many Apache projects focus on solving hard Big Data performance and
> >>>> scalability challenges, while others provide tools for performance
> >>>> engineering - but there are few projects that don’t care about some
> >>>> aspect of software performance.
> >>>> 
> >>>> This track will enable Apache projects members to share their
> >>>> experiences of performance engineering best practices, tools,
> >>>> techniques, and results, from their own communities, with the benefits
> >>>> of cross-fertilization between projects. Performance Engineering in the
> >>>> wider open source community is pervasive and includes methods and tools
> >>>> (including automation and agile approaches) for performance:
> >>>> architecting and design, benchmarking, monitoring, tracing, analysis,
> >>>> prediction, modeling and simulation, testing and reporting, regression
> >>>> testing, and source code analysis and instrumentation techniques.
> >>>> 
> >>>> Performance Engineering also has wider applicability to DevOps, the
> >>>> operation of cloud platforms by managed service providers (hence some
> >>>> overlap with SRE - Site Reliability Engineering), a

Re: Performance Engineering Track at ApacheCon NA?

[Sharan Foga]

Hi Paulo

Yes we are still looking for reviewers. The duties are to read through the 
submission abstracts and rate them. It's a fairly simple process. If you are 
still interested then let me know and I'll request your setup.

Thanks
Sharan

On 2022/05/20 19:02:21 Paulo Motta wrote:
> Hi Sharan,
> 
> Are you still looking for track reviewers on the perf. engineering track?
> What are the duties involved?
> 
> Thanks,
> 
> Paulo
> 
> On Wed, 6 Apr 2022 at 12:14 Sharan Foga  wrote:
> 
> > Hi Paulo
> >
> > We have great news - the Performance Engineering track has been accepted
> > so we will be looking to encourage and promote CFP submissions for it. We
> > are also looking for reviewers to help us rate the submissions---if you are
> > still interested in doing that. ;-)
> >
> > Thanks
> > Sharan
> >
> > On 2022/03/16 15:36:04 Sharan Foga wrote:
> > > Hi Paulo
> > >
> > > Thanks for the feedback. If we do get the track accepted then we will
> > definitely be needing help reviewing the submissions - so may take you up
> > on your offer :-)
> > >
> > > Thanks
> > > Sharan
> > >
> > > On 2022/03/14 16:32:23 Paulo Motta wrote:
> > > > This Apachecon track sounds fun! I hope someone from the Cassandra
> > > > community steps up to help on this track.
> > > >
> > > > I would be happy to help on reviews but not organize the event per se
> > as I
> > > > will likely not attend the event.
> > > >
> > > > Em sex., 11 de mar. de 2022 às 09:26, sharanf 
> > escreveu:
> > > >
> > > > > Hi All
> > > > >
> > > > > The call for tracks for ApacheCon NA is open. There is a suggestion
> > to
> > > > > try and run a Performance Engineering track at ApacheCon this year.
> > At
> > > > > the end of the message I have included some details including a
> > > > > definition of what we mean by it and some reasoning about why it
> > could
> > > > > be good to run. We have a list of projects that have something to do
> > > > > with performance engineering and if you take a look -  you will see
> > that
> > > > > this project is on the list!
> > > > >
> > > > > So what I need is a some feedback as to whether the community thinks
> > > > > that this could be an interesting track topic to run at
> > ApacheCon..and
> > > > > more importantly would the community be willing to submit talks for
> > it
> > > > > or attend ApacheCon to see it.
> > > > >
> > > > > Like I say - this is just an idea at this stage. If the Performance
> > > > > Engineering track does get approval to be included at ApacheCon  -
> > do we
> > > > > have any volunteers willing to help with managing and promoting the
> > > > > track on behalf of the project?
> > > > >
> > > > > Thanks
> > > > > Sharan
> > > > >
> > > > > -
> > > > >
> > > > > *Performance Engineering*  is the science and practice of engineering
> > > > > software with the required performance and scalability
> > characteristics.
> > > > > Many Apache projects focus on solving hard Big Data performance and
> > > > > scalability challenges, while others provide tools for performance
> > > > > engineering - but there are few projects that don’t care about some
> > > > > aspect of software performance.
> > > > >
> > > > > This track will enable Apache projects members to share their
> > > > > experiences of performance engineering best practices, tools,
> > > > > techniques, and results, from their own communities, with the
> > benefits
> > > > > of cross-fertilization between projects. Performance Engineering in
> > the
> > > > > wider open source community is pervasive and includes methods and
> > tools
> > > > > (including automation and agile approaches) for performance:
> > > > > architecting and design, benchmarking, monitoring, tracing, analysis,
> > > > > prediction, modeling and simulation, testing and reporting,
> > regression
> > > > > testing, and source code analysis and instrumentation techniques.
> > > > >
> > > > > Performance Engineering also has wider appl

RE: [EXTERNAL] Re: Performance Engineering Track at ApacheCon NA?

[Sharan Foga]

Hi German

Thanks for the offer of help. 

Please confirm if you'd like to be a reviewer for the track. Note that the one 
thing we are asking is that you are not submitting a talk to the track that you 
are reviewing. So as long as you are not planning to submit a talk for the 
Performance Engineering track then we'd be happy to have you as a reviewer.

Thanks
Sharan

On 2022/05/20 20:06:59 German Eichberger wrote:
> Hi Sharan,
> 
> I am planning to attend the summit and happy to help as well.
> 
> Thanks,
> German
> 
> From: Paulo Motta 
> Sent: Friday, May 20, 2022 12:02 PM
> To: dev@cassandra.apache.org
> Subject: [EXTERNAL] Re: Performance Engineering Track at ApacheCon NA?
> 
> Hi Sharan,
> 
> Are you still looking for track reviewers on the perf. engineering track? 
> What are the duties involved?
> 
> Thanks,
> 
> Paulo
> 
> On Wed, 6 Apr 2022 at 12:14 Sharan Foga 
> mailto:sha...@apache.org>> wrote:
> Hi Paulo
> 
> We have great news - the Performance Engineering track has been accepted so 
> we will be looking to encourage and promote CFP submissions for it. We are 
> also looking for reviewers to help us rate the submissions---if you are still 
> interested in doing that. ;-)
> 
> Thanks
> Sharan
> 
> On 2022/03/16 15:36:04 Sharan Foga wrote:
> > Hi Paulo
> >
> > Thanks for the feedback. If we do get the track accepted then we will 
> > definitely be needing help reviewing the submissions - so may take you up 
> > on your offer :-)
> >
> > Thanks
> > Sharan
> >
> > On 2022/03/14 16:32:23 Paulo Motta wrote:
> > > This Apachecon track sounds fun! I hope someone from the Cassandra
> > > community steps up to help on this track.
> > >
> > > I would be happy to help on reviews but not organize the event per se as I
> > > will likely not attend the event.
> > >
> > > Em sex., 11 de mar. de 2022 às 09:26, sharanf 
> > > mailto:sha...@apache.org>> escreveu:
> > >
> > > > Hi All
> > > >
> > > > The call for tracks for ApacheCon NA is open. There is a suggestion to
> > > > try and run a Performance Engineering track at ApacheCon this year. At
> > > > the end of the message I have included some details including a
> > > > definition of what we mean by it and some reasoning about why it could
> > > > be good to run. We have a list of projects that have something to do
> > > > with performance engineering and if you take a look -  you will see that
> > > > this project is on the list!
> > > >
> > > > So what I need is a some feedback as to whether the community thinks
> > > > that this could be an interesting track topic to run at ApacheCon..and
> > > > more importantly would the community be willing to submit talks for it
> > > > or attend ApacheCon to see it.
> > > >
> > > > Like I say - this is just an idea at this stage. If the Performance
> > > > Engineering track does get approval to be included at ApacheCon  - do we
> > > > have any volunteers willing to help with managing and promoting the
> > > > track on behalf of the project?
> > > >
> > > > Thanks
> > > > Sharan
> > > >
> > > > -
> > > >
> > > > *Performance Engineering*  is the science and practice of engineering
> > > > software with the required performance and scalability characteristics.
> > > > Many Apache projects focus on solving hard Big Data performance and
> > > > scalability challenges, while others provide tools for performance
> > > > engineering - but there are few projects that don't care about some
> > > > aspect of software performance.
> > > >
> > > > This track will enable Apache projects members to share their
> > > > experiences of performance engineering best practices, tools,
> > > > techniques, and results, from their own communities, with the benefits
> > > > of cross-fertilization between projects. Performance Engineering in the
> > > > wider open source community is pervasive and includes methods and tools
> > > > (including automation and agile approaches) for performance:
> > > > architecting and design, benchmarking, monitoring, tracing, analysis,
> > > > prediction, modeling and simulation, testing and reporting, regression
> > > > testing, and source code analysis and instrumentation techniques.
> > > >
> >

Re: [Marketing] For Review: Learn How CommitLog Works in Apache Cassandra

[Sharan Foga]

Hi Chris

I've added a few comments and suggestions. Please feel free to use /ignore 
whichever ones you think :-)

Thanks
Sharan

On 2022/08/23 00:08:52 Chris Thornett wrote:
> Opening up Alex Sorokoumov's guide 'Learn How CommitLog Works in Apache
> Cassandra' for a 72-hr community review by lazy consensus.
> 
> Please add any amends and suggestions in the comments:
> https://docs.google.com/document/d/1cyOi-IeU_I9GBkpQbJS6IIrmemAesEqvzLb-eeFs_rM/edit#
> 
> Thanks!
> 
> -- 
> 
> Chris Thornett
> Senior Content Strategist, Constantia.io
> 

Re: [Marketing] For Review: Performance Benchmarking of Apache Cassandra in the Cloud

[Sharan Foga]

Hi Chris

Added a few suggestions (and I see some others have too!). As always please 
feel free to use or ignore as you think.

Thanks
Sharan

On 2022/08/24 21:35:01 Chris Thornett wrote:
> Here is Part 1 in a series of 3 on performance benchmarking in Apache
> Cassandra by Daniel Seybold:
> https://docs.google.com/document/d/1eMFYEOp8lNxZCYelYCWj6jXZ-VaJGNbl2YE3jLWRdOA/edit?usp=sharing
> 
> We are opening this up for 72-hour community review. Please add your amends
> in the comments—thanks very much!
> 
> We are looking at 30 August for publication.
> 
> Thanks,
> -- 
> 
> Chris Thornett
> Senior Content Strategist, Constantia.io
> 

Re: Looking for documentation tasks to work on

[Sharan Foga]

Hi Josh

Excellent and thanks for this. I'll take a look.

Thanks
Sharan

On 2022/10/18 20:35:50 Josh McKenzie wrote:
> Hey Sharan! Documentation is near and dear to my heart; the longer I spend on 
> this project the more I think it's one of the higher leverage things we can 
> invest our energy into. A general high level view of open documentation work 
> in the project in reverse key order can be found here: 
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20cassandra%20and%20resolution%20%3D%20unresolved%20and%20summary%20~%20%22documentation%22%20order%20by%20issuekey%20desc
> 
> Specifically I have my eye on our CI and contribution process and should have 
> a variety of documentation tickets opening up based on some of the changes 
> Andres made in CASSANDRA-17939 and some follow up work (see comment here if 
> curious: 
> https://issues.apache.org/jira/browse/CASSANDRA-17939?focusedCommentId=17617880&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17617880)
> 
> If I'm not mistaken Derek said he ran into some dead / not working links in 
> the how to contribute structure (link: 
> https://cassandra.apache.org/_/development/index.html) - @Derek were you 
> taking that or is that part of the above workload?)
> 
> And at the risk of flooding you w/too many options, last but not least is a 
> pretty straightforward resurrection of some documentation that got dropped 
> for the Denylisting functionality 
> (https://issues.apache.org/jira/browse/CASSANDRA-17547) - you can ping Jordan 
> West on ASF slack to see if he's active on that ticket. Of all the issues 
> that may be one of the more straightforward.
> 
> Hit me up on slack with any questions and glad to have you here!
> 
> ~Josh
> 
> On Tue, Oct 18, 2022, at 6:28 AM, sharanf wrote:
> > Hi All
> > 
> > It was really good to be at ApacheCon in New Orleans and finally put 
> > some real faces to the names I've seen on the mailing list. And sitting 
> > in the Cassandra BOF session has made me even more motivated to help 
> > out. I've been thinking of getting involved and contributing to the docs 
> > so please can someone point me in the direction of something that needs 
> > doing around documentation :-)
> > 
> > Thanks
> > Sharan
> > 
> 

Re: Looking for documentation tasks to work on

[Sharan Foga]

Hi Paulo

Great to meet you at ApacheCon! And thanks for this suggestion - it's on my 
list :-)

Thanks
Sharan

On 2022/10/19 14:37:26 Paulo Motta wrote:
> Welcome Sharan! :)
> 
> One of the features that is going to be released in 4.1 is the ability to
> add TTL to snapshots, but this hasn't been documented yet afaik.
> 
> There's a preliminary documentation patch available on
> https://issues.apache.org/jira/browse/CASSANDRA-16887 if you want to take a
> stab at it.
> 
> Em ter., 18 de out. de 2022 às 16:36, Josh McKenzie 
> escreveu:
> 
> > Hey Sharan! Documentation is near and dear to my heart; the longer I spend
> > on this project the more I think it's one of the higher leverage things we
> > can invest our energy into. A general high level view of open documentation
> > work in the project in reverse key order can be found here:
> > https://issues.apache.org/jira/issues/?jql=project%20%3D%20cassandra%20and%20resolution%20%3D%20unresolved%20and%20summary%20~%20%22documentation%22%20order%20by%20issuekey%20desc
> >
> > Specifically I have my eye on our CI and contribution process and should
> > have a variety of documentation tickets opening up based on some of the
> > changes Andres made in CASSANDRA-17939 and some follow up work (see comment
> > here if curious:
> > https://issues.apache.org/jira/browse/CASSANDRA-17939?focusedCommentId=17617880&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17617880
> > )
> >
> > If I'm not mistaken Derek said he ran into some dead / not working links
> > in the how to contribute structure (link:
> > https://cassandra.apache.org/_/development/index.html) - @Derek were you
> > taking that or is that part of the above workload?)
> >
> > And at the risk of flooding you w/too many options, last but not least is
> > a pretty straightforward resurrection of some documentation that got
> > dropped for the Denylisting functionality (
> > https://issues.apache.org/jira/browse/CASSANDRA-17547) - you can ping
> > Jordan West on ASF slack to see if he's active on that ticket. Of all the
> > issues that may be one of the more straightforward.
> >
> > Hit me up on slack with any questions and glad to have you here!
> >
> > ~Josh
> >
> > On Tue, Oct 18, 2022, at 6:28 AM, sharanf wrote:
> >
> > Hi All
> >
> > It was really good to be at ApacheCon in New Orleans and finally put
> > some real faces to the names I've seen on the mailing list. And sitting
> > in the Cassandra BOF session has made me even more motivated to help
> > out. I've been thinking of getting involved and contributing to the docs
> > so please can someone point me in the direction of something that needs
> > doing around documentation :-)
> >
> > Thanks
> > Sharan
> >
> >
> >
> 

Re: Looking for documentation tasks to work on

[Sharan Foga]

Hi Ekaterina

Thanks for the suggestion! Looks like documentation is a hot topic so great 
there are a few opportunities to get involved. :-)

Thanks
Sharan

On 2022/10/19 15:06:23 Ekaterina Dimitrova wrote:
> One more idea, I was looking to update the What’s new page - a few links to
> docs or blog pages and referral to NEWS.txt and CHANGES.txt maybe.
> Currently the 4.1 and trunk What’s new pages point to the 4.0 one things
> and the config docs only. I will open a ticket later today. That should be
> a quick fix I think but nice to have now when beta is out.
> 
> On Wed, 19 Oct 2022 at 10:37, Paulo Motta  wrote:
> 
> > Welcome Sharan! :)
> >
> > One of the features that is going to be released in 4.1 is the ability to
> > add TTL to snapshots, but this hasn't been documented yet afaik.
> >
> > There's a preliminary documentation patch available on
> > https://issues.apache.org/jira/browse/CASSANDRA-16887 if you want to take
> > a stab at it.
> >
> > Em ter., 18 de out. de 2022 às 16:36, Josh McKenzie 
> > escreveu:
> >
> >> Hey Sharan! Documentation is near and dear to my heart; the longer I
> >> spend on this project the more I think it's one of the higher leverage
> >> things we can invest our energy into. A general high level view of open
> >> documentation work in the project in reverse key order can be found here:
> >> https://issues.apache.org/jira/issues/?jql=project%20%3D%20cassandra%20and%20resolution%20%3D%20unresolved%20and%20summary%20~%20%22documentation%22%20order%20by%20issuekey%20desc
> >>
> >> Specifically I have my eye on our CI and contribution process and should
> >> have a variety of documentation tickets opening up based on some of the
> >> changes Andres made in CASSANDRA-17939 and some follow up work (see comment
> >> here if curious:
> >> https://issues.apache.org/jira/browse/CASSANDRA-17939?focusedCommentId=17617880&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17617880
> >> )
> >>
> >> If I'm not mistaken Derek said he ran into some dead / not working links
> >> in the how to contribute structure (link:
> >> https://cassandra.apache.org/_/development/index.html) - @Derek were you
> >> taking that or is that part of the above workload?)
> >>
> >> And at the risk of flooding you w/too many options, last but not least is
> >> a pretty straightforward resurrection of some documentation that got
> >> dropped for the Denylisting functionality (
> >> https://issues.apache.org/jira/browse/CASSANDRA-17547) - you can ping
> >> Jordan West on ASF slack to see if he's active on that ticket. Of all the
> >> issues that may be one of the more straightforward.
> >>
> >> Hit me up on slack with any questions and glad to have you here!
> >>
> >> ~Josh
> >>
> >> On Tue, Oct 18, 2022, at 6:28 AM, sharanf wrote:
> >>
> >> Hi All
> >>
> >> It was really good to be at ApacheCon in New Orleans and finally put
> >> some real faces to the names I've seen on the mailing list. And sitting
> >> in the Cassandra BOF session has made me even more motivated to help
> >> out. I've been thinking of getting involved and contributing to the docs
> >> so please can someone point me in the direction of something that needs
> >> doing around documentation :-)
> >>
> >> Thanks
> >> Sharan
> >>
> >>
> >>
> 

Re: Looking for documentation tasks to work on

[Sharan Foga]

Hi Josh

I've added a note for Jordan in the Jira Ticket 
https://issues.apache.org/jira/browse/CASSANDRA-17547 to see if he's still on 
it and if not then I'd be happy to take it. It looks like a conversion of the 
rst format to adoc then adding it back into the docs structure.

Thanks
Sharan 

On 2022/10/20 07:56:57 Sharan Foga wrote:
> Hi Josh
> 
> Excellent and thanks for this. I'll take a look.
> 
> Thanks
> Sharan
> 
> On 2022/10/18 20:35:50 Josh McKenzie wrote:
> > Hey Sharan! Documentation is near and dear to my heart; the longer I spend 
> > on this project the more I think it's one of the higher leverage things we 
> > can invest our energy into. A general high level view of open documentation 
> > work in the project in reverse key order can be found here: 
> > https://issues.apache.org/jira/issues/?jql=project%20%3D%20cassandra%20and%20resolution%20%3D%20unresolved%20and%20summary%20~%20%22documentation%22%20order%20by%20issuekey%20desc
> > 
> > Specifically I have my eye on our CI and contribution process and should 
> > have a variety of documentation tickets opening up based on some of the 
> > changes Andres made in CASSANDRA-17939 and some follow up work (see comment 
> > here if curious: 
> > https://issues.apache.org/jira/browse/CASSANDRA-17939?focusedCommentId=17617880&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17617880)
> > 
> > If I'm not mistaken Derek said he ran into some dead / not working links in 
> > the how to contribute structure (link: 
> > https://cassandra.apache.org/_/development/index.html) - @Derek were you 
> > taking that or is that part of the above workload?)
> > 
> > And at the risk of flooding you w/too many options, last but not least is a 
> > pretty straightforward resurrection of some documentation that got dropped 
> > for the Denylisting functionality 
> > (https://issues.apache.org/jira/browse/CASSANDRA-17547) - you can ping 
> > Jordan West on ASF slack to see if he's active on that ticket. Of all the 
> > issues that may be one of the more straightforward.
> > 
> > Hit me up on slack with any questions and glad to have you here!
> > 
> > ~Josh
> > 
> > On Tue, Oct 18, 2022, at 6:28 AM, sharanf wrote:
> > > Hi All
> > > 
> > > It was really good to be at ApacheCon in New Orleans and finally put 
> > > some real faces to the names I've seen on the mailing list. And sitting 
> > > in the Cassandra BOF session has made me even more motivated to help 
> > > out. I've been thinking of getting involved and contributing to the docs 
> > > so please can someone point me in the direction of something that needs 
> > > doing around documentation :-)
> > > 
> > > Thanks
> > > Sharan
> > > 
> > 
>