[Gpg4win-devel] how to make new gpg frontend available to users.

[Vineet Madan]

Dear Marcus,

i am building a frontend in vc++for gpg.  using gpg1.4.5.
Besides that using md5 and sha1.exe to be included separately which i
downloaded from the internet.
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 .

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..

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.

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

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.
what aspects are to be looked after  other than coding i am not aware. so
please educate me in simple terms........

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....

lots of regards and thx that u took out time to write long lines in ur reply

vineet madan



On 10/25/06, Marcus Brinkmann <marcus.brinkmann at ruhr-uni-bochum.de> wrote:
>
> At Wed, 25 Oct 2006 11:22:42 +0530,
> "Vineet Madan" <vineet1408 at gmail.com> wrote:
> >
> > dear bernhard
> >
> > i asked werner but he  didn't reply. i am about to complete a new
> frntend
> > for gpg. i want to put it or user feed back. what policy, licence should
> i
> > set in it so that i get the needfull acknowledgement and feedback,,,,
>
> It would help to know which license you intended to use.  If you
> license your software under the GPL v2 or later, which I recommend,
> then you ensure maximum compatibility.  Incompatible licenses coupled
> with tight integration can enter a legal grey area.
>
> To usefully answer the license question, one also has to know the
> license of all components you are using in your software, especially
> the libraries you are using.
>
> Let's assume the best case scenario: All the software you are using is
> GPL'ed or under a license compatible to the GPL (see
> http://www.gnu.org/licenses/license-list.html#GPLCompatibleLicenses
> for an extensive list).  In that case, the standard procedure is to
> have a copyright notice in each file of your sources, stating the
> originator of all parties that have contributed to the content of that
> particular file and a license notice for each contribution.  I
> recommend to have a list of all projects and licenses used directly in
> your source code in a file README at the top level directory, and a
> file COPYING with a copy of the full license texts.  You can find more
> detailed information at
> http://www.gnu.org/prep/maintain/maintain.html#Copyright-Notices
>
> This is for source code you are actually including in your program.
> For libraries and other components used (like gpg), normally no notice
> is provided, so no particular action is necessary, although you should
> ensure that the licenses are in fact compatible.  As you do this check
> anyway, I'd recommend to include a list of all dependencies and their
> license type in the README, like this:
>
> "This program has the following dependencies:
>
> libreadline 5.1 (GPL)
> libfoobar 0.2 (LGPL) http://www.foobar.org/"
>
> This is generally useful information for people who want to build and
> package your software, so I think it's a good idea to include it.  For
> example, if your software will be included in Debian, the Debian
> maintainer will have to do a license check, and this information will
> speed up the process considerably.
>
> I hope this information is helpful.  If any doubts remain, please just
> ask.  In general, I think it's a good idea to just look at how it is
> done in high-profile software packages, such as GNU Emacs or GNU
> shellutils or other packages like that.
>
> Thanks,
> Marcus
>
>


-- 
God is Great
VINEET MADAN
emailid: vineet1408 at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.wald.intevation.org/pipermail/gpg4win-devel/attachments/20061025/3d54be23/attachment.html