Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <b75c9696-9abb-7a3f-0fb2-56af8ef21bb6@redhat.com>
Date:   Mon, 5 Jun 2023 18:48:44 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.10.0
Subject: Re: [PATCH v2] KVM: MAINTAINERS: note that linux-kvm.org isn't
 current
Content-Language: en-US
To:     Sean Christopherson <seanjc@google.com>,
        Randy Dunlap <rdunlap@infradead.org>
Cc:     linux-kernel@vger.kernel.org, kvm@vger.kernel.org
References: <20230525153204.27960-1-rdunlap@infradead.org>
 <ZHqSYbYscprsU2qT@google.com>
From:   Paolo Bonzini <pbonzini@redhat.com>
In-Reply-To: <ZHqSYbYscprsU2qT@google.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 6/3/23 03:07, Sean Christopherson wrote:
> It's definitely stale, though unless Red Hat (presumed hoster) plans on decomissioning
> the site, I'd prefer to keep the reference and instead improve the site.  We (Google)
> are planning on committing resources to update KVM documentation that doesn't belong
> in the kernel itself, and updatingwww.linux-kvm.org  instead of creating something new
> seems like a no-brainer.  I can't promise an updates will happen super quickly, but I
> will do what I can to make 'em happen sooner than later.

We don't plan to decommission the website (especially not the old KVM 
Forum content), though we might move it over to the same 
(container-based) setup as wiki.qemu.org.

What content do you have in mind that doesn't fit in the kernel 
Documentation/ tree?

Paolo