On Mon, Nov 2, 2015 at 10:35 AM, Matthias Klumpp <matth...@tenstral.net> wrote:
> 2015-11-01 22:31 GMT+01:00 Albert Astals Cid <aa...@kde.org>:
>> El Sunday 01 November 2015, a les 21:17:03, Ben Cooksley va escriure:
>>> On Fri, Oct 30, 2015 at 12:52 AM, Martin Graesslin <mgraess...@kde.org>
>> wrote:
>>> > On Thursday, October 29, 2015 12:31:23 PM CET Milian Wolff wrote:
>>> >> > In general, can we configure Phabricator somehow to be more open _by
>>> >> > default_? I don't want to force people to login just to look at what's
>>> >> > going on in KDE land.
>>> >>
>>> >> ^-- this becomes more relevant now. If, by default, everything is public
>>> >> then issues such as the one above don't occur. Can we configure that
>>> >> somehow?
>>> >
>>> > +1 for open by default (if that's possible)
>>>
>>> Unfortunately Phabricator does not permit you to change the defaults
>>> of Panels at this time, at least with the version we are running.
>>> Unless i've missed something that is.
>>
>> Forcing people to log in just to have a peek is indeed not nice, have we 
>> asked
>> upstream about it?
>
> Actually, Phabricator has very fine-grained permission control. We use
> that at Tanglu (http://tracker.tanglu.org).
> Just switch the policy.allow-public setting to true, and the use the

That is already enabled.

> Applications panel to limit write access to Phabricator modules to
> specific users or groups or project members (or any combination of
> those).

Unfortunately the Dashboard application settings do not allow changing
the default permissions for Panels / Dashboards.

> Cheers,
>     Matthias

Thanks,
Ben

>
> --
> Debian Developer | Freedesktop-Developer
> I welcome VSRE emails. See http://vsre.info/
>
>>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Reply via email to