I think open-source is good.
For people who look for "free" (as in free beer) software we would need a different tag.
I suggest gratis.
Improvement from comments (Nicolas Raoul):
When someone starts typing "free", we should display "Do you mean gratis? If not, please use tag open source"
I'm not really convinced so. "Old hardware" is relative - I've currently got a core2duo I consider slow and old, but I've also fixed up even older hardware. What's old hardware is also relative and a bit of a sliding scale with time.
I'd say the question requirements should cover it.
Be broader in the tag than in your question. Let's say I want (using the example Gilles tossed out) something very specific that runs on Windows 2000. I would apply the windows tag to my question, then within the question itself:
This has to be able to run on a 32 bit Windows 2000 setup, with 8MB of Ram powered by hamsters fed intravenously from an ...
The operating system should be included in the title if it's an important requirement. It often is.
It is not recommended to remove the name of the language on Stack Overflow! I think you're confusing this with the recommendation not to include language names as “tags” in titles. That is:
“How do I frobnicate a widget in C?” is a good title
“C Frobnicate a ...
DONE (re-tagged by Braiam; synonym still needed)
We've got two tags for translation software:
We only need one, so I would recommend merging and creating a synonym from one to the other. I personally think this should be translation > translators.
We got rid of the tag free because it is ambiguous: it could mean free (libre) software (i.e. open source, software that you can adopt and modify), or freeware (gratis software, i.e. software that the vendor doesn't charge for).
It has recently become possible to show a short guidance text when a poster tries to use a blacklisted tag. I propose:
The tag '...
This to me sounds more like a specific requirement that should be spelled out in the body of the request rather than a tag in the system. If you need multi-language support, just state in the question. It would get somewhat unwieldy to start creating tags for all the personal requirements of a software request. It should just be stated in the question.
Gratis is a legitimate English word. Let's expand everyone's vocabulary a little bit and keep the tag as-is. I think a one word tag is better than a three word tag anytime.
If you want to get technical, gratis doesn't mean exactly the same as "free of cost." It really means available without charge. The software might not cost you anything, but it does ...
Support for required tags exists in the engine (on meta sites, all questions must have one of the tags discussion, support, bug or feature-request. However no main site currently has such a restriction.
I don't see how we could force a platform tag on this site. Not all questions are about a specific operating system. Library requests are often OS-agnostic ...
Tags are not really for features. Features are usually too precise for a tag.
Tags on this site should be mainly about application domains or domains of expertise. For example, windows, text-editors, math, …
Tags like free are still being debated, and definitely shouldn't be applied if the characteristic is optional — you shouldn't find non-free answers ...
In my opinion, they should only be used for required features.
So in the example question, the tag open-source should be removed. The OP only requires that the software must be available for free, so users might answer with proprietary and with open-source software anyway. That the OP prefers open-source software can of course still be mentioned in the ...
Edit Comments suggested desktop-client as alternative which I suggest we should use. /Edit
I wanted to express that it must run as a regular program on my desktop PC.
As in: Not mobile, Not a webapp. I want to have a window.
It's not meant as desktop vs. laptop (as my laptop is my desktop PC and I haven't heard anybody distinguishing them in the last 5 ...
[Library-Programming], for things like Boost and OpenMP, whioh are used for programming
[Library-Books] be for things like Koha, Calibre, to do with managing physical or electronic libraries of texts
[Library] tag be black-listed, as it is too unclear on this site.
Why we need [Library-Books] Tag:
(and why we can't let Library-programming hog ...
No. We had a similar issue over at Android.SE (with CyanogenMod and version specific tags) and decided they are only leading to clutter. If the question is specific to a version, that should be stated explicitly in the question text.
While on some SE sites "versioned tags" serve a good purpose (at Android.SE we e.g. have those for different Android versions)...
I think this tag is redundant and should be removed. We should encourage askers to use more meaningful tags:
a library to embed in their application: Tag as library
a web service to call from their app: Tag as web-services
a client app that is compatible with a particular existing API: Tag as the product providing that API, for instance ebay or outlook.
Yes, sure, there can be tags for specific products, such as windows or vim. These tags are about finding software that interacts with that product: a program that runs on Windows, a Vim plugin. The X tag does not mean “alternative for X”.
lightroom (better worded as adobe-lightroom) would be a fine tag for an Adobe Lightroom plugin request. On a question ...
I'd feel its a meta tag. Specific accessibility requirements (or product classes - say 'screen-reader' might make decent tags, or potentially accessibility at the end of the day, but at the end of the day, your question would probably set out the requirements better. Don't forget, while tags make it easier to search, we still have full text search.
I think we should omit these suffixes.
Not everything is a plugin(/module/extension/…)
There are cases where a solution is required to work with a software, but it doesn’t necessarily have to be a plugin (or similar).
Example question: Offline WordPress post editor/creator - Here a solution is required to work with WordPress, but it can’t be a WordPress ...
Now that we've had some discussion, let me sum up a potential solution I think we should chose:
We already have gratis and open-source. So when needed, the two can be used side-by-side.
There's no need for another "free-X" tag. Though Pandya pointed out what it is, estimated 95% of all users wouldn't see the difference anyway – too difficult for the average ...
Though I see your point, I doubt that will be a useful tag. If a user wishes that approach, it should be pointed out with the question itself.
Currently, we don't even have any tag specifying "payed". People who'd accept to pay for software certainly wouldn't reject the very same tools just because they're available for free – so we have the gratis tag for ...
I am indeed very familiar with all of these projects. While they might sound excessively related, most are as unrelated as two different Adobe products.
Everything being open, each site has its own community of developers and its own crazy amount of custom tools, most of them unadvertised and hard to find.
I support keeping all of the tags mentioned in the ...
cycling sounds like a good tag.
As I said over there, be sure to explain:
Your final goal
All of your requirements
Your operating system (ex: Android)
Whether it must be able to work offline or not
Your budget/license requirements (ex: free open source)
Also see What is required for a question to contain "enough information"?
Questions that are ...
Seeing a question tagged only gratis makes me really dislike this tag. The same goes for open-source.
A tag that can't work as the only tag on a question is a likely criterion for a bad tag. The other “smell test” passes: gratis and open-source do have objective meanings (mostly). And sure enough, they can be useful in searches — but not to be subscribed to ...
children covers all software for children and people with children, parental control is only an example. The tag also covers educational software for children (example).
I propose to reserve children for software intended to be used by children, and use parental-control for parental control software, which is intended to be used by parents.