We're putting together some grant applications, and are wondering what skills and availability exist in our wider community π§βπβ¨
-
We're putting together some grant applications, and are wondering what skills and availability exist in our wider community π§β
We're particularly looking for people who can do feature work and technical management around things like GNOME, Flatpak, systemd, Freedesktop, Pipewire, ModemManager, etc.
Contact us if you think you'd be a good fit, either DM or email hi@modal.cx
-
We're putting together some grant applications, and are wondering what skills and availability exist in our wider community π§β
We're particularly looking for people who can do feature work and technical management around things like GNOME, Flatpak, systemd, Freedesktop, Pipewire, ModemManager, etc.
Contact us if you think you'd be a good fit, either DM or email hi@modal.cx
-
We're putting together some grant applications, and are wondering what skills and availability exist in our wider community π§β
We're particularly looking for people who can do feature work and technical management around things like GNOME, Flatpak, systemd, Freedesktop, Pipewire, ModemManager, etc.
Contact us if you think you'd be a good fit, either DM or email hi@modal.cx
@modal the Unix philosophy is about mixing-and-matching components. The combination "GNOME, Flatpak, systemd, Freedesktop, Pipewire, ModemManager, etc." imho violates that idea. It's monoculture. It would be well invested time to make sure that none of these components have subtle dependencies on each other/unduly favor each other.
-
@modal the Unix philosophy is about mixing-and-matching components. The combination "GNOME, Flatpak, systemd, Freedesktop, Pipewire, ModemManager, etc." imho violates that idea. It's monoculture. It would be well invested time to make sure that none of these components have subtle dependencies on each other/unduly favor each other.
@modal In other words, make sure to run a non-Gtk desktop environment for a while, run BSD for a while (not Linux), run another init system for a while (not systemd) , run XLibre (not Wayland) for a while, and so on. Everything needs to work with everything. Make sure things work well. Otherwise it is Red Hat centric spaghetti architecture.
-
@modal In other words, make sure to run a non-Gtk desktop environment for a while, run BSD for a while (not Linux), run another init system for a while (not systemd) , run XLibre (not Wayland) for a while, and so on. Everything needs to work with everything. Make sure things work well. Otherwise it is Red Hat centric spaghetti architecture.
@probono we only have a limited amount of energy and resources. If we spend of all of our effort chasing a massive amount of combinations of everything then we have not really moved in a direction that brings real benefits for the user. We are deeply admiring of the Unix philosophy and we appreciate your input and enthusiasm, but we will likely take a more focused approach.
-
@modal In other words, make sure to run a non-Gtk desktop environment for a while, run BSD for a while (not Linux), run another init system for a while (not systemd) , run XLibre (not Wayland) for a while, and so on. Everything needs to work with everything. Make sure things work well. Otherwise it is Red Hat centric spaghetti architecture.
