Welcome to Codidact Meta!
Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.
How should we approach our (non-developer) software community proposals?
We have some software (but not software-development) proposals:
Are these three separate, distinct communities, or should any of them be combined? Office suites strike me as a subset of the kinds of software applications that would be in scope on the first, and the line between OS and software application can get a little blurry on Linux. (I mean, most of the things you can run on the command line are also software applications; they just usually don't have GUIs.)
For our Software Development community, after much discussion, we created a single community instead of several different ones based on the domain or language or specific discipline within the software-dev world. Codidact is still a small community (or set of communities), growing but not growing super-quickly, and we felt there would be more power in a shared space. If someday a single community is too large to function, we can spin off more targeted communities if that's what people want. We've planned for that from the start.
Should we bring these three proposals together? Are operating systems different enough from applications that Linux should stay separate regardless of what we do with the other two? Are we comfortable with a single "software users" community (better name needed) where you can ask questions about Firefox, Excel, Google Docs, iBooks, Android apps, cygwin, git, or vim? And about environment variables, file permissions, admin tools, yum, WSL, or VPNs?
How much overlap is there in the communities that form around these three topic areas? Is there benefit to working together?