Maybe you can try making a simple SQL database in which people post their results. It should have different tables for different test days. This would allow you to easily sort the data and would not be very difficult to implement.
The advertisement part is easy to do but I think your main problem is collection of data and making that data easily accessible to users.
On Aug 23, 2012 5:03 AM, "Adam Williamson" <awilliam@xxxxxxxxxx> wrote:
On 2012-08-22 2:33, Jóhann B. Guðmundsson wrote:
On 08/22/2012 08:20 AM, Arnav Kalra wrote:
Would this method help?
---------- Forwarded message ----------
From: "Arnav Kalra" <arnavkalra007@xxxxxxxxx [1]>
Date: Aug 21, 2012 8:33 PM
Subject: Re: Helping to improve advertising of test days and other
things
To: "Fedora Marketing team"
If we want a method to aggregate responses we can modify smolt a
bit.
1. Smolt would collect data without user's intervention in test
released and make a profile on a webpage which catalogs test
releases.
2. On this page we can add a few more columns to the table in which
testers write about their test experiences.
3. We can make a page which describes how to test releases as a
page which is displayed when the first time Firefox is started.
4. The qa team sees the results constantly being uploaded on that
page and analyses it together on gobby.
5. I think this would solve a part of the problem.
What do you guys think about it?
I dont think smolt was intended to be used like this + The more
bureaucracy that reporters need to perform will most likely result in
less participation.
The only think the marketing team needs to do is advertise test days
on Twitter G+ Facebook etc.. and notify any media contacts we are in
contact with.
I think I'd agree with Johann on this one - smolt isn't really designed for this and I don't think the smolt maintainers would see it as an appropriate direction for smolt. It's really just meant to be for tracking hardware information.
In addition, I don't think the idea quite lines up with how test days actually work. Test days aren't about doing general testing of pre-release images, they're meant to be for real-time, collaborative testing of specific subject areas. The process described above doesn't really fit into this, so far as I can see.
Thanks a lot for trying to help out, though!
I do quite like one idea from the above in isolation - it might be nice to have the default browser home page in pre-releases point to somewhere which explains how to perform useful testing of pre-releases. Seems logical. We could look into that...
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
--
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
-- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
