LINUX.IE, website of the Irish Linux Users' Group
Tux rules!

   
Home
New Users
Articles
Download
Projects
Community
Vendors

  Print Version
Email to...
 
Archives:


planetILUG

Recent News

News Archive


Join the
ILUG
on FaceBook


Join the
ILUG
on LinkedIn


Join the
ILUG SETI
Group



















 
 :: Mailing Lists

[ILUG] Gaining experience through code, and reusing experience.

[ILUG] Gaining experience through code, and reusing experience.

Justin Mason jm at jmason.org
Thu Jul 28 02:03:21 IST 2005


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


So I think you want to know if you can work off open-source code, and use
that to implement closed-source code?

You're entirely constrained by copyright. If lines of code from one wind
up verbatim in another, or nearly-verbatim apart from some trivial
modifications (whitespace, var names etc.) that's *definitely* considered
copying, and you've got to respect the license.  No way around it.

(btw the same applies for sample code and examples -- although I've never
heard of any company/publisher producing sample code that restricts
its reuse...)

However, as Ole noted, BSD-licensed code can be modified and the changes
kept in-house -- most "commercial-friendly" open source licenses allow
this, too.  As far as I know Eclipse's license fits the bill.

But if you need to base your work off GPL-licensed code, you've got
to respect the GPL license and its publishing requirements.

- --j.

Turloch O'Tierney writes:
> ILUG,
> 
> The company I work for makes extensive use of linux, and has released
> PHP development support in its products.
> 
> I vaguely understand the BSD, GPL and LGPL licenses.
> 
> As a developer I am going into new areas. How much am I constrained by
> copyright once I go beyond published API, examples and code in the
> public domain, of which there seems very little? I am currently
> interested in developing for eclipse.org as part of my commercial
> work.
> 
> My extreme answer is:
> It all depends on the license. If the source code was proprietary you
> would not even get to look at it, so consider yourself signing a
> nondisclosure agreement when you are looking at it and not submitting
> patches.
> 
> The less extreme answer is:
> Programmers learn from everywhere, your past experience is what is
> paid for and that includes having a vague idea how to do things from
> having read open source, and previous companies proprietary code +
> coded.
> 
> This may be flame war stuff and a lawyer would give me the best
> answer, but I thought I would spin it out there to get what the
> current developer practice is...
> 
> Thank you for your time,
> 
> Turloch
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Exmh CVS

iD8DBQFC6C7YMJF5cimLx9ARApbVAJ9h1oPWf1pBMmFRXk6rUq8E2RflwgCgpV9w
MO7X0X/O/GXeww2lS4Gu730=
=WsMT
-----END PGP SIGNATURE-----




More information about the ILUG mailing list
Read this without the formatting.
                                                                                                    

 

Hosted by HEAnet


Maintained by the ILUG website team. The aim of Linux.ie is to support and help commercial and private users of Linux in Ireland. You can display ILUG news in your own webpages, read backend information to find out how. Networking services kindly provided by HEAnet, server kindly donated by Dell. Linux is a trademark of Linus Torvalds, used with permission. No penguins were harmed in the production or maintenance of this highly praised website. Looking for the Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!
RSS Version
Powered by Dell