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<!-- 11if (window.self==window.top) 12 window.top.location.replace("index.html#"+window.location.pathname+window.location.hash); 13else { 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 25By now, I've invested an enormous amount of time in <b>ProGuard</b>. You can 26help by providing feedback! If you have problems, bugs, bug fixes, ideas, 27encouragements, etc., please let me know: 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) 38 and <a href="http://stackoverflow.com/questions/tagged/proguard" 39 target="other">Stack Overflow</a> are common places to ask questions about 40 any problems you might have configuring and running ProGuard. At this 41 time, I can generally only assist other open source projects though. If 42 you're working on commercial software, please consider our professional 43 support above.</li> 44 45<li>The <a href="https://sourceforge.net/projects/proguard/forums/forum/182455" 46 target="other">open discussion forum</a> (at SourceForge) offers a place 47 to share your thoughts and discuss new ideas.</li> 48 49<li>The <a href="http://sourceforge.net/p/proguard/bugs/" target="other">bug 50 tracking page</a> (at SourceForge) allows you to submit and consult bug 51 reports. Please make sure the reports are complete and concise. If I can't 52 reproduce the problem, I most likely can't fix it either.</li> 53 54<li>The <a href="http://sourceforge.net/p/proguard/feature-requests/" 55 target="other">feature request page</a> (at SourceForge) allows you to 56 submit and consult feature requests. I generally have my own road map in 57 mind, but this is the place express your interest in new and existing 58 ideas.</li> 59 60<li>The <a href="https://sourceforge.net/projects/proguard/files/" 61 target="other">download section</a> at SourceForge and the <a 62 href="http://software.freecode.com/projects/proguard" 63 target="other">project page</a> at Freecode (Freshmeat) offer the 64 possibility to subscribe to the announcements of new releases. They are 65 the most efficient way to stay abreast of the latest developments.</li> 66 67<li>For anything that doesn't fall in the above categories, you can mail me 68 directly at 69 70<script type="text/javascript" language="JavaScript"> 71<!-- 72document.write("<a href=\"ma"); 73document.write("ilto:"); 74document.write("lafortune"); 75document.write("@"); 76document.write("users.sourceforge.net\">"); 77document.write("lafortune"); 78document.write("@"); 79document.write("users.sourceforge.net"); 80document.write("</a>"); 81document.write(" <em>or</em> at "); 82document.write("<a href=\"ma"); 83document.write("ilto:"); 84document.write("eric"); 85document.write("@"); 86document.write("graphics.cornell.edu\">"); 87document.write("eric"); 88document.write("@"); 89document.write("graphics.cornell.edu"); 90document.write("</a>"); 91//--> 92</script> 93<noscript> 94< lafortune @ users . sourceforge . net > 95<em>or</em> at 96< eric @ graphics . cornell . edu > (please remove the spaces) 97</noscript> 98.</li> 99</ul> 100<p> 101I can't promise a swift answer, or any answer at all, for that matter, but it's 102always great to see constructive comments. 103<p> 104 105<b>ProGuard</b> isn't a typical open source project, in the sense that I am 106<em>not</em> looking for code contributions. Developing on my own allows me to 107do things my way, without the overhead and compromises associated with larger 108projects. 109 110<hr /> 111<noscript><div><a target="_top" href="index.html" class="button">Show menu</a></div></noscript> 112<address> 113Copyright © 2002-2013 114<a target="other" href="http://www.lafortune.eu/">Eric Lafortune</a>. 115</address> 116 117</body> 118</html> 119