From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id EB4F5C433F5 for ; Wed, 12 Jan 2022 17:52:43 +0000 (UTC) Received: from localhost ([::1]:58144 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1n7hne-0005zA-Ob for qemu-devel@archiver.kernel.org; Wed, 12 Jan 2022 12:52:42 -0500 Received: from eggs.gnu.org ([209.51.188.92]:34488) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n7hmt-0004oO-Sc for qemu-devel@nongnu.org; Wed, 12 Jan 2022 12:51:55 -0500 Received: from us-smtp-delivery-124.mimecast.com ([170.10.129.124]:23276) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n7hmr-0004EH-D6 for qemu-devel@nongnu.org; Wed, 12 Jan 2022 12:51:54 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1642009912; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=mr5KqhADTml6/2QQreqHel+Uw3+uu165ASzlV647GFo=; b=TAS4FzD9+JwQCsJ6lIJlk+DJyiKQu2X8HI4fvnc5/HQcyEgzQrubKco7uME7ALfbXGAhPy c4JokVsMiPY4Qb3I+WcuCFqnQ7vMfVA0qm52AkXAsgLU9KnSbuCo5v8ok7hYzHgorqPR+T 85STVY5KZEwcirIY8S5hOVEgQlHwRR8= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-637-1NGLUQ4kPaGEAw3uJsIohg-1; Wed, 12 Jan 2022 12:51:42 -0500 X-MC-Unique: 1NGLUQ4kPaGEAw3uJsIohg-1 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 7FE4E92500; Wed, 12 Jan 2022 17:51:41 +0000 (UTC) Received: from redhat.com (unknown [10.33.36.138]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 111247E641; Wed, 12 Jan 2022 17:51:30 +0000 (UTC) Date: Wed, 12 Jan 2022 17:51:27 +0000 From: Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?= To: John Snow Subject: Re: PyPI account Message-ID: References: MIME-Version: 1.0 In-Reply-To: User-Agent: Mutt/2.1.3 (2021-09-10) X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=berrange@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit Received-SPF: pass client-ip=170.10.129.124; envelope-from=berrange@redhat.com; helo=us-smtp-delivery-124.mimecast.com X-Spam_score_int: -33 X-Spam_score: -3.4 X-Spam_bar: --- X-Spam_report: (-3.4 / 5.0 requ) BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.595, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?= Cc: Peter Maydell , Alex =?utf-8?Q?Benn=C3=A9e?= , qemu-devel , Stefan Hajnoczi , Cleber Rosa Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: "Qemu-devel" On Wed, Jan 12, 2022 at 12:47:01PM -0500, John Snow wrote: > On Wed, Jan 12, 2022 at 12:34 PM Daniel P. Berrangé wrote: > > > > On Wed, Jan 12, 2022 at 12:25:16PM -0500, John Snow wrote: > > > On Wed, Jan 12, 2022 at 5:56 AM Stefan Hajnoczi wrote: > > > > > > > > [Context: John created a PyPI QEMU user in order to publish the qemu.qmp > > > > package. If anyone wants to publish additional Python packages from > > > > qemu.git, please contact him for PyPI access.] > > > > > > > > On Tue, Jan 11, 2022 at 03:42:23PM -0500, John Snow wrote: > > > > > Account made: https://pypi.org/user/QEMU/ > > > > > > > > > > I can't update the wiki, I lack admin perms to edit > > > > > https://wiki.qemu.org/AdminContacts > > > > > > > > > > I assume in the event that I fall into a black hole or get launched > > > > > out of a cannon into the sun, any mails sent to jsnow@redhat.com can > > > > > be recovered by Red Hat in general, so there's a sufficient recourse > > > > > for recovering the account in that circumstance. > > > > > > > > Thanks, I have added the PyPI QEMU user and added you as the admin > > > > contact: > > > > https://wiki.qemu.org/AdminContacts#Other_resources > > > > > > > > Stefan > > > > > > Thanks, Stefan! > > > > > > As additional context, there is currently a single package that > > > belongs to that user, "qemu.qmp" [1]. I published it "in advance" to > > > be able to test integration in an RFC patch set I posted to the list > > > just before the winter break [2]. The package is an "alpha prerelease" > > > and is at a very low-risk to be installed by accident. The version > > > chosen here will be considered "less than" any other valid version > > > string chosen, and can be deleted permanently from PyPI after > > > consensus on list review. Please forgive the mid-review publishing. > > > The exact metadata, wording of the README, etc is still under review > > > here [3]. > > > > > > As for the PyPI account itself, I have volunteered to administer it. > > > If anyone wants access (esp. a leadership committee member from > > > another employer), please contact me - I'm happy to share. > > > > As a general rule we should ensure we always have 2 nominated people > > with access to any account held on behalf of the QEMU project, so we > > have some redundancy in case of unexpected events. So we definitely > > ought to have a 2nd person with access to PyPI even if they do nothing > > with it. > > > > I'm perfectly fine with that. It'd increase the fault tolerance to > have someone from outside of RH be the paper-admin there. Any > volunteers? > > (I can add your email as a secondary contact to the account such that > you would be able to use that email to initiate an account recovery, > but you wouldn't receive email from PyPI concerning the comings and > goings of the account. Your name and email would not show up on any > PyPI package pages, so it should very hopefully not involve really any > actual maintainership on your part.) In my case I expect it could complain that my email(s) are already in use for other PyPI accounts of my own. 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 :|