All of lore.kernel.org
 help / color / mirror / Atom feed
From: sz.lin@moxa.com (SZ Lin (林上智))
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Kernel maintenance weekly meeting through IRC
Date: Thu, 12 Apr 2018 01:43:25 +0800	[thread overview]
Message-ID: <CAFk6z8PjT2xqGXF6rrKvjaSXfaGfdTOaGHe=MwLq-fZuSMKBnA@mail.gmail.com> (raw)
In-Reply-To: <1637483.JF1BPEa7VF@linux-if6s>

Hi Agustin,

I've organized the current member candidates and preferred subsystem in below

Member candidates/ subsystem
--------------------------------------------
Tzongyen/ RT preempt/ xenomai
Gavin/ Networking
Vidda/ Wireless networking
Taiyi/ Storage
Harry/ Linux Security Modules (LSM)
SZ/ Cellular
Wes/ Ethernet driver

We have learned maintenance policy of LTS;therefore, I think the next
step is to discuss how to start hands-on tasks.

Here is the proposed agenda for the meeting:

1. CIP kernel maintenance team working flow
e.g., by subsystem driven.

2. Hands-on tasks for team member

Any suggestions are welcome.

SZ

2018-04-03 17:01 GMT+08:00 Agust?n Benito Bethencourt
<agustin.benito@codethink.co.uk>:
>
> Dear colleagues at Moxa,
>
> what about having the agreed weekly IRC meeting on Thursdays at 10 BST (UTC
> +1), which is 11 CEST (UTC+2) and 17:00 CST (UTC+8) , in the #cip channel at
> freenode ?
>
>
> Best Regards
> --
> Agust?n Benito Bethencourt
> Principal Consultant
> Codethink Ltd
> _______________________________________________
> cip-dev mailing list
> cip-dev at lists.cip-project.org
> https://lists.cip-project.org/mailman/listinfo/cip-dev

  reply	other threads:[~2018-04-11 17:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-03  9:01 [cip-dev] Kernel maintenance weekly meeting through IRC Agustín Benito Bethencourt
2018-04-11 17:43 ` SZ Lin (林上智) [this message]
2018-04-16 11:06   ` SZ Lin (林上智)
2018-04-18 14:52     ` Ben Hutchings
2018-04-18 14:58       ` Agustín Benito Bethencourt
2018-04-18 15:32         ` Ben Hutchings
2018-04-16 11:54   ` Jan Kiszka

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='CAFk6z8PjT2xqGXF6rrKvjaSXfaGfdTOaGHe=MwLq-fZuSMKBnA@mail.gmail.com' \
    --to=sz.lin@moxa.com \
    --cc=cip-dev@lists.cip-project.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.