ChanServ 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]
co1umbarius has joined #freedesktop
columbarius has quit [Ping timeout: 480 seconds]
ybogdano has quit [Ping timeout: 480 seconds]
ximion has quit [Quit: Detached from the Matrix]
tzimmermann has joined #freedesktop
sima has joined #freedesktop
alanc has quit [Remote host closed the connection]
<bentiss>
basically, they are targetting personal repos, and given that by default the notification is not set, nobody notices it
<bentiss>
I am currently mass deleting thosee accounts, and I'll probably mass disable issues on personal projects if there is no created issues on those forks/personal repos
<bentiss>
(looks like I got them all now)
<bentiss>
and FWIW, whot also made a good purge this morning
<bentiss>
if anyone wonders, when I started, we had 660 opened issues instance wide with the keyword "download", and we are now at 416 -> ~250 spam issues
<bentiss>
in 3 days
<bentiss>
`User.find_by_login('bentiss').projects.each { |project| if project.issues_enabled? and project.issues.count == 0 then puts project.name_with_namespace ; project.issues_enabled = false ; project.save! end}; 1` works for my projects, attempting to do this for everyone
<pq>
can you opt me out of that, please?
<bentiss>
pq: why?
<bentiss>
(genuine question)
<pq>
not all my projects are forks from somewhere else
<bentiss>
I can tune this for only forks
<pq>
however, is does look like I do have at least 1 (closed) issue on any project I care to keep issues open
<bentiss>
but we might still have undetected spam this way
<bentiss>
let me give you what would happen for you
<pq>
sure, personally I have "watch" on all my projects, because I want to know what happens there.
<emersion>
can we enable notifications by default for forks and personal projects?
<bentiss>
emersion: never saw that option
<emersion>
i missed a number of MRs to my forks due to this
<bentiss>
emersion: AFAICT, it's either "please give me everything for everyone by default, or the current one which is opt-in to your own projects (which is completely dumb)
<emersion>
i see
<pq>
Personally I'd be fine to disable issues and MRs on my forks, and have then disabled by default when forking anything.
<emersion>
yeah, and you can always enable explicitly
<pq>
I also think "watch" should be the default notification for anything added under personal namespace.
<bentiss>
agree to all of that too
<pq>
bentiss, yup, all those are fine to disable issues and MRs on.
<bentiss>
so far, I don't think we have spam targetting MRs
<bentiss>
(and they can't because they don't have repo creation privileges)
<bentiss>
so just issues should be fine
<pq>
ok
<bentiss>
and I just tested, I think I can check if a repo is a fork or not, but there are corner cases, like: https://gitlab.freedesktop.org/pq/mutter -> clearly a fork, but not registered as such
<bentiss>
not an issue in itself, but that means we might have too many opened projects
<pq>
right, is it even possible to register as fork across gitlab instances?
<bentiss>
I don't think so. You can manually recreate the fork relation through the API, but that's only for the current instance, not cross instances
<orowith2os>
IIRC there was some work for fediverse-like federation with Git, probably relevant here.
<bentiss>
I guess that should makes things harder for spammers: count = 0; User.where('id IN (select distinct(user_id) from project_authorizations)').each {|user| user.projects.each { |project| if project.issues_enabled? and project.issues.count == 0 then count += 1 end} }; count => 12981
<bentiss>
(and we have 14188 projects)
<bentiss>
actually adding if project is public
<bentiss>
and it's done
<bentiss>
hopefully this did not leaked too much on projects we care :/
acidbong has quit [Remote host closed the connection]
AbleBacon has quit [Read error: Connection reset by peer]
Leopold_ has quit [Remote host closed the connection]
<bentiss>
emersion: swick[m] is not part of any groups, and that repo is not on a public group, so that is expected I would say
<bentiss>
emersion: you should be able to go to the pipeline tab and click "run pipeline"
<emersion>
i want new contributors to be able to contribute…
<bentiss>
emersion: 2 solutions: either you run the pipelines after reviewing it, or you migrate libdisplay-info to another group (wayland?)
<bentiss>
emersion: but in the long run, there is a chance that the "run pipeline for new contributors" will be required even for groups projects
<swick[m]>
I'm not a new contributor though
<bentiss>
swick[m]: I know, but you are not part of any groups
<swick[m]>
and for color-and-hdr pq is already clicking the run button for me
<swick[m]>
every time i push something I get at least 3 mails
<bentiss>
swick[m]: if you were added as a guest at least to any groups you contribute to, you wouldn't have to ask for running pipelines on your behalf
<swick[m]>
those repos don't really belong to a group either
<swick[m]>
people don't want me to add to groups just because of the pipelines