<div><br>Dear Marcus,</div>
<div> </div>
<div>i am building a frontend in vc++for gpg. using gpg1.4.5.</div>
<div>Besides that using md5 and sha1.exe to be included separately which i downloaded from the internet. </div>
<div>i have not used any libraries or other material other than this. ofcourse to learn to build this i have read variuos books, links, and references .</div>
<div> </div>
<div>i am new in field of programming so only know that to obtain the result say X i need to work so and so way....other than that i don't know anything else..</div>
<div> </div>
<div>source code is mine...as i have written it myself. so no libraries ...i didn't know how to use and which to use....i learnt vc++ to do my job..that's all. but yes my fronend does basic job of gpg using only gpg behind the scene..... and i have done coding using visual studio 6.
</div>
<div> </div>
<div>i don't know what is a licence, how to write it , what are other things to be done...since you often see so i thought it's a formality</div>
<div> </div>
<div>i just wanted that the work i have done should be acknowledged on my name and i should get feed back frm users as to how could i improve it to make it to a state at which it should be. </div>
<div>what aspects are to be looked after other than coding i am not aware. so please educate me in simple terms........</div>
<div> </div>
<div>i repeat that as of now i have the frontend ready to some aspect, final completion would take a little more time and all i have is a working frontend with its source code....what all to be done next.pl educate me....
</div>
<div> </div>
<div>lots of regards and thx that u took out time to write long lines in ur reply</div>
<div> </div>
<div>vineet madan</div>
<div> </div>
<div><br> </div>
<div><span class="gmail_quote">On 10/25/06, <b class="gmail_sendername">Marcus Brinkmann</b> <<a href="mailto:marcus.brinkmann@ruhr-uni-bochum.de">marcus.brinkmann@ruhr-uni-bochum.de</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">At Wed, 25 Oct 2006 11:22:42 +0530,<br>"Vineet Madan" <<a href="mailto:vineet1408@gmail.com">
vineet1408@gmail.com</a>> wrote:<br>><br>> dear bernhard<br>><br>> i asked werner but he didn't reply. i am about to complete a new frntend<br>> for gpg. i want to put it or user feed back. what policy, licence should i
<br>> set in it so that i get the needfull acknowledgement and feedback,,,,<br><br>It would help to know which license you intended to use. If you<br>license your software under the GPL v2 or later, which I recommend,
<br>then you ensure maximum compatibility. Incompatible licenses coupled<br>with tight integration can enter a legal grey area.<br><br>To usefully answer the license question, one also has to know the<br>license of all components you are using in your software, especially
<br>the libraries you are using.<br><br>Let's assume the best case scenario: All the software you are using is<br>GPL'ed or under a license compatible to the GPL (see<br><a href="http://www.gnu.org/licenses/license-list.html#GPLCompatibleLicenses">
http://www.gnu.org/licenses/license-list.html#GPLCompatibleLicenses</a><br>for an extensive list). In that case, the standard procedure is to<br>have a copyright notice in each file of your sources, stating the<br>originator of all parties that have contributed to the content of that
<br>particular file and a license notice for each contribution. I<br>recommend to have a list of all projects and licenses used directly in<br>your source code in a file README at the top level directory, and a<br>file COPYING with a copy of the full license texts. You can find more
<br>detailed information at<br><a href="http://www.gnu.org/prep/maintain/maintain.html#Copyright-Notices">http://www.gnu.org/prep/maintain/maintain.html#Copyright-Notices</a><br><br>This is for source code you are actually including in your program.
<br>For libraries and other components used (like gpg), normally no notice<br>is provided, so no particular action is necessary, although you should<br>ensure that the licenses are in fact compatible. As you do this check
<br>anyway, I'd recommend to include a list of all dependencies and their<br>license type in the README, like this:<br><br>"This program has the following dependencies:<br><br>libreadline 5.1 (GPL)<br>libfoobar 0.2 (LGPL)
<a href="http://www.foobar.org/">http://www.foobar.org/</a>"<br><br>This is generally useful information for people who want to build and<br>package your software, so I think it's a good idea to include it. For<br>example, if your software will be included in Debian, the Debian
<br>maintainer will have to do a license check, and this information will<br>speed up the process considerably.<br><br>I hope this information is helpful. If any doubts remain, please just<br>ask. In general, I think it's a good idea to just look at how it is
<br>done in high-profile software packages, such as GNU Emacs or GNU<br>shellutils or other packages like that.<br><br>Thanks,<br>Marcus<br><br></blockquote></div><br><br clear="all"><br>-- <br>God is Great<br>VINEET MADAN
<br>emailid: <a href="mailto:vineet1408@gmail.com">vineet1408@gmail.com</a>