PageRenderTime 8ms CodeModel.GetById 7ms app.highlight 0ms RepoModel.GetById 0ms app.codeStats 0ms

/jcl/docs/Contacting authors.html

https://github.com/the-Arioch/jcl
HTML | 35 lines | 34 code | 1 blank | 0 comment | 0 complexity | a6710841f061677d0b5b80c8d7401db7 MD5 | raw file
Possible License(s): BSD-3-Clause
 1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
 2<html>
 3<head>
 4<title>Contacting authors</title>
 5<style type="text/css">
 6@import url(styles/default.css);
 7</style>
 8</head>
 9<body>
10<h1>Contacting authors</h1>
11<p>
12The JEDI Code Library is built upon donations by various individuals. In the
13documentation for each subroutine or class you will find who the author of that
14particular code is by looking in the "Quick Info" section. However,
15generically speaking, you should <b>never contact an author</b> regarding code included
16in this library. There are various reasons for this with the two most prominent
17being that some authors explicitly requested this and because "author" means
18different things in different context. Usually "author" means that the described
19code was donated to the JCL by that individual and included after reformatting and
20only minor modifications. However, sometimes code was significantly altered,
21rewritten several times or 'merely' based upon or inspired by code from that
22individual. Consequently there exist several routines which in no way resemble
23the original code as it was donated by the "author". Nevertheless, the individual
24that orginally donated the code is still documented as the author.
25</p><p>
26In general, if you like some routine very much and it has proven to work correctly:
27be grateful to the author (in thought, not by sending him or her an e-mail). On
28the other hand, if some routine turns out to be buggy, incorrect or for whatever
29reason is not to your liking: complain to me. It was most likely we who screwed
30it up and introduced those bugs into code that was working perfectly until we got
31our hands on it! To report bugs, use Project JEDI's
32<a href="http://issuetracker.delphi-jedi.org/">Issue Tracker</a>.
33
34</p><div class="footer">Built on Saturday, October 20, 2010</div>
35</body></html>