<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 26 March 2015 at 17:28, Bojan Smojver <span dir="ltr"><<a href="mailto:bojan@rexursive.com" target="_blank">bojan@rexursive.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">Kevin Fenzi <kevin <at> <a href="http://scrye.com" target="_blank">scrye.com</a>> writes:<br>
<br>
> If you wish to test something before it's fully pushed to testing, you<br>
> can download it directly from the buildsystem via the web interface,<br>
> koji command line or bodhi client command line.<br>
<br>
</span>I am fully aware of that. I'm making a different point entirely here.<br>
<br>
Imagine a regular Fedora user - the one that has no idea about koji. This<br>
regular user wants to contribute by testing packages as they are built. This<br>
user is willing to trust a lower quality key in his/her Software (or<br>
whatever is the current fashion) manager to get the latest stuff, hot off<br>
the presses.<br>
<br>
And yet, such a user would have no idea new packages were available and<br>
would have a hard time (relatively speaking) getting them. So, I'm<br>
suggesting we create a "fastrack" for Fedora, so that more people can do<br>
this and easier. It would be totally optional etc.<br>
<div class="HOEnZb"><div class="h5"><br></div></div></blockquote><div><br><br></div><div>Here is the problems I see with this analogy:<br><br></div><div>1) Most regular users just want to have a system which allows them to surf the web, play some games of solitaire, and possibly read email (if it isn't on the web). This is what the majority of people who use computers want to do.. if the user wants to start testing things.. he is already not a regular user.<br><br></div><div>2) This user who wants to test things is going to need to know a lot of things which having a faster test system isn't going to fix.<br></div><div>A. They need to know how to test the software (oh look it installed.. now what do I do?)<br></div><div>B. They need to know where to report that the software is working or not.<br></div><div>C. They need to know how to get help and/or backout the problem if the software doesn't work.<br><br></div><div>There are probably other things we need them to know if we want any quicker testing process. And working on them would actually be a lot less work than trying to get a fastertrack repo to deal with occasional 2 day delays in pushing to updates-testing. <br></div><div><br> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">
--<br>
Bojan<br>
<br>
--<br>
devel mailing list<br>
<a href="mailto:devel@lists.fedoraproject.org">devel@lists.fedoraproject.org</a><br>
<a href="https://admin.fedoraproject.org/mailman/listinfo/devel" target="_blank">https://admin.fedoraproject.org/mailman/listinfo/devel</a><br>
Fedora Code of Conduct: <a href="http://fedoraproject.org/code-of-conduct" target="_blank">http://fedoraproject.org/code-of-conduct</a></div></div></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature"><div dir="ltr">Stephen J Smoogen.<br><br></div></div>
</div></div>