ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: Mark Brown <broonie@kernel.org>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Talking code or talking in code!
Date: Mon, 3 Jun 2019 11:39:55 -0600	[thread overview]
Message-ID: <b75ac5fd-3734-fbc1-a0af-bd143c70761e@linuxfoundation.org> (raw)
In-Reply-To: <20190603155102.GX2456@sirena.org.uk>

On 6/3/19 9:51 AM, Mark Brown wrote:
> On Fri, May 31, 2019 at 09:42:52AM -0600, Shuah Khan wrote:
> 
>> Let me go over my vision for this time slot at the Maintainers Summit
>> if we choose to add it. This isn't going to be a long deep dive session
>> on the research. I asked Isabella to work with the following outline:
> 
>> - A short summary of Sentimine
>> - A short survey of 2 or 3 emails. We do the survey - I can have her
>>    share the survey format ahead of time. Based on my recollection of
>>    the survey from OSLS presentation, it asks participants to identify
>>    the tone of the email. Positive/negative/neutral.
>> - Isabella compares these results to the tool's analysis. The goal
>>    is to see how far off the tool's analysis from real developers
>>    take on these emails.
> 
> Does that need to be done at the summit or could it be done offline with
> the summit attendees (or with a list of people pulled from the active
> developers stats or something for that matter)?  But then...
> 

I like this idea. This helps us gather data from more developers than
just the Maintainer summit attendees. We can do this after the trial
run at the Maintainer summit, provided we do add the topic to the
agenda.

>> In addition, I think the tool should also look at clarity of
>> communication not just tone. To me this is the most useful part for
>> us. My motivation and goal is to explore if we can take this opportunity
>> to influence the direction of this research to look at what would be
>> useful to us as a community.
> 
> ...it does sound like a useful way of kicking off a discussion.  Perhaps
> the survey could be done in advance and then the discussion jump
> straight on to any differences in evaluation?  I do agree that clarity
> is worth looking at, especially with regard to non-native English
> speakers.
> 

Doing survey ahead of time would help us spend more time on differences
in evaluation and help identify areas for improvement in the tool and
the assumptions it is making.

If we chose to go this route, I can work with Isabella to send the
survey out a day or two in advance to gather data.

thanks,
-- Shuah

  reply	other threads:[~2019-06-03 17:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-30 22:19 [Ksummit-discuss] [MAINTAINERS SUMMIT] Talking code or talking in code! Shuah Khan
2019-05-31  2:14 ` Theodore Ts'o
2019-05-31  2:42   ` Matthew Wilcox
2019-05-31 12:12     ` Laura Abbott
2019-05-31 15:54       ` Shuah Khan
2019-05-31 15:42   ` Shuah Khan
2019-05-31 16:25     ` Joe Perches
2019-05-31 16:34       ` Shuah Khan
2019-06-03 15:51     ` Mark Brown
2019-06-03 17:39       ` Shuah Khan [this message]
2019-07-28 22:05         ` [Ksummit-discuss] [MAINTAINERS SUMMIT] (withdrawn) " Shuah Khan

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=b75ac5fd-3734-fbc1-a0af-bd143c70761e@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=broonie@kernel.org \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    /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).