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?
Ben.
-- Agustín Benito Bethencourt Principal Consultant Codethink Ltd
