#linuxcnc-devel Logs

Sep 28 2024

12:26 AM pere: rigid: did you consider that others might be right and you might be wrong?
01:35 AM pere: your loss, I guess.
01:36 AM rigid: pere: and when I see folks complaining about lack of free time for the project but still arguing about a fix that doesn't even take a minute, it's telling that time isn't the issue but attitude. I'm not sure if this awareness exists among linuxcnc developers and thus i'm commenting.
01:36 AM rigid: well, a loss for the FOSS world overall. i'm fine CNC wise. :)
01:38 AM pere: I doubt someone alienating developers will affect the free software world much.
01:41 AM rigid: pere: right? and also users. there are tons of contribution requests like this that get blocked for mere attitude/policy and no rational reasons at all. with endless discussions instead of just agreeing on how to best do the fix. this usually goes nowhere.
01:43 AM pere: I guess the attitude I mostly react to here is the 'them versus us' framing.
01:45 AM rigid: i think you're making assumptions then. there's no "them" in here. This is a developer channel.
01:47 AM rigid: pere: what you react to might be frustration about this recurring situation I personally experienced when trying to make linuxcnc enforce it's own - decade old - style guide, but ppl instead rather wound up in discussions
01:48 AM rigid: *my frustration
01:48 AM pere: The statement "you guys are hillarious" clearly express to me that you separate yourself from other developers, which is the separation I talk about.
01:49 AM pere: and sure, I understand there is frustration underlying this.
01:49 AM rigid: ah ok, yeah you're right. I'm strictly adressing the ones with github access and taking part or not speaking up against
01:50 AM rigid: i'm don't have write access so i'm not considering myself a developer. just commenting (non-publicly in IRC instead of the mailinglist)
01:50 AM pere: I doubt you would get the urge to help me if I expressed 'you are hillarious' based on what I suspect you believe are valuable contributions.
01:51 AM rigid: oh, there seems to be a misconception about me seeking help. I couldn't care less about this not getting fixed.
01:51 AM pere: "assume good faith" is generally a good strategy.
01:52 AM rigid: linuxcnc is needing help as a project and i'm not the one frustrating bug-reporters and other contributors over and over again.
01:53 AM rigid: anyway, gotta run. ttyl
01:53 AM pere: so you are part of the solution?
01:53 AM rigid: pere: check my PRs if you're really interested
01:53 AM pere: have fun. :)
01:53 AM rigid: tnx :)
01:54 AM pere: I have no idea which are your PRs. At the moment my limited linuxcnc time is spent on keeping the linuxcnc-weblate sync going.
01:54 AM pere: and some times responding to irc.:)
04:57 AM -!- #linuxcnc-devel mode set to +v by ChanServ
06:31 AM rmu: what on irc is "non-public"?
07:00 AM pere: I guess it depend on what you mean by public. unencrypted and shared across the internet is quite public, while private messages can be seen as less public, despite it being unencrypted and shared across the internett too.
07:10 AM rmu: I don't see much difference between linuxcnc-devel@ mailinglist and #linuxcnc-devel regarding "publicness"
07:10 AM rmu: but just MHO.
07:43 AM pere: I assume you are refering to something I have not noticed. Both are public to me, but one is more transient than the other.
08:19 AM rmu: just rigd's comment that he commented non-publicly in IRC seemed strange
08:19 AM rmu: nevermind. waste of time.
08:44 AM pere: indeed. probably better spent improving linuxcnc, evauluating github patches and handling user feedback. :)
08:57 AM lcnc-relay: <knoxmachining#0> That was fun to watch. Ahh the drama. 🙂
09:02 AM Tom_L: i'd rather watch 2 pages of bot build failures
09:49 AM lcnc-relay_ is now known as lcnc-relay
10:11 AM carsten: Hi
10:46 AM JT-Woodshop is now known as JT-Autoshop
11:23 AM -!- #linuxcnc-devel mode set to +v by ChanServ
11:31 AM carsten__: I want to prepare a small pull request for issue #3135 to get used to the process. I am here due to
11:31 AM carsten__: 7.3. Commit to the proper branch
11:31 AM carsten__: Bugfixes should go on the oldest applicable branch. New features should go in the master branch. If you’re not sure where a change belongs, ask on irc or on the mailing list.
11:34 AM Tom_L: be patient, sometimes slow to respond here
12:18 PM carsten__: ok
12:22 PM pere: carsten__: what is the question, really? If the problem is in 2.9, fix it for 2.9. If it is in 2.8, fix it for 2.8. And if it is in master, fix it for master. Would be nice if you could also test the other versions, but it is not a requirement for providing a patch. As for #3135, I do not know the subsystem and have nothing sensible to say about it.
12:30 PM carsten__: I don't know how to find the "oldest applicable branch".
12:33 PM pere: carsten__: which branch did you exprience the problem on, how did you get to this branch? relevant branches are 2.8, 2.9 and master, as far as I know.
12:35 PM rmu: I would not touch anything non-critical in 2.8
12:36 PM pere: me neiter, but do not know if this is critical or present in 2.8. :)
01:09 PM Unterhaus__ is now known as Unterhausen
02:51 PM carsten: ok, i create a pull request for master.
05:25 PM linuxcnc-build2: Build [#2768](http://buildbot2.highlab.com/buildbot/#builders/7/builds/2768) of `10-rip.debian-11-bullseye-rtpreempt-amd64` 8completed with warnings.
06:15 PM linuxcnc-build2: Build [#2893](http://buildbot2.highlab.com/buildbot/#builders/13/builds/2893) of `00-checkin` 3completed successfully.
06:48 PM Unterhaus_ is now known as Unterhausen