On Tue, 3 Nov 2020 08:41:56 +0000 Ineiev <ine...@gnu.org> wrote: > 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.
Basically, today we would need: - health-hmis (maybe this one can be kept as the current "health" so we keep the release history). - health-hmis-client - health-fhir-server - health-thalamus - health-federation-portal - health-mygnuhealth We would then move from the current repo the different directories to the new target repositories. I appreciate if we can create these repositories now, for the sake of time, because it's getting a bit critical. It would be great that in the short time the maintainer could create them? I don't want to bothering and waiting anytime we need to create a new repository. New repositories in GNU Health won't happen very often, but it happens. > > 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. Yes. We've been doing that already with the hmis-client ("gnuhealth-client") > 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). This is non-optimal, but is not a blocker either. We can create different fields or even prefixes. Thank you! Luis
pgpnCs8i81ISJ.pgp
Description: OpenPGP digital signature
