savannah-hackers-public
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Savannah-hackers-public] support for repository(ies) contact/descri


From: Sylvain Beucler
Subject: Re: [Savannah-hackers-public] support for repository(ies) contact/description
Date: Mon, 9 Jun 2008 23:39:59 +0200
User-agent: Mutt/1.5.17+20080114 (2008-01-14)

Hey,

On Mon, Jun 09, 2008 at 10:05:40AM +0200, Aleix Conchillo Flaqué wrote:
> On Sun, Jun 8, 2008 at 11:27 AM, Sylvain Beucler <address@hidden> wrote:
> >
> > My main concern is: will this fit all VCSes? Though, maybe we can just
> > add a separate joined table if a VCS requires additional fields .
> >
> > 'contact' is not used by 'bzr' afaics; maybe that field can be just
> > ignored by the bzr backend, or maybe the field can be disabled in the
> > edit form (so users don't expect it to be used).
> >
> 
> I think it can also be used, not for any bzr internals, but just to
> provide information. That is, there could be a page (read-only) or
> existing one, providing repository description and contact
> information.
> 
> >
> > The alternate way is to create a specific table for each VCS, but this
> > sounds much more difficult to me anyway.
> >
> 
> And it likely has performance penalties. For example, if you want to
> obtain all the repositories that 'show_in_source_menu', with one table
> it can be done at once with a simple select. The other way would mean
> as many selects as activated VCS (which is not a lot).
> 
> >
> > I'd suggest changing 'is_default' to 'show_in_source_menu'.  This way,
> > main repositories would be proeminently displayed in the "Source Code"
> > menu, as well as in the project homepage. Other repositories would be
> > displayed in a separate "other repositories" page; this would exclude,
> > for example, experimental repos and obsolete repos (such as CVS repos
> > if you switched to Mercurial, but still wish to keep the old CVS
> > around :)).
> >
> > The bottom line is: I think some project will have several main
> > repositories (I do :)).
> >
> 
> OK, that makes more sense.
> 
> >
> > I think listing all repositories at once is easier to edit.
> >
> 
> OK.

I agree with everything :)


We didn't consider the backend more than that, but I don't see any
obvious problem there either.

-- 
Sylvain




reply via email to

[Prev in Thread] Current Thread [Next in Thread]