On Wed, 29 Jun 2016 10:51:13 -0700 Adam Williamson <adamwill@xxxxxxxxxxxxxxxxx> wrote: > On Wed, 2016-06-29 at 18:18 +0200, Adam Samalik wrote: > > Hi everyone, > > > > I would like to hear your opinion/need your help! > > > > I am working on a component of the Fedora Modularity[1] project, > > called Build Pipeline Overview (BPO). It will be a single user > > interface (probably both web and API) that would give you > > information about "everything". And I would like your help with > > defining what that "everything" means. > > > > To make the definition of "everything" easier, we are using a > > concept of personas. These are basically groups of people that > > would use the BPO UI that will help us to identify possible > > use-cases. > > > > @threebean have identified four personas: > > - Engineers/packagers > > - Release Engineering > > - QA > > - Project Management > > > > I have put them into an Etherpad document [2]. > > > > > > What I'm asking from you: Could you please discuss here or in the > > document what would you like to see in the BPO UI? Or what do you > > think should be there. I would like to get as much input as > > possible. > > For the record, as a QA person, I find this kind of squishy 'I'm > building a thing, tell me what it should look like' question just > impossible to answer. I cannot come up with anything until there's > something more concrete to look at. Other QA folks may have better > input, but it would be a good idea to send this mail to test@, since > that is the official QA list. Yeah, it's a bit hard when we don't know what "everything" means here. :) That said a few comments: * Should there be a 'developer' or 'end user' type here? Ie, is it expected that they would want to look at this to see what the latest version of some module they care about is, or if there's new ones that might be coming along soon? Or is that another tool? * Depending again on the kinds of things this can report on, infrastructure might be interested in it. Could we query it via nagios to let us know about problems in module building or testing ? * Modules can depend on other modules right? If so, a way to see that tree of dependencies in building would be nice (ie, moduleA depends on moduleB, and moduleB is currently rebuilding for foo, moduleA should show that it's pending rebuilding after that, etc) I'm not sure I can provide much more until we have more information on what information we can have there. ;) kevin
Attachment:
pgpBrY_oIuEah.pgp
Description: OpenPGP digital signature
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx
