All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luo Zhenhua-B19537 <B19537@freescale.com>
To: "openembedded-devel@lists.openembedded.org"
	<openembedded-devel@lists.openembedded.org>,
	"elizabeth.flanagan@intel.com" <elizabeth.flanagan@intel.com>
Subject: Re: [PATCH meta-oe 5/9] nerperf: add
Date: Wed, 21 Dec 2011 06:26:34 +0000	[thread overview]
Message-ID: <CA452391058F6D4E9715FB2C29D9312A010B9F06@039-SN2MPN1-023.039d.mgd.msft.net> (raw)
In-Reply-To: CAPhnLPDSpXjAi+V9gjJCsrdoYez5CJWzv-+ejmDqm8P5mFu_Kw@mail.gmail.com

I have sent an email to netperf-feedback@netperf.org to query the appropriate license type yesterday and not response.

I'd like to adopt following option, does it make sense?
> > 2. We'll need to add a Netperf license to common-licenses and set LICENSE = "Netperf"


Best Regards,

Zhenhua


> -----Original Message-----
> From: Luo Zhenhua-B19537
> Sent: Tuesday, December 20, 2011 10:32 AM
> To: openembedded-devel@lists.openembedded.org
> Subject: RE: [oe] [PATCH meta-oe 5/9] nerperf: add
> 
> Thanks for the feedback.
> 
> I saw netperf is licensed under "netperf" in oe
> http://cgit.openembedded.org/openembedded/plain/recipes/netperf/netperf_2.4.4.bb.
> 
> Anyway, I will send an email to the author to query about the license type.
> 
> 
> Best Regards,
> 
> Zhenhua
> 
> > -----Original Message-----
> > From: Flanagan, Elizabeth [mailto:elizabeth.flanagan@intel.com]
> > Sent: Tuesday, December 20, 2011 6:32 AM
> > To: openembedded-devel@lists.openembedded.org; Luo Zhenhua-B19537
> > Subject: Re: [oe] [PATCH meta-oe 5/9] nerperf: add
> >
> > On Fri, Dec 16, 2011 at 1:54 PM, Khem Raj <raj.khem@gmail.com> wrote:
> > > On (16/12/11 10:22), Koen Kooi wrote:
> > >>
> > >> Op 16 dec. 2011, om 10:19 heeft Luo Zhenhua-B19537 het volgende geschreven:
> > >>
> > >> > Hello Koen,
> > >> >
> > >> >> -----Original Message-----
> > >> >> From: openembedded-devel-bounces@lists.openembedded.org
> > >> >> [mailto:openembedded- devel-bounces@lists.openembedded.org] On
> > >> >> Behalf Of Koen Kooi
> > >> >> Sent: Friday, December 16, 2011 3:52 PM
> > >> >>
> > >> >>> +++ b/meta-oe/recipes-benchmark/netperf/netperf_2.4.4.bb @@
> > >> >>> +++ -0,0
> > >> >>> +++ +1,47
> > >> >>> @@ +DESCRIPTION="Network performance benchmark including tests
> > >> >>> for TCP, UDP, sockets, ATM and more." +SECTION = "console/network"
> > >> >>> +HOMEPAGE = "http://www.netperf.org/" +LICENSE = "netperf"
> > >> >>
> > >> >> Can you include a comment on what type of license netperf is?
> > >> >> MIT like, BSD like, GPL like?
> > >> > [Luo Zhenhua-B19537] May I know which license type should be with
> > >> > following
> > COPYING content?
> > >>
> > >> That looks like a BSD or MIT derivative, maybe Beth can give us
> > >> some guidance on what to use as LICENSE
> > >
> > > it says "for non-commercial purposes only"
> >
> > Yeah.... in this case, I would do one of two things (and I have a
> > feeling one will be more valid that the other):
> >
> > 1. Email the author and see if we can use BSD-4-Clause. My guess is no.
> > 2. We'll need to add a Netperf license to common-licenses and set
> > LICENSE = "Netperf"
> >
> > I've checked the openSuSE Build Service and they have this as an
> > "Other" license, so, check with the author first, but be prepared to
> > add Netperf to the common- licenses directory.
> >
> > And yes, Koen is right. I wouldn't use BSD or MIT for this,
> > specifically because of the non-commercial clause in (ii).
> >
> > -b
> >
> > >
> > >>
> > >> regards,
> > >>
> > >> Koen
> > >>
> > >>
> > >> >
> > >> >              Copyright (C) 1993 Hewlett-Packard Company
> > >> >                         ALL RIGHTS RESERVED.
> > >> >
> > >> >  The enclosed software and documentation includes copyrighted
> > >> > works
> > >> >  of Hewlett-Packard Co. For as long as you comply with the
> > >> > following
> > >> >  limitations, you are hereby authorized to (i) use, reproduce,
> > >> > and
> > >> >  modify the software and documentation, and to (ii) distribute
> > >> > the
> > >> >  software and documentation, including modifications, for
> > >> >  non-commercial purposes only.
> > >> >
> > >> >  1.  The enclosed software and documentation is made available at
> > >> > no
> > >> >      charge in order to advance the general development of
> > >> >      high-performance networking products.
> > >> >
> > >> >  2.  You may not delete any copyright notices contained in the
> > >> >      software or documentation. All hard copies, and copies in
> > >> >      source code or object code form, of the software or
> > >> >      documentation (including modifications) must contain at
> > >> > least
> > >> >      one of the copyright notices.
> > >> >
> > >> >  3.  The enclosed software and documentation has not been
> > >> > subjected
> > >> >      to testing and quality control and is not a Hewlett-Packard Co.
> > >> >      product. At a future time, Hewlett-Packard Co. may or may
> > >> > not
> > >> >      offer a version of the software and documentation as a product.
> > >> >
> > >> >  4.  THE SOFTWARE AND DOCUMENTATION IS PROVIDED "AS IS".
> > >> >      HEWLETT-PACKARD COMPANY DOES NOT WARRANT THAT THE USE,
> > >> >      REPRODUCTION, MODIFICATION OR DISTRIBUTION OF THE SOFTWARE
> > >> > OR
> > >> >      DOCUMENTATION WILL NOT INFRINGE A THIRD PARTY'S INTELLECTUAL
> > >> >      PROPERTY RIGHTS. HP DOES NOT WARRANT THAT THE SOFTWARE OR
> > >> >      DOCUMENTATION IS ERROR FREE. HP DISCLAIMS ALL WARRANTIES,
> > >> >      EXPRESS AND IMPLIED, WITH REGARD TO THE SOFTWARE AND THE
> > >> >      DOCUMENTATION. HP SPECIFICALLY DISCLAIMS ALL WARRANTIES OF
> > >> >      MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
> > >> >
> > >> >  5.  HEWLETT-PACKARD COMPANY WILL NOT IN ANY EVENT BE LIABLE FOR
> > >> > ANY
> > >> >      DIRECT, INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL
> > >> > DAMAGES
> > >> >      (INCLUDING LOST PROFITS) RELATED TO ANY USE, REPRODUCTION,
> > >> >      MODIFICATION, OR DISTRIBUTION OF THE SOFTWARE OR DOCUMENTATION.
> > >> >
> > >> >
> > >> > Best Regards,
> > >> >
> > >> > Zhenhua
> > >> >
> > >>
> > >
> > >
> > >
> > >> _______________________________________________
> > >> Openembedded-devel mailing list
> > >> Openembedded-devel@lists.openembedded.org
> > >> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-de
> > >> ve
> > >> l
> > >
> > >
> > > --
> > > -Khem
> > >
> > > _______________________________________________
> > > Openembedded-devel mailing list
> > > Openembedded-devel@lists.openembedded.org
> > > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-dev
> > > el
> >
> >
> >
> > --
> > Elizabeth Flanagan
> > Yocto Project
> > Build and Release





  parent reply	other threads:[~2011-12-21  6:33 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-16  2:39 [PATCH meta-oe 1/9] bridge-utils: add b19537
2011-12-16  2:39 ` [PATCH meta-oe 2/9] ietutils: add b19537
2011-12-16  7:48   ` Koen Kooi
2011-12-16  2:39 ` [PATCH meta-oe 3/9] ipsec-tools: add b19537
2011-12-16  7:49   ` Koen Kooi
2011-12-16  2:39 ` [PATCH meta-oe 4/9] libnfnetlink: add b19537
2011-12-16  7:50   ` Koen Kooi
2011-12-16  2:39 ` [PATCH meta-oe 5/9] nerperf: add b19537
2011-12-16  7:51   ` Koen Kooi
2011-12-16  9:19     ` Luo Zhenhua-B19537
2011-12-16  9:22       ` Koen Kooi
2011-12-16 21:54         ` Khem Raj
2011-12-19  9:52           ` Luo Zhenhua-B19537
2011-12-19 19:20             ` Khem Raj
2011-12-19 22:31           ` Flanagan, Elizabeth
2011-12-20  2:31             ` Luo Zhenhua-B19537
2011-12-21  6:26             ` Luo Zhenhua-B19537 [this message]
2011-12-21 17:37               ` Flanagan, Elizabeth
2011-12-22  2:44                 ` Luo Zhenhua-B19537
2011-12-29 18:19                   ` Flanagan, Elizabeth
2011-12-16  2:39 ` [PATCH meta-oe 6/9] ptpd: add b19537
2011-12-16  7:52   ` Koen Kooi
2011-12-16 21:57   ` Khem Raj
2011-12-16  2:39 ` [PATCH meta-oe 7/9] strongswan: add b19537
2011-12-16  7:53   ` Koen Kooi
2011-12-16  2:39 ` [PATCH meta-oe 8/9] rng-tools: add b19537
2011-12-16  7:53   ` Koen Kooi
2011-12-16  2:39 ` [PATCH meta-oe 9/9] xfsprogs: add b19537
2011-12-16  7:54   ` Koen Kooi
2011-12-16  7:45 ` [PATCH meta-oe 1/9] bridge-utils: add Koen Kooi
2011-12-16  8:48   ` Luo Zhenhua-B19537

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=CA452391058F6D4E9715FB2C29D9312A010B9F06@039-SN2MPN1-023.039d.mgd.msft.net \
    --to=b19537@freescale.com \
    --cc=elizabeth.flanagan@intel.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.