Hi Karanbir,<br><br><div class="gmail_quote">2011/1/5 Karanbir Singh <span dir="ltr">&lt;<a href="mailto:mail-lists@karan.org">mail-lists@karan.org</a>&gt;</span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">

[...]<br>
The development for CentOS is no more open or closed than anything that<br>
can and should be reasonably expected from what the input to the process<br>
and the output from the process is. Also think about exactly &#39;what&#39; the<br>
testing could and should entail, how it might run w.r.t timescales and<br>
what the feedback loop should be. Feel free to elaborate and quantify<br>
that. eg. Having been on the QA team for &#39;years&#39;, how many patches did<br>
you send through ?<br>
[...]<br></blockquote><div><br>the process could be more open, see SL i.e., but regardless how open the process is, due to the fact that no alpha, beta whatever relaeases are in the wild it is not possible to test the current state, check for errors and report these to some point like a Bugzilla. As far as I understood from the website, this is only possible for QA members, not normal users. The next thing is that I can&#39;t start testing CentOS in live environments before the final version is out (which is odd for things like Puppet, Cobbler or so).<br>

 <br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
&gt; Are there any plans to tackle the human bottleneck issues within the<br>
&gt; CentOS development process?<br>
Absolutely, but tackle them by doing the right thing - and finding<br>
people who both (a) know what they are doing, (b) understand the CentOS<br>
process and (c) are able to bring a certain trust level to the community<br>
of users.<br></blockquote><div><br>Why not an open approach. I&#39;m pretty sure there are a lot of people outside with a lot of knowledge who are able to support the rebuild of RHEL6 with patches, reports or whatever if there is a simple an fast way to send these information to some point (at least I can do such things but I don&#39;t have the time to be a full QA member).<br>

 <br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
[...]<br>
The aim was to focus people&#39;s attention to the upstream beta, better<br>
product and that loop etc. We could have started earlier, sure. But now<br>
that we have started 2 months back and your own contribution status<br>
stays at nil, why are you interested ?<br></blockquote><div><br>How and what should be contributed if the normal user didn&#39;t even know what problems remains?<br><br>Kind regards, Thomas<br>
</div></div>