[openstack-dev] Process for proposing patches attached to launchpad bugs?

Dean Troyer dtroyer at gmail.com
Mon Dec 23 17:07:49 UTC 2013

On Mon, Dec 23, 2013 at 3:50 AM, Robert Collins
<robertc at robertcollins.net>wrote:

> On 23 December 2013 17:35, Chet Burgess <cfb at metacloud.com> wrote:
> > It's unclear to me what exactly constitutes writing a new patch. I can
> check
> > out oslo.messaging, and without trying to merge the patch just go and
> make
> > the same change (its literarily a 2 line change). I can write the tests,
> and
> > I can submit it (which I'm happy to do, I really want this bug fixed).
> > Honestly though this change is so trivial I don't see how my patch would
> > look all that different from the one already posted. I know there is
> prior
> > art. The mixin class that kombu provides does the exact same thing. Is
> that

Research the term 'de minimis' WRT copyright and decide (with the help of
actual legal advice if necessary) when to just go ahead and submit a patch.

Prior art is a patent concept, not related to copyright. Copyright is

+1...this stuff gets confused too much these days...



Dean Troyer
dtroyer at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131223/b4bd72b8/attachment.html>

More information about the OpenStack-dev mailing list