What about provide some metadata for branches ?

[Jan Hudec]

On Sat, Jan 20, 2007 at 19:28:34 +0100, Simon Rozet wrote:
> I am thinking about writing a plugin who add metadata capabilities
> to bzr branches.

What would be the *purpose* of that plugin. When do you want to use it? When
do you think others could use it?

Basically to get a branch you need to get it's URL somewhere. And I don't
expect many people will tell you "there is a branch at
http://somewhere.org/some/dir" and don't tell you branch of what it is.

> Here is some metadata example, 
> inspired by the [DOAP spec](http://www-128.ibm.com/developerworks/xml/library/x-osproj3/) :
> 
> - Name
> - Description
> - Developer
> - Homepage
> - Mailing-list
> - Programming language
> - ...

Are you sure these are useful to have attached on a branch? Are you sure
other people would see it as important enough to actually fill it in?

> We could imagine something like :
> 
>   ~/codes/bzr$ bzr meta
>   Name : Bazaar
>   Description : Bazaar will help you to be the master of the univers
>   ...

Wouldn't that be best served by:
 bzr cat http://wherever.com/bzr/branch/doap.xml
(and piping that through a doap parser)?

> and a nice GUI ala gcommit to set theses meta.
> 
> So, what do you think about that ? Am I completly crazy ?

Now I can see one reason to keep some metadata about branches. It's when you
provide a revision browsing capability via bzrweb or similar tool. But
I don't think this should contain a full doap record or anything similar.
A .bzr/branch/branch-comment, similar to .bzr/branch/branch-nic would be
about enough (and about what users might actually care to fill in).

-- 
						 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/20070121/8dd63539/attachment.pgp