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</head>
10<body>
11
12<script type="text/javascript" language="JavaScript">
13<!--
14if (window.self==window.top)
15  document.write('<a class="largebutton" target="_top" href="index.html#feedback.html">ProGuard index</a> <a class="largebutton" target="_top" href="http://www.saikoa.com/dexguard">DexGuard</a> <a class="largebutton" target="_top" href="http://www.saikoa.com/">Saikoa</a> <a class="largebutton" target="other" href="http://sourceforge.net/projects/proguard/">Sourceforge</a>')
16//-->
17</script>
18<noscript>
19<a class="largebutton" target="_top"  href="index.html#feedback.html">ProGuard index</a>
20<a class="largebutton" target="_top"  href="http://www.saikoa.com/dexguard">DexGuard</a>
21<a class="largebutton" target="_top"  href="http://www.saikoa.com/">Saikoa</a>
22<a class="largebutton" target="other" href="http://sourceforge.net/projects/proguard/">Sourceforge</a>
23</noscript>
24
25<h2>Feedback</h2>
26
27By now, I've invested an enormous amount of time in <b>ProGuard</b>. You can
28help by providing feedback! If you have problems, bugs, bug fixes, ideas,
29encouragements, etc., please let me know:
30<p>
31<ul class="spacious">
32<li>Through
33    <a href="http://www.saikoa.com/proguard/support" target="_top">Saikoa</a>,
34    we provide professional support for ProGuard. If you find ProGuard useful
35    and you would like to have some professional backing, this is the place to
36    go.</li>
37
38<li>The <a href="https://sourceforge.net/projects/proguard/forums/forum/182456"
39    target="other">help forum</a> (at SourceForge)
40    and <a href="http://stackoverflow.com/questions/tagged/proguard"
41    target="other">Stack Overflow</a> are common places to ask questions about
42    any problems you might have configuring and running ProGuard. At this
43    time, I can generally only assist other open source projects though. If
44    you're working on commercial software, please consider our professional
45    support above.</li>
46
47<li>The <a href="https://sourceforge.net/projects/proguard/forums/forum/182455"
48    target="other">open discussion forum</a> (at SourceForge) offers a place
49    to share your thoughts and discuss new ideas.</li>
50
51<li>The <a href="http://sourceforge.net/p/proguard/bugs/" target="other">bug
52    tracking page</a> (at SourceForge) allows you to submit and consult bug
53    reports. Please make sure the reports are complete and concise. If I can't
54    reproduce the problem, I most likely can't fix it either.</li>
55
56<li>The <a href="http://sourceforge.net/p/proguard/feature-requests/"
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.freecode.com/projects/proguard"
65    target="other">project page</a> at Freecode (Freshmeat) offer the
66    possibility to subscribe to the announcements of new releases. They are
67    the most 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<!--
74document.write("<a href=\"ma");
75document.write("ilto:");
76document.write("lafortune");
77document.write("&#64;");
78document.write("users.sourceforge.net\">");
79document.write("lafortune");
80document.write("&#64;");
81document.write("users.sourceforge.net");
82document.write("<\/a>");
83document.write(" <em>or<\/em> at ");
84document.write("<a href=\"ma");
85document.write("ilto:");
86document.write("eric");
87document.write("&#64;");
88document.write("graphics.cornell.edu\">");
89document.write("eric");
90document.write("&#64;");
91document.write("graphics.cornell.edu");
92document.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>
103I can't promise a swift answer, or any answer at all, for that matter, but it's
104always great to see 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
109do things my way, without the overhead and compromises associated with larger
110projects.
111
112<hr />
113<address>
114Copyright &copy; 2002-2014
115<a target="other" href="http://www.lafortune.eu/">Eric Lafortune</a> @ <a target="top" href="http://www.saikoa.com/">Saikoa</a>.
116</address>
117
118</body>
119</html>
120