All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: Thomas Huth <thuth@redhat.com>, qemu-devel@nongnu.org
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
	"Peter Krempa" <pkrempa@redhat.com>,
	"Daniel P . Berrangé" <berrange@redhat.com>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH 2/2] Gitlab: Add "Feature Request" issue template.
Date: Fri, 21 May 2021 11:49:39 -0400	[thread overview]
Message-ID: <9a619043-aa44-caa7-b242-bc590008ebb4@redhat.com> (raw)
In-Reply-To: <e79bc75c-93b7-6810-e07e-35c03c9c2983@redhat.com>

On 5/20/21 2:52 AM, Thomas Huth wrote:
> On 19/05/2021 23.32, John Snow wrote:
>> Copied from Peter Krempa's libvirt template, feature.md.
>>
>> CC: Peter Krempa <pkrempa@redhat.com>
>> Signed-off-by: John Snow <jsnow@redhat.com>
>> ---
>>   .gitlab/issue_templates/feature_request.md | 13 +++++++++++++
>>   1 file changed, 13 insertions(+)
>>   create mode 100644 .gitlab/issue_templates/feature_request.md
>>
>> diff --git a/.gitlab/issue_templates/feature_request.md 
>> b/.gitlab/issue_templates/feature_request.md
>> new file mode 100644
>> index 00000000000..26901ff00c4
>> --- /dev/null
>> +++ b/.gitlab/issue_templates/feature_request.md
>> @@ -0,0 +1,13 @@
>> +## Goal
>> +<!-- Describe the final result you want to achieve. Avoid design 
>> specifics. -->
> 
> Since some people apparently had wrong expectations when filing a 
> feature request in the past, it might be good to add some words about 
> what to expect. Maybe something like this (re-using some wording that 
> Daniel already added to some tickets in the past IIRC):
> 
>   Please note that the QEMU, like most open source projects, relies on 
> contributors who have motivation, skills and available time to work on 
> implementing particular features. Contributors naturally tend to focus 
> on features that result in the greatest benefit to their own use cases. 
> Thus the QEMU project doesn't implement new big features (like target 
> architectures or board models) on demand based on feature requests here; 
> they're a lot of work to do. Instead we simply code-review and 
> incorporate new big features as and when people decide to write them and 
> submit the patches. So please only submit small requests here. Thanks!
> 
> ?
> 

OK, I may edit it just a little bit to appear a touch softer. A concern 
I have is that users may not really know the difference between a 
'small' and a 'big' feature, necessarily.

Still, setting an expectation might help...

--js



  reply	other threads:[~2021-05-21 15:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-19 21:32 [PATCH 0/2] Gitlab: Add issue templates John Snow
2021-05-19 21:32 ` [PATCH 1/2] Gitlab: Add "Bug" issue reporting template John Snow
2021-05-20  6:34   ` Peter Krempa
2021-05-21 15:46     ` John Snow
2021-05-19 21:32 ` [PATCH 2/2] Gitlab: Add "Feature Request" issue template John Snow
2021-05-20  6:52   ` Thomas Huth
2021-05-21 15:49     ` John Snow [this message]
2021-05-21 16:18       ` Daniel P. Berrangé

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=9a619043-aa44-caa7-b242-bc590008ebb4@redhat.com \
    --to=jsnow@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=berrange@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=pkrempa@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=thuth@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.