There's this one house in Ulverstone, Tasmania that's had a Linux sign out the front for years. No context. Just chilling in the front yard. I have no idea why.
@Gargron I think the other advantage is that you have to make a schema of some type, and that would give new admins some guidance and ideas on what to limit or ban on their servers.
Also, the fact that they could be translated would probably help in some situations.
Of course, you'll always need an "other" for extra stuff.
Tried installing my Steam games on a microsd card, and it didn't work. Reformed ext4 and then it did. Turns out that Steam needs to be able to create symbolic links.
@popey@milan certainty when you consider the entire product there is more to consider than just the license. But here we are just talking about the visualization of the license field. Which is a simpler discussion.
I would agree that making proprietary red isn't fair either, but the western values associated with green are 'good' and 'go', which is saying it something you should do or find positive.
@popey@milan sure, you don't have to make it red. It could be grey for instance. Or desaturated version of the GTK theme's color.
I think the value here is to give a visual signal that free software is better. You don't need to mark proprietary software as 'red' or dangerous, but you can visually promote better choices.
So 'fix' is perhaps wrong. But, I think the visualization can be improved.
@tinker I'll definitely consider it, but I'm probably going to wait and see what they actually ship.
They've made some odd choices about actually building a large part of their SW stack from scratch. Which isn't inherently bad, but it also means a lot of work, which could really delay things.
Disturbing quote to finish up this article about data: "You may forget Facebook; it could happen sooner than you expect. But it’s not likely to forget you."