From: John Snow <jsnow@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: Eduardo Habkost <eduardo@habkost.net>,
Beraldo Leal <bleal@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
Wainer dos Santos Moschetta <wainersm@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>, Cleber Rosa <crosa@redhat.com>
Subject: Re: [RFC qemu.qmp PATCH 03/24] Update maintainer metadata
Date: Thu, 16 Dec 2021 11:34:02 -0500 [thread overview]
Message-ID: <CAFn=p-Y+oo7HUKBCfRZNJG==51xT10_DNEYXV9uFneZMVLp36w@mail.gmail.com> (raw)
In-Reply-To: <YbsYO514CsqjYn5t@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1857 bytes --]
On Thu, Dec 16, 2021 at 5:43 AM Daniel P. Berrangé <berrange@redhat.com>
wrote:
> On Wed, Dec 15, 2021 at 04:06:13PM -0500, John Snow wrote:
> > I'm the primary author of this particular component; update the metadata
> > accordingly.
> >
> > Signed-off-by: John Snow <jsnow@redhat.com>
> > ---
> > setup.cfg | 4 +++-
> > 1 file changed, 3 insertions(+), 1 deletion(-)
> >
> > diff --git a/setup.cfg b/setup.cfg
> > index 9999bca..7cd8470 100644
> > --- a/setup.cfg
> > +++ b/setup.cfg
> > @@ -1,7 +1,9 @@
> > [metadata]
> > name = qemu.qmp
> > version = file:VERSION
> > -maintainer = QEMU Developer Team
> > +author = John Snow
> > +author_email = jsnow@redhat.com
>
> Isn't the authorship of this more of a collaborative effort ?
> IOW, shouldn't it just be "The QEMU Project" as for the
> maintainer.
>
Sorta. The code in this specific package is > 95% written by me, so I felt
the authorship credit here was roughly appropriate. So, I put myself as the
"Author" but "QEMU Project" as the "maintainer". I put a lot of work into
this, so it felt weird to say that it was authored by a mailing list.
I also wanted to avoid not listing my own name at all, since this has
largely been my initiative to polish it up, write docs, and split it out --
it feels rude to just dump responsibility straight back on the list and
pretend I'm not the point of contact for it.
>
> > +maintainer = QEMU Project
> > maintainer_email = qemu-devel@nongnu.org
> > url = https://www.qemu.org/
> > download_url = https://www.qemu.org/download/
>
> 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 :|
>
>
[-- Attachment #2: Type: text/html, Size: 3345 bytes --]
next prev parent reply other threads:[~2021-12-16 16:36 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 21:06 [RFC qemu.qmp PATCH 00/24] Python: Fork qemu.qmp Python lib into independent repo John Snow
2021-12-15 21:06 ` [RFC qemu.qmp PATCH 01/24] Fork qemu.qmp from qemu.git John Snow
2021-12-15 21:06 ` [RFC qemu.qmp PATCH 02/24] Update VERSION to 0.0.0a1 John Snow
2021-12-15 21:06 ` [RFC qemu.qmp PATCH 03/24] Update maintainer metadata John Snow
2021-12-16 10:43 ` Daniel P. Berrangé
2021-12-16 16:34 ` John Snow [this message]
2021-12-15 21:06 ` [RFC qemu.qmp PATCH 04/24] Update project description John Snow
2021-12-15 21:06 ` [RFC qemu.qmp PATCH 05/24] Update project URLs John Snow
2021-12-15 21:06 ` [RFC qemu.qmp PATCH 06/24] Move README.rst to INDEX.rst and update John Snow
2021-12-15 21:06 ` [RFC qemu.qmp PATCH 07/24] Move PACKAGE.rst to README.rst " John Snow
2021-12-15 21:06 ` [RFC qemu.qmp PATCH 08/24] Update Pipfile.lock John Snow
2021-12-15 21:06 ` [RFC qemu.qmp PATCH 09/24] Remove sub-dependency pins from Pipfile John Snow
2021-12-15 21:06 ` [RFC qemu.qmp PATCH 10/24] Add build and test container to gitlab CI configuration John Snow
2021-12-15 21:06 ` [RFC qemu.qmp PATCH 11/24] Add package build step to GitLab CI John Snow
2021-12-15 21:06 ` [RFC qemu.qmp PATCH 12/24] GitLab CI: Add check-dco script John Snow
2021-12-15 21:06 ` [RFC qemu.qmp PATCH 13/24] GitLab CI: Add pipenv and tox tests John Snow
2021-12-15 21:06 ` [RFC qemu.qmp PATCH 14/24] GitLab CI: Add avocado junit XML output to tests John Snow
2021-12-15 21:06 ` [RFC qemu.qmp PATCH 15/24] GitLab CI: Publish python packages to GitLab package repo John Snow
2021-12-15 21:06 ` [RFC qemu.qmp PATCH 16/24] Add setuptools_scm package versioning John Snow
2021-12-15 21:06 ` [RFC qemu.qmp PATCH 17/24] Makefile: add build and publish targets John Snow
2021-12-16 10:48 ` Daniel P. Berrangé
2021-12-16 23:35 ` John Snow
2021-12-17 13:45 ` Daniel P. Berrangé
2022-01-11 19:48 ` John Snow
2022-01-12 10:07 ` Daniel P. Berrangé
2022-01-12 17:30 ` John Snow
2021-12-15 21:06 ` [RFC qemu.qmp PATCH 18/24] add Sphinx documentation config stub John Snow
2021-12-15 21:06 ` [RFC qemu.qmp PATCH 19/24] python: configure sphinx John Snow
2021-12-15 21:06 ` [RFC qemu.qmp PATCH 20/24] python: adjust apidoc stubs John Snow
2021-12-15 21:06 ` [RFC qemu.qmp PATCH 21/24] Fix doc cross-reference regressions John Snow
2021-12-15 21:06 ` [RFC qemu.qmp PATCH 22/24] docs: add Makefile target John Snow
2021-12-15 21:06 ` [RFC qemu.qmp PATCH 23/24] docs: add doc build to GitLab CI build step John Snow
2021-12-15 21:06 ` [RFC qemu.qmp PATCH 24/24] v0.0.1 John Snow
2021-12-16 10:41 ` [RFC qemu.qmp PATCH 00/24] Python: Fork qemu.qmp Python lib into independent repo Daniel P. Berrangé
2021-12-16 16:18 ` John Snow
2022-01-12 21:41 ` John Snow
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='CAFn=p-Y+oo7HUKBCfRZNJG==51xT10_DNEYXV9uFneZMVLp36w@mail.gmail.com' \
--to=jsnow@redhat.com \
--cc=berrange@redhat.com \
--cc=bleal@redhat.com \
--cc=crosa@redhat.com \
--cc=eduardo@habkost.net \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wainersm@redhat.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).