Project name (System76 vs. Pop) about system76-scheduler HOT 9 CLOSED

Not in particular, besides being developed by System76 and not specific to Pop.

from system76-scheduler.

Does this need to be used with pop-os/shell in order for proper identification of foreground processes and their sub-processes?

Yes, pop-shell is what would tell this daemon what's focused at any given time. Without pop-shell (or something else reporting the focused window via the dbus interface), this daemon would only be able to apply priorities set in the configuration files.

from system76-scheduler.

I was just thinking about it from the perspective of e.g. power-profiles-daemon claiming system76-power could have been used as its base "if it was more of an upstream project instead of a PopOS!/System76 project," which, considering the license of system76-power, doesn't make a lot of sense unless they're referring to the name.

I suppose pop-scheduler would still imply a tie to Pop!_OS, which is (at least partially) why the new desktop environment components are being branded as cosmic-*, so other distros can package COSMIC without feeling like they're packaging Pop!_OS. It just seemed to me that the scheduler is a feature of Pop!_OS and that Pop!_OS is still less specific/would apply to more users of the project than System76. (And we've seen some acceptance of other distros packaging Pop components with pop-shell, whereas I'm not aware of any System76-branded components being officially packaged by other distros yet.)

We can probably close this if nobody else has strong feelings about it, although I like the idea of the shorter names too.

from system76-scheduler.

So yeah, makes even more sense (to me) that the naming is not specific to PopOS

The full functionality of this daemon is available in any compositor/desktop-environment that calls appropriate DBus SetForeground method as appropriate

I think you're missing my point that the scheduler daemon is even less specific to System76. The scheduler daemon is preinstalled on all computers with Pop!_OS. On the other hand, if you install any other Linux distribution on a System76 computer, you will not have the scheduler daemon preinstalled.

The pop-launcher backend can be used with any frontend that calls its JSON IPC interface, it doesn't have to be used with pop-shell as the frontend, but it's not called system76-launcher. It's called pop-launcher because it's developed as part of Pop!_OS and has first-party integration with pop-shell.

from system76-scheduler.

We could change the name to something more unique, such as Scheduler76 or PopProc.

from system76-scheduler.

The README includes this:

Processes are regularly sweeped and assigned process priorities based on configuration files. When combined with pop-shell, foreground processes and their sub-processes will be given higher process priority.

These two sentences connect in my brain in a confusing way, haha

Does this need to be used with pop-os/shell in order for proper identification of foreground processes and their sub-processes?

Or does this functionality work regardless? Or is there some automatic benefit gained by using pop-os/shell that can be filled in with manual configuration in other environments?

from system76-scheduler.

Ah, awesome

So yeah, makes even more sense (to me) that the naming is not specific to PopOS

The full functionality of this daemon is available in any compositor/desktop-environment that calls appropriate DBus SetForeground method as appropriate

from system76-scheduler.

So cosmic-scheduler / cosmic-launcher might be a better fit?

from system76-scheduler.

I kind of like scheduler76, but cosmic-scheduler is probably more likely to get relevant results via a search engine query? (EDIT: Actually pop-scheduler and cosmic-scheduler produced results from other domains that would need some extra keywords, while system76-scheduler is already producing top ranking results, meanwhile scheduler76 top result is "Maximo Scheduler 7.6"). If search results matter at all, that might be worth pointing out.

I use Plasma, and have no experience with these projects or System76 hardware (I am aware of the company, and roughly what they offer in hardware and software though). At first it sounded like it's only meant as a scheduler associated to the project name from each suggestion. system76-scheduler seems most appropriate (system76 probably ranks well as a keyword related to linux more than pop or cosmic, if that matters at all).

It sounds like other shells could adopt support for it in future, and having pop/cosmic when not using anything else from those projects might seem more out of place than system76? (doesn't bother me either way)

from system76-scheduler.