accessibility docs

[Matthew East]

On Thu, Nov 27, 2008 at 4:17 AM, Emma Jane Hogbin <emmajane at ubuntu.com> wrote:
> Matthew East wrote:
>>
>> Most work that gets done on the Accessibility Guide is done upstream.
>> The key thing for you to decide is whether you want to work on
>> improving it generally (in which case your patches should be done
>> against the latest upstream version [1]) or to make specific
>> Ubuntu-related changes. The latter is rather more difficult, because
>
> I don't think it makes sense to have references to Solaris in our
> documentation. Apart from a bit of time twice a year pre-release to remove
> references from the upstream merges is there anything else I'm missing?

No, that's basically it. With gnome-user-docs, how we work is to
create a branch which will contain the Ubuntu package for a particular
release. I've created one for Jaunty [1]. Then, we merge the changes
that take place upstream into that branch from the upstream import
[2].

[1] https://code.launchpad.net/~ubuntu-core-doc/gnome-user-docs/ubuntu-jaunty
[2] https://code.launchpad.net/~vcs-imports/gnome-user-docs/trunk

What I suggest you do is create a patch or bzr bundle against the
ubuntu-jaunty branch. Then, when we merge changes to the document from
upstream during the cycle, these will either apply cleanly (if
upstream change an area which you haven't touched) or create a
conflict (if upstream changes the same line which you have touched).

If you're willing to help out with resolving those conflicts every now
and again (bzr makes it quite easy to see where they are) then I think
you're good to go.

> I have already downloaded the source files from Launchpad and am now looking
> to make the changes before submitting a patch...

Great, look forward to that. Let me know if you have any other questions.

-- 
Matthew East
http://www.mdke.org
gnupg pub 1024D/0E6B06FF