qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, Thomas Huth <thuth@redhat.com>,
	raimue@macports.org, alex.bennee@linaro.org,
	Yu Ning <yu.ning@intel.com>, Eric Blake <eblake@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [qemu-web PATCH] Document how to test the site with jekyll locally
Date: Wed, 28 Nov 2018 16:47:13 +0000	[thread overview]
Message-ID: <20181128164713.GS24355@redhat.com> (raw)
In-Reply-To: <165bc19e-8ed2-8979-aea7-0f6031fc6df2@redhat.com>

On Wed, Nov 28, 2018 at 05:44:09PM +0100, Paolo Bonzini wrote:
> On 28/11/18 16:35, Daniel P. Berrangé wrote:
> > Add a README file that tells people this is a jekyll based static
> > website, and shows people how to run jekyll for testing purposes.
> > 
> > Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> > ---
> > 
> > NB, we should really mention a license in the README too, but I don't
> > see info about what license we consider qemu-web to be covered by...
> 
>     47	Paolo Bonzini <pbonzini@redhat.com>
>     44	Michael Roth <mdroth@linux.vnet.ibm.com>
>     13	Thomas Huth <thuth@redhat.com>
>      3	Eric Blake <eblake@redhat.com>
>      2	Daniel P. Berrange <berrange@redhat.com>
>      2	Jeff Cody <jcody@redhat.com>
>      1	Alex Bennée <alex.bennee@linaro.org>
>      1	Daniel P. Berrangé <berrange@redhat.com>
>      1	Fam Zheng <famz@redhat.com>
>      1	Rainer Müller <raimue@macports.org>
>      1	Stefan Hajnoczi <stefanha@gmail.com>
>      1	Yu Ning <yu.ning@intel.com>
> 
> Anybody (especially non-RH people) disagrees with dual-license CC-BY-SA
> 4.0 and GPLv2+?  (So that we can copy from blog posts to manuals)?

This dual license is exactly what I would have suggested too, as CC-BY-SA
is common place for collaborative web content projects & formal docs
efforts.

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|

  reply	other threads:[~2018-11-28 16:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-28 15:35 [Qemu-devel] [qemu-web PATCH] Document how to test the site with jekyll locally Daniel P. Berrangé
2018-11-28 16:44 ` Paolo Bonzini
2018-11-28 16:47   ` Daniel P. Berrangé [this message]
2018-11-28 17:16   ` Eric Blake
2018-11-28 17:50   ` Alex Bennée
2018-11-28 18:36   ` Thomas Huth
2018-11-28 21:04   ` Rainer Müller
2018-11-29  2:19   ` Ning, Yu
2018-12-06 16:50   ` Daniel P. Berrangé
2018-12-06 17:15     ` Michael Roth
2018-11-28 17:15 ` Eric Blake
2018-11-28 17:20   ` Daniel P. Berrangé
2018-11-28 17:23     ` Eric Blake
2018-11-28 17:27       ` Eric Blake

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=20181128164713.GS24355@redhat.com \
    --to=berrange@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=eblake@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=raimue@macports.org \
    --cc=stefanha@redhat.com \
    --cc=thuth@redhat.com \
    --cc=yu.ning@intel.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;
as well as URLs for NNTP newsgroup(s).