Rather than adding a bunch of comments to the existing proposal, I'm going to add an
alternative scope proposal
The community should cover Unix-like operating systems, but only to the extent that the Unix-like portions are what the question is about.
This uses "Unix-like operating systems" to refer collectively to such diverse systems as Linux (including both the kernel proper, typical general-purpose userlands such as GNU, and distribution-specific idiosyncrasies), the various *BSDs, Mac OS X, Windows Subsystem for Linux, Cygwin, the various proprietary UNIXes, and other operating systems and environments that operate similarly from a user (including system administrator) perspective.
- Questions about installation, configuration, usage, administration, troubleshooting and repair of the Unix-like portions of Unix-like operating systems.
- Questions about system startup of Unix-like operating systems, including configuration and error recovery thereof. (Editor's note: this includes, but is not limited to, Grub as a bootloader; it could also include, say, LILO or Syslinux. It can also include kernel initialization and system bootstrapping; asking about, say, root file system pivoting during the Linux boot process would fall into this category.)
- Questions about performing, scripting and automating tasks using tools commonly used for such purposes on Unix-like operating systems.
- Questions about how to accomplish a task in a GUI that can run on more than one Unix-like operating system. (Editor's note: the latter criteria excludes "how do I do X on Android?" or "how do I do Y using the OS X GUI?" because, while those are GUIs running on top of a Unix-like foundation, the GUIs are specific to those OSes and are therefore more of defining features of those specific OSes than of Unix-like operating systems in general. Questions about how to accomplish a task in a distribution-centric way on a Unix-like operating system, such as "how do I configure Z on Ubuntu?" are allowed under the "distribution-specific idiosyncrasies" allowance as long as the GUI itself can run on more than one Unix-like operating system.)
- Questions about the history of Unix-like operating systems, including historical implementations.
- Software development in a more general sense, even for software intended to run on a Unix-like operating system (should go on Software Development instead).
- For Unix-like environments running within other operating systems (such as Cygwin, WSL, or the terminal in Mac OS X), questions relating solely to the operating system hosting the Unix-like environment, unless that is itself Unix-like. (Editor's note: the last exception allows for example questions about hosting of containers, namespaces and jails, where a Unix-like environment operates within another Unix-like environment, possibly constrained in some manner by the outer environment.)
- General software usage questions that are unrelated to the operating system; it's not enough to add "when run on insert-favorite-*nix-here" to make "how do I draw a rectangle in LibreOffice Draw?" on-topic.
- Software recommendations; ask how to accomplish a defined task, not which tool to use to accomplish a task.
There are going to be some issues defining which exact task-automation questions fall within or outside of the community's scope, no matter the delineation, simply because in some sense, task automation is what all software development is all about. My intent in the bullet point on performing, scripting and automating tasks is to cover typical usage of a shell, including shell scripting (after all, nothing particularly magical happens because commands are placed in a file instead of typed manually at a terminal), while excluding development of larger-scale software.
As for the suggestion that configuring the boot sequence is on-topic but configuring an Apache web server is off topic, I'm torn on the issue. Near one extreme, "how do I configure LibreOffice to include my name in documents I save?" clearly has nothing to do with anything Unix-like, even though LibreOffice can run on Unix-like OSes; somewhere close to the other extreme, "how do I configure my insert-favorite-*nix-here system to not activate the kernel-implemented system facility XYZ during the boot process?" would pretty clearly be on topic; but there are quite fine lines between questions like "how do I configure Apache to do X without intervention during FreeBSD system boot?", "how do I configure the OpenIndiana NFS subsystem to export the Y file system automatically once it becomes available?" and "how do I configure the DHCP client daemon to do Z during Debian system boot?". Personally, I would be inclined to go for a slightly more permissive stance at first and revisit the issue later if it becomes a problem.