and added some basic info and FAQ. I did that mainly because I was dealing with a flood of email notifications lately and wanted to reduce it. Some of you might find it helpful as well.
After a conversation with Kamil earlier today, I started looking into
making our phabricator instance a bit more public friendly.
Blender's instance is a good example of what I'd like to see ours do in
terms of sidebar configuration and public landing page:
The awesome part is that the blender folks keep their modifications in
a public repo as a branch of the upstream phabricator code, so figuring
out how they got it to work is possible :)
I was able to get the root uri display a similar page as what a logged
in user can see:
It does require hacking on the code and as near as I can tell, the
changes can't be done as an extension. The changes are pretty sane,
though so I'll start a conversation with upstream on whether they'd be
interested in a patch.
Changing the sidebar layout, however, is a different story. The
placement logic uses metadata in the code to determine where the icons
are placed and how big they are. This is great from a dev point of view
because you don't need any crazy logic for layout or need to update it
all the time. Not so much if you want to change the default layout,
If we want to change the default layout, I see 3 options:
1. maintain an out-of-band patch that either changes the application
metadata so that the display works how we want or change the display
logic so that it works differently.
This is how the blender instance is set up - they changed the
metadata in applications so that they would be rendered differently
from the defaults. Not the prettiest thing ever but reasonably
maintainable and effective. I suspect this would cause problems
with any custom layouts that folks set, though.
2. hack a hard-coded default into the display logic, overriding the
current logic-based defaults.
This should allow for users to customize the sidebar as they want
while not being a terrible hack. It would require more work and a
decent understanding of the codebase, though. I also suspect that
maintenance would be a bit more difficult.
3. Work with upstream (if they're interested) on a way to set a default
layout for the sidebar.
This would be quite a bit of work, assuming that upstream would
even be interested in the functionality. It would be most likely to
not cause maintenance headaches in the future, though.
If we're going to change the sidebar layout, I'm of the opinion that
option 1 is the best for us, for now. We're already on a tight deadline
and I don't want to spend too much more time hacking on support tools
right now. FAS auth integration is already going to take some work, so
there's that task for the near future as well but phabricator already
has persona auth support and I'm not expecting that task to be terrible.
I wonder if we should enable authentication through providers like GitHub instead of just username/password (and FAS in the future). This would make it easier for non-fas users to report bugs or contribute to the project. I also noticed that anonymous access to view tickets is possible but one need to know the link, is there a way to fix this?
I just tried to create a ticket in Phab. I understand that the Project field is similar to Component field that we used in Trac. (It's a bit unfortunate that a project can't be further separated into components). However, there's no text completion in that field unless you type in something. There's no list of projects nearby (unless you know which icon to click in Phab and find it in a separate page). I'm a bit afraid that people won't be able to report bugs in Phab unless it's easy to find "taskotron" or something through the Project field.
Sure, I assume we can provide custom URLs which fill in the project field through GET arguments, but then you need to spread these links everywhere so that people don't find a different way to the system.
Am I missing something?
I was asked to forward this to qa-devel. The tickets are already migrated, but I at least responded to Jan Pazdziora that FAS support should come to Phab soon.
----- Forwarded Message -----
From: "Jan Pazdziora" <jpazdziora(a)redhat.com>
To: "Adam Williamson" <awilliam(a)redhat.com>
Sent: Tuesday, January 21, 2014 8:25:21 AM
Subject: Re: [AutoQA] #220: Check domains of running services after installation
On Mon, Jan 20, 2014 at 10:18:36PM -0000, AutoQA wrote:
> #220: Check domains of running services after installation
> Changes (by adamwill):
> * resolution: => wontfix
> * status: new => closed
> Migrated to Phabricator: https://phab.qadevel.cloud.fedoraproject.org/T67
> Ticket URL: <https://fedorahosted.org/autoqa/ticket/220#comment:5>
so you are closing the tickets and creating new ones, in a system
which apparently does not support FAS so everyone interested in being
still informed about those tickets should create yet another account
in yet another system du jour?
Principal Software Engineer, Identity Management Engineering, Red Hat