ティージェーグレェ on Nostr: Thank you for the kind words of encouragement! I guess I like to keep others updated ...
Thank you for the kind words of encouragement!
I guess I like to keep others updated when I went so far as to boost grunfink's 2.67 announcement, but had stalled out on my own efforts to update the MacPorts' Portfile?
A lot of the time, I can knock that stuff out relatively quickly (it takes more effort to jump through all the GitHub BS than it does to update and diff and test locally usually) but occasionally some more tweaks are needed and it takes me longer. Thankfully, it wasn't a lot of extra effort, just more than I could devote focused time and attention to earlier today and I wanted to make sure others (however few there may be) were looped in so that they weren't wondering why I hadn't submitted a Pull Request.
No doubt, it will take even longer for that to get merged and for MacPorts users to benefit even now that I have had some additional time to get around to doing what needed to be done; but I am rather intentionally doing my best to not take on more responsibilities at the moment. Decades of ops work habits are hard to break, but maybe it's better for my sanity and collaboration?
OFC, there are times where I just kind of miss diving in, doing some tweaks and moving on without concerns about all of the formalities of Pull Requests and commit messages and all that rigamarole. ;)
I still think RANCID set forth the kind of prod/ops first, diffs later (and more automated) paradigm that I prefer, but much of the rest of the world seems really into this front loaded code check ins and CI pipelines first paradigm, even if it feels as if it is putting the cart in front of the horse to me; I am doing my best to collaborate with others' persnickety preferences as possible.
(As an aside, but sort of related, this reminded me I submitted a Pull Request to update MacPorts' signify, but since that Portfile maintainer has been AWOL for years, that PR went into "maintainer timeout" and will probably require even more formalities to address before it can or will be merged. If I were wearing my "ops hat" and had commit access, mostly likely it would have already been done a week ago and I would have moved onto other things and forgotten about it by now. Instead, I have updated the PR with a comment about "next steps" and who knows how much longer it will take to get a response to that. Feels like a snail's pace to me! But, tis the nature of that beast! ;)
Meanwhile, I have more $dayjob obligations in a little bit and will be AFK again; but I'm grateful to have had a bit of a "really long lunch breaks to destroy capitalism" respite in between this morning/afternoon's work and this evening's Christmas concert (which is a free event anyway and more done for the local community's benefit).
I hope your bday weekend has been awesome!
I guess I like to keep others updated when I went so far as to boost grunfink's 2.67 announcement, but had stalled out on my own efforts to update the MacPorts' Portfile?
A lot of the time, I can knock that stuff out relatively quickly (it takes more effort to jump through all the GitHub BS than it does to update and diff and test locally usually) but occasionally some more tweaks are needed and it takes me longer. Thankfully, it wasn't a lot of extra effort, just more than I could devote focused time and attention to earlier today and I wanted to make sure others (however few there may be) were looped in so that they weren't wondering why I hadn't submitted a Pull Request.
No doubt, it will take even longer for that to get merged and for MacPorts users to benefit even now that I have had some additional time to get around to doing what needed to be done; but I am rather intentionally doing my best to not take on more responsibilities at the moment. Decades of ops work habits are hard to break, but maybe it's better for my sanity and collaboration?
OFC, there are times where I just kind of miss diving in, doing some tweaks and moving on without concerns about all of the formalities of Pull Requests and commit messages and all that rigamarole. ;)
I still think RANCID set forth the kind of prod/ops first, diffs later (and more automated) paradigm that I prefer, but much of the rest of the world seems really into this front loaded code check ins and CI pipelines first paradigm, even if it feels as if it is putting the cart in front of the horse to me; I am doing my best to collaborate with others' persnickety preferences as possible.
(As an aside, but sort of related, this reminded me I submitted a Pull Request to update MacPorts' signify, but since that Portfile maintainer has been AWOL for years, that PR went into "maintainer timeout" and will probably require even more formalities to address before it can or will be merged. If I were wearing my "ops hat" and had commit access, mostly likely it would have already been done a week ago and I would have moved onto other things and forgotten about it by now. Instead, I have updated the PR with a comment about "next steps" and who knows how much longer it will take to get a response to that. Feels like a snail's pace to me! But, tis the nature of that beast! ;)
Meanwhile, I have more $dayjob obligations in a little bit and will be AFK again; but I'm grateful to have had a bit of a "really long lunch breaks to destroy capitalism" respite in between this morning/afternoon's work and this evening's Christmas concert (which is a free event anyway and more done for the local community's benefit).
I hope your bday weekend has been awesome!