Follow

Dear developers, especially those working on free and open software: every new release is an opportunity to have someone discover your tool.

Make sure you explain what your tool is when announcing a new release and have links to where people can learn more about it.

Removing barriers of entry and rights of passage includes never assuming that people already know what your tool or app is or what it does.

(The same goes for not using – or at least introducing/explaining – acronyms and jargon in your prose.)

@aral +1

Also:
“… Please make sure it's #accessible as an average 15% of the population (and it's a conservative estimation) will benefit from it, some of which will not be able to use it **at all** if it is not accessible.”
😊

#a11y

@aral

not to be a downer but I really get suprised by how bad organization, the lack of communication skills and work or even interest in having these things being good and how little usertesting there is being done in the libre software world.

Most professional developers I know kind of scuff at this scuff and how bad it is when talking about it and possibly within reason too.

GIMP is a clear example of it

And it kind of breaks my heart 😔

@aral I agree. In an ideal world, we would actually have time to properly test and document things..

@aral I can't even remember how many times I've heard people talk about anew release for a software and wondered what it does.

@aral there's this guy that announces every new release of a software project but the only thing he mentions is the name of the software and the new version name. So much effort, so useless :/

Sign in to participate in the conversation
Aral’s Mastodon

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!