README: Find more sane first words we have to say about Linux
PATCH 1/1 README: Find more sane first words we have to say about Linux
Imagine you're completely new to Linux, just real quick, ok? What do you do? Wouldn't having a look at README be under first if no *the* first thing? Ah there it is: README. "Linux kernel". nice! So what's that? "This file was moved to ...... Please notice that there are several....". Wtf!? Why? Can't they just tell me what's going on like a normal person?
I'm sorry for the exaggeration, but really honestly I think we could do better. I'm all for not really having content in README, but come on :)
I only try to avoid the biggest damage here and find some nice first words at least.
---
please ignore if too irrelevant, but I personally would put this in 4.11, if still possible, and rewrite the REAME for 4.12 to be even more friendly.
thanks
martin
README | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-)
README +4 -3
@@ -1,10 +1,11 @@ Linux kernel ============ -This file was moved to Documentation/admin-guide/README.rst +Linux is a Unix-like operating system, originally written by Linus Torvalds. +Please read Documentation/admin-guide/README.rst for an introduction. -Please notice that there are several guides for kernel developers and users. -These guides can be rendered in a number of formats, like HTML and PDF. +There are several guides for kernel developers and users. These guides can be +rendered in a number of formats, like HTML and PDF. In order to build the documentation, use ``make htmldocs`` or ``make pdfdocs``.
Signature · 1 line
2.11.0
Quoted 5 lines · On Sun, 30 Apr 2017 22:11:35 +0200 Martin Kepplinger <[email protected]> wrote:
Imagine you're completely new to Linux, just real quick, ok? What do you do? Wouldn't having a look at README be under first if no *the* first thing? Ah there it is: README. "Linux kernel". nice! So what's that? "This file was moved to ...... Please notice that there are several....". Wtf!? Why? Can't they just tell me what's going on like a normal person?
So I don't doubt we could put something better there, but can we think for a moment about who the audience is here? If you're "completely new to Linux", will you really start by jumping into the kernel source tree? Somehow I'm not quite convinced... It seems to me that the README file should be aimed at developers who know what the kernel is but are not yet familiar with the process of configuring and building it.
Thanks,
jon
Am 2017-05-01 um 17:24 schrieb Jonathan Corbet:
Quoted 9 lines
Quoted 5 lines · On Sun, 30 Apr 2017 22:11:35 +0200 Martin Kepplinger <[email protected]> wrote:
Imagine you're completely new to Linux, just real quick, ok? What do you do? Wouldn't having a look at README be under first if no *the* first thing? Ah there it is: README. "Linux kernel". nice! So what's that? "This file was moved to ...... Please notice that there are several....". Wtf!? Why? Can't they just tell me what's going on like a normal person?
Quoted 7 lines
So I don't doubt we could put something better there, but can we think for a moment about who the audience is here? If you're "completely new to Linux", will you really start by jumping into the kernel source tree? Somehow I'm not quite convinced... It seems to me that the README file should be aimed at developers who know what the kernel is but are not yet familiar with the process of configuring and building it.
It should definitely be aimed at developers. But even as a developer who is completely new to kernel development, it's nice to have some broad context in 2 or 3 lines first.
(again, I'm a little exaggerating and) trying to see from an outside point of view:
What other "official brief definition" of what Linux is could there be? Right now one has the impression that the Linux Foundation has "official" information, but that's (very strictly speaking) pretty random right? Besides developers, I can imagine technical literature to have a look at projects' README files for that.
I mean there *is* the new README.rst which is awesome. But it wouldn't hurt to summarize the first few things in the README and then refer to the doc. It should be something for people who
* already checked out the source obviously (developers, but or technical authors, or any interested engineer), and
* who would *maybe* say, "what? nothing in the README? ok. I'll take some definition I found online then" and not bother reading the Documentation directory just yet.
martin