All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: virtio-fs-list <virtio-fs@redhat.com>
Subject: [Virtio-fs] [ANNOUNCE] Bi-weekly community calls for virtiofs discussions
Date: Thu, 25 Feb 2021 13:52:25 -0500	[thread overview]
Message-ID: <20210225185225.GC53072@redhat.com> (raw)

Hi All,

We are planning to host bi-weekly 1 hour call to discuss virtiofs
development and issues. We already have folks sending patches on 
email list and asking questions privately. We thought it probably
is a good idea to do a face to face call once in a while to discuss
issues, current state, what are the shortcomings and how to improve
virtiofs further.

Lets give it a try and hopefully it helps. If it does not, we can stop
these meetings. :-)

I have setup a public etherpad which has details of meetings and
also a section for agenda for the next meeting on March 10, 2021,
14:00UTC.

https://etherpad.opendev.org/p/virtiofs-external-meeting

Feel free to join us for the call and also feel free to add items
to the agenda list.

Stefan has also updated the https://virtio-fs.gitlab.io/ webpage with
details of community call.

Looking forward to see you on these calls.

Thanks
Vivek


             reply	other threads:[~2021-02-25 18:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-25 18:52 Vivek Goyal [this message]
2021-03-09 13:42 ` [Virtio-fs] [ANNOUNCE] Bi-weekly community calls for virtiofs discussions Vivek Goyal
2021-03-23 17:30 ` Vivek Goyal
2021-04-06 16:43 ` Vivek Goyal
2021-04-20 22:12 ` Vivek Goyal
2021-05-04 17:49 ` Vivek Goyal
2021-05-18 19:57 ` Vivek Goyal
2021-06-02 11:46 ` Vivek Goyal
2021-06-16 12:38 ` Vivek Goyal
2021-06-30 12:36 ` Vivek Goyal
2021-08-09 13:27 ` Vivek Goyal

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=20210225185225.GC53072@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=virtio-fs@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.