>7.) ... The minimal thing
>would be to collect the changes/bugfixes/improvements made
>by others and integrate it into the fork...
Be VERY careful of this one. Individual
patches/changes/whatever-you-want-to-call-them are owned by their
authors and placed under the project's license voluntarily. Anything
contributed after the switch to AGPL is under that (viral) license
unless you get permission from the individual who submitted it to add it
to a non-AGPL fork. Don't be too shocked if they say "no"... expect it
in the case of the project leads/contributors.
Changes submitted to the mailing list without any license attribution
are up in the air. Might be kosher, might not. Lawyer territory.
Even looking at the source of an AGPL change before writing your own
opens you up to Legal Action... a la "dirivative works".
Forks are a pain, copyright law is a pain, international law is a pain.
Is all that pain greater than the pain involved in being seperated from
your money? Only you can decide that.
Having said all that, I maintain my own fork for use by my employer. I
started it way back with 1.44paulo (long before there was any issue with
such things), and have since integrated it with 2.1.4. I'd like to get
on the trunk, but between some of the changes I've made which have been
turned down for one reason or another and Corporate Reluctance to
license ANY third party software... odds aren't good. I DO NOT port
patches from 5.x to my fork.
I'm hoping that at some point we'll NEED something from the trunk, at
which point The Powers That Be will exchange X dev time for a license.
Expenses can get torpedoed by the higher-ups... but my time? Not their
concern.
--Mark Storer
Senior Software Engineer
Cardiff.com
import legalese.Disclaimer;
Disclaimer<Cardiff> DisCard = null;
------------------------------------------------------------------------------
Nokia and AT&T present the 2010 Calling All Innovators-North America contest
Create new apps & games for the Nokia N8 for consumers in U.S. and Canada
$10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing
Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store
http://p.sf.net/sfu/nokia-dev2dev
_______________________________________________
iText-questions mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/itext-questions
Buy the iText book: http://www.itextpdf.com/book/
Check the site with examples before you ask questions:
http://www.1t3xt.info/examples/
You can also search the keywords list: http://1t3xt.info/tutorials/keywords/
