Maintainership status for Workspacer up ahead #485
Replies: 8 comments
-
Same here.
And if I ever use Windows, I've switched to using komorebi as my tiling wm of choice. I've been maintaining its application rules for the past year, so it should be quite apparent that I've moved away from using workspacer 😅 |
Beta Was this translation helpful? Give feedback.
-
IMO Workspacer has been good enough for a while, in fact, I haven't updated it since last year, which means this is already mature, usable, and feature complete. Great work everyone! |
Beta Was this translation helpful? Give feedback.
-
I'm unfortunately not versed enough with the language and libraries to be
able to take over such a project. Thanks for dedicating so much of your
time and expertise Jostein. I remain nearby if ever there is anything I can
do. In the meantime, I wish you the best of luck with your future projects.
…On Fri, Sep 22, 2023 at 8:16 AM Mateo ***@***.***> wrote:
IMO Workspacer has been good enough for a while, in fact, I haven't
updated it since last year, which means this is already mature, usable, and
feature complete. Great work everyone!
—
Reply to this email directly, view it on GitHub
<#485 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACFLDZRQEOTYHCN6FBEX3DTX3WFTDANCNFSM6AAAAAA5DALLH4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
@josteink first, a massive thank you for managing this project. Workspacer would probably have died an early death had you not reached out and offered to help maintain it. I can't thank you enough; truly a great example of open source magic. I'm in a similar boat with workspacer, in that I don't use it day-to-day any more and as such find it hard to dedicate time to maintaining this, and am also probably not the best steward of the project as a non-user. If someone who is interested in helping review PRs/issues wants to reach out, please feel free, especially if you are already/have contributed to the project or participated in discussions. In the mean time, @josteink don't feel obligated to do anything more than you wish to, Workspacer is in a good state as far as I can tell, and short of Windows breaking changes to explorer/dwm in the future, I imagine it will behave in the medium/long term. I think that it is probably a good idea to put some kind of notice/warning on the README that indicates that workspacer is 1. not actively being maintained and 2. looking for a maintainer (although probably with a bit of a disclaimer, In the mean time, I'll pin this issue to give it some more visibility. Thanks again to everyone who has contributed to workspacer, I want to give a shout out to the many people who've contributed code, experience, or feedback:
|
Beta Was this translation helpful? Give feedback.
-
I would like to offer my services in vetting new PRs from any new maintainers as it would be an absolute shame if anything malicious made it into the codebase. |
Beta Was this translation helpful? Give feedback.
-
A massive thank you to @rickbutton for creating Workspacer and to @josteink for shepherding it for the past few years. I haven't been using Workspacer for a while, as I've been working on a new window manager which is very much inspired by Workspacer, but tries to extend it past some of the limitations I've encountered with it. Consequently, I felt it may not be entirely appropriate for me to actively maintain Workspacer. In terms of ongoing support, I agree with @rickbutton that putting a warning on the README is probably best. If the project isn't archived, I'd be open to keeping an eye on any severe issues that come up, but I wouldn't actively work on it. A big thanks again to everyone who has contributed to Workspacer over the years. It's been a great project to work on and I've learned a lot from it. |
Beta Was this translation helpful? Give feedback.
-
Thanks a lot for @rickbutton and @josteink for maintaining the project over the past years. Sadly I'm in the same boat as most of the other people, as I've not been using Windows much. Thanks a lot to everyone else who has been contributing to workspacer as well, and good luck with whatever projects you decide to pick up in the future. |
Beta Was this translation helpful? Give feedback.
-
I think the project is already mature enough. I previously tried almost all other TWMs made for windows (komorebi, bug.n, etc.) but none of them was solid enough. Note that most of them were ahk based, which is not good enough base for tiling window manager IMO. Anyway, I personally wrote small code to put cursor in the center of the newly focused window.
|
Beta Was this translation helpful? Give feedback.
-
Hey everyone.
A quick, dramatic 3-point executive summary:
More in depth...
I haven't really used Windows as my "main" OS in a few years now, and it's not about to change. That means I don't currently need (nor have needed) Workspacer for anything for quite a while.
That makes me a pretty bad candidate for being "the" maintainer.
I've stuck around as a maintainer none the less, because approving easy patches is not that much work... But I think the time has come for me to step down, as I really don't have any investment in this project anymore.
Right now, I don't see much activity from anyone at all. I don't know if that's because you've left for different projects, or because Workspacer currently covers all your needs well enough.
Do you think you can take a more active role? Do you depend on this software and would be sad to see it left to (bit)rot? Or have you left entirely?
What's the status of you guys out there? And what should be the status of the workspacer project from now on?
Any feedback appreciated.
CC: @rickbutton @Aareon @dalyIsaac @wiredmatt @N1x0 @sitiom @tlsomers
Beta Was this translation helpful? Give feedback.
All reactions