Re: Subprojects in Savannah

[Ineiev]

On Fri, Oct 30, 2020 at 01:14:25PM +0000, Luis Falcon wrote:
> On Thu, 29 Oct 2020 17:49:28 -0600
> Bob Proulx <bob@proulx.com> wrote:
> 
> > Luis Falcon wrote:
> > > The GNU Health project has different components that would need
> > > their own repository, releases, bugs...  
> > 
> > Does Mercurial handle subdirectories in the repository?  If so then
> > it would be easy to set up sub-projects in the hg repository as a
> > subdirectory.  If this is something that we would simply need to
> > experiment with to try then we could try it.
> 
> Mercurial has the concept of "subrepository" to create "siblings" repos
> withing a main repository, but I think is adding extra complexity,
> there are still caveats and is not really what we need.
> 
> What I think would be best is to treat each component as a repository,
> inside a parent directory.
> 
> At filesystem level, it would look something like this
> 
> health (directory)
> |- hmis (independent repository)
> |- thalamus (independent repository)
> |- mygnuhealth (independent repository)
> |- ghportal (independent repository)
> 
> Each repo would have its own changesets

Currently, we have a procedure for additional Git repositories
synced with frontend (i.e. the web UI lists them with descriptions
on group's main page); we could work out something similar
for Mercurial as well.

> > For releases I assume you mean on download?  Or elsewhere?  Because I
> > note that the download directory for GNU health is empty currently.
> > But subdirectories are okay there too.
> 
> We are not using the "Download" functionality from Savannah. We
> directly upload the stable version to ftp.gnu.org/gnu/health
> I will look into it, because it might be a nice thing to link and use
> in development versions.
> 
> For releases I mean each subproject has its own version and
> release cycle. This is important for savannah tasks and bugs. I guess
> we can use a preffix for each component when creating or updating the
> resource, but is suboptimal.

You can upload the releases for each subproject to a respective
subdirectory like ftp.gnu.org/pub/health/thalamus/ like explained in
https://www.gnu.org/prep/maintain/html_node/FTP-Upload-Directory-Trees.html.
I think that would be the most intuitive way for the users.

> > > 1) GNU Health HMIS
> > > 2) Thalamus
> > > 3) Federation Portal
> > > 4) MyGNUHealth
> > > 
> > > Is that feasible in the current infrastructure?  
> > 
> > For the Savannah web UI bug tracker we need Ineiev to join the
> > conversation as I know very little about it.

A group can't have multiple bug trackers, but you can use additional
fields, including cumstom ones, to assign items to their
subprojects, and then select items of a specific subproject
(or a set of subprojects).

signature.asc
Description: PGP signature