<br><br><div class="gmail_quote">On Fri, Oct 5, 2012 at 11:23 PM, Gary Buhrmaster <span dir="ltr"><<a href="mailto:gary.buhrmaster@gmail.com" target="_blank">gary.buhrmaster@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Fri, Oct 5, 2012 at 3:31 PM, Scott harris <<a href="mailto:scott.harris0509@gmail.com">scott.harris0509@gmail.com</a>> wrote:<br>
.....<br>
<div class="im">> Though I'm sure it's meaningless to the profoundly useful "if you don't like<br>
> it ask for your money back" types that so frequently crop up in the Open<br>
> Source community, who seem to have the attitude "if you can't fix it or<br>
> patch it, keep quiet", I did what I am capable of doing a while ago....<br>
><br>
> <a href="http://code.mythtv.org/trac/ticket/11119#comment:3" target="_blank">http://code.mythtv.org/trac/ticket/11119#comment:3</a><br>
<br>
</div>And while reports of bugs are useful, there are probably other things<br>
you *could* do, but have not chosen to do. Not everyone can code<br>
c++/qt. But perhaps you can create a theme. Perhaps you can<br>
update the wiki (there is a bit of "stuff" that is old/obsolete/wrong).<br>
Even if you cannot code, you could contribute some QA resources<br>
for every patch by committing a development system and your time.<br>
Perhaps you could look into assisting with various distro packaging.<br>
Perhaps you can help others on the user list with obscure questions<br>
(freeing Mike's time:-). Last I looked, the doxygen output was still a<br>
bit incomplete (that was being nice to it), and Improving developer<br>
documentation for the coder developers helps them get things done<br>
faster (and perhaps allows them to get to your issue). And, of course,<br>
if you want your bug/feature to gain priority, hire a contractor to work<br>
on it (the wiki tells you where to post, and I would guess a number of<br>
the "developers for rent" companies would gladly take your money too).<br>
The developers have consistently said they do want bug reports, but<br>
if/when they get looked at or addressed will totally depend on the<br>
time/energy available to the volunteers. The reality is that the more<br>
that you contribute, the more you are part of the supporting community<br>
and the more likely it is that your issue will be considered a higher<br>
priority (you scratch their back, they will scratch your back).<br></blockquote><div><br></div><div>"The reality is that the more that you contribute, the more you are part of the supporting community and the more likely it is that your issue will be considered a higher priority (you scratch their back, they will scratch your back)."</div>
<div><br></div><div>I completely agree with Gary's statement above. Even if you can't code, you can:</div><div>1. respond to questions on IRC or the MAILING LIST.</div><div>2. edit the wiki pages, <a href="http://mythtv.org/wiki">http://mythtv.org/wiki</a></div>
<div>3. File bugs.</div><div>4. document how you resolve issues and publish it, so others can follow.</div><div><br></div><div>The more the mythtv community seems alive, the more people it will attract.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class="HOEnZb"><font color="#888888"><br>
Gary<br>
</font></span><div class="HOEnZb"><div class="h5">_______________________________________________<br>
mythtv-users mailing list<br>
<a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br>
<a href="http://www.mythtv.org/mailman/listinfo/mythtv-users" target="_blank">http://www.mythtv.org/mailman/listinfo/mythtv-users</a><br>
</div></div></blockquote></div><br>