1<!doctype html PUBLIC "-//W3C//DTD HTML 3.2 Final//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</head> 10<body> 11 12<h2>Feedback</h2> 13 14By now, I've invested a fair amount of time in <b>ProGuard</b>. You can help 15by providing feedback! If you have problems, bugs, bug fixes, ideas, 16encouragements, etc., please let me know: 17<p> 18<ul> 19<li>The <a href="http://sourceforge.net/forum/forum.php?forum_id=182456" 20 target="other">help forum</a> (at SourceForge) is the right place to ask 21 questions about any problems you might have configuring and running 22 <b>ProGuard</b>. 23 <p> 24 25<li>The <a href="http://sourceforge.net/forum/forum.php?forum_id=182455" 26 target="other">open discussion forum</a> (at SourceForge) offers a place 27 to share your thoughts and discuss new ideas. 28 <p> 29 30<li>The <a 31 32 href="http://sourceforge.net/tracker/?atid=474704&group_id=54750&func=browse" 33 target="other">bug tracking page</a> (at SourceForge) allows you to submit 34 and consult bug reports. Please make sure the reports are complete and 35 concise. If I can't reproduce the problem, I most likely can't fix it 36 either. 37 <p> 38 39<li>The <a 40 41 href="http://sourceforge.net/tracker/?atid=474707&group_id=54750&func=browse" 42 target="other">feature request page</a> (at SourceForge) allows you to 43 submit and consult feature requests. I generally have my own road map in 44 mind, but this is the place express your interest in new and existing 45 ideas. 46 <p> 47 48<li>The <a href="http://sourceforge.net/project/showfiles.php?group_id=54750" 49 target="other">download section</a> at SourceForge and the <a 50 href="http://software.freshmeat.net/projects/proguard/" 51 target="other">project page</a> at FreshMeat offer the possibility to 52 subscribe to the announcements of new releases. They are the most 53 efficient way to stay abreast of the latest developments. 54 <p> 55 56<li>For anything that doesn't fall in the above categories, you can mail me 57 directly at 58 59<script type="text/javascript" language="JavaScript"> 60<!-- 61document.write("<a href=\"ma"); 62document.write("ilto:"); 63document.write("lafortune"); 64document.write("@"); 65document.write("users.sourceforge.net\">"); 66document.write("lafortune"); 67document.write("@"); 68document.write("users.sourceforge.net"); 69document.write("</a>"); 70document.write(" <em>or</em> at "); 71document.write("<a href=\"ma"); 72document.write("ilto:"); 73document.write("eric"); 74document.write("@"); 75document.write("graphics.cornell.edu\">"); 76document.write("eric"); 77document.write("@"); 78document.write("graphics.cornell.edu"); 79document.write("</a>"); 80//--> 81</script> 82<noscript> 83< lafortune @ users . sourceforge . net > 84<em>or</em> at 85< eric @ graphics . cornell . edu > (please remove the spaces) 86</noscript> 87. 88</ul> 89<p> 90I can't promise a swift answer, or any answer at all, for that matter, but I 91like seeing any constructive comments. 92<p> 93 94<b>ProGuard</b> isn't a typical open source project, in the sense that I am 95<em>not</em> looking for code contributions. Developing on my own allows me to 96do things my way, without the overhead and compromises associated with larger 97projects. 98 99<hr> 100<address> 101Copyright © 2002-2009 102<a href="http://www.graphics.cornell.edu/~eric/">Eric Lafortune</a>. 103</address> 104 105</body> 106</html> 107