[RFC] New name for 'repositories' - 'baskets'

[Jan Hudec]

On Wed, Mar 01, 2006 at 09:42:47 +0100, Erik Bågfors wrote:
> >
> > I agree, that the object should have a name. But from users perspective,
> > the Repository(is_shared=true) is manipulated by user explicitly, while
> > the Repository(is_shared=false) is created behind the scenes and the
> > user does not need to think about it. However when explaining the
> > concept, you need a name for Repository() as well.
> 
> What am I missing here?
> 
> -------
> A repository is a "place/thing/whatever" that stores your revision
> data. There are two kinds of repositories in bzr.
> 
> A shared repository can contain multiple branches, this is the kind of
> repository that you find in for example subversion.
> 
> A "none shared/internal/branch specific/private/whatever" repository
> is contained in a stand alone branch and is automatically created
> whenever you create a stand alone branch.  This type of repository can
> not contain multiple branches
> -------
> 
> Is there anything not clear about that description?

This description is perfectly clear. The point is whether at least all the
core developers can agree on it and use it consistently.

> I think we just need to find a clear name for "shared" and "none shared".

I think 'shared' could remain 'shared'. The oposite could probably reamin
simply 'non-shared', since user's don't manipulate with these directly and
therefore the need to name them does not arrise as often.

-- 
						 Jan 'Bulb' Hudec <bulb at ucw.cz>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20060302/4f2fd7d5/attachment.pgp