Re: Gnome and Ubuntu UGs (Was: string freeze?)

[Matthew East <mdke ubuntu com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

* karderio:
> When talking about working together I was referring to the proposals for
> somehow making it trivial to use parts of the GUG in a downstream
> distribution without any modification. One of the things Joachim
> proposed was to chop the guide into smaller files.

{snip}

> Could such a solution assist you in integrating the GUG into your
> documentation as you have been planning ?

Potentially, it depends how it is done. But I can't see this being
achieved for Gnome 2.18 because rationalising out a working structure
would take a lot of work. If it were, that's the sort of solution we'd
be looking at, instead of simply taking a couple of chapters.

> I'll try and explain this better. If you use a document, the GUG in this
> case, one day as the document changes upstream, you will have to update
> said document. If you had made arbitrary changes to the document, these
> changes will need redoing.
> 
> If what you are suggesting is indeed comparable to copy-pasting parts of
> the GUG into your documentation (from what you have explained, this
> seems to be what you are considering), then every time we update the GUG
> you would have to re-copy and re-paste the contents into your docs. We
> are simply proposing to try and make this easier, and some of the
> suggested solutions would make a documentation freeze seem irrelevant.

I still don't really understand. A freeze means that you *wouldn't*
update the document after that time. It would permit us to know when is
an appropriate time to fork the document, because after that time no
further upstream changes would be made. We can then copy it and make
whatever changes are needed.

Anyway, let's drop the subject.

> Do you have any ideas how we could make it easier for you to achieve
> what you are trying to do considering we do not have a documentation
> freeze ?

No, it's no big deal. It simply means doing the fork without the certain
knowledge that it is stable and won't change further after doing so.
- From what I've heard, not a lot of work is going to be done on the
material anyway, so it will probably not matter much.

Matt
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFjYXptSaF0w5rBv8RAkPCAJwJSu+s/PTyW/9sw5Jl70i9mq4vpgCfTkh7
ftkXI49PaFatlP6IT2zqRQQ=
=5vWD
-----END PGP SIGNATURE-----