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@xxxxxxxxx> 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@xxxxxxxxxxxxxxxxxxxxxxx > https://admin.fedoraproject.org/mailman/listinfo/infrastructure _______________________________________________ infrastructure mailing list infrastructure@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/infrastructure
