On 18/09/16 13:48 +0100, Jonathan Wakely wrote:
On 17/09/16 08:46 -0600, Kevin Fenzi wrote:
On Sat, 17 Sep 2016 15:30:34 +0100
Jonathan Wakely <jwak...@fedoraproject.org> wrote:

On 16/09/16 12:55 -0600, Kevin Fenzi wrote:
On Fri, 16 Sep 2016 10:54:57 -0500
Michael Catanzaro <mcatanz...@gnome.org> wrote:

On Fri, 2016-09-16 at 10:33 +0100, Jonathan Wakely wrote:
> Given how hard it is to enable those notifications correctly, we
> should just enable them by default for everyone. Or at least for
> anyone maintaining a critpath package (which are the only ones
> being abichecked today anyway).

FWIW gave up trying to configure my notifications and just turned
them all off. Last time I checked, I couldn't find a way to
configure notifications on a package-specific basis. The flood of
notifications from packages I have commit access to but don't want
to receive notifications for was pretty overwhelming.

I know a lot of folks find it difficult to configure.

I proposed some docs changes that might (I hope) help people:


Other suggestions to make it easier welcome.

Fixing the 404 for the taskotron docs would help :-)

Can you be more specific? "The taskotron docs" ?


See the specifics I gave in

The "Particular taskotron task outcome" rule has a link to "the
libtaskotron documentation" which links to
which gives a 404.

It appears that the link is missing "docs/" as this looks like the
relevant documentation:

I tried looking in fmn.web for that link, but it doesn't seem to come
from there, so I can't send a github pull request with a fix.
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Reply via email to