Re: GitLab, moving non-GNOME projects currently hosted on git.gnome.org

On Thu, Feb 15, 2018 at 11:57:07AM -0600, Michael Catanzaro wrote: > On Thu, Feb 15, 2018 at 10:23 AM, Sébastien Wilmet > wrote: > > Isn't there a better solution? What do you recommend? > > FWIW, the GNOME group already contains a *lot* of modules that are not > "Projects

Re: GitLab, moving non-GNOME projects currently hosted on git.gnome.org

On February 15, 2018 11:23:14 AM EST, "Sébastien Wilmet" wrote: >Hi, > >I would like to move all the projects I maintain to gitlab.gnome.org. >Currently those projects are hosted on git.gnome.org, but not all of >them are officially part of GNOME. > >When looking at:

Re: GNOME 3.27.90 released

On Thu, Feb 15, 2018 at 4:37 AM, Sam Thursfield wrote: Does it makes sense to create a tagged commit in gnome-build-meta.git for each release, instead of publishing the release metadata only as a tarball? I guess that could be quite useful, if people want to see what the

GitLab, moving non-GNOME projects currently hosted on git.gnome.org

Hi, I would like to move all the projects I maintain to gitlab.gnome.org. Currently those projects are hosted on git.gnome.org, but not all of them are officially part of GNOME. When looking at: https://gitlab.gnome.org/explore/groups the best group that fits is "Incubator", but I'll probably

Re: GNOME 3.27.90 released

Hi Michael, Thanks for all the hard work on what sounded like a particularly tricky release! On Wed, Feb 14, 2018 at 6:23 PM, wrote: > If you want to compile GNOME 3.27.90, you can use the official BuildStream > project snapshot. Thanks to BuildStream's build sandbox, it