fedmsg notifications

[Ralph Bean]

I started brainstorming some ideas for a general end-user
notification system driven by fedmsg and wrote up my notes here:
https://github.com/fedora-infra/fedmsg-notifications#fedmsg-notifications

I got down to the part about how to specify a users profile when I had
to stop and begin considering all the different notification scenarios
we might want.  I kind of roadblocked on it and I thought I'd write
the list to see what kind of notification capabilities we might want
to have.

Let's just use "email" as our example here: what kinds of
"emails"
might users want to receive?

- Emails when your koji build finishes.
- Emails when a koji build for a certain package finishes.
- Emails when any package that you own in pkgdb has a change made to
  it.

... hopefully you get the idea.  It would be a help if you could write
the list (or me) with "scenarios" that are important to you.  That
will help me figure out what kind of representation I would need in
the database to handle all these cases.

[Clint Savage]

I would want to be able to query the system for a status. I kind of
think of the life cycle of a package. So I would want to ask fedmsg to
tell me about pkg a and what is it's current status. I might get
something back like:

2013-01-21 11:01:34 pkg-0.31-1 submitted to dist-git
2013-01-21 14:23:44 pkg-0.31-1 submitted for build on builda.fp.o
2013-01-21 14:27:00 pkg-0.31-1.src.rpm build complete
2013-01-21 14:27:45 pkg-0.31-1.fc18.x86_64 submitted on buildb.fp.o
2013-01-21 14:27:48 pkg-0.31-1.fc18.i686 submitted on buildc.fp.o
---End of History---

Clearly, there could be more to it, like bodhi approvals and statuses
too. I just think it'd be cool to see the history in one place. If the
status changes, I might want to know about it. Or I might want a
summary of the entire process from start to finish. Maybe it would be
good to make it possible for someone to define a set of data they want
to know and aggregate that report into a db. Once it hits the end
state have it sent along to the requestor.

I'm sure others have more/better thoughts on this, but I think these
would be useful to me in terms of packaging.

Cheers,

herlo

On Mon, Jun 10, 2013 at 2:35 PM, Ralph Bean <ralph.bean(a)gmail.com&gt; wrote:
>  I started brainstorming some ideas for a general end-user
>  notification system driven by fedmsg and wrote up my notes here:
>  https://github.com/fedora-infra/fedmsg-notifications#fedmsg-notifications
>
>  I got down to the part about how to specify a users profile when I had
>  to stop and begin considering all the different notification scenarios
>  we might want.  I kind of roadblocked on it and I thought I'd write
>  the list to see what kind of notification capabilities we might want
>  to have.
>
>  Let's just use "email" as our example here: what kinds of
> "emails"
>  might users want to receive?
>
>  - Emails when your koji build finishes.
>  - Emails when a koji build for a certain package finishes.
>  - Emails when any package that you own in pkgdb has a change made to
>    it.
>
>  ... hopefully you get the idea.  It would be a help if you could write
>  the list (or me) with "scenarios" that are important to you.  That
>  will help me figure out what kind of representation I would need in
>  the database to handle all these cases.
>
>  _______________________________________________
>  infrastructure mailing list
>  infrastructure(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/infrastructure

[Ralph Bean]

On Mon, Jun 10, 2013 at 04:08:41PM -0600, Clint Savage wrote:
>  I would want to be able to query the system for a status. I kind of
>  think of the life cycle of a package. So I would want to ask fedmsg to
>  tell me about pkg a and what is it's current status. I might get
>  something back like:
>  
>  2013-01-21 11:01:34 pkg-0.31-1 submitted to dist-git
>  2013-01-21 14:23:44 pkg-0.31-1 submitted for build on builda.fp.o
>  2013-01-21 14:27:00 pkg-0.31-1.src.rpm build complete
>  2013-01-21 14:27:45 pkg-0.31-1.fc18.x86_64 submitted on buildb.fp.o
>  2013-01-21 14:27:48 pkg-0.31-1.fc18.i686 submitted on buildc.fp.o
>  ---End of History--- 
You can actually already do this!  :)  I just wrote up and posted an
example of how:
http://threebean.org/blog/querying-datagrepper-example/

[Ralph Bean]

On Mon, Jun 10, 2013 at 04:08:41PM -0600, Clint Savage wrote:
>  I would want to be able to query the system for a status. I kind of
>  think of the life cycle of a package. So I would want to ask fedmsg to
>  tell me about pkg a and what is it's current status. I might get
>  something back like:
>  
>  2013-01-21 11:01:34 pkg-0.31-1 submitted to dist-git
>  2013-01-21 14:23:44 pkg-0.31-1 submitted for build on builda.fp.o
>  2013-01-21 14:27:00 pkg-0.31-1.src.rpm build complete
>  2013-01-21 14:27:45 pkg-0.31-1.fc18.x86_64 submitted on buildb.fp.o
>  2013-01-21 14:27:48 pkg-0.31-1.fc18.i686 submitted on buildc.fp.o
>  ---End of History--- 
You can actually already do this!  I just wrote up an example on how:
http://threebean.org/blog/querying-datagrepper-example/

[Kevin Fenzi]

On Mon, 10 Jun 2013 16:35:46 -0400
Ralph Bean <ralph.bean(a)gmail.com&gt; wrote:

>  I started brainstorming some ideas for a general end-user
>  notification system driven by fedmsg and wrote up my notes here:
>  https://github.com/fedora-infra/fedmsg-notifications#fedmsg-notifications
>  
>  I got down to the part about how to specify a users profile when I had
>  to stop and begin considering all the different notification scenarios
>  we might want.  I kind of roadblocked on it and I thought I'd write
>  the list to see what kind of notification capabilities we might want
>  to have.
>  
>  Let's just use "email" as our example here: what kinds of
> "emails"
>  might users want to receive?
>  
>  - Emails when your koji build finishes.
>  - Emails when a koji build for a certain package finishes.
>  - Emails when any package that you own in pkgdb has a change made to
>    it.
>  
>  ... hopefully you get the idea.  It would be a help if you could write
>  the list (or me) with "scenarios" that are important to you.  That
>  will help me figure out what kind of representation I would need in
>  the database to handle all these cases. 
Here's some things I would think would be of interest: 

- When composes finish syncing
- When a wiki page you are 'watching' is edited
- When someone asks a ask question with "regex" in the title. 
- Bodhi comment on package
- New source upload for package
- Planet post with 'regex' in title
- When package gets stable karma
- When any Bodhi comment is -1 karma
- It would awesome to get an email when your package is in buildroot
  override, but I don't think we have enough info from fedmsg to tell
  that, or do we?

kevin