From: Julien Desfossez <jdesfossez@efficios.com>
To: diamon-discuss@lists.linuxfoundation.org
Subject: [diamon-discuss] Conference calls topics
Date: Fri, 21 Oct 2016 16:18:03 -0400 [thread overview]
Message-ID: <20161021201803.GF4618@sinkpad.internal.efficios.com> (raw)
Hi,
I am looking for topics and people interested in giving conference calls
to this workgroup in the near future.
The format is short calls (between 20-60 minutes), with or without
visual support, and oriented around discussions between developers and
users of diagnostic and monitoring tools (focused on Linux and Open
Source mostly, but not necessarily limited to).
The subjects include:
- New diagnostic and monitoring tools or features currently in
development that would benefit from early feedback by this workgroup
(it does not need to be fully working/finished),
- Stories about diagnostic and monitoring use-cases in various
situations,
- Workflow: show us your workflow or ask recommendations based on the
problems you are facing,
- War stories ("How we identified that specific problem"),
- Open questions to address common problems/limitations with the
existing tools or identify what is the right tool/method to
solve/understand a problem
- Other ideas around these subjects.
The goal would be to organize 1 of those calls each month.
If you are interested to present, please reply with a short description
of the presentation you would be willing to give when you expect to be
ready, and I will schedule it.
Also, if you know other people from outside this group that might have
interesting presentations/stories to tell, please forward them this
message or ask them to contact me.
Thanks,
Julien
next reply other threads:[~2016-10-21 20:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 20:18 Julien Desfossez [this message]
2016-10-26 15:31 ` [diamon-discuss] Conference calls topics Mathieu Desnoyers
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=20161021201803.GF4618@sinkpad.internal.efficios.com \
--to=jdesfossez@efficios.com \
--cc=diamon-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 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.