Documentation Channel for #raku | This channel is logged | Roadmap: github.com/raku/doc/wiki
Set by [Coke] on 23 May 2022.
04:22 Kaiepi left 05:51 Kaiepi joined 07:46 sena_kun joined 10:18 sena_kun left 11:09 sena_kun joined 12:01 Kaiepi left 12:56 Nemokosch joined
|I'm going to take my rant here ironically, exactly because of the implications: the ultimate issue with getting ANYTHING Raku-related done is that no one on planet Earth feels responsible for making decisions or even just taking a stance on an issue.
|No matter all the trickery I'm doing within Raku spaces, be it IRC, Discord, GH discussions, issues under several repositories, linking them together, responding, trying to get to fixes when possible
|Even to get a banal PR merged is a matter of sheer luck
13:04 Kaiepi joined
|I don't know what it was like when all issues were essentially dumped onto jnthn but it absolutely couldn't be worse than the current situation
|Also, let's release this "we are volunteers and therefore everyone contributes as much as they can/want to" excuse for good
|Not all volunteer-driven projects are equally badly managed and Raku itself has had ups and downs from management point of view
|Nemokosch, do you mind a private conversation?
|lizmat assume a private conversation is taking place
|Nemokosch: maybe you should apply for a commit bit to Rakudo ?
|lizmat: Maybe I should apply for something, you are right. I'm trying to help with Rakudo as well, as much as I can comprehend after more or less 2 months of looking closer - but I honestly don't think that requires the most help at the moment
|it would solve the issue of PR's not getting merged
|That was the most extreme example, the problems go way deeper than that
|Somebody pointed it out more than 2 years ago that "problem solving" was not working. Around that time, there were people to argue with that.
|Today, nobody would argue with that. Not because there couldn't be a discussion about it but because it has a much bigger proof: nobody cares about solving any sort of problems.
|not arguing with that
|I can try to sort out Rakudo content but with my qualifications, that seems more like a sure way to burnout than achieving anything visible. Also, from what I see with some of the issues I remember: a Rakudo PR can be a place where a design decision gets stuck. And then we are back to "problem solving"
|"forgiveness > permission" is wise but how far can one go? Say, somebody can decide that lazy lists don't ACCEPT any single item. What about deprecation and undeprecation of things? That's also a prevalent topic. Or infrastructure: I'm still pondering who *knows* the current state at all, let alone the possible answers themselves
|I don't know if the RSC was created with this sort of topics in mind or how feasibly operable it is wrt these topics
|I was also thinking that we might get closer to give squashathons a (re)try; I have a superficial plan that I can still refine better. Secretly I'm hoping that it could be an "excuse" for having public(-ish) meetings with multiple people regularly.
|And you know, when I have these plans... that's when it really hits me that so many people aren't even willing to dedicate 5 minutes of consistent attention to issues that could really be resolved forever
|"vote" about a language decision, pass ownership of a repo, minor things like this
16:23 sena_kun left 16:24 Nemokosch left 16:50 Kaiepi left 17:04 sena_kun joined 17:44 Kaiepi joined 17:51 Kaiepi left 18:31 Kaiepi joined 21:19 sena_kun left
|you'll get better traction with the community on community issues if you don't restricvt your conversation to the documentation channel.