Handling flavor docs (re: LP teams, permissions)

[Connor Imes]

On 09/10/2012 07:41 PM, Elizabeth Krumbach wrote:
> On Mon, Sep 10, 2012 at 4:07 PM, Connor Imes <rocket2dmn at ubuntu.com> wrote:
>> Hey Lyz,
>>
>> Sorry for the delayed response.  Long story short - with the current
>> setup, you need somebody on the ~ubuntu-core-doc team to commit.
>>
>> Clearly the docs there are quite out of date now - are you planning on
>> starting from scratch or is the current documentation still the starting
>> point?  The latter may be beneficial to take advantage of existing build
>> procedures, even if you discard the existing content.  In order to get
>> somebody new on the team, they just need to show us that they are
>> familiar with bzr, docbook, and the docs build process.  Once we're
>> reasonably comfortable with that person (or persons), they can be
>> granted commit privileges.  Since nobody on the doc team is maintaining
>> the xubuntu-docs at this time, bringing in somebody new to do that would
>> be great.
> Thank you!
>
> We took the old docs and tossed them up on a team wiki for
> collaborative editing so we could include folks who don't know
> DocBook. We changed pretty much everything so there is very little
> resemblance to the previous docs.
>
> Xubuntu Project Lead Pasi Lallinaho has been working with DocBook so
> he (and some other volunteers) can convert the wiki stuff back to
> DocBook. Our plan is to submit MPs and hope someone on the
> ~ubuntu-core-doc will see them and be able to review and approve them.
> Is this the best strategy for "showing" familiarity with bzr, docbook,
> and the docs build process?
>
> Moving forward we really hope to simply maintain the docs in
> bzr+docbook each cycle so it won't turn into the "we need a full
> rewrite" situation we find ourselves in now.
>
That should be fine.  Remember that string freeze is approaching and it
rarely works to push merges or other changes through at the last minute.

-Connor