On Fri, 2018-04-13 at 02:12 -0400, Sumantro Mukherjee wrote:
> > I picked 'a month' more or less arbitrarily, 'a week' is certainly an
> > OK choice too. Note that the template really is just a *template*, and
> > can (and should!) be adapted to each event as appropriate. So if *some
> > specific event* is very time sensitive, this text could be changed as
> > appropriate - to say 'a day' or whatever.
> True. I will keep this in mind from next time :)

To be clear, if you wanna change the template to 'a week', that sounds
fine to me.

> > 
> > > # Proposal 2: We would love to see more coverage on the test cases,
> > > let's take Modularity and as an example, Contributors found bugs in
> > > Rpi 3 (ARM) which weren't the case with x86_64, Profile field in the
> > > test day results
> > > page becomes very important and crucial. Maybe, we should avoid
> > > putting "Fedora-Server-dvd-xxxxxyyyyyyz.n.0.iso" which doesn't give
> > > much info about the testing environment or how it was executed. We
> > > might
> > > want to flesh out the importance of that field and it will be very
> > > helpful in coming future.
> > 
> > I'm actually not quite sure what you're referring to here, or where the
> > "Fedora-Server-dvd-xxxxxyyyyyyz.n.0.iso" example comes from. Could you
> > provide a bit more context?
> The context where it stems from was, if you have a look at http://tes
> tdays.fedorainfracloud.org/events/38
> we have mostly all testers, mentioning Fedora 28 Server on
> (KVM,ARM,x86_64,VMware,ppc64le) which gives
> us a bit more idea if there is a failure. Just writing Fedora server
> dvd gives us absolutely no idea as to how the
> test were executed. In one certain case during Modularity test day, a
> certain issue just came up which was specific to
> ARM ... the profile also lets us know about the coverage across archs
> and various virtualizations. I felt, we should,
> flesh out a bit more about the importance of the same.

OK, I see. The tricky part is it's a free text field, so all you can
really do is try to provide very specific instructions for filling it
out in each Test Day page, really clearly explaining what people should
include in it - at least, that's what I'd do.

I suppose we could also enhance the app and the metadata format so the
metadata could specify some 'hint text' for the profile field, or
something like that...

> > Are you saying there should be a specifically-identified 'team' for
> > each individual test day, or an ongoing permanent 'team' for test days
> > as a whole? Either could potentially work, but I think the proposal
> > could do with a few more details...
> No, I am good with either, I am strictly against people editing the 
> organizing list.
> The team is defined and kept there to make sure the contributors know where 
> to come and
> whom to grab hold of , when something is breaking. Randomly editing the 
> section renders to pupose moot.
> Context:
> [http://fedoraproject.org/wiki/Test_Day:2018-02-22_Kernel_4.15_Test_Day] 
> [http://fedoraproject.org/wiki/Test_Day:2018-04-10_Add-On_Modularity_Test_Day]

OK, I see. So perhaps we should edit the template to include an
{{admon}} in that section asking people not to edit it unless they're
really part of the organizing team? Including some text that
specifically says "If you're just joining as a tester, you shouldn't
add yourself here"?

Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org

Reply via email to