Recently, I threw out an idea on how we might be able to do "User Driven Testing" with some new code on both the client and server side, to leverage our existing userbase to test package updates.
I've documented the framework of this here: https://fedoraproject.org/wiki/User_Driven_Testing
As Colin Walters pointed out "This needs to go through the Fedora Design group.", and as Greg DeKoenigsberg wrote "I think it's big enough that it would be worth organizing a FAD for. It's exactly the kind of 'infrastructure of participation' solution that requires significant investment, but drives major change."
I agree whole-heartedly with both of them. So, let's do a FAD and see if over the course of a few days (possibly as much as 5), we can hash out a solid design and the basis of an implementation.
Schedule-wise, I'm looking at sometime between June and September 2010. If you're interested in participating, please either reply here, or let me know offlist. We'll figure out where the best location for this is when we have an idea of who wants to participate. Also, if you want to participate, but have specific dates which will not work, be sure to state that too.
This isn't just for Red Hat folks either! If you want to help, please, chime in!
Thanks,
~spot
On Wednesday 31 March 2010 02:42:56 pm you wrote:
Recently, I threw out an idea on how we might be able to do "User Driven Testing" with some new code on both the client and server side, to leverage our existing userbase to test package updates.
I've documented the framework of this here: https://fedoraproject.org/wiki/User_Driven_Testing
As Colin Walters pointed out "This needs to go through the Fedora Design group.", and as Greg DeKoenigsberg wrote "I think it's big enough that it would be worth organizing a FAD for. It's exactly the kind of 'infrastructure of participation' solution that requires significant investment, but drives major change."
I agree whole-heartedly with both of them. So, let's do a FAD and see if over the course of a few days (possibly as much as 5), we can hash out a solid design and the basis of an implementation.
Schedule-wise, I'm looking at sometime between June and September 2010. If you're interested in participating, please either reply here, or let me know offlist. We'll figure out where the best location for this is when we have an idea of who wants to participate. Also, if you want to participate, but have specific dates which will not work, be sure to state that too.
This isn't just for Red Hat folks either! If you want to help, please, chime in!
Thanks,
~spot _______________________________________________ fudcon-planning mailing list fudcon-planning@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/fudcon-planning
Count me in. Anytime is good for me with enough notice to get the time off. For location I vote Raleigh since its home for me. -)
Steven
Schedule-wise, I'm looking at sometime between June and September 2010. If you're interested in participating, please either reply here, or let me know offlist. We'll figure out where the best location for this is when we have an idea of who wants to participate. Also, if you want to participate, but have specific dates which will not work, be sure to state that too.
This actually strikes me as a cool thing that Campus Ambassadors could do to kick off the school year - maybe do a first FAD during the summer (June-Sep) to get a first round up and going, and then student groups can pick it up immediately afterwards (in September, say) and say "okay, cool - let's try this out as a way to get new contributors on our campuses started!" and have people in the background hacking on code and/or docs more if needed.
Campus Ambassadors, for context, the discussion is from: http://lists.fedoraproject.org/pipermail/fudcon-planning/2010-March/000603.h...
--Mel
fudcon-planning@lists.fedoraproject.org