<HTML><HEAD></HEAD>
<BODY dir=ltr>
<DIV dir=ltr>
<DIV style="FONT-FAMILY: 'Calibri'; COLOR: #000000; FONT-SIZE: 12pt">
<DIV>
<DIV
style="FONT-STYLE: normal; DISPLAY: inline; FONT-FAMILY: 'Calibri'; COLOR: #000000; FONT-SIZE: small; FONT-WEIGHT: normal; TEXT-DECORATION: none">>>>
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>>>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></DIV>
<DIV class=gmail_quote>
<DIV> </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> </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> </DIV>
<DIV>>The more the mythtv community seems alive, the more people it will
attract.</DIV>
<DIV> </DIV>
<DIV>I’m not quite sure how to respond to someone who tells me the best way I
can help the community is to respond in the mailing list and file bugs by
quoting one of my responses in the mailing list with a link to my one of my bug
reports..... </DIV>
<DIV> </DIV>
<DIV>FWIW, I have and do edit the wiki when I come across something lacking,
incorrect or out dated. Having said that, I rarely use the wiki because my
system has been up and running for several years and I mostly tend to find bugs
now with new versions....when it breaks something that previously worked.
I have filed many bug reports and provided as much information as possible when
requested. I’ll never develop a theme, because I find stick men
challenging.</DIV>
<DIV> </DIV>
<DIV>Regardless of that, the “If you don’t like it, you can always ask for your
money back” responses are EQUALLY as useless as complaining without being
willing to try to help.</DIV></DIV></DIV></DIV></DIV></BODY></HTML>