ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy6545@gmail.com>
To: "Theodore Y. Ts'o" <tytso@mit.edu>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Talking code or talking in code!
Date: Thu, 30 May 2019 22:42:34 -0400	[thread overview]
Message-ID: <CAFhKne_20HD6kQqLcPKncFUmbhQbwj-htWeJ8B0oEn-xRnX6Jg@mail.gmail.com> (raw)
In-Reply-To: <20190531021421.GA8123@mit.edu>

[-- Attachment #1: Type: text/plain, Size: 2704 bytes --]

I'd be interested to know how this compares to Dawn Foster's work that was
presented last year:
https://ossna18.sched.com/event/FAON/kernel-mailing-list-collaboration-dawn-m-foster-the-scale-factory

On Thu., May 30, 2019, 22:15 Theodore Ts'o, <tytso@mit.edu> wrote:

> On Thu, May 30, 2019 at 04:19:20PM -0600, Shuah Khan wrote:
> > We as a community talk code in emails. Do we talk in code at times? How
> > effective are we in communicating with each other?
> >
> > I would like to propose a topic to explore our communication styles to
> > get a better understanding of how effective we are. I am hoping, we
> > could become more productive, if we get some insight into whether or not
> > we talk in code while we talk code.
> >
> > We could do this by inviting Isabella Ferreira, PhD Student in Computer
> > Engineering, Polytechnique Montréal to tell us about Sentimine,
> > which is a plugin on top of the cregit platform focused on analyzing
> > communication in open source communities. It will include a short survey
> > focused on analyzing a few emails for clarity and perception.
>
> Hi Shuah,
>
> If the goal is to get Isabella's ideas more exposure, perhaps it would
> be better to ask if she would be willing to give a presentation at the
> more open Kernel Summit track during the LPC?
>
> It would appear that it's fairly early days for her work, from doing
> some web searching, the only thing I could really find was her 2019
> Open Source Leadership Summit presentations (slides here[1]) and the
> more formal academic paper[2].
>
> [1]
> https://events.linuxfoundation.org/wp-content/uploads/2018/07/OSS_Summit_Presentation.pdf
> [2] http://mcis.polymtl.ca/publications/2019/SEMotion_2019.pdf
>
> As near as I can tell the talk was not video recorded; which is a
> shame, since I wasn't able to pick up from the slide presentation the
> same kind of excitement that you clearly have over her work.  I was
> also very confused about how cregit (which analyzes code) mentioned in
> the last two slides relates to the work described in the first 80% of
> the slide deck, which appears to be analyzing mailing list text.
>
> I'd also think that if the goal is to have a conversation about
> communication styles, having that discussion with a wider circle might
> be more productive.  Or did you have something in mind about some
> decision that might get made at the Maintainer's Summit?
>
>                                     - Ted
> _______________________________________________
> Ksummit-discuss mailing list
> Ksummit-discuss@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss
>

[-- Attachment #2: Type: text/html, Size: 3743 bytes --]

  reply	other threads:[~2019-05-31  2:42 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 [this message]
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
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=CAFhKne_20HD6kQqLcPKncFUmbhQbwj-htWeJ8B0oEn-xRnX6Jg@mail.gmail.com \
    --to=willy6545@gmail.com \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=tytso@mit.edu \
    /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).