qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Dave Hello <hsu@peterdavehello.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Zhao Liu <zhao1.liu@intel.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [PATCH] Add zh_TW Traditional Chinese translation
Date: Tue, 14 Jan 2025 14:34:46 +0000	[thread overview]
Message-ID: <Z4Z2BsF1QYSvjxqe@redhat.com> (raw)
In-Reply-To: <w0C7I-STdtazH_QTikLVqdGlKEDYBJd-xCkX1BXBPY-rRhhU6E0ARjv0_t9QiJpptsNzSJeGpotLRYaBMa2VGyucNEE9zOaCQ8YKWhGPlYk=@peterdavehello.org>

On Tue, Jan 14, 2025 at 01:45:03PM +0000, Peter Dave Hello wrote:
> On Tuesday, June 25th, 2024 at AM 1:06, Daniel P. Berrangé <berrange@redhat.com> wrote:
> > > We can't give legal advice, but the QEMU project doesn't do
> > > copyright assignment. Copyright remains with the original author
> > > (or with their employer).
> > 
> > 
> > While we can't give legal advice, going back to the original question
> > I have an observation that may resolve this.
> > 
> > IIUC, the orignal question was what to put at the top of the .po file
> > where it has:
> > 
> > # Copyright (C) 2024 THE QEMU'S COPYRIGHT HOLDER
> > 
> > I don't believe the QEMU community has any stated requirement that every
> > file have a "Copyright" line present. Entirely omitting this line is a
> > valid choice from QEMU's POV.
> > 
> > What matters to QEMU primarily is that the file has a declared license
> > statement.
> > 
> > Any Copyright lines present are woefully inaccurate in most places, since
> > they're rarely updated despite 100's of contributors working on a file.
> > The respective contributors still retain copyright over their own work
> > regardless of what a 'copyright' line says or doesn't say.
> > 
> > IOW, the contributor (or their employer) may decide for themselves
> > a policy of whether to include or omit such a "Copyright" line, on
> > contributions submitted.
> 
> Thanks for the solution! So, to confirm, I will send PATCH v2 with the
> other metadata fixes but without the "Copyright" line. Is that correct?

Yes, that is acceptable.

With 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:[~2025-01-14 14:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-16 11:31 [PATCH] Add zh_TW Traditional Chinese translation Peter Dave Hello
2024-04-16 13:27 ` Peter Maydell
2024-04-16 16:41   ` Zhao Liu
2024-04-16 16:32     ` Daniel P. Berrangé
2024-04-17 13:07       ` Peter Dave Hello
2024-04-18  2:22         ` Zhao Liu
2024-04-23 18:20           ` Peter Dave Hello
2024-06-21 12:50             ` Peter Dave Hello
2024-06-21 13:07               ` Peter Maydell
2024-06-24 17:06                 ` Daniel P. Berrangé
2025-01-14 13:45                   ` Peter Dave Hello via
2025-01-14 14:34                     ` Daniel P. Berrangé [this message]
2024-04-16 16:34 ` Zhao Liu

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=Z4Z2BsF1QYSvjxqe@redhat.com \
    --to=berrange@redhat.com \
    --cc=hsu@peterdavehello.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=zhao1.liu@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).