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?
I would not merge everything together, but rather have the following communities: - leave Software Development as it …
4y ago
We have just launched Linux Systems and Power Users. Both communities have some outstanding scope issues from their pro …
3y ago
I agree with @Alexei. While Superuser and Linux is for OS but, Office Suites isn't. So, it is better to separate the …
3y ago
Software is an insanely broad term. I.E. the approach to software could be done from several perspectives: - Research …
1y ago
4 answers
You are accessing this answer with a direct link, so it's being shown above all other answers regardless of its score. You can return to the normal view.
I agree with @Alexei.
While Superuser and Linux is for OS but, Office Suites isn't. So, it is better to separate them. I have actually added a proposal on it. I am adding some more information for Office Suites here also.
- Linux user uses Libre-Office Writer while Windows user uses Microsoft Office.
- Software Codidact is ok. I was thinking to propose a site like Stackoverflow. But, Software Codidact is only for solving issues. So, I will also say that leave the Software Codidact as it is.
- Linux and Superuser should be added in a single site. I explained why in my proposal.
- I think you should add Adobe, Office Suites and Libre-Office(I don't remember if I left anything. I will edit this question if I something comes to my head then.) in a single site.
I would not merge everything together, but rather have the following communities:
- leave Software Development as it is
- Power User community separate and define a category for Office suites
- have a Linux community. Linux OS (installation, configuration etc.) is an entire world that cannot mix with software application usage.
My rationale for such a division is given by trying to answer the following question: how interesting are the questions from one area for a person mainly interested in another area?
- many Office suites related questions from Software development were not welcomed (had downvotes) or removed.
- not sure, but Linux related questions might seem gibberish for most of the general applications users and even developers that are mainly working on Windows
We have just launched Linux Systems and Power Users. Both communities have some outstanding scope issues from their proposals, but that's fine: there's enough of a baseline to get started, and the communities can continue to work out details on their community metas.
Welcome aboard everyone. We're looking forward to seeing how these communities grow. We're here to help.
Software is an insanely broad term. I.E. the approach to software could be done from several perspectives:
- Research & Academic (state of the art)
- Education
- Education system
- Educator (education program designer, professor, teacher, instructor, ...)
- Educand (student, mentee, learner, ...)
- Professional (making software work, making use of software in a professional setting)
- Non-Professional (consumer, anyone making use of software in a non-professional setting)
Even each of the above perspectives could their several communities out there that might or might have friendly links among them.
I think that the new site proposal, which requires proposal participants to create real questions and answer during the proposal evaluation is a great way to clarify a lot of things, but I think that there are elements that should be clarified before a new site is launched like having committed people to supply a steady flow of posts until the "community" is consolidated as an attractive place to have new posts organically created.
0 comment threads
0 comment threads