Michael Catanzaro commented:
It might look nicer if we register separate top-level domains for each project.
E.g. https://libsoup.org/ or https://gtk.org/.
--
Reply to this email directly or view it on GitLab:
Emmanuele Bassi commented on a discussion:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/486#note_1061963
It's likely because libhandy uses Meson, and library-web does not know how to
handle modules that have no documentation inside their release tarballs. You'd
have to
Guido Günther commented:
there's https://developer.gnome.org/` too like
https://developer.gnome.org/gcr/ but for libhandy it's empty:
https://developer.gnome.org/libhandy/ - is that because libhandy has a
different versioning?
Wouldn't that be the canonical place for the docmentation of
Adrien Plazas commented on a discussion:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/486#note_962702
It starts to be a bit long, loosing some of the interest… I wonder if we could
find something better, maybe something shorter than "project". "app" is short
and nice but
Andrea Veri commented:
Adrien, we reserve first level sub-domains to GNOME services, we can probably
go with something like $project_name.project.gnome.org, what do you think?
--
Reply to this email directly or view it on GitLab:
Adrien Plazas created an issue:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/486
Some projects I maintain have GitLab pages in the GNOME group:
- https://gnome.pages.gitlab.gnome.org/libhandy
- https://gnome.pages.gitlab.gnome.org/libmanette
-
