• 5 Posts
  • 245 Comments
Joined 1 year ago
cake
Cake day: October 9th, 2023

help-circle






  • Cosmic-comp is my second favorite after hyprland so far due to their tiling being quite well thought-out. The problem is, it’s part of a DE and is somewhat cumbersome to configure as a standalone compositor (can be fixed by patching libcosmic, tho), and also it’s quite bare-bones when it comes to features.

    Then there’s pinnacle which looks promising, but I haven’t yet tried to daily-drive it.

    Also, maybe qtile, which has a Wayland back-end.











  • I’m not sure you can classify this as a failure, as explicitly prohibiting interfacing with non-agpl stuff would greatly limit the amount of stuff you can license under it, perhaps up to the point of making it generally unusable. As for “not like that”… Well, yeah. But you can’t deny it’s misleading, right? Free software kinda implies you can modify it whatever you want, and if it’s a free ui relying on a source-available middleware… Turns out, not so much.

    Although, a posdible solution would be require explicitly mentioning if you’re basically a front-end for something; but I’m not sure if it can be legally distinguished from the rest of use-cases.




  • Thanks for sharing your concerns here. We have been progressing use of our SDK in more use cases for our clients. However, our goal is to make sure that the SDK is used in a way that maintains GPL compatibility.

    • the SDK and the client are two separate programs
    • code for each program is in separate repositories
    • the fact that the two programs communicate using standard protocols does not mean they are one program for purposes of GPLv3

    Being able to build the app as you are trying to do here is an issue we plan to resolve and is merely a bug.

    I.e. “fuck you and your foss”