From: Shuah Khan <skhan@linuxfoundation.org>
To: ksummit-discuss@lists.linuxfoundation.org
Subject: [Ksummit-discuss] [MAINTAINERS SUMMIT] Talking code or talking in code!
Date: Thu, 30 May 2019 16:19:20 -0600 [thread overview]
Message-ID: <96c97a27-83a2-b86c-2880-984c9fa6d4b5@linuxfoundation.org> (raw)
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.
I participated in one of her previous presentations and found it a
useful experiment, as it made me stop and think about my understanding
and perception of interactions.
thanks,
-- Shuah
next reply other threads:[~2019-05-30 22:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 22:19 Shuah Khan [this message]
2019-05-31 2:14 ` [Ksummit-discuss] [MAINTAINERS SUMMIT] Talking code or talking in code! 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
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=96c97a27-83a2-b86c-2880-984c9fa6d4b5@linuxfoundation.org \
--to=skhan@linuxfoundation.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 read-only IMAP folder(s) and NNTP newsgroup(s).