daniels changed the topic of #freedesktop to: https://www.freedesktop.org infrastructure and online services || for questions about freedesktop.org projects, please see each project's contact || for discussions about specifications, please use https://gitlab.freedesktop.org/xdg or xdg@lists.freedesktop.org
Haaninjo has quit [Quit: Ex-Chat]
Leopold has joined #freedesktop
Thymo_ has joined #freedesktop
Thymo has quit [Ping timeout: 480 seconds]
Leopold has quit [Remote host closed the connection]
Leopold_ has joined #freedesktop
Leopold_ has quit [Remote host closed the connection]
Leopold has joined #freedesktop
alanc has quit [Remote host closed the connection]
alanc has joined #freedesktop
Leopold has quit [Remote host closed the connection]
Leopold has joined #freedesktop
Leopold has quit [Remote host closed the connection]
Leopold_ has joined #freedesktop
zxrom has quit []
alpernebbi has quit [Ping timeout: 480 seconds]
Leopold_ has quit [Remote host closed the connection]
Leopold has joined #freedesktop
alpernebbi has joined #freedesktop
jarthur has quit [Quit: Textual IRC Client: www.textualapp.com]
ximion has quit [Quit: Detached from the Matrix]
AbleBacon has quit [Read error: Connection reset by peer]
vx has quit [Quit: G-Line: User has been permanently banned from this network.]
vx has joined #freedesktop
bmodem has joined #freedesktop
Leopold has quit [Ping timeout: 480 seconds]
Leopold_ has joined #freedesktop
mrpops2ko has quit [Remote host closed the connection]
mrpops2ko has joined #freedesktop
lsd|2 has quit [Quit: KVIrc 5.0.0 Aria http://www.kvirc.net/]
vx has quit [Quit: G-Line: User has been permanently banned from this network.]
vx has joined #freedesktop
dri-logger has quit [Remote host closed the connection]
dri-logger has joined #freedesktop
Leopold_ has quit [Ping timeout: 480 seconds]
Leopold_ has joined #freedesktop
tzimmermann has joined #freedesktop
sima has joined #freedesktop
enick_416 has quit []
mvlad has joined #freedesktop
ximion has joined #freedesktop
ximion has quit [Quit: Detached from the Matrix]
vx has quit [Quit: G-Line: User has been permanently banned from this network.]
vx has joined #freedesktop
imre has quit [Ping timeout: 480 seconds]
<mripard> bentiss: hi
<bentiss> mripard: hello
<mripard> around?
<bentiss> sure
<mripard> do you still have time to do the drm-misc migration today?
<bentiss> yep, I was waiting for your ping
<bentiss> it should be quicker this time :)
<mripard> I'm waiting for sima ack, once it's done we can do the migration
<bentiss> k
konradybcio has left #freedesktop [#freedesktop]
blatant has joined #freedesktop
tchar__ is now known as tchar
<bentiss> mripard: looking at https://lore.kernel.org/dri-devel/20240226113610.46343-1-mripard@kernel.org/ and I wonder if you do not want to keep an equivalent of the current process instead of a plain "request access"
<bentiss> mripard: I would suggest to keep a "open an issue, get it acked by a couple of people, and then send the invite to the group"
<bentiss> instead of having the person request the access, as there will be no traces on why this person was authorized
<mripard> yeah, that's one of the things we considered with daniels indeed
<bentiss> and you could also set the repo/group as invite only
<mripard> and we didn't consider the "archival" side of things
<mripard> that's a good point
<bentiss> I mean, for kernel.org I'm not sure there are a lot of archives, but I think we need to make the request to Konstantin through a public ML
<bentiss> mripard: maybe we'll postpone the drm-misc migration to this afternoon or tomorrow (unless sima comes in the next 20-30 min). I'll be out for lunch
<mripard> for kernel.org, we need to send a mail to helpdesk@kernel.org, so it's not public but there's probably an archive
<mripard> and yeah, let's see this afternoon if sima is around
<bentiss> sounds good
<sima> oops was away, back now
<sima> mripard, ack
<mripard> awesome, we'll do it this afternoon then
<mripard> sima: thanks
<sima> mripard, wrt the issue discussion, I'd disable those for now since if we silently enable them but no one is looking, it's just an bug black hole :-/
<mripard> sima: the issue discussion was about the process to ask for a drm-misc account
<sima> oops, misread
<mripard> yeah, I was about to say that it still applied to that discussion :)
<sima> atm for drm-misc driver the bug process is still to send them into the dri-devel black hole
<sima> ah
<sima> :-)
<mripard> sorry, I got confused, we also discussed using issues to create a drm-misc account here about an hour ago
<sima> mripard, and yeah we probably need to update that page since we don't want people to ask for legacy accounts anymore
<mripard> we initially discussed with daniels and found the request access page to be enough
<sima> and yeah for account requests we probably want to use issues
<sima> *might want to
<mripard> but bentiss point is that it wouldn't be archived and it still would be better to have issues, which is indeed a good idea
<sima> yeah issues also allow the requester to explain why and all that
<sima> plus the acks to get recorded
<mripard> I'll create the issue template for that
<sima> mripard, maybe jani has one for the intel repos already?
<mripard> and, I'll tell jani that we don't want to use gitlab issues atm for drm-misc
<mripard> I'll have a look
<sima> bit of commonality for issues templates might not hurt
<mripard> neither amd nor intel has one
<jani> what do we not have? do I need to read the entire log above? :)
<mripard> an issues template to request access to the gitlab repo
<jani> where would that be placed? in some freedesktop project/repo?
<jani> also, what do you want to use for drm-misc issues? what are you going to do about issues currently filed at drm-misc?
<mripard> it's not clear yet at this point
<mripard> there's a lot of old, stale, issues I've been looking into
<mripard> but rn it looks pretty clear that no-one looks at the gitlab issues
<mripard> if we had some triage bot or something that would assign people properly I guess it could be doable
<mripard> but I don't see that happening in the near future, so it's probably best to just not use it at the moment
<mripard> (aside from requesting access to the group)
<sima> mripard, oh right we have some there
<sima> not sure how that happened :-)
<sima> since nouveau also has its own kernel repo
<sima> so pretty good mess I'd say
blatant has quit [Quit: WeeChat 4.2.1]
<mripard> also, part of the issue is, drm-misc is a kernel tree, so we won't really be able to store the issue templates there
<mripard> so maybe we should contact them about it and let them know we kind of need that particular feature ? I'm sure starting to host linux trees is a good incentive to them
<jani> mripard: I'm sure they don't give a shit. really.
<mripard> :)
<jani> the main downside with shutting down drm-misc issues purely from *my* perspective is that the issues will be piled on i915
<mripard> does it change anything from the situation today?
<mripard> I mean, we didn't have them shut down so far, but we didn't have more than 10 issues over 5 years, and nothing piled on i915
<jani> idk. if there's an issue outside of i915 that gets triggered by running i915, it'll be filed on i915, and there's really nowhere we can move it
<jani> we haven't really moved anything to drm-misc, because the bugs just die in a different place there :p
<jani> btw people are filing bugs at bugzilla.kernel.org too, idk if anyone cares. I go there maybe once every couple of months and close all i915 related bugs with "please file at fdo"
<mripard> sorry, I'm not entirely sure I understand. What would you like to improve over what we have today?
<jani> I'd like people to look at drm-misc bugs. and I'd also like a pink unicorn pony. :)
<jani> I'd also like there to be some unified place for people to file drm bugs that aren't for drivers that have their dedicated trackers. I don't know what that would be if it's not the drm-misc gitlab. just email?
zxrom has joined #freedesktop
vx has quit [Quit: G-Line: User has been permanently banned from this network.]
vx has joined #freedesktop
<mripard> I guess that's the current expectation then :)
<mripard> like I said, I think the main issue with using issues right now for drm-misc is that if we're not triaging them, nobody will look at it
<mripard> and doing it by hand seems way too tedious to me :)
vkareh has joined #freedesktop
<mripard> bentiss: we're ready for when you come back from lunch
privacy has joined #freedesktop
blatant has joined #freedesktop
zxrom has quit []
blatant has quit [Quit: WeeChat 4.2.1]
blatant has joined #freedesktop
<bentiss> mripard: OK, I'm back
<bentiss> can you confirm the full URLs we are talking about?
<bentiss> I'd guess the ones in https://lore.kernel.org/dri-devel/20240306153841.698693-1-mripard@kernel.org/ but I'd rather double check :)
<bentiss> mripard:ack, thanks
<mripard> first step would be to deny any push like we did last time
<bentiss> k, should I shoot now?
<mripard> yes, I'll say it on IRC
<bentiss> k, done
<mripard> ok, I'm pushing the cgit branches to the gitlab repo
* bentiss is starting the preparation of the mirroring from gitlab to cgit
<bentiss> looks like gitlab/drm/misc already has the dim pre-receive hook
<mripard> yep, can confirm
<bentiss> you need to relax some rules?
<bentiss> *you need me to relax
<bentiss> ?
<mripard> no, it's fine, I've cheated and set the push option by hand :)
<bentiss> heh
<bentiss> can I enable the mirror then?
<mripard> not yet, I haven't pushed everything
<bentiss> it feels like it's so easier when it's the second time we do it :)
<mripard> ok, it's done
<mripard> you can enable the mirroring
<bentiss> well, easier but there are always hiccups :)
<mripard> what's going on?
<bentiss> permission errors on push
<mripard> that one is easy to solve, chmod -R 777
<mripard> :)
zxrom has joined #freedesktop
<bentiss> OK, seems to be OK :)
<bentiss> anyway, we'll see soon enough if the mirroring is not working I guess (not sure if the merge window impacts commits to drm-misc)
<mripard> let's try to merge something
<mripard> (it doesn't)
Guest1962 has left #freedesktop [Leaving]
<mripard> it works
<bentiss> \o/
<bentiss> so we are good I suppose?
<bentiss> should we do another next week?
<mripard> as far as you're concerned, we're done :)
<bentiss> \o/, even better :)
<mripard> there's still the intel and amd repos to migrate, but it's not clear when and how that will happen
<mripard> so we'll probably ping daniels or you when we'll have a plan
<bentiss> k, ideally if we could do that soon-ish, so we remember what has been done
<mripard> I tried to track everything down here: https://gitlab.freedesktop.org/freedesktop/freedesktop/-/issues/69
<bentiss> shouldn't cgit.fd.o/drm/drm get the same level of care?
itaipu has quit [Ping timeout: 480 seconds]
<mripard> what do you mean?
<bentiss> mirror and prevent pushes to cgit?
<mripard> yeah, we should do it too
<bentiss> k, on it
<mripard> iirc sima wanted to delay the mirroring a bit to catch any issue we might have but it looks like everything's working fine since
<sima> mripard, yeah that was as a test with mild consequences to see whether the automatic upgrade in dim works
<sima> so should be fine to do the same mirroring there now too
<sima> since we had a week of -fixes and seems to have all gone fine
<bentiss> OK, mirroring properly set up!
<mripard> the dim pre-receive hook as well?
<bentiss> sir yes sir
<bentiss> not on gitlab though, haven't checked that
<bentiss> alright, pre-receive hook on gitlab set up too
<mripard> awesome, thanks :)
bmodem has quit [Ping timeout: 480 seconds]
itaipu has joined #freedesktop
AbleBacon has joined #freedesktop
Leopold__ has joined #freedesktop
Leopold_ has quit [Ping timeout: 480 seconds]
blatant has quit [Ping timeout: 480 seconds]
blatant has joined #freedesktop
jarthur has joined #freedesktop
tzimmermann has quit [Quit: Leaving]
lsd|2 has joined #freedesktop
blatant has quit [Quit: WeeChat 4.2.1]
vkareh has quit [Quit: WeeChat 4.2.1]
privacy has quit [Quit: Leaving]
scrumplex has quit [Quit: Quassel - Signing Off]
vx has quit [Quit: G-Line: User has been permanently banned from this network.]
scrumplex has joined #freedesktop
vx has joined #freedesktop
vx has quit [Quit: G-Line: User has been permanently banned from this network.]
vx has joined #freedesktop
Leopold__ has quit [Ping timeout: 480 seconds]
Leopold has joined #freedesktop
agd5f has quit [Read error: No route to host]
Haaninjo has joined #freedesktop
agd5f has joined #freedesktop
agd5f_ has joined #freedesktop
agd5f_ has quit [Remote host closed the connection]
agd5f_ has joined #freedesktop
jarthur has quit [Read error: Connection reset by peer]
agd5f_ has quit []
lsd|2 has quit [Quit: KVIrc 5.0.0 Aria http://www.kvirc.net/]
agd5f has quit [Ping timeout: 480 seconds]
pzanoni has quit [Ping timeout: 480 seconds]
jarthur has joined #freedesktop
lsd|2 has joined #freedesktop
lsd|2 has quit []
vx has quit [Quit: G-Line: User has been permanently banned from this network.]
vx has joined #freedesktop
lsd|2 has joined #freedesktop
ximion has joined #freedesktop
navarre has quit []
agd5f has joined #freedesktop
<DavidHeidelberg> whot: :D
<DavidHeidelberg> bentiss: can I get the nine-tests name space under mesa? 😉
<bentiss> DavidHeidelberg: I'd rather you ask one of the owners/maintainers of mesa. I'm merely an admin so I can not take responsibility for projects :)
<DavidHeidelberg> bentiss: thx,pinged mesa NS admins :)
sima has quit [Ping timeout: 480 seconds]
mvlad has quit [Remote host closed the connection]
pzanoni has joined #freedesktop
Haaninjo has quit [Quit: Ex-Chat]