On Thu, Feb 04, 2016 at 08:59:32AM -0700, Kevin Fenzi wrote: > On Thu, 4 Feb 2016 10:57:22 +0100 > Pierre-Yves Chibon <pingou@xxxxxxxxxxxx> wrote: > > > On Wed, Feb 03, 2016 at 04:59:29PM -0700, Kevin Fenzi wrote: > > > On Tue, 2 Feb 2016 16:19:36 +0100 > > > Pierre-Yves Chibon <pingou@xxxxxxxxxxxx> wrote: > > > > > > > That's not currently there, I do think people @mentioned in a > > > > ticket should be added, but it's not there yet. As for batch or > > > > CC'ing a group, it'd be a second stage. > > > > > > > > I added a ticket to trac the @mention question : > > > > https://pagure.io/pagure/issue/690 > > > > > > ok. > > > > > > The always cc/bcc thing gets used by a lot of trac's where some > > > group of people always want to get all traffic. For example, I get > > > all infrastructure trac ticket changes and it's very handy to keep > > > track of whats being updated. > > > > Oh we can easily do that with FMN: Get all the notification about the > > project `foo` or the projects tagged `bar`. That's even how we do the > > notifications on #fedora-apps > > Sure, although how do we handle 'private/sensitive' issues? Project admins get notifications for everything happening in their projects, which I realize now is even better than the FMN approach I described above :) > ...snip... > > > Oh, I just thought of one other thing: rss feeds? For > issues, prs, > > > etc? > > > > > > In fact that could possibly take the place of always cc/bcc > > > (although rss feeds likely wouldn't have the private/sensitive > > > tickets perhaps). > > > > > > Some of our trac instances use rss to update via zodbot to irc. > > > > Hm, I guess this should be a doable, would the rss feed have only the > > tickets created or also the comments on tickets? > > Seperate feeds I would say... one for ticket status (created, closed, > add tag) and one for comments? Or take the bodhi approach and make > everything seperate rss feeds. ;) We should make a ticket of this :) Pierre
Attachment:
pgp77JuPZp9Fm.pgp
Description: PGP signature
_______________________________________________ infrastructure mailing list infrastructure@xxxxxxxxxxxxxxxxxxxxxxx http://lists.fedoraproject.org/admin/lists/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
