From mboxrd@z Thu Jan 1 00:00:00 1970 From: ben.hutchings@codethink.co.uk (Ben Hutchings) Date: Wed, 18 Apr 2018 16:32:04 +0100 Subject: [cip-dev] Kernel maintenance weekly meeting through IRC In-Reply-To: <1605667.vNQfNKazDM@linux-if6s> References: <1637483.JF1BPEa7VF@linux-if6s> <1524063136.2587.8.camel@codethink.co.uk> <1605667.vNQfNKazDM@linux-if6s> Message-ID: <1524065524.2587.10.camel@codethink.co.uk> To: cip-dev@lists.cip-project.org List-Id: cip-dev.lists.cip-project.org On Wed, 2018-04-18 at 16:58 +0200, Agust?n Benito Bethencourt wrote: > Hi Ben, > > On Wednesday, 18 April 2018 16:52:16 CEST Ben Hutchings wrote: > > On Mon, 2018-04-16 at 19:06 +0800, SZ Lin (???) wrote: > > > Hi Ben, > > > > > > The following questions are which we want to know, please feel free to > > > discuss with us. > > > > > > 1. CIP kernel maintenance team working model > > > > > > Do you have any suggested working model for CIP kernel maintenance team ? > > > e.g., Debian kernel team (CPU architecture based) or upstream kernel > > > (subsystem based) > > > > I think this would depend on how many developers would be working on it > > (from all CIP members) and how much time they can devote. > > > > > 2. Hands-on tasks for team member > > > > > > We can start to review changes on the LTS branch; however, we would > > > like to know if you have any preferred collaboration model for > > > reviewing the results from team member. > > > > I think that developers who are used to doing public review of patches > > should do that directly on the stable mailing list.??If you have > > developers that don't have that experience, but want to start, then > > they should initially send their review responses to an experienced > > colleague or to me. > > In case the Moxa developers prefer you to mentor them for some time, should? > they be looking into patches selected by them or do you have in mind some they? > should start looking at? I suggest looking at the most recent series sent out for review (4.4.128). I can send this as a mailbox file for those who weren't already susbcribed to the stable list. Ben. -- Ben Hutchings Software Developer, Codethink Ltd.