[Mesa-dev] mirroring ogl-sample source code in gitlab?
erik.faye-lund at collabora.com
Wed Jun 12 08:25:53 UTC 2019
On Tue, 2019-06-11 at 12:41 -0400, Adam Jackson wrote:
> On Tue, 2019-06-11 at 11:13 +0200, Erik Faye-Lund wrote:
> > So here's the question: How does people feel about hosting this
> > under
> > https://gitlab.freedesktop.org/mesa/ogl-sample/? If people are OK
> > with
> > this, I will make that happen, and send out a patch to update the
> > link
> > we have in our FAQ once that's done.
> Sounds fine to me. I've needed to refer to the SI more than once, I'd
> be happy to have it in a well-known location.
> Vaguely related: Old-timers may remember that DRI used to have its
> CVS repo on dri.sourceforge.net. If you want a git import of that
> you can find it here:
Hmm, for some reason I can't see the repo here, just the (empty) issue
tracker. Even though the project is listed as public... Strange.
> I'd be happy to move this under mesa/ too if we want.
I think that'd be nice, yeah. I think it would be nice to keep things
like this in some central location.
One could also imagine that the SGI GLX realease in it's original form
would be interesting to preserve in case other mirrors go down as well.
Just for the heck of it, I've archived that as well, even though it's
just a single tarball, so it ends up as just a single commit:
This could also be a candidate for moving under the mesa-group.
> > I would further propose we mark the repo as archived, which would
> > clearly mark that we're not maintaining it and also prevent it from
> > appearing in searches.
> Enh. Less sold on this, though if it's linked from the FAQ I guess
> okay. I find that gitlab's archive makes things a little too hard to
> find, I would often prefer to see archived results in searches. But
> there's not really a better way to make a repo read-only, so I won't
> object too strongly.
Yeah, I was kinda left a bit disappointed when I read that archived
projects don't show up in searches as well. But I guess it makes sense
for most uses of archived projects. It would be nice if there was a
separate switch for searchability, just so code-historians can find
things like this easily ;)
And just to be clear, they would show up here, together with other no-
I don't really feel strongly about archived or not. We should make sure
nobody thinks this is somewhere they can contribute fixes. Perhaps it's
enough to just state this in the project description, disable merge-
requests, and protect all branches.
More information about the mesa-dev