Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
MIME-Version: 1.0
In-Reply-To: <52F9148C-6BBC-4DC7-9388-91D128E030C7@apache.org>
References: 
 <CAHdjip+mB49q8Pa96-1WPiOuoYZLmy9xyUo-nhtHE4U4VAet3Q@mail.gmail.com>
	<CAPaJBx4HeH7Xi3HH+gjcyD4Sx15u8KSAa8gnVt=eiYyLALjbTA@mail.gmail.com>
	<52F9148C-6BBC-4DC7-9388-91D128E030C7@apache.org>
Date: Thu, 30 Jan 2014 14:04:31 +0100
Message-ID: 
 <CAPaJBx6fSXVb1FaQa5282u6mwKKHxj3zdjxDAeCh93-p1ocMjA@mail.gmail.com>
Subject: Re: Git repositories: migration to couchdb-documentation
From: Noah Slater <nslater@apache.org>
To: "dev@couchdb.apache.org" <dev@couchdb.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

Similarly, "documentation" might refer to documentation *about*
medical professionals.

I suggest "couchdb-the-repository-for-documentation-about-couchdb-itself".

On 30 January 2014 13:56, Robert Samuel Newson <rnewson@apache.org> wrote:
> "docs" is ambiguous and might refer to medical professionals.
>
> B.
>
> On 30 Jan 2014, at 12:26, Noah Slater <nslater@apache.org> wrote:
>
>> Wow. "couchdb-documentation" is very long! Why not "couchdb-docs"? :)
>>
>> Anyway, you can probably dispense with make. Just get a decent Sphinx
>> thing set up.
>>
>> On 29 January 2014 11:18, Alexander Shorin <kxepal@gmail.com> wrote:
>>> Hi all,
>>>
>>> Paul, this question might be most up to you, but may be any other
>>> knows the answer.
>>>
>>> 1) What git-magic commands should I enter to fill
>>> couchdb-documentation[1] repository with
>>> preserving(?) commit history of share/doc but only?
>>> 2) Have I keep current directory structure for it?
>>> 3) How docs will build: via rebar or plain make and where is better
>>> place the artefacts to handle from root repo?
>>>
>>> Thanks!
>>>
>>> [1]: https://git-wip-us.apache.org/repos/asf?p=couchdb-documentation.git;a=summary
>>>
>>> --
>>> ,,,^..^,,,
>>
>>
>>
>> --
>> Noah Slater
>> https://twitter.com/nslater
>


-- 
Noah Slater
https://twitter.com/nslater