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 X-Spam-Level: X-Spam-Status: No, score=-7.7 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id DA296C11F64 for ; Thu, 1 Jul 2021 19:49:04 +0000 (UTC) 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 mail.kernel.org (Postfix) with ESMTPS id 517B161406 for ; Thu, 1 Jul 2021 19:49:04 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 517B161406 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=redhat.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Received: from localhost ([::1]:49246 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lz2gJ-00066E-CE for qemu-devel@archiver.kernel.org; Thu, 01 Jul 2021 15:49:03 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:59362) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lz2fX-0005Kg-Sg for qemu-devel@nongnu.org; Thu, 01 Jul 2021 15:48:15 -0400 Received: from us-smtp-delivery-124.mimecast.com ([216.205.24.124]:48919) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lz2fR-00023l-MO for qemu-devel@nongnu.org; Thu, 01 Jul 2021 15:48:14 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1625168887; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=mHncT7m9Wq/D3Ci1osJ3XJCW44hmjskAh+Vbhfceq8Q=; b=HX2i6L2CUXXS/czmWGMEroipHWcAhDpAHEAB1GaWIdIURbLP8OpsbQdOHU1pFir44bXCpP w7LGBleEAYXIVhl9RVHFT3wVtBBKc6r4QTHpcxUsPhYUUFYE7lsKAPdTC6a/yRHxKg7d+d C6ZAAqbZojkJHZN1l8AhM0HG5FGepu8= Received: from mail-pf1-f198.google.com (mail-pf1-f198.google.com [209.85.210.198]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-301-idvCpEaHPHetnXej53UI4Q-1; Thu, 01 Jul 2021 15:48:06 -0400 X-MC-Unique: idvCpEaHPHetnXej53UI4Q-1 Received: by mail-pf1-f198.google.com with SMTP id s15-20020a056a0008cfb0290306b50a28ecso4710976pfu.10 for ; Thu, 01 Jul 2021 12:48:06 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=mHncT7m9Wq/D3Ci1osJ3XJCW44hmjskAh+Vbhfceq8Q=; b=fENsSH9abTN+RQ3ZTqD8HWpBgN2fd+vHbLeehwOYg38yNJN1puXZPZaI7vlnCP+wT4 CZmjDyGFLqP+4sQiA2T25/byZ6F/gPcgtfYH/U6azZSoMRrnPx3Ht4mJX+Y4f7Zxhey0 ZoSb85b/K3O40k/DD6oPx+ufRJ8S4oc3e1A+XPJmmVZ6vpkS9RE0PiVwzuhra/zK+ZMq MtFHMV+jpeVxb7zoXL2hY+ITNjbY9heV1OK0rWJK88KU9p3xvhzsVV1IoVCzW0R6SXzj tSR1sZxm7wU28d46ZVVPVodlKMmS97W43OjLOCt75aB0QXVUiNWPos0CLBuxX4aQHPIj TZ6w== X-Gm-Message-State: AOAM533xb83Ydci7gXDYuEBTJsM6mJhMyERjA07vrC3tgCNhXuiLJ7oG 5OqQ0B41lVK98AlLdMImlI1AjUQLPefjP3eBryDE6kwbyvxN0odhqFbWipq1BPafFkMhTG2OEiZ ZSdqyx7woZpL0s41z7+sIeqc7Jg8bKNbfMShxjFHcS4fp3SmMt9o1l+U5sZ7Jks6B X-Received: by 2002:a17:90a:b94c:: with SMTP id f12mr11220513pjw.58.1625168885160; Thu, 01 Jul 2021 12:48:05 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxOjOwIXYnMbuZE18lfY6IA4PHe9KuuWOYAnS4K7dxZv8nYAV4pZau/EYRUwZfd0qsMwB5bHg== X-Received: by 2002:a17:90a:b94c:: with SMTP id f12mr11220487pjw.58.1625168884738; Thu, 01 Jul 2021 12:48:04 -0700 (PDT) Received: from ?IPv6:2601:1c0:4600:3f84:cb33:5075:e7f0:7862? ([2601:1c0:4600:3f84:cb33:5075:e7f0:7862]) by smtp.gmail.com with ESMTPSA id b3sm825046pfi.179.2021.07.01.12.48.04 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 01 Jul 2021 12:48:04 -0700 (PDT) Subject: Re: Contributions: Adding New Devices To: Federico Vaga , qemu-devel@nongnu.org References: <20210630140102.ecuyxyeqnthvausb@cwe-513-vol689.cern.ch> From: Connor Kuehl Message-ID: Date: Thu, 1 Jul 2021 12:48:03 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0 MIME-Version: 1.0 In-Reply-To: <20210630140102.ecuyxyeqnthvausb@cwe-513-vol689.cern.ch> Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=ckuehl@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Received-SPF: pass client-ip=216.205.24.124; envelope-from=ckuehl@redhat.com; helo=us-smtp-delivery-124.mimecast.com X-Spam_score_int: -31 X-Spam_score: -3.2 X-Spam_bar: --- X-Spam_report: (-3.2 / 5.0 requ) BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.402, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=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.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: "Qemu-devel" On 6/30/21 7:01 AM, Federico Vaga wrote: > Hello, > > I can't find this information on the website, so here I am. > > I developed a QEMU device that virtualises a PCI card that we widely use at CERN. > But this card is only used at CERN. > > Clearly, having CERN specific devices in QEMU does not help much the qemu > community, hence I maintain an internal QEMU fork. > > But, I was wondering what is the QEMU policy about contributions that are known to be > used only by a handful of people (one organization in this case)? Are they accepted? Your first instinct is correct that it's unlikely that the community will be able to maintain a device if it's really so niche as to only be used at your organization. However, if you do decide to try to upstream it, it could only help your chances if you or some of your colleagues agreed to maintain it for the QEMU community. This mainly involves adding an entry to the MAINTAINERS file where, if accepted, the expectation is that you'll be reachable within reason to review patches, make pull requests, help discuss bugs in the subsystem, etc. Sorry I don't have a concrete "yes" or "no" for you; but I'd recommend giving it a shot if you have the time. Connor