Notices by Cassidy James :eos: :gg: :fh: (cassidy@mastodon.blaede.family)

@mattdm ha, I didn't know Fedora did this! It's not an uncommon pattern, but I think it could be tweaked to be just as useful to maintainers while being more welcoming to issue reporters.

A simple solution could be to label *untriaged* issues as stale (or better: “Needs Attention”) after some time of inactivity with a gentler comment about, “Sorry we haven't been able to triage this. If you know it’s still an issue in the latest release, feel free to comment to help us triage it.”

I get that issue trackers are hard, but I feel like stale bots that *close issues* come off as so hostile. I shouldn't have to come back to the issue tracker every month to confirm, “Yes, this is still an issue!” to prevent the issue from getting closed.

Tag an issue as “stale” for easier triage—that’s fine! But “oops you aren’t engaged enough, sorry, your issue doesn’t exist anymore” feels like a bit of a slap in the face. Especially if it gets closed as “not planned.”

I’m honored to have been appointed to the GNOME Foundation Board of Directors! This is a midterm appointment due to a vacancy; I had expressed interest in running for the board, and was graciously offered the appointment for the remainder of this term.

I’m thrilled to roll up my sleeves and get to work as a director to help operate GNOME Foundation day to day, and I look forward to the opportunity to earn Foundation members' votes when the regular term elections come up.

Time to get to work. 💪

@aardrian @fedijedi THANK YOU. I always find “a11y” shorthand ironic for accessibility. It doesn’t save *that much* time or space, it only introduces difficulty for people not in the “in group.” It is its very self an accessibility issue!

@Conan_Kudo I just don’t see where in the post I suggest we gut the essence of what GNOME is, that we give up on personality, etc. That seems like a huge stretch from what I actually wrote, which is why I questioned if you’d read it. I’m explicitly saying we should retain personality, and I think I lay out a fairly natural evolution of *what the community has already been doing* design-wise.

@Conan_Kudo did you read the blog post?

@Conan_Kudo the foot is quirky—and actively hard to work with. Rather than use a logo at all, we've repeatedly seen it just completely dropped from spaces _anyway_.

Instead, I'm proposing we come up with something better, even if whimsical and quirky, but that actually works in the contexts we need to use it.

I don’t think any of the modern GNOME design work has been “giving up the ‘personality’ of projects and communities.” In fact, quite the opposite as I feel like GNOME’s is strongest now.

Friday night? Perfect time to drop a blog post that might sound like clickbait, but that I genuinely hope can help forge a path forward while making everyone happy—or at least pissing everyone off equally (sometimes the best you can ask for!)

https://cassidyjames.com/blog/gnome-foot-logo-rebrand/

#GNOME #OpenSource #Linux #GNOMEdesign

@jorge @downey not explicitly, but a growing number of GNOME Foundation members and volunteers have been hoping we could improve the brand. The foot has a legacy but also has practical issues.

Nobody has explicitly approved getting rid of it, but also the board approved the new website design afaik; they could have said, “Looks great, but it needs the foot,” but as far as I’m aware, that didn’t happen.

@jorge @downey maybe I should just bite the bullet and propose a referendum or whatever; I’d have to look up how that all works.

The two main arguments I have heard are, “But we like the foot!” which of course, anyone will say about their baby, and “Ugh trademarks are expensive,” which, okay, fine, but also that shouldn’t mean we are stuck with something that a bunch of contributors actively dislike.

@ebassi @jorge @downey nobody snuck anything; the website was being worked on for months and was signed off on by the board.

Also, that sentiment hardly seems productive. GNOME has had three or more logos over its existence. Why is the current one (with practical, observed issues in the wild) somehow the best that ever could be? How would you feel if you thought a particular codebase was bad, but a contributor told you you could pry the current code from their cold dead hands? 🤷♂️

@ebassi I haven't heard anything about it being offensive, but I have objections to the foot:

1. I think it's ugly, but sure, that's just my opinion

2. It is hard to fit into an avatar, whether a square or circle, since it's very unbalanced

3. Anyone outside the FOSS bubble has absolutely no idea what it is, other than a weird foot—which is usually a negative

I helped design the new site and wasn't up there saying our brand is cringe. But Jakub was, and he helped design the current brand.

Something fun we’ve been doing at @EndlessOS is running learning programs where we help learners get used to actual open source collaboration—with video games!

WAIT

Not “educational games” or “gamified learning”—no, actually contributing to a real game using real open source workflows. Here are some fun results from one cohort so far; check out the Extra Levels in Everlasting Candy, an extension of the open source game Candy Wrapper:

https://endlessm.github.io/everlasting-candy/

#GodotEngine #GameDev #OpenSource

@forteller these static entries are Desktop Actions, which are a FreeDesktop spec: https://specifications.freedesktop.org/desktop-entry-spec/latest/extra-actions.html

Dynamic actions aren't currently part of the spec, but are implemented on many desktops with the Unity LauncherEntry API. I hope that support will be added to GNOME either for this API or another one, specifically because that’s something we identified as missing from the Background portal as a replacement for status icons.

Do I know any designers explicitly experienced in *brand* design who would be willing to help out an open source project? I’m working with a project that is interested in a new logo, and I’d love to connect you.

Unfortunately I don’t know that there’s a budget, so this would likely be a volunteer/pro bono effort unless we think we could crowdfund/find a sponsor to pay for the work. Still, if you’re interested, let me know in a reply, please!

#design #OpenSource #OpenSourceDesign

Local-first peer-to-peer GNOME people… if I wanted to make a GNOME app similar to those party games where you enter a code and then all join one host's game, then compete for trivia questions or something, is that relatively straightforward to do with our current tech stack? What would I use to do that?

I'm tempted to make a FOSS Kahoot-alike game in Godot, but it could be fun as a GNOME app, instead.

#GNOME #gamedev #Godot #GodotEngine

Designing for the Digital Age is a great one that is dense like a textbook but extremely comprehensive; it's what we used at Visual Logic and taught me most of my formal UX knowledge (in addition to the actual internship and excellent mentorship from the designers there).

I still have a digital copy but don't ever find myself flipping through the physical one, so I'd love someone else to be able to.

I have a bunch of physical UX/design books that I'm getting rid of; I've had them for years and honestly just never read all the way through them, as most of my experience was from a specific internship and textbook and then real world experience—and lots of blogs and ebooks rather than physical books.

Is anyone in the Denver area interested? I would rather give them to someone who is getting into UX than just donate or sell them to a generic book store.

#Denver #UXdesign #free #GiveAway

How do I help people understand that *for an indie app store,* taking only a 30% cut of each app purchase is literally not even sustainable on its own?

And suggesting that 10% is too high and that it should be 5% for proprietary apps and 0% for FOSS apps is just… literally impossible??

We’re not talking Apple or Google here—we’re talking a small, indie open source app store that doesn’t collect personal data, respects and protects privacy, prioritizes FOSS apps, and does everything openly.

Of course these are sweeping generalizations; I know not every game dev thinks/works in these ways. My point, though, is that “game development” in many ways is a *parallel* field to “software development,” and expecting them to be the same is going to give you a bad time.

We’re trying to instill good software dev practices when teaching game-making at Endless due to the upsides (like easier collaboration and maintenance), but this disconnect is something I think we’ll always come up against.