One set of documentation needs to go

[Martin Dixon]

Hi :)
Too many good points have been made to just add +1*n. As a Newbie I
agree with so many of them.
There appears to be a need for more than one "document" (official, wiki
book, whatever)
and an associated reason to use a different "tool" to create each.
At any point in time there will be a basic body of facts - what it (say
14.04) looks like, what it does, etc)
which could be organised to act as a basis from which each "team" can
work.  
There will be some "pages" which are additional - work around
techniques, etc which are outside this "plan" and don't need to be
duplicated,
Particularly I agree with the suggestion of a "wiki" page to concentrate
ideas as multiple threads are already appearing.
Hope this helps a bit.  Martin

On 09/10/13 06:14, Vikram Dhillon wrote:
> On Wed, Oct 9, 2013 at 12:25 AM, Elizabeth Krumbach Joseph
> <lyz at ubuntu.com> wrote:
>> On Tue, Oct 8, 2013 at 5:11 PM, Phill Whiteside <PhillW at ubuntu.com> wrote:
>>> ...
>>> It is precisely because several people new to docs knew or would understand
>>> that call, that I issued the call to join ranks and just 'get on with it'.
>>> ...
>> ..different teams have very good reasons for their different tools...in each of these
>> instances the tools used were selected specifically to suit the pool
>> of contributors they had.

> ... There aren't that many hoops to jump when working with
> documentation and if you feel like there are, that's why there is a
> community to help you with it. .... Any good content is
> usable and extremely helpful to us.
>
> As a contributor, there are many ways we can work this out friends .
> If you feel like the manual project is splitting the efforts and so
> on, just submit the draft that you have to both mailing lists, and
> then let them worry about how to organize and pull the content
> together. Of course there are issues that we still need to iron out
> and I am sure in the upcoming months we will hopefully work towards a
> better solution.
>