Home | History | Annotate | Download | only in docs 
      1 <!doctype html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
      2 <html>
      3 <head>
      4 <meta http-equiv="content-type" content="text/html; charset=iso-8859-1">
      5 <meta http-equiv="content-script-type" content="text/javascript">
      6 <meta http-equiv="content-style-type" content="text/css">
      7 <link rel="stylesheet" type="text/css" href="style.css">
      8 <title>ProGuard Feedback</title>
      9 <script type="text/javascript" language="JavaScript">
     10 <!--
     11 if (window.self==window.top)
     12   window.top.location.replace("index.html#"+window.location.pathname+window.location.hash);
     13 else {
     14   var hash="#"+window.location.pathname.replace(window.top.location.pathname.replace("index.html", ""), "");
     15   if (window.top.location.hash!=hash)
     16     window.top.location.hash=hash;
     17 }
     18 //-->
     19 </script>
     20 </head>
     21 <body>
     22 
     23 <h2>Feedback</h2>
     24 
     25 By now, I've invested a fair amount of time in <b>ProGuard</b>. You can help
     26 by providing feedback! If you have problems, bugs, bug fixes, ideas,
     27 encouragements, etc., please get in touch:
     28 <p>
     29 <ul class="spacious">
     30 <li>Through
     31     <a href="http://www.saikoa.com/proguard/support" target="_top">Saikoa</a>,
     32     we provide professional support for ProGuard. If you find ProGuard useful
     33     and you would like to have some professional backing, this is the place to
     34     go.</li>
     35 
     36 <li>The <a href="https://sourceforge.net/projects/proguard/forums/forum/182456"
     37     target="other">help forum</a> (at SourceForge) is the right place to ask
     38     questions about any problems you might have configuring and running
     39     ProGuard. At this time, I can generally only assist other open source
     40     projects though. If you're working on commercial software, please consider
     41     our professional support above.</li>
     42 
     43 <li>The <a href="https://sourceforge.net/projects/proguard/forums/forum/182455"
     44     target="other">open discussion forum</a> (at SourceForge) offers a place
     45     to share your thoughts and discuss new ideas.</li>
     46 
     47 <li>The <a
     48     href="http://sourceforge.net/tracker/?atid=474704&group_id=54750&func=browse"
     49     target="other">bug tracking page</a> (at SourceForge) allows you to submit
     50     and consult bug reports. Please make sure the reports are complete and
     51     concise. If I can't reproduce the problem, I most likely can't fix it
     52     either.</li>
     53 
     54 <li>The <a
     55 
     56     href="http://sourceforge.net/tracker/?atid=474707&group_id=54750&func=browse"
     57     target="other">feature request page</a> (at SourceForge) allows you to
     58     submit and consult feature requests. I generally have my own road map in
     59     mind, but this is the place express your interest in new and existing
     60     ideas.</li>
     61 
     62 <li>The <a href="https://sourceforge.net/projects/proguard/files/"
     63     target="other">download section</a> at SourceForge and the <a
     64     href="http://software.freshmeat.net/projects/proguard/"
     65     target="other">project page</a> at FreshMeat offer the possibility to
     66     subscribe to the announcements of new releases. They are the most
     67     efficient way to stay abreast of the latest developments.</li>
     68 
     69 <li>For anything that doesn't fall in the above categories, you can mail me
     70     directly at
     71 
     72 <script type="text/javascript" language="JavaScript">
     73 <!--
     74 document.write("<a href=\"ma");
     75 document.write("ilto:");
     76 document.write("lafortune");
     77 document.write("&#64;");
     78 document.write("users.sourceforge.net\">");
     79 document.write("lafortune");
     80 document.write("&#64;");
     81 document.write("users.sourceforge.net");
     82 document.write("</a>");
     83 document.write(" <em>or</em> at ");
     84 document.write("<a href=\"ma");
     85 document.write("ilto:");
     86 document.write("eric");
     87 document.write("&#64;");
     88 document.write("graphics.cornell.edu\">");
     89 document.write("eric");
     90 document.write("&#64;");
     91 document.write("graphics.cornell.edu");
     92 document.write("</a>");
     93 //-->
     94 </script>
     95 <noscript>
     96 &lt;&nbsp;lafortune&nbsp;&#64;&nbsp;users&nbsp;.&nbsp;sourceforge&nbsp;.&nbsp;net&nbsp;&gt;
     97 <em>or</em> at
     98 &lt;&nbsp;eric&nbsp;&#64;&nbsp;graphics&nbsp;.&nbsp;cornell&nbsp;.&nbsp;edu&nbsp;&gt; (please remove the spaces)
     99 </noscript>
    100 .</li>
    101 </ul>
    102 <p>
    103 I can't promise a swift answer, or any answer at all, for that matter, but I
    104 like seeing any constructive comments.
    105 <p>
    106 
    107 <b>ProGuard</b> isn't a typical open source project, in the sense that I am
    108 <em>not</em> looking for code contributions. Developing on my own allows me to
    109 do things my way, without the overhead and compromises associated with larger
    110 projects.
    111 
    112 <hr />
    113 <noscript><div><a target="_top" href="index.html" class="button">Show menu</a></div></noscript>
    114 <address>
    115 Copyright &copy; 2002-2011
    116 <a target="other" href="http://www.lafortune.eu/">Eric Lafortune</a>.
    117 </address>
    118 
    119 </body>
    120 </html>
    121