We discussed about the video call on the dev list and everyone agreed to it.
I also welcome Josh in helping with the project. Like Josh and Dinesh
mentioned, let’s encourage contributions by allowing non-committers to do first
round of review as I don’t see a downside of doing this. These
This will be rambling as I’m typing on my phone while watching The Office and
I’m not going to proofread, but:
PMC votes on releases, and code policies, and trademarks, and things of that
nature. While the link suggests PMCs *can* sponsor meetings, nothing should
preclude anyone from meeting
Happy to add detail on the origin of this from my side –
At NGCC 2019 alongside ApacheCon in Las Vegas this year, I proposed the idea of
periodic public video calls and an approach toward executing on the roles of
product and release management as a community of volunteers. The thesis of the
To be clear, as it seems like I'm being very negative here, I'm really pleased
to see DataStax suddenly increase their participation, even if currently it's
limited to administrative activities. But let's try really hard to do things
in the right way.
Isn’t doing such things the way people who are not writing code become part of
a project? By offering their time to do things that benefit the project?
Why does anyone “with a formal role” need to agree that Patrick is allowed to
use his time to try and get some people together to discuss
This is also great. But it's a bit of a weird look to have two people, neither
of whom have formal roles on the project, making decisions like this without
the involvement of the community. I'm sure everyone will be supportive, but it
would help to democratise the decision-making.
On
Scott and I had a talk this week and we are starting the contributor
meetings on 1/22 as we talked about at NGCC. (Yeah that was back in
September) Stay tuned for the details and agenda in the project confluence
page.
Patrick
On Fri, Jan 10, 2020 at 3:21 PM Jeff Jirsa wrote:
> On Fri, Jan 10,
If I gave the impression I was advocating for just plopping tickets on
people as assignees that was a significant miscommunication on my part.
My mental model is to go back to the Jirsa approach of a pulsed status
update with a list of open unassigned tickets and call for volunteers on
the dev
On Fri, Jan 10, 2020 at 3:19 PM Jeff Jirsa wrote:
>
>
> On Fri, Jan 10, 2020 at 2:35 PM Benedict Elliott Smith <
> bened...@apache.org> wrote:
>
>>
>> Yes, I also miss those fortnightly (or monthly) summaries that Jeff
>> used to do. They were very useful "glue" in the community. I imagine
On Fri, Jan 10, 2020 at 2:35 PM Benedict Elliott Smith
wrote:
>
> Yes, I also miss those fortnightly (or monthly) summaries that Jeff
> used to do. They were very useful "glue" in the community. I imagine they'd
> also make writing the board report easier.
>
> +1, those were great
>
>
>
I'll
Yes, I also miss those fortnightly (or monthly) summaries that Jeff used to
do. They were very useful "glue" in the community. I imagine they'd also make
writing the board report easier.
+1, those were great
-
To
> Isn’t this the point of project management; to avoid this issue?
Is the point of project management to avoid the problems caused by project
management? That feels like a Dilbert cartoon.
To be clear, I'm simply responding to the apparent suggestion that we assign
every 4.0 ticket to
Just to be clear, I welcome Josh's help with project management.
Dinesh
> On Jan 10, 2020, at 12:53 PM, Dinesh Joshi wrote:
>
> My 2¢.
>
> We need more folks reviewing tickets and providing feedback and testing the
> submitted patches. There are many low complexity patches out there that are
> Thank you for getting this fixed, Mick! Would it be possible to provide
> CI feedback on Jira tickets?
Yes, i know that Hadoop does this.
For example
My 2¢.
We need more folks reviewing tickets and providing feedback and testing the
submitted patches. There are many low complexity patches out there that are in
need of reviews. Any help in that direction is appreciated. Even if they aren't
familiar with the part of codebase, a first review
Thank you for getting this fixed, Mick! Would it be possible to provide CI
feedback on Jira tickets?
Dinesh
> On Jan 8, 2020, at 12:34 AM, Mick Semb Wever wrote:
>
>
> I'm chuffed to say that ASF Jenkins builds for branches 2.2, 3.0, 3.11, and
> trunk, are now all working.
>
> Trunk:
I also find that assigning tickets to people when they have no bandwidth to
implement them is counterproductive.
Isn’t this the point of project management; to avoid this issue?
Lets say there are 10 blocking tickets for 4.0, and they are all on you; a
PM could help by finding others who could
> One thing I'd love to see
> again is a regular (every two weeks?) update on progress on the dev list
> (similar to what Jeff Jirsa used to send around -- it also included a call
> for reviews iirc).
Yes, I also miss those fortnightly (or monthly) summaries that Jeff used to do.
They were
> I can only speak to my experience on this and other software projects, but I
> find a lot of things slip through the cracks by virtue of not having
> ownership for various points in their pipeline or stall based on people not
> realizing things are on their plate.
I also find that assigning
Extra time contributed to the project by an experienced community member in
either developer or project management areas would be very helpful in
completing 4.0. Thanks for volunteering Josh -- and +1 on thanking Scott
for his existing efforts (and Benedict and others who worked to improve the
>
> On my 16gb quad i7 laptop dtests take 4-5 hours
Hm. This is actually faster than I'd have expected so that's a positive for
my Friday :). Makes me wonder how things would behave on one of the new
threadrippers w/PCIe-4.
And yes, I'm looking for excuses to get one of those.
On Fri, Jan 10,
I personally welcome your increased participation in any role, and more focus
on project delivery is certainly a great thing. But developer time from your
employer would probably be more impactful, as the main active contributors
right now have their own project management infrastructure, and
Hey all,
I've recently had some cycles free up I can dedicate to the open-source
project. My intuition is that I can add the most value right now by
engaging in some simple project management type work (help get assignees
and reviewers for things critical path for 4.0, help stimulate and
> We had roughly 7 jenkins slaves DS had donated languish I'm looking into
> (came up on slack yesterday morning) so hopefully we'll have some more
> resources back in the pool soon.
Thanks Josh!
Currently all the hardware is provided by Instaclustr.
Any hardware for running dtests, from
24 matches
Mail list logo
