-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
THIS IS AMAZING #1
Comments
Hi, I can try to write something to the mailing list. I haven't posted this anywhere yet since I've been meaning to document and clean up the code more, but haven't gotten around to it. I agree that it probably doesn't fit that well as a contrib, because the stumpwm side does depend on internal details that may be broken by updates. Linking from the readme is ok with me. |
Hi, Can we move this to the stumpwm organization? You'll retain commit access to the repo. David |
Hi, Yeah, that's ok with me. I haven't really done anything with this in a long time, so if someone else is interested in taking over it, that would be good as well. |
I forked this to stumpwm. If you'd rather transfer ownership to stumpwm let me know and I'll add you to the organization as a member so you can initiate the process. |
This is the most amazing thing to happen to stumpwm since stumpwm! I'm so impressed. I just played with this. I want to advertise this from the mountaintops. It is so awesome! Can you post it to stumpwm-devel? I can, but I feel it would be better coming from you.
This is such a large piece of software, I don't think it matches the current module setup for contrib. That's a "fire and forget" sort of contribution system. This seems like it may need some care to keep it current. Can we link it from the readme?
Honestly, I haven't been this excited about something stumpwm related for a very long time!
The text was updated successfully, but these errors were encountered: