[INTRODUCTIONS] New Non Coding Contributor

[sharanf]

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, meetups, 
etc).  As a start I will take a look through the project website, wiki 
space and the existing documentation and see if I can find something to 
work on :-)


Please feel free to reach out to me if there is anything specific that 
need doing as I am happy to help. Really looking forward to being part 
of the community!


Thanks
Sharan



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

Re: [INTRODUCTIONS] New Non Coding Contributor

[sharanf]

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 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

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, meetups,
etc).  As a start I will take a look through the project website, wiki
space and the existing documentation and see if I can find something to
work on :-)

Please feel free to reach out to me if there is anything specific that
need doing as I am happy to help. Really looking forward to being part
of the community!

Thanks
Sharan



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





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

Re: [INTRODUCTIONS] New Non Coding Contributor

[sharanf]

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 website is looking really cool!)  I will run 
though it and see how it goes.  I've joined the #cassandra-website and 
#cassandra-events slack channels so will follow those too.


On the non coding committers topic - I do have some experience around it 
and would be happy to share what I know.


Thanks
Sharan

On 2021-11-23 12:23, Mick Semb Wever wrote:

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, meetups,
etc).  As a start I will take a look through the project website, wiki
space and the existing documentation and see if I can find something to
work on :-)



Hi Sharan! Thanks for connecting. We are honoured to have an ASF Board
Director 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 amount of work has gone into this, but it is still very new and
needs many small fixes and eyeballs. All, and any, help we can get there is
most welcome. It should be a super easy place for a non coder contributor
to get started, and it is definitely intended to be that very soon, but for
the moment we are blocked and still working on merging CASSANDRA-16763.

To build the website, you need docker, and to run the following steps:
```
 git clone https://github.com/apache/cassandra-website.git
 cd cassandra-website
 ./run.sh website-ui bundle
 ./run.sh website build -i -b cassandra:trunk,cassandra-3.11 -u
cassandra:https://github.com/polandll/cassandra.git -z
./site-ui/build/ui-bundle.zip

 # preview in your browser
 open site-content/build/html/_/index.html
```
(Note the second run.sh step will switch to use the official repo fork and
branches once 16763 is merged.)

There's a number of tickets that have been created that relate to the new
website and docs, under CASSANDRA-16761.

Otherwise, the docs are asciidoc that are easy enough to directly edit and
open a PR against; so just reach out on #cassandra-website slack and the
folk there will be very happy to help out in any way they can. There, and
also on #cassandra-events,  is where the activity around events and social
media is happening too. There's been some interesting discussions there the
past month around our twitter account, hashtags, and having a content
pipeline in place.

Beyond such hands-on non-coding type of contributions, we are also looking
for inspiration on how better to recognise non-coding contributors, and
even if the idea of non-coding committers has a place in the project. Ideas
and examples on how other projects have done this would be a real
contribution.




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

[DISCUSS] Non Coding Committers

[sharanf]

Hi All

I mentioned a while ago that I would start a discussion about having 
Committers on the project that can focus on non coding contributions.


Let me start by saying that I wouldn't be doing what I do at the ASF 
today if the first project I contributed to (Apache OFBiz) had not 
recognised my non coding contributions and made me a committer. My 
contributions to the project were mainly testing and documentation. One 
year when ApacheCon EU came around I helped organise an ApacheCon track 
for the project.


I must admit that I went through quite a few emotions when I received 
the committership email.. first surprise, excitement but also a little 
apprehension, because being a committer carries some responsibility. I 
really didn't want to mess up a project that I cared so much about. What 
really made the difference for me was that the email highlighted that 
the PMC trusted me. They trusted me with the codebase - or more 
importantly they trusted that I would use my judgement about whether or 
not to do any code changes. And initially it wasn't an issue - I didnt 
need to update the codebase so I even though I was a committer, I didn't 
commit anything. Why should I? I continued making sure that the blogs, 
documentation and social media promotion all kept happening - which 
really helped the project.


A little later on we started incorporating documentation into the 
codebase as asciidoc files so that was when being able to commit changes 
to the repo became a bit more important. So yes I do commit changes 
every now and then - but only in the scope of the work I am doing. I 
went on to become their first ever non coding PMC member too :-). And I 
can say that being a non coder brings another perspective.


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.


I would say that any contribution that helps a project in a positive way 
is valid contribution so recognising the people that do that work by 
making them Committers helps not only with motivation but also shows 
that you value those skills as well as coding.


We want both coding and non coding contributions to earn the same merit 
so I see it is more about trusting people to do the right thing for the 
project.


This is written from my own experience so I'm happy to get any feedback, 
comments and other viewpoints!


Thanks

Sharan

Performance Engineering Track at ApacheCon NA?

[sharanf]

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


 2. Real time insights into LinkedIn's 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

 6. Performance-Regression Pitfalls Every Project Should Avoid


 7. How to benchmark your websites with the open source Apache Bench
tool


 8. Benchmarking Pulsar and Kafka - A More Accurate Perspective on
Pulsar’s Performance


 9. Performance-Analyse: Apache Cassandra 4.0.0 Release

10. Log4J Performance - This page compares the performance of a number
of logging frameworks

11. SystemML Performance T

RE: FOR REVIEW: blog post - Kinetic Data case study

[sharanf]

HI Chris

It looks good to me.

Thanks
Sharan

On 2022/03/24 17:23:01 Chris Thornett wrote:
> For the next blog, we're highlighting a recent user case that is 
going/gone

> live in the 'Case Study' section of the website.
>
> Here's the Google Doc for 72-hour review, please add any edits or
> suggestions as comments, please:
> 
https://docs.google.com/document/d/1xWXWgo-bB3Lx32tEhA77h14-40uN_8N2OnMFu7m-8gg/edit?usp=sharing

>
> On case studies generally, if you're aware of companies/organizations 
that
> haven't provided one for the project or we need to do a refresh, 
please let

> me know.
>
> Thanks,
>
> --
>
> Chris Thornett
> senior content strategist, Constantia.io
> ch...@constantia.io
> LinkedIn  | Twitter
> 
>

Podcast Interviews for Feathercast

[sharanf]

Hi All

For those who are not familiar withFeatherCast 
 -  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.


Thanks
Sharan

Performance Engineering Track CFP for ApacheCon NA New Orleans

[sharanf]

Hi All

I hope that you have already heard that ApacheCon NA is back as a live 
event in New Orleans later this year. You can find out more details 
here: https://apachecon.com/acna2022/


For the first time ever - we will be running a Performance Engineering 
track. So what is Performance Engineering? You can find a definition and 
a track description here: https://s.apache.org/3ykqk


If you are interested in making a submission to this new track then you 
can find a link to the CFP here: https://apachecon.com/acna2022/cfp.html


We are looking forward to receiving your submissions and hopefully 
seeing those of you who can make it to New Orleans in October.


Thanks
Sharan

Looking for documentation tasks to work on

[sharanf]

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