user guide help (definitions of terms)

[Inky 788]

On Thu, Aug 6, 2009 at 7:39 PM, Martin Pool<mbp at canonical.com> wrote:
> 2009/8/7 John Yates <jyates at netezza.com>:
>
>
> If you use words, like say branch, that people may have heard before,
> they will have diverse reactions and expectations because they've
> heard it in cvs or clearcase or perforce or git.  On the other hand if
> you use a word that's previously unbound, like say 'loom', you can be
> criticized for using quirky or unfamiliar terms.
>
> We are introducing new concepts.  There are no existing words that
> mean precisely the right thing.
>

I'm very happy to learn a new word if it represents something truly
not similar enough to a feature in Git or Mercurial. This would be
vastly less confusing than overloading an existing term or verbing an
existing noun or nouning an existing verb (hat tip to Ben). Just
please be very specific when defining that term. If it represents an
internal Bazaar object that takes the physical form of a file (or
files) in my project's .bzr directory, please say so.

And also, purging of synonyms from not only the docs but also the bzr
command aliases (ex. branch vs. clone vs. checkout) would clarify
things immensely, IMO.

One last bit: (I'm new here.) Is there a 2.0 release coming out soon?
I think I saw a link somewhere to the docs for 2.0 -- now being
handled by Sphinx? How can people here get in on tightening up those
docs (i.e. maybe removing synonyms or at least tightening up some
definitions of terms) before the 2.0 release? What's the proper
procedure for cloning, making local changes, and asking to have those
changes considered for inclusion?