<div dir="ltr"><div>We should make an effort to mention this to new contributors when on say #pulp we encourage someone to submit or comment so they don't wonder what's wrong.</div><div><br></div><div>--Dana</div><div><br></div><div><br></div><div><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div> <p style="font-weight:bold;margin:0;padding:0;font-size:14px;text-transform:uppercase;margin-bottom:0"><span>Dana</span> <span>Walker</span></p> <p style="font-weight:normal;font-size:10px;margin:0px 0px 4px;text-transform:uppercase"><span>Associate Software Engineer</span><span style="font-weight:normal;color:#aaa;margin:0"></span></p> <p style="font-weight:normal;margin:0;font-size:10px;color:#999"><a style="color:#0088ce;font-size:10px;margin:0;text-decoration:none;font-family:'overpass',sans-serif" href="https://www.redhat.com" target="_blank">Red Hat <span><br><br></span></a></p> <table border="0"><tbody><tr><td width="100px"><a href="https://red.ht/sig" target="_blank"> <img src="https://www.redhat.com/files/brand/email/sig-redhat.png" width="90" height="auto"></a> </td> </tr></tbody></table> </div></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr">On Fri, Dec 7, 2018 at 4:24 PM Robin Chan <<a href="mailto:rchan@redhat.com">rchan@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Removing incentive seems like a good tactic to try. And perhaps we can take a look at some metrics to see if it's helping after trying for a bit.<br></div><br><div class="gmail_quote"><div dir="ltr">On Fri, Dec 7, 2018 at 7:26 AM Austin Macdonald <<a href="mailto:amacdona@redhat.com" target="_blank">amacdona@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto"><div><br><br><div class="gmail_quote"><div dir="ltr">On Wed, Oct 31, 2018, 3:57 PM Austin Macdonald <<a href="mailto:amacdona@redhat.com" rel="noreferrer" target="_blank">amacdona@redhat.com</a> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="auto"><div dir="ltr">On Wed, Oct 31, 2018, 2:23 PM Daniel Alley <<a href="mailto:dalley@redhat.com" rel="noreferrer noreferrer" target="_blank">dalley@redhat.com</a> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Maybe the first comment / issue posted by an account would need to be approved, but once approved they could post subsequent comments / issues without delay?<br></div><div class="gmail_extra"><br></div></blockquote><div> </div></div><div dir="auto">@dalley, sounds right to me. I think this could be implemented using bmbouters b) option, with 1 difference. If the user can't even file until approved, I think we shouldn't do it. If the user can file an invisible issue, I'm ok with this.<br></div><div dir="auto"><br></div><div dir="auto">On Wed, Oct 31, 2018 at 1:28 PM, Brian Bouterse <span dir="ltr"><<a href="mailto:bbouters@redhat.com" rel="noreferrer noreferrer noreferrer" target="_blank">bbouters@redhat.com</a>></span> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto">b) create a "trusted users" group and have that allow users to either post comments, post issues, or both and then disable those permissions for "other accounts". This would prevent a new user from filing a bug in a self-service way though.</div></blockquote><div dir="auto"><br></div><div>b) Story >>> A new user is created, they file an issue. Issue is not visible until approved. When issue is approved, user is moved to "trusted user" group. Further issues are not delayed.<br></div><div><br></div><div>This would fix the problem at the cost of delaying response to new contributors at a critical time, right after their first contribution. Using "trusted users" would allow us to filter out most issues, significantly reducing the workload to review for spam.</div><div></div></div></blockquote></div></div><div dir="auto"><br></div><div dir="auto">Nothing has changed except my patience. Ugh. </div><div dir="auto"><br></div><div dir="auto">IMO we need to remove the incentive, which means hiding the first issue/comment of new users. </div><div dir="auto"><br></div><div dir="auto">Unless anyone is strongly against this, I'll file an issue and we can discuss the technical details there. </div><div dir="auto"><br></div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><br></div><div>However, we could also users "trusted users" as an invisible flag that makes no difference to the user. This would be the exact same amount of work as b) for us, but new contributor issues are always visible. So after all this, I'm leaning toward a) + 1/2 b)<br></div><div dir="auto">On Wed, Oct 31, 2018 at 1:28 PM, Brian Bouterse <span dir="ltr"><<a href="mailto:bbouters@redhat.com" rel="noreferrer noreferrer noreferrer" target="_blank">bbouters@redhat.com</a>></span> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto">a) manage the spam better</div></blockquote><div><br></div><div>a) Story >>> A new user is created they file an issue. Issue is visible immediately. Spam review must review every new issue from every user. <br></div><div> </div><div>a) + 1/2 b) Story >>> A new user is created, they file an issue. Issue is visible immediately. Issue is flagged internally for spam review, if not spam, user is added to trusted group. Further issues would skip this process.</div><div><br></div><div class="gmail_quote">I have one last thought that might make b) more attractive, but its a shot in the dark. Since the spam is coming from humans, someone is paying them. If we never show the spam, we remove the incentive, and hopefully someone will notice and stop it. If y'all think this is how things woud go down, we could always do b) until the problem stops and switch to a) + 1/2 b).<br></div></div></blockquote></div></div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><br></div> </blockquote></div> </div></div> _______________________________________________<br> Pulp-dev mailing list<br> <a href="mailto:Pulp-dev@redhat.com" target="_blank">Pulp-dev@redhat.com</a><br> <a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/pulp-dev</a><br> </blockquote></div> _______________________________________________<br> Pulp-dev mailing list<br> <a href="mailto:Pulp-dev@redhat.com" target="_blank">Pulp-dev@redhat.com</a><br> <a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/pulp-dev</a><br> </blockquote></div>