Moving bugs to Phabricator

Mike Blumenkrantz zmike at
Wed Feb 3 15:56:30 UTC 2016


It seems that opening any of these links requires a login. A valid use case for bug trackers is something like:

* user searches web for issue keywords (eg. "wayland has no ssd!")
* results include link to bug
* user views bug report

Requiring a login will create more hassle and reduce the likelihood that tickets will be seen.

For reference, we switched to phabricator a few years ago for EFL and had this exact issue. Some parts of the site can be made public, but the majority of it seems to be locked down and only accessible to logged-in users.

On Wed, 03 Feb 2016 12:25:26 +0000
Daniel Stone <daniel at> wrote:

> Hi,
> On 2 February 2016 at 20:28, Bill Spitzak <spitzak at> wrote:
> > Can you make a clone of the current Bugzilla state in Phabricator so that we
> > can see what it looks like?  
> Good idea! Here they are:
> Please bear in mind these are REAL IMPORTED BUGS linked to REAL ACTUAL
> PEOPLE. Manipulating these tasks will lead to actual people being
> emailed, just as it would on Bugzilla. But please feel free to mess
> around with your own bugs, or create new ones and play with those.
> The workboard columns aren't fixed in the current single-column
> format: depending on what works best, we could use any combination of
> one column per release, status-based columns (WIP / mid-bikeshed /
> etc), or anything really.
> Also, you can make more general (and more advanced) queries from
> Would be interested to hear some more feedback from people!
> Cheers,
> Daniel
> _______________________________________________
> wayland-devel mailing list
> wayland-devel at

More information about the wayland-devel mailing list