Hi folks,
I'm familiar with the codebase and can help with the maintenance and
evolution.
I already have some additional profiles that I can push there which were
never merged in the main branch of tlp-cluster.
I love this tool (I know I'm biased) and hope it gets the attention it
deserves.
Le
I would likely commit to it as well
Jordan
On Mon, Apr 29, 2024 at 10:55 David Capwell wrote:
> So: besides Jon, who in the community expects/desires to maintain this
> going forward?
>
>
> I have been maintaining a fork for years, so don’t mind helping maintain
> this project.
>
> On Apr 28,
> So: besides Jon, who in the community expects/desires to maintain this going
> forward?
I have been maintaining a fork for years, so don’t mind helping maintain this
project.
> On Apr 28, 2024, at 4:08 AM, Mick Semb Wever wrote:
>
>> A separate subproject like dtest and the Java driver
>
> A separate subproject like dtest and the Java driver would maybe help
> address concerns with introducing a gradle build system and Kotlin.
>
Nit, dtest is a separate repository, not a subproject. The Java driver is
one repository to be in the Drivers subproject. Esoteric maybe, but ASF
The current cassandra-stress is in poor condition and clocks in at a hefty
16k lines of Java code. I was involved in some work with it last Summer
(CASSANDRA-18529) and it was tricky.
I'm strongly in favor of replacing it with a modern tool which is easier to
configure and more user friendly.
@mck I haven't done anything with IP clearance. Not sure how to, and I
want to get a feel for if we even want it in the project before I invest
time in. Jeff's question about people willing to maintain the project is a
good one and if people aren't willing to maintain it with me, it's only
going
On Fri, 26 Apr 2024 at 00:11, Jon Haddad wrote:
> I should probably have noted - since TLP is no more, I renamed tlp-stress
> to easy-cass-stress around half a year ago when I took it over again.
>
Do we have the IP cleared for donation ?
At what SHA did you take and rename tlp-stress, and who
I do have some familiarity w/ the codebase, and I could help support it in a minor capacity. (Reviews, small fixes, etc.) Probably not something I could spend hours on every week.On Apr 25, 2024, at 5:11 PM, Jon Haddad wrote:I should probably have noted - since TLP is no more, I renamed
I should probably have noted - since TLP is no more, I renamed tlp-stress
to easy-cass-stress around half a year ago when I took it over again.
Jon
On Thu, Apr 25, 2024 at 3:05 PM Jeff Jirsa wrote:
> Unless there’s 2-3 other people who expect to keep working on it, I don’t
> see how we justify
Unless there’s 2-3 other people who expect to keep working on it, I don’t see how we justify creating a subprojectAnd if there’s not 2-3 people expressing interest, even pulling it into the main project seems riskySo: besides Jon, who in the community expects/desires to maintain this going
I am not familiar with ECS but if we’re going to go for it I would prefer
it to be a sub project really. Jon, what do you think?
On Thu, Apr 25, 2024 at 2:44 PM Brandon Williams wrote:
> I want to begin by saying I am generally +1 on this because I have
> become a fan of easy-cass-stress after
Yeah, I agree with your concerns. I very firmly prefer a separate
subproject. I've got zero interest in moving from a modern Gradle project
to an ant based one. It would be a lot of work for not much benefit.
If we wanted to replace cassandra-stress, I'd say bring in the release
artifact as
I want to begin by saying I am generally +1 on this because I have
become a fan of easy-cass-stress after using it, but I am curious if
this is intended to be a subproject, or replace cassandra-stress? If
the latter, we are going to have to reconcile the build systems
somehow. I don't really
I've been asked by quite a few people, both in person and in JIRA [1] about
contributing easy-cass-stress [2] to the project. I've been happy to
maintain the project myself over the years but given its widespread use I
think it makes sense to make it more widely available and under the
project's
14 matches
Mail list logo
