Ampere's CCLA Schedule A update 2025-02-10

Thang Nguyen OS thang at amperemail.onmicrosoft.com
Fri Feb 14 17:41:03 AEDT 2025


Thanks Andrew for your feedback. Please see my comment inline

> On 14 Feb 2025, at 12:23, Andrew Jeffery <andrew at codeconstruct.com.au> wrote:
> 
> On Thu, 2025-02-13 at 04:17 +0000, Thang Nguyen OS wrote:
>> Hi Andrew Geissler,
>> Attachment is the updated schedule A of CCLA from Ampere.
>> 
>> Please help review.
>> 
>> Note that Hieu Le will replace me as Ampere CLA Manager. I will check
>> with you in Discord to change maintainer access from me to Hieu for
>> what I am handling (openbmc/meta-ampere and ampere-ipmi-oem,
>> ssifbridge).
> 
> I don't have concerns with Hieu replacing you as CLA manager, however
> the expectations are different for maintenance roles. Background here:
> 
> https://github.com/openbmc/docs/blob/master/community-membership.md
> 
> Specifically:
> 
> * https://github.com/openbmc/docs/blob/master/community-
>   membership.md#platform-maintainer
> * https://github.com/openbmc/docs/blob/master/community-
>   membership.md#subproject-owner
> 
> openbmc/meta-ampere still has Thu as maintainer, ampere-ipmi-oem has
> Dung, and ssifbridge still has Chuong. These won't become unmaintained.
Actually, Chuong changed to another role in Ampere before so I am the one who reviewed and merged changes in ssifbridge so far.
Dung is inactive in ampere-ipmi-oem also.
> 
> Hieu should be subject to the expectations outlined in the community
> membership document, as everyone else is. Currently Hieu has few
> changes pushed to Gerrit.
Do you think I should update the Ampere CCLA to add me as member again so that I will continue to maintain these repos until Hieu satisfies requirements?
> Working through the process is an important demonstration of alignment
> with community norms and values. It takes time. It protects the project
> and community. It is what provides social and technical stability.
> 
> Andrew
> 



More information about the openbmc mailing list