linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Jani Nikula <jani.nikula@linux.intel.com>,
	Linux Doc Mailing List <linux-doc@vger.kernel.org>
Subject: Re: "staging" area for unsorted random files under Documentation/*.rst
Date: Thu, 20 Feb 2020 06:29:34 +0100	[thread overview]
Message-ID: <20200220062934.552d2941@kernel.org> (raw)
In-Reply-To: <20200219022951.6127e48b@lwn.net>

Em Wed, 19 Feb 2020 02:29:51 -0700
Jonathan Corbet <corbet@lwn.net> escreveu:

> On Tue, 18 Feb 2020 14:26:14 +0200
> Jani Nikula <jani.nikula@linux.intel.com> wrote:
> 
> > On Tue, 18 Feb 2020, Mauro Carvalho Chehab <mchehab+huawei@kernel.org> wrote:  
> > > Shifting those around is not easy (I tried a few times), as some discussions
> > > are required in order to get them at their rightful places.
> > >
> > > So, my current proposal is to just rename them to *.rst, keeping them
> > > where they are, and adding them into an "staging" area at the main
> > > index.rst. See the enclosed patch.    
> > 
> > The obligatory bikeshedding comment, how about adding an actual
> > "staging" directory under Documentation, perhaps with an index.rst of
> > its own?  
> 
> I kind of agree, actually.  If we absolutely must create a trashpile of
> random documents, the top-level directory seems like the worst place for
> it.  Let's hide our shame rather than rubbing everybody's nose in it.

Ok. I'll prepare a patch creating a Documentation/staging and move those
unsorted stuff into it.

I may try to do another attempt to move at least some of those unsorted
documents to a better place before the final one that will place the
remaining ones under staging/.

> > Personally I don't really mind having .txt files around either, just
> > *not* at the top level Documentation directory.  
> 
> In general, RST conversion is not my highest priority at this point.

Well, right now on my TODO list there are just ~20 files left to convert.

I'm excluding from my TODO a few exceptions like config files with .txt 
extensions and translations, plus a couple of text files whose previous
conversion attempts generated heated discussions.

> There is only so much value in creating a more nicely formatted version
> of an unorganized heap of obsolete documentation.  Hopefully we get get a
> bit more focus on quality once this is all behind us...

Yeah, there's little value nicely formatting outdated stuff. However, 
having them converted make those docs more visible, which in turn helps 
to attract devels to send patches updating them.

The more important is that, once we get past this step, we can have a
clearer view about what's left undocumented.

Cheers,
Mauro

  reply	other threads:[~2020-02-20  5:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-18 10:32 "staging" area for unsorted random files under Documentation/*.rst Mauro Carvalho Chehab
2020-02-18 12:26 ` Jani Nikula
2020-02-19  9:29   ` Jonathan Corbet
2020-02-20  5:29     ` Mauro Carvalho Chehab [this message]
2020-02-22  8:41       ` Mauro Carvalho Chehab

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200220062934.552d2941@kernel.org \
    --to=mchehab+huawei@kernel.org \
    --cc=corbet@lwn.net \
    --cc=jani.nikula@linux.intel.com \
    --cc=linux-doc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).