Gesendet: Samstag, 23. Februar 2019 um 10:31 Uhr Von: "Mathias Homann" <Mathias.Homann@opensuse.org> An: opensuse-project@opensuse.org Betreff: Re: [opensuse-project] dis-Connect
Am Samstag, 23. Februar 2019, 10:26:51 CET schrieb Sarah Julia Kriesch:
Gesendet: Samstag, 23. Februar 2019 um 08:37 Uhr Von: "Mathias Homann" <Mathias.Homann@opensuse.org> An: opensuse-project@opensuse.org Betreff: Re: [opensuse-project] dis-Connect
Am Samstag, 23. Februar 2019, 04:10:35 CET schrieb Fraser_Bell:
Hi, Christian:
<Fraser_Bell> Thanks. BTW: I would join Heroes and work on the Connect.o.o replacements, if I had any idea what I was doing. But, not till elections are over. <cboltz> :-) <cboltz> the important part of connect.o.o is handling the membership and maybe being a "phonebook" for openSUSE <cboltz> the other parts (groups, polls etc.) are more or less useless and can easily be dropped
<snip>
<cboltz> Fraser_Bell: I also like the https://connect.opensuse.org/pg/profile/$USERNAME pages so if you work on a replacement and keep them, I'll be more than happy ;-) <Fraser_Bell> Yes.
<snip>
cboltz> oh, I'm quite sure someone will happily upgrade you if you promise to do the work ;-) <Fraser_Bell> cboltz: Wait until after the Elections, please, I am now down to 20 pounds soaking wet and red, bleary eyes!!!!
Elections are over. Let's get started.
How about we think of a way to block out all these d*ck*w**ds that create accounts on it without even knowing what an operating system is, let alone linux, and then just wipe out everything that is not posted by an active member of the community as determined by the same mechanism.
My first thought of how to filter could be:
To be trustworthy, a Member has to have one or more of:
- an active maintainership of packages and / or projects on the build service, or at least a home project with noticeable activity in it - logged into one of the IRC channels under their registered irc nickname in the last 30 days - posted on one of the mailinglists in the last 30 days - a pgp key in the public keyserver infrastructure that is certified by at least one other trustworthy person, trustworthy meaning either a public gpg CA like heise, or another already confirmed opensuse member
Sounds any way of doable?
The problem is that we have more possible contributions than that. You can contribute on github, our wiki, translations on Weblate as an Advocate at open source events, ....
How do you want to handle that all? Sometimes there are unknown "good" contributions. Anybody has to look manually whether that was an acceptable contribution.
This would be a one time process,. to identify all those spammer bot accounts.
There would also have to be rules in place, for example IF you have an opensuse membership AND you want to contribute on github, use the same email address so we can identify you. Same for the wiki, weblate, etc. Eventually all the different ways to contribute should actually be tied into a SSO setup anyway.
Cheers MH
If that would be done on github.... I know different openSUSE Members who are not accepted for the group openSUSE on Github. Any time that has not been a part of the openSUSE Membership any more. Something like that would make it easier to filter these active openSUSE Members compared to no openSUSE Members. But that is a lot of work now to add all openSUSE Members subsequently. Regards, Sarah -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org