Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of nslater@tumbolia.org designates
 209.85.214.52 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CABvT1DHrSsr25vAc3tfDnOn1wQbmtn8N2kxp=MajrCb3oG8=Rw@mail.gmail.com>
References: 
 <CAHZBNKZS1fRmPr1S+SZB-bruZNw=Vt5xCw39X-jgsiX6hHLgxw@mail.gmail.com>
	<CAHZBNKYCpRMpKmhgNJ-h6yGK2KwAd-myrMcmXPZ3p83OrF4-3A@mail.gmail.com>
	<CABvT1DFAxMEw06bW_ZX2vHSd_PxFhm_LpgJ7ZBt=oC+XWRiWjQ@mail.gmail.com>
	<CA+Y+446hCaL1qACC+tsGBBMKE2UE_5qL2kEXGXUKsYscp4Nt_w@mail.gmail.com>
	<2DF4B21F-FB3D-46C8-A566-4F57EDAC22E3@kristinaschneider.com>
	<CAJNb-9qSV8PrRD7FhpxO-CpkOUyMjkBNrTzxES1NDGqF4KBJ7Q@mail.gmail.com>
	<E755048B-8491-4B5E-8B82-339D9DF24A92@dionne-associates.com>
	<CAHZBNKZMjhJOAFe4cOm7bkrxRMNHrB3Yb0iX29q9C-rtLgisYg@mail.gmail.com>
	<CABvT1DHrSsr25vAc3tfDnOn1wQbmtn8N2kxp=MajrCb3oG8=Rw@mail.gmail.com>
Date: Sat, 26 Nov 2011 20:05:44 +0000
Message-ID: 
 <CA+Y+447P3pmafEUo07yoHeMnRL0fMWfP=kbADT8YafSZLNADzw@mail.gmail.com>
Subject: Re: [VOTE] Apache CouchDB new docs proposal
From: Noah Slater <nslater@tumbolia.org>
To: dev@couchdb.apache.org
Content-Type: multipart/alternative; boundary=0015174c1e3a76ce0f04b2a8cb29

--0015174c1e3a76ce0f04b2a8cb29
Content-Type: text/plain; charset=ISO-8859-1

Sure.

Well, I'd like to link to the docs from the website. And some amount of
basic typesetting would be nice. HTML is the bare minimum if we want text
(obviously) and hyperlinks. I think hyperlinks would be useful. Even if
it's only so we can use anchors.

If you look at the source of the CouchDB book, we could strip HTML down to
its barest elements. The "administrative debris" like navigation, style,
etc can be added with a single common JavaScript file and a single common
CSS file.

If we want to move forward with this, I am happy to drive the effort.

Our first steps should be:

   - Get some plain text only documentation together from the committers

   - Speak to Infra about how to host the documentation

If someone can co-ordinate the first point, I can take this stuff and shape
it in to some basic HTML for us to use.

I can take care of the second item.

On Sat, Nov 26, 2011 at 7:53 PM, Robert Newson <rnewson@apache.org> wrote:

> Noah: All I really mean is that the docs/ are widely available. If
> it's infeasible to push them to the wiki then let's not do it, but I'd
> be surprised if that's a technical challenge for a group with our
> diverse superpowers.
>
> As for choice of markup language, I have no preference. What's the
> minimum here? Do we need more than just plain text? The linux kernel's
> Documentation/ dir seems to get away with it.
>
> B.
>
> On 26 November 2011 19:47, Dave Cottlehuber <dave@muse.net.nz> wrote:
> > On 26 November 2011 14:25, Robert Dionne <dionne@dionne-associates.com>
> wrote:
> >> +1 for Latex
> >
> > Hi Robert, all,
> >
> > Thanks for taking the time to read all that!
> >
> > Specific design & tools aside, are you willing to support at least the
> > principle of upgrading/improvement of the documentation?
> >
> > Or are you fundamentally against docbook? Personally, I am agnostic on
> > the tool but I would like to know that I can contribute something that
> > won't require rework in future, and I'll happily learn tool X to
> > support that.
> >
> > I see little point in counting a few +1 votes and then making
> > wholesale changes; this should be a consensus otherwise I'd rather
> > revert to incremental changes to the wiki.
> >
> > A+
> > Dave
> >
>

--0015174c1e3a76ce0f04b2a8cb29--