Page MenuHomePhabricator

Let unregistered users file reports in phabricator
Closed, DeclinedPublic

Description

Axiom: it would be nice if more people filed reports directly into phabricator instead of posting them in random places from which they need to be moved.

Problem: people don't like to do things which require them to register an account. You can spend hours explaining them that registering takes few seconds, it doesn't work anyway: the human mind is not rational, they'll prefer spending multiple minutes or even hours explaining you how they don't have the time/will/whatever to register.

Solution: let people file reports without registering, then just tell them "please fill the contact form" so that they don't worry about learning what "report", "issue tracker", "phabricator" and stuff mean but instead just see something familiar, a text area to fill and submit. Sub-items:

  • would be nice for the unregistered user to be later mergeable to a registered one as soon as the user logins, a bit like StackExchange does;
  • of course initially this could only be a test, until we confirm we're not overrun with spam etc.

Evaluation: probably the number of non-WMF people creating reports over a month; IIRC, this number is stable since bugzilla times, but we don't have a specific measure, only what the monthly issue tracker report does.

I remember we mentioned this possibility in the past but I don't think it's currently tracked. In fact I think it was the only benefit I could see in Phabricator over Bugzilla when the comparisons were made, but maybe I'm misremembering, I didn't check Phabricator docs.

Event Timeline

Nemo_bis created this task.Aug 19 2015, 8:17 AM
Nemo_bis raised the priority of this task from to Needs Triage.
Nemo_bis updated the task description. (Show Details)
Nemo_bis added a project: Phabricator.
Nemo_bis added a subscriber: Nemo_bis.
Restricted Application added subscribers: scfc, Aklapper. · View Herald TranscriptAug 19 2015, 8:17 AM
Qgil added a subscriber: Qgil.Aug 19 2015, 8:54 AM

Interesting. Do you see any relation with this proposal and T29852: Wikimedia wikis need better issue reporting system?

Let's discuss this in T972.

Merging the other way, because this report has more information.

Nemo_bis changed the task status from Duplicate to Declined.EditedAug 20 2015, 9:48 AM
Nemo_bis claimed this task.

Interesting. Do you see any relation with this proposal and T29852: Wikimedia wikis need better issue reporting system?

No. AFAIK, that's for issues with content.

Merging the other way, because this report has more information.

I disagree and would expect you to copy relevant information over, like
https://phabricator.wikimedia.org/T972#16750 in this case:

While we need a good balance between making it unnecessarily hard (so people would not report issues) and too easy (too many reports with bad quality) I am strongly against this.

  • Many users only ever create a single report (http://dirkriehle.com/uploads/byhand/theses/2013/capraro_2013_arbeit.pdf page 65) and are not familiar with the expectations of developers what makes a good bug report. Guidelines are often ignored. Hence some tickets are „filed by well-meaning but inexperienced or ill-informed users“ (Karl Fogel, "Producing Open Source Software - How to run a successful free software project", 2006, page 77). Only experienced users manage to create bug reports which have all needed information included in the initial comment. If anonymous reporting was possible the feedback rate on followup questions will be even worse.
  • We allow creating tickets via email without registration (T52) so users could always create a throw-away email address if they really wanted. I consider that an acceptable obstacle. Again, it's a trade-off.