Thanks for the response. I agree, asking you "I am building something I haven't described, how do you want to use it?" might have not been the best idea... So please, let me try that again and better. :-)
I have created a wiki page [1] that briefly describes the BPO component, what data would be available, and the main three possible functions. > > * 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? > It would be probably both. But I would focus mainly on developers in the early stage. Later, there might be something similar to what you described for the end user. > > * 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 ? > If you would use something like this, I would be happy to include it in the BPO. > > * 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) > Yes. This should also be there. [1] https://fedoraproject.org/wiki/Modularity/BPO -- Adam Šamalík --------------------------- Associate Software Engineer Red Hat
-- devel mailing list devel@lists.fedoraproject.org https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
