hould have that explicitly
authorizes me to release this software (copyright still held by the company)
to the public under a DFSG compliant license.
Thanks!
john
--
John Morrissey _o/\ __o
[EMAIL PROTECTED]_-< \_
).
Thanks to everyone who mentioned having the company license the software
with a signed copy of the license declaration to back it up. That's exactly
what I'm looking for, particularly the signed paper copy so it's explicit
that the licensing has the their blessing.
jo
e bugfixes to the source without updating the
copyright information. Do I need to have upstream update the copyright
notice on these files before packaging this software?
john
--
John Morrissey _o/\ __o
j...
I'm packaging the PHP PEAR Crypt_Blowfish module. I noticed:
http://www.debian.org/legal/notificationfornewpackages
which seems to indicate I need to update the US Bureau of Export
Administration before uploading this package for the first time.
Is this still a requirement?
john
--
27;m covered by dak's
notifications.
Thanks for your advice, Steve.
john
--
John Morrissey _o/\ __o
j...@horde.net_-< \_ / \ < \,
www.horde.net/__(_)/_(_)/\___(_) /_(_)__
--
To UNSUBSCRIBE, email
5 matches
Mail list logo