Re: Issue while trying to run pytest command

[Manish G]

It works if you are in cassandra-dtest directory.

And it seems I need to create the loopback interfaces by running 'for i in
{1..9}; do sudo ifconfig lo0 alias 127.0.0.$i up; done;' !

Thanks.

Manish

On Mon, Jan 10, 2022 at 12:23 AM Francisco Guerrero 
wrote:

> Hi Manish,
>
> I suspect this has to do with spaces (or special characters) in the
> cassandra-dir argument. Can you try again wrapping the path in quotes, for
> example:
>
> pytest --cassandra-dir="/Users//cassandra"
>
> Hope that helps.
>
> - Francisco
>
> On 2022/01/09 10:43:05 Manish G wrote:
> > I am trying to run pytest command :
> >
> > (dtest) manish.ghildiyal@MacBook-Pro-3 cassandra % pytest
> > > --cassandra-dir=/Users/../cassandra
> >
> >
> > But I get error as:
> >
> > pytest: error: unrecognized arguments:
> > > --cassandra-dir=/Users/./cassandra
> >
> >
> > I have done initial installation following  this.
> >
> > Do I need to do any more configuration?
> >
> > Manish
> >
>

Re: Issue while trying to run pytest command

[Manish G]

Initial installation is done following
https://github.com/apache/cassandra-dtest#python-dependencies.


On Sun, Jan 9, 2022 at 11:43 AM Manish G 
wrote:

> I am trying to run pytest command :
>
> (dtest) manish.ghildiyal@MacBook-Pro-3 cassandra % pytest
>> --cassandra-dir=/Users/../cassandra
>
>
> But I get error as:
>
> pytest: error: unrecognized arguments:
>> --cassandra-dir=/Users/./cassandra
>
>
> I have done initial installation following  this.
>
> Do I need to do any more configuration?
>
> Manish
>

Issue while trying to run pytest command

[Manish G]

I am trying to run pytest command :

(dtest) manish.ghildiyal@MacBook-Pro-3 cassandra % pytest
> --cassandra-dir=/Users/../cassandra


But I get error as:

pytest: error: unrecognized arguments:
> --cassandra-dir=/Users/./cassandra


I have done initial installation following  this.

Do I need to do any more configuration?

Manish

Re: Cassandra project biweekly status update 2022-01-03

[Manish G]

There is already a list of tickets with mentors associated. Do these 'lhfs'
also fall in same category?

On Mon, Jan 3, 2022, 8:51 PM Joshua McKenzie  wrote:

> /wave Happy 2022 everyone!
>
> [New contributors getting started]
> There are two curated options for getting started if you're new to the
> project and looking to get oriented: Failing tests, or starter tickets we
> label "lhf" (low hanging fruit). Don't let either fool you - it's almost
> always interesting work with more depth than expected at first glance. Yay
> mature distributed infrastructure software! :)
>
> Query for failing tests:
> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252
> Query for unassigned starter tickets:
> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=484=2162=2160
>
> We've bumped up a bit on open test failure tickets; have 26 unassigned to
> choose from and we have just over 30 good starter tickets evenly split
> between our next minor release and next major. Feel free to self-select
> from any of the above lists or reach out on slack if you want some guidance
> on where to get involved. 2022 is a good year to start getting involved in
> some coding don't you think?
>
> [Dev list discussions in the past 14 days]
> https://lists.apache.org/list?dev@cassandra.apache.org:lte=2w:
>
> We were slightly less chatty than usual over the past couple of weeks
> which is to be expected. Still - some interesting things to discuss:
>
> - When should we cut our next major release (early signs of consensus)?
> https://lists.apache.org/thread/lsr45h2n72m8fbz3xqby6lsm7lqr7vm8
> - How should we version releases and snapshots (early signs of... not so
> much consensus :D)
> https://lists.apache.org/thread/zz3x1zl1lo8rkqpf0cl992y6fsy4r9gc
>
> And some various and sundry, mostly around me being irritated with failing
> tests when I try to merge things and trying to figure out how to kill this
> problem with fire. A grand and well established tradition on the project
> stretching back years.
>
> [Tickets Closed in the past 14 days]
>
> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=484=2175
>
> Not surprisingly things were very slow on the close front (3 total,
> minimal things). On the plus side, this means picking patches back up that
> are works in flight here in Jan will require minimal, if any, rebasing. :)
>
> [Tickets that need attention]
> Needs Reviewer:
> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=484=CASSANDRA-16547=2259
>
> Down from 10 to 9 needing review on 4.0.2 and holding steady at 30 on
> 4.1.0. I'm going to get a little bit more active in trying to track down or
> provide review for things on this list; patches rotting (and people having
> to drag things forward via repeated rebasing) due to lack of review is not
> my personal favorite.
>
> [Test Failure Trendlines]
> Butler: https://butler.cassandra.apache.org/#/
> Stable branches are holding steady and trending slightly down which is
> what we'd expect for where they are in their lifecycle and the holiday
> season.
> * 3.0:30 -> 28
> * 3.11:   42 -> 40
> * 4.0:10 -> 9
> * trunk:  ... varied.
>
> We've been discussing in the #cassandra-dev slack about workflow and ways
> to make the Butler <-> JIRA relationship a bit more turnkey and the
> introduction of the Build Lead role. Should have some draft wikis up for
> review on that shortly.
>
> It's been incredibly encouraging to see how active the project has been in
> 2021 and I look forward to seeing how things evolve with some of the
> upcoming significant CEP's and features this year. Thanks everyone!
>
> ~Josh
>

Code formatting

[Manish G]

Hi,

Is there any code formatter file which can be configured in intellij?

With regards
Manish

Re: [DISCUSS] Proposal for a December event

[Manish G]

Hi,

I would like to work on these tickets for newcomers.

With regards
Manish

On Fri, Dec 3, 2021, 2:17 PM Paulo Motta  wrote:

> Here is my contribution to the advent calendar effort (I'm willing to
> mentor these tickets):
> - CASSANDRA-16436: Add startup check for large read_ahead_kb setting [1]
> - CASSANDRA-16664: Log JVM Arguments at in-JVM Test Class Initialization
> [2]
> - CASSANDRA-16584: Allow sstableloader to specify keyspace/table without
> relying on path [3]
>
> [1] - 
> [2] - 
> [3] - 
>
> Em qui., 25 de nov. de 2021 às 13:50, Benjamin Lerer 
> escreveu:
>
> > I totally agree with your analysis of our LHF situation Paulo.
> >
> > The idea is to promote one ticket per day for 24 days. That approach
> should
> > give us enough time to clean and enhance some tickets. We only need to
> > prepare one per day :-)
> > I have a few candidates in mind already. If 8 persons provide 3 each we
> > have our set of tickets. That seems reasonable, no?
> >
> > I also think that it is fine if the level of difficulty is different as
> > long as we mention it clearly and that we provide some clear approach to
> > solve the problem. Different people might be interested in different
> levels
> > of difficulties.
> >
> > Le mer. 24 nov. 2021 à 18:46, Paulo Motta  a
> > écrit :
> >
> > > The idea sounds great to me in principle - the only issue I see is:
> > >
> > > > we promote a simple ticket everyday for a newcomer to pickup
> > >
> > > During GSoC this year I had difficulty selecting "simple tickets for
> > > newcomers to pickup" for the following reasons:
> > > - inconsistency in LHF tagging (not many of the existing tasks are
> > markedd
> > > as LHF/newcomer-friendly)
> > > - inconsistency in LHF difficulty (some are easy while others have
> > > considerable difficulty for a newcomer)
> > > - LHF tasks lacking a clear description of what needs to be
> accomplished
> > >
> > > For these reasons I don't think the LHF pool is currently in a good
> state
> > > to use it as a pool of tasks for this campaign, but perhaps this could
> > be a
> > > good reason to improve the quality of our LHF pool for this and other
> > > mentoring initiatives in the future - my only fear is that we may not
> > have
> > > sufficient time to build this pool of tasks in time for a Christmas
> > > campaign.
> > >
> > > Em qua., 24 de nov. de 2021 às 14:13, Benjamin Lerer <
> ble...@apache.org>
> > > escreveu:
> > >
> > > > Hi everybody,
> > > >
> > > > I would like to take the occasion of the month of December and of the
> > > > holiday seasons to attract new contributors and to create more
> > visibility
> > > > for the project.
> > > > I was thinking of creating some kind of Advent calendar on Twitter
> > where
> > > we
> > > > promote a simple ticket everyday for a newcomer to pickup. The ticket
> > > > should have the main steps described and some mentor associated with
> > it.
> > > If
> > > > by the 1st of March the patch for the ticket has been committed the
> > > > contributor will receive a special T-shirt as a gift.
> > > >
> > > > I will be happy to hear your opinion on this proposal,
> > > >
> > > > Benjamin
> > > >
> > >
> >
>

Re: Local build failure

[Manish G]

I had java 10, so replaced it by java 11, and then following command was
successful:
*ant -Drat.skip=true -Duse.jdk11=true*

May be this can be updated somewhere in documentation.

On Wed, Jun 2, 2021 at 9:35 PM Benjamin Lerer  wrote:

> The RAT check does not work on Windows. If you want to build on Windows you
> need to use -Drat.skip=true in your ant command. It should build fine at
> least it does for me.
>
>
> Le mer. 2 juin 2021 à 17:55, Joshua McKenzie  a
> écrit :
>
> > I had good luck in the past using WSL w/C* - highly recommend using that
> > for your build env on windows. And just in general. :)
> >
> >
> > On Wed, Jun 2, 2021 at 11:41 AM Brandon Williams 
> wrote:
> >
> > > Another problem you are likely to run into is that Windows is no
> > > longer supported directly:
> > > https://www.mail-archive.com/dev@cassandra.apache.org/msg15583.html
> > >
> > >
> > > On Wed, Jun 2, 2021 at 10:14 AM Manish G  >
> > > wrote:
> > > >
> > > > As per the link provided in last mail, 'ant' must work out of the
> box.
> > I
> > > ran following commands:
> > > >
> > > > >git status
> > > > On branch trunk
> > > > Your branch is up to date with 'origin/trunk'.
> > > >
> > > > >ant
> > > > Buildfile: D:\work\oss\cassandra\build.xml
> > > >
> > > > validate-build-conf:
> > > >
> > > > BUILD FAILED
> > > > D:\work\oss\cassandra\build.xml:339: -Duse.jdk11=true or
> > > $CASSANDRA_USE_JDK11=true must be set when building from java 11
> > > >
> > > > >set CASSANDRA_USE_JDK11=true
> > > >
> > > > >ant
> > > >
> > > > Log for last command is attached.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > nothing to commit, working tree clean
> > > >
> > > > On Wed, Jun 2, 2021 at 4:04 PM Mick Semb Wever 
> wrote:
> > > >>
> > > >> Manish, images don't come through the mailing list, so we can't see
> > > those
> > > >> errors you've posted :(
> > > >>
> > > >> And you may find this doc more up to date:
> > > >> https://cassandra.apache.org/doc/latest/development/ide.html
> > > >>
> > > >> On Wed, 2 Jun 2021 at 12:11, Manish G  >
> > > wrote:
> > > >>
> > > >> > I have no local changes.
> > > >> >
> > > >> > [image: image.png]
> > > >> >
> > > >> > I am following this
> > > >> > <
> > >
> >
> https://cwiki.apache.org/confluence/display/CASSANDRA2/RunningCassandraInIDEA
> > > >
> > > >> > .
> > > >> > After cloning the repo, when I run 'ant generate-idea-files', I
> see
> > > this:
> > > >> >
> > > >> > [image: image.png]
> > > >> >
> > > >> > So I do: set CASSANDRA_USE_JDK11=true, and rerun 'ant
> > > >> > generate-idea-files', and how I see error:
> > > >> >
> > > >> > [image: image.png]
> > > >> >
> > > >> >
> > > >> >
> > > >> > On Wed, Jun 2, 2021 at 3:14 PM Mick Semb Wever 
> > > wrote:
> > > >> >
> > > >> >> > I tried both 'ant realclean' and ''git clean -xdff' before
> > running
> > > the
> > > >> >> > 'ant' command, but still build fails.
> > > >> >>
> > > >> >>
> > > >> >> Manish, the failure should list (some of) the offending files
> > > (instead
> > > >> >> of `${rat.failed.files}`).
> > > >> >> What are the offending files listed in build/rat.txt ?
> > > >> >>
> > > >> >> Are you by chance working on a patch, and have added new files
> > which
> > > >> >> don't have the correct license headers?
> > > >> >>
> > > >> >>
> > -
> > > >> >> 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
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> > > For additional commands, e-mail: dev-h...@cassandra.apache.org
> > >
> > >
> >
>

Re: Local build failure

[Manish G]

As per the link provided in last mail, 'ant' must work out of the box. I
ran following commands:



*>git statusOn branch trunkYour branch is up to date with 'origin/trunk'.*








*>antBuildfile: D:\work\oss\cassandra\build.xmlvalidate-build-conf:BUILD
FAILEDD:\work\oss\cassandra\build.xml:339: -Duse.jdk11=true or
$CASSANDRA_USE_JDK11=true must be set when building from java 11*


*>set CASSANDRA_USE_JDK11=true*

*>ant*

Log for last command is attached.





nothing to commit, working tree clean

On Wed, Jun 2, 2021 at 4:04 PM Mick Semb Wever  wrote:

> Manish, images don't come through the mailing list, so we can't see those
> errors you've posted :(
>
> And you may find this doc more up to date:
> https://cassandra.apache.org/doc/latest/development/ide.html
>
> On Wed, 2 Jun 2021 at 12:11, Manish G 
> wrote:
>
> > I have no local changes.
> >
> > [image: image.png]
> >
> > I am following this
> > <
> https://cwiki.apache.org/confluence/display/CASSANDRA2/RunningCassandraInIDEA
> >
> > .
> > After cloning the repo, when I run 'ant generate-idea-files', I see this:
> >
> > [image: image.png]
> >
> > So I do: set CASSANDRA_USE_JDK11=true, and rerun 'ant
> > generate-idea-files', and how I see error:
> >
> > [image: image.png]
> >
> >
> >
> > On Wed, Jun 2, 2021 at 3:14 PM Mick Semb Wever  wrote:
> >
> >> > I tried both 'ant realclean' and ''git clean -xdff' before running the
> >> > 'ant' command, but still build fails.
> >>
> >>
> >> Manish, the failure should list (some of) the offending files (instead
> >> of `${rat.failed.files}`).
> >> What are the offending files listed in build/rat.txt ?
> >>
> >> Are you by chance working on a patch, and have added new files which
> >> don't have the correct license headers?
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> >> For additional commands, e-mail: dev-h...@cassandra.apache.org
> >>
> >>
>
>ant
Buildfile: D:\work\oss\cassandra\build.xml

validate-build-conf:

init:

_resolver_download:

resolver-init:
[resolver:resolve] Resolving artifacts
[resolver:resolve] Resolving artifacts
[resolver:resolve] Resolving artifacts
[resolver:resolve] Resolving artifacts
[resolver:resolve] Resolving artifacts

write-poms:

validate-build-conf:

init:

maven-ant-tasks-localrepo:

maven-ant-tasks-download:

_resolver_download:

resolver-init:

maven-ant-tasks-init:

maven-declare-dependencies:

_write-poms:

resolver-retrieve-build:
[resolver:resolve] The POM for org.perfkit.sjk.parsers:sjk-jfr5:jar:0.5 is 
invalid, transitive dependencies (if any) will not be available: 2 problems 
were encountered while building the effective model for 
org.perfkit.sjk.parsers:sjk-jfr5:0.5
[resolver:resolve] [ERROR] 'dependencies.dependency.systemPath' for 
com.jrockit.mc:com.jrockit.mc.common:jar must specify an absolute path but is 
${jmc5.path}/plugins/com.jrockit.mc.common_${jmc5.version}.jar @
[resolver:resolve] [ERROR] 'dependencies.dependency.systemPath' for 
com.jrockit.mc:com.jrockit.mc.flightrecorder:jar must specify an absolute path 
but is ${jmc5.path}/plugins/com.jrockit.mc.flightrecorder_${jmc5.version}.jar @
[resolver:resolve] The POM for org.perfkit.sjk.parsers:sjk-jfr6:jar:0.7 is 
invalid, transitive dependencies (if any) will not be available: 2 problems 
were encountered while building the effective model for 
org.perfkit.sjk.parsers:sjk-jfr6:0.7
[resolver:resolve] [ERROR] 'dependencies.dependency.systemPath' for 
com.oracle.jmc:com.oracle.jmc.common:jar must specify an absolute path but is 
${jmc6.path}/plugins/com.oracle.jmc.common_${jmc6.version}.jar @
[resolver:resolve] [ERROR] 'dependencies.dependency.systemPath' for 
com.oracle.jmc:com.oracle.jmc.flightrecorder:jar must specify an absolute path 
but is ${jmc6.path}/plugins/com.oracle.jmc.flightrecorder_${jmc6.version}.jar @
[resolver:resolve] The POM for org.perfkit.sjk.parsers:sjk-nps:jar:0.5 is 
invalid, transitive dependencies (if any) will not be available: 3 problems 
were encountered while building the effective model for 
org.perfkit.sjk.parsers:sjk-nps:0.5
[resolver:resolve] [ERROR] 'dependencies.dependency.systemPath' for 
jdk.org.netbeans:profiler:jar must specify an absolute path but is 
${visualvm.path}/profiler/modules/org-netbeans-modules-profiler.jar @
[resolver:resolve] [ERROR] 'dependencies.dependency.systemPath' for 
jdk.org.netbeans:lib-profiler:jar must specify an absolute path but is 
${visualvm.path}/profiler/modules/org-netbeans-lib-profiler.jar @
[resolver:resolve] [ERROR] 'dependencies.dependency.systemPath' for 
jdk.org.netbeans:lib-profiler-common:jar must specify a

Re: Local build failure

[Manish G]

I have no local changes.

[image: image.png]

I am following this

.
After cloning the repo, when I run 'ant generate-idea-files', I see this:

[image: image.png]

So I do: set CASSANDRA_USE_JDK11=true, and rerun 'ant generate-idea-files',
and how I see error:

[image: image.png]



On Wed, Jun 2, 2021 at 3:14 PM Mick Semb Wever  wrote:

> > I tried both 'ant realclean' and ''git clean -xdff' before running the
> > 'ant' command, but still build fails.
>
>
> Manish, the failure should list (some of) the offending files (instead
> of `${rat.failed.files}`).
> What are the offending files listed in build/rat.txt ?
>
> Are you by chance working on a patch, and have added new files which
> don't have the correct license headers?
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
>
>

Re: Local build failure

[Manish G]

Yes its trunk.

I tried both 'ant realclean' and ''git clean -xdff' before running the
'ant' command, but still build fails.


On Wed, Jun 2, 2021 at 11:21 AM Berenguer Blasi 
wrote:

> Is that on 'trunk'? I just tested and it works for me. Try 'ant
> realclean' before building or 'git clean -xdff' to make sure all is
> really clean before building.
>
> On 2/6/21 6:42, Manish G wrote:
> > Hi,
> >
> > I am trying to build the repo(https://github.com/apache/cassandra)
> locally,
> > and I get following issue:
> >
> >
> > *BUILD FAILED\cassandra\.build\build-rat.xml:79: Some files have
> > missing or incorrect license information. Check RAT report in
> > \cassandra/build/rat.txt for more details! \n ${rat.failed.files}*
> >
> > Do I need to do some pre-configuration here?
> >
> > Manish
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
>
>

Local build failure

[Manish G]

Hi,

I am trying to build the repo(https://github.com/apache/cassandra) locally,
and I get following issue:


*BUILD FAILED\cassandra\.build\build-rat.xml:79: Some files have
missing or incorrect license information. Check RAT report in
\cassandra/build/rat.txt for more details! \n ${rat.failed.files}*

Do I need to do some pre-configuration here?

Manish

Query

[Manish G]

Hi All,

Is there any documentation someone new can look into in terms of
understanding cassandra code base?

Manish

Re: [DISCUSSION] Attracting new contributors

[Manish G]

Is it possible if a new comer works together with a mentor on an issue?
This way mentor can gradually introduce the newcomer into the codebase, and
newcomer would get timely feedback too.


On Wed, Apr 28, 2021 at 2:51 PM Benedict Elliott Smith 
wrote:

> > I believe that it can be a virtuous circle where we produce new
> committers that help mentoring newcomers.
>
> That's the dream, and kudos for keeping it alive! I have become jaded
> about this possibility, after years of trying.
>
>
> On 28/04/2021, 10:18, "Benjamin Lerer"  wrote:
>
> >
> > I think there are two main hurdles, one is restoring contributor
> interest
> > in mentoring, and the other is finding newcomers that actually want
> to
> > stick around.
>
>
> I am interested in mentoring new committers to help the project grow
> and
> some of the new committers expressed the same interest to me. I believe
> that it can be a virtuous circle where we produce new committers that
> help
> mentoring newcomers.
>
> What we need is to be well organized and make sure that we have a
> reasonable response time to newcomers.
>
> Berenguer created this board to help to track newcomers contributions:
>
> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=463=2088
> Apparently Brandon is cheating to appear as a newcomer but we will
> solve
> that. He should be at the Nightmare level  ;-)
>
> Le mer. 28 avr. 2021 à 10:54, Benedict Elliott Smith <
> bened...@apache.org>
> a écrit :
>
> > I think there are two main hurdles, one is restoring contributor
> interest
> > in mentoring, and the other is finding newcomers that actually want
> to
> > stick around. These are perhaps two sides of the same coin, though.
> An ugly
> > truth is that it isn't very enjoyable or rewarding to help newcomers
> when
> > they mostly don't stick around - often even to complete their first
> patch!
> > The patches are mostly uninteresting, the work often done to a low
> > standard, and it is easy to underestimate the amount of time
> involved in
> > every such failed interaction.
> >
> > I think making it easier to contribute and demonstrate a lasting
> interest
> > in the project without the hand holding of long term contributors may
> > benefit both sides of the equation, as it is more rewarding to help
> > somebody who's demonstrated a persistent interest in the community.
> >
> >
> > On 28/04/2021, 03:24, "Paulo Motta" 
> wrote:
> >
> > > There is no great hurdle in finding something to work on, it's
> > solely finding
> > someone with the knowledge that can help you work on something
> and
> > progress
> > it to commit.
> >
> > I agree the primary challenge is to engage existing contributors
> to
> > mentor
> > newcomers, but this doesn’t preclude having good documentation
> and a
> > well
> > maintained task pool to allow newcomers to self-serve as much as
> > possible
> > and reduce the mentoring burden, so these efforts are
> complimentary.
> >
> > For instance, a few students were interested in picking random
> tasks to
> > work on in preparation for Google Summer of Code, but it was not
> > straightforward for them to find a task to work on because we
> don’t
> > consistently label tickets as “Low Hanging Fruit” and the ones
> that are
> > tagged sometimes don’t have meaningful descriptions making it
> hard for
> > these students to get started on tasks without unnecessarily
> taking
> > some
> > time from the mentor (which could have been saved if the tasks
> were
> > properly described and labeled in the first place).
> >
> > On Tue, 27 Apr 2021 at 22:24 Kane Wilson  wrote:
> >
> > > The main problem, as has always been, is that the big players
> have a
> > > stranglehold on all the committer resources, and bringing in
> new
> > > contributors is not high on their priorities. All that's really
> > required
> > > here is that existing committers are directed to spend some
> > non-negligible
> > > portion of their time assisting non-committers (especially
> those not
> > > already employed in their own organisation). That should
> really be a
> > > starting point, as any other measures you take will not help
> until
> > the time
> > > is allocated so people can actually receive feedback and help
> from
> > the
> > > small pool of knowledge available.
> > >
> > > There is no great hurdle in finding something to work on, it's
> solely
> > > finding someone with the knowledge that can help you work on
> > something and
> > > progress it to commit.
> > >
> > >
> > > > Run a committer incubator program: Take applications for a
> 

Re: [DISCUSSION] Attracting new contributors

[Manish G]

Contributor bootcamps can really help new people like me.

On Tue, Apr 27, 2021, 5:08 PM Jeremy Hanna 
wrote:

> One thing we've done in the past is contributor bootcamps along with the
> the new contributor guide and the LHF complexity tickets.  Unfortunately, I
> don't know that the contributor bootcamps were ever recorded.
> Presentations were done to introduce people to the codebase generally (I
> think Gary did this at one point) as well as specific parts of the
> codebase, such as compaction.  What if we broke up the codebase into
> categories and people could volunteer to do a short introduction to that
> part of the codebase in the form of a video screenshare.  I don't think
> this would take the place of mentoring someone, but if we had introductions
> to different parts of the codebase, I think it would lower the bar for
> interested contributors and scale the existing group more easily.  Besides
> the codebase itself, we could also introduce things like CI practices or
> testing or documentation.
>
> > On Apr 24, 2021, at 12:49 AM, Benjamin Lerer  wrote:
> >
> > Hi Everybody,The Apache Cassandra project always had some issues to
> > attract and retain new contributors. I think it would be great to change
> > this.According to the "How to Attract New Contributors" blog post (
> > https://www.redhat.com/en/blog/how-attract-new-contributors) having a
> good
> > onboarding process is a critical part. How to contribute should be
> obvious
> > and contributing should be as easy as possible for all the different
> types
> > of contributions: code, documentation, web-site or help with our CI
> > infrastructure.I would love to hear about your ideas on how we can
> improve
> > things.If you are new in the community, do not hesitate to share your
> > experience and your suggestions on what we can do to make it easier for
> you
> > to contribute.
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
>
>

Re: [DISCUSS] Documentation donation

[Manish G]

I would like to contribute here.
Please let me know.

Manish

On Fri, Apr 24, 2020 at 9:03 PM Deepak Vohra  wrote:
>
>
> While the DataStax documentation could supplement the Apache Cassandra 
> documentation, DataStax is a commercial product based on open source Apache 
> Cassandra with enhancements made to the  open source Cassandra. Moreover, 
> DataStax documentation requires to be maintained and updated and as it is the 
> documentation has not been updated to version 4.0.
> thanks,DeepakOn Friday, April 24, 2020, 03:11:26 p.m. UTC, Joshua 
> McKenzie  wrote:
>
>  All,
>
> A few of us have the opportunity to offer a large portion of documentation
> to the apache foundation and specifically the Apache Cassandra project as
> well as dedicate a good portion of time to maintaining this going forward.
> For those of you familiar, this is the DataStax sponsored / authored
> Cassandra documentation people often refer to in the community. Links can
> be found here
> .
>
> I've spoken with some of the doc writers and there's going to be
> significant work involved to go from the doc writing system these are
> authored in to Sphinx, or some other doc authoring system if we as a
> project decide to switch things. I know Jon Haddad has some opinions here
> and I think that'd be a great conversation to have on this thread for those
> interested. A couple of people in the near future are going to have the
> opportunity to continue working on these docs full-time in the in-tree
> docs, so maintenance going forward should represent little disruption to
> the project's workings day-to-day.
>
> Looking for feedback on:
>
>   1.
>
>   Are there any questions or concerns about this donation?
>   2.
>
>   Any thoughts on documentation system to use long-term, since a donation
>   of this size would be a reasonable time to consider switching to something
>   more preferable (not advocating for the system these current docs are in to
>   be clear - poking Haddad to speak up since he has a strong PoV here ;) )
>   3.
>
>   What are next steps?
>
>
> I'm genuinely excited about this; here's to hoping everyone else is too!
>
>
> ~Josh
>

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

Re: 20200407 4.0 Status Update

[Manish G]

Hi,

Can there be a filter like 'good first issue' which new people can use to
find issues to start with?

Manish

On Tue, Apr 7, 2020 at 10:44 PM Jordan West  wrote:

> Hi Everyone,
>
> The board can be found here:
> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355
>
> [Tickets That Need Attention]
> A reminder that Josh has added a new 'Needs Attention' filter to show any
> tasks that are stalled, need an assignee or need a reviewer. Makes it easy
> if you would like to find something to work on that helps push us closer to
> 4.0.0's release.
>
> Needs Attention:
>
> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355=1719
>
> [Alpha Status]
> We continue to have no tickets that need assignees in alpha. Of the
> remaining tickets in alpha, 8 have a reviewer / reviews are in progress, 3
> are in need of reviewers, 3 are in progress, and 3 are not started or
> require more information (or are being worked on but haven't had ticket
> metadata updated). The tickets in need of a reviewer or are not yet started
> are a great place to help out if you are looking for something to
> contribute.
>
> Needs Reviewer:
>
> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355=1659
>
> [Stalled Tickets]
> 63 tickets are stalled (have not been updated in >14d). 6 of these are
> tagged for alpha. Of the remaining, 14 are in beta and 43 are in rc.
>
> Stalled:
>
> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355=1694
>
> [Open vs. Closed Last 7 Days & Cumulative Flow]
> We opened 14 issues in the last 7 days and closed 26 (8 of which were new).
> Most of the new tickets were test failures that were fixed in alpha. While
> the number of issues in the release continues to grow (many of which are
> flaky test failures), we continue to make more progress completing issues
> (as shown by this week's net of 12 closed tickets.
>
> Notable New Tickets:
> https://issues.apache.org/jira/browse/CASSANDRA-15690 is a critical read
> path bug that can lead to a transient incorrect response. This affects 4.0
> as well as previous versions of Cassandra including 3.11 and 3.0.x.
>
> Opened:
>
> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355=1670
> Closed:
>
> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355=1671
>
> Cumulative Flow:
>
> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355=reporting=cumulativeFlowDiagram=939=936=931=1505=1506=1514=1509=1512=1507=30
>
> Thanks for all your efforts! Also, if there is anything else you would like
> to see in these weekly updates please let us know.
>
> Jordan
>