> > Well, are we sure now how exactly the client setup process will be > > hooked into taskotron or its underlying tools? > > I'm not exactly sure how this will work, either. It's going to depend > on what we end up using for graphical testing, what openstack is > capable of, what cloud resources we have access to and what the cloud > SIG ends up needing for their testing. > > > Are we committed to using buildbot, or might it change? > > I don't really see how this is relevant. Can you elaborate on how using > buildbot or not would factor in here?
Hmm. In AutoQA, we used Autotest for managing test clients. Any disposable client support would most probably needed some support in Autotest. I assumed it's the same for Buildbot. Instead of using a pre-defined machine, it will need to be able to say "you there, create me a machine matching these requirements; zzz; thank you". > > So, two different systems (i.e. two different databases) displayed in > > a single web frontend, right? I guess it makes sense. > > Yeah, that's what I had in mind, anyways. > > Since student registration has started, I'd like to get our proposed > ideas in the wiki soon. The question of whether any of these projects > would be worth distracting folks from other dev/testing work remains - > any thoughts on that front? So far it seems you're the only candidate for mentoring, you it's probably up to your decision and past experience. Of course any of us will help the student when needed, but I assume most of the communication will be between the mentor and the student. Josef says that he recommend picking a project for which we don't need to spend weeks to introduce and explain to the student the whole project, our needs, etc. Something that is simple to explain, and can be implemented without being blocked on us. > > It sounds like the results middleware project, the graphical > installation project, the gnome-continuous project and _maybe_ the > disposable client project are the best candidates. Any thoughts on the > value for those? I don't know much about gnome-continuous, but the rest of the projects you mentioned really seems to be the best picks. Results middleware is probably closest to Josef, graphical testing is closest to me and disposable clients is closest to you. When it comes to importance, disposable clients have probably the highest priority, then results middleware, and then comes the rest. But that's just my guesses. _______________________________________________ qa-devel mailing list qa-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/qa-devel
