From: Dave Chinner <david@fromorbit.com>
To: "Epp, Mike" <MEpp@KrollOntrack.com>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: Question on how to submit changed code
Date: Wed, 2 Dec 2015 09:39:29 +1100 [thread overview]
Message-ID: <20151201223929.GC19199@dastard> (raw)
In-Reply-To: <105716A9A63E8A4C9CB26A0F29E203DCF40BE069@usbpx2pmxmbx12>
On Tue, Dec 01, 2015 at 03:16:11PM +0000, Epp, Mike wrote:
> I have changed code in libxfs and repair projects for xfsprogs. I
> don't view the changes as desired for ongoing deployment, as they
> allowed scanning of active volumes and bring the chance of false
> errors. To stay compliant with GNU GPL though we must publish the
> code. What are the steps I need to follow to publish the changes?
Many options, but you should really be asking you company's legal
counsel this question.
>From my perspective, either of these would work:
- add a page to your company's website with a link from the
home page that contains the tarballs of modified packages.
- put the modified source code up in a repository on github
(or similar) and include a link from the website
- send patches to an archived mailing list whenever you
change the code, and place a link to the archive on your
website home page.
> Do I need to publish just the source files I changed, the entire
> projects I changes, or all of xfsprogs?
-> legal counsel
The license spells out what is necessary. All of the above are valid
interpretations....
> Mike Epp, Senior Software Engineer Kroll Ontrack | 9023 Columbine
> Road, Eden Prairie, MN 55347
> mepp@krollontrack.com<mailto:mepp@krollontrack.com>
> www.krollontrack.com<http://www.krollontrack.com/ohttp:/www.krollontrack.com/>
> This communication contains information that is confidential,
> proprietary in nature, and may also be attorney-client privileged
> and/or work product privileged. It is for the exclusive use of the
> intended recipient(s).
[snip]
And any code you send to the mailing list must have a valid
signed-off-by and not have a bunch of restrictive legal mumbo jumbo
on the end of it....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2015-12-01 22:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-01 15:16 Question on how to submit changed code Epp, Mike
2015-12-01 16:33 ` Carlos Maiolino
2015-12-01 17:28 ` Bill O'Donnell
2015-12-01 17:41 ` Roger Willcocks
2015-12-01 17:44 ` Carlos Maiolino
2015-12-01 17:47 ` Carlos Maiolino
2015-12-01 18:03 ` Roger Willcocks
2015-12-01 18:10 ` Epp, Mike
2015-12-01 22:27 ` Dave Chinner
2015-12-01 17:53 ` Bill O'Donnell
2015-12-01 22:39 ` Dave Chinner [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151201223929.GC19199@dastard \
--to=david@fromorbit.com \
--cc=MEpp@KrollOntrack.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox