budgie-do-not-disturb-status

[ianmjones]

Please confirm there isn't an existing package request

• [X] I have searched through package requests

Homepage

https://git.sr.ht/~ianmjones/budgie-do-not-disturb-status

Maintainer

• [X] Would you like to be the maintainer for this package?

Why should this be included in the repository?

Get and set Budgie Desktop's Do Not Disturb status via the CLI.

Are we allowed to redistribute it?

MIT

What kind of user will use this package, and how many users do you think will use this package?

Useful for scripting the turning on or off Budgie's Do Not Disturb setting, e.g. when starting or stopping recording a video, sharing a screen during a presentation, or any other situation where notifications might not want to be seen.

Link to source archive file

https://git.sr.ht/~ianmjones/budgie-do-not-disturb-status/archive/v1.0.1.tar.gz

[ianmjones]

@malfisya, like with https://github.com/getsolus/packages/issues/3574, please can you let me know what information is needed in order to move this request forward?

[malfisya]

I would defer the questioning to @EbonJaeger as he maintains Budgie. Cheers!

[EbonJaeger]

I'm not sure how much value-add this package would really have. It's already really easy to toggle DND from Raven. There's even a patch I can backport to toggle it by clicking on the notification panel icon with the middle mouse button. Is doing this in scripts that common of a thing? Even so, it would be one call to send-dbus in Bash.

[ianmjones]

Ever been in a situation where you or someone in a meeting, gets a notification while screen sharing that includes information that should not be shared? Or seen a streamer get such a notification?

Being able to script the disabling and re-enabling of notifications when such an activity starts or stops seems like a good idea to me.

I admit though, it is very much a "does one thing well" tool to avoid a rare (but potentially embarrassing) problem, on a niche of a niche setup.

it would be one call to send-dbus in Bash

I do think running budgie-do-not-disturb-status off is probably a lot easier for someone to handle adding to a script than whatever the long cryptic dbus-send command is, and working out what the address, object path and message format are that works and is escaped properly.

But yeah, I may very well be the only Solus user of the package, so I'd fully understand if you'd prefer to reject and close this package request given its likely very low usage.

[TraceyC77]

@EbonJaeger , what are your current thoughts on this? I see the value of being able to script the DNS setting. I defer to you as our lead Budgie maintainer.

[ianmjones]

I'm closing this packaging request as I'm pretty sure I'd be the only user of the package, at least for a good while, if not forever.

If in the future it turns out a few people end up finding Budgie DO Not Disturb Status useful and want it packaged, then I guess they could could open a request and gather some votes.