Hi All,
We all know Arm-Arch SIG was built months ago. It absolutely is a good news for all who
have strong interests on Arm64. But SIG seems a bit too quiet. So I would like to raise
some ideas below to trigger the possible wide discussion.
Because Arm-Arch SIG is just initiated, some general questions probably make sense.
* What is role and objective of Arm-Arch SIG
* To steer the Arm64 based technology directions? To productize some valuable
architectural features based on service scenarios? To stabilize Arm64 based OS as the
cornerstone of OpenAnolis? Or ….
* There are many other SIGs, such as Cloud Kernel, what is the relationship with or
difference from those partner SIGs?
* As the downstream of Linux kernel mainline, how to interact with mainline?
* …
* What is the governance hierarchy or model of this SIG
* Are there any consistent principles about SIG governance?
* Are there any role definitions for this SIG?
* How to keep the balance between efficiency and high quality output based on some
governance rules?
* …
* Are there any facilities or resources needed to support SIG running
* How to improve the cooperation among multiple participators?
* How to make engineering contributions in this SIG?
* How to make the engineers’ life more easier?
* …
* The first step for Arm-Arch
* What can/should we do as the first step?
* Can we discuss everything about Arm-Arch in public channels from now on?
* …
Any comments are welcome! To make Arm-Arch SIG better.
Cheers,
Erik
显示某日回复
Thanks Erik for the input.
Suggest to arrange the 1st Arm arch SIG meeting to address those topics if not all and
reach certain agreement first.
In addition, we may use this 1st meeting to confirm and agree on meeting logistics, such
as meeting tool (MS Teams or Zoom or DingTalk), meeting cadence (monthly or bi-weekly),
meeting date/time, meeting host (dedicated person or in-turn) and minutes taker.
After the 1st meeting, it’s better for next meeting host to collect topics before next
meeting and track action items of previous meeting in beginning of next meeting.
Best Regards,
Tony Chen
Director Software Ecosystem
Infrastructure Line of Business
Arm China
+8615801991960
From: Erik Yuan <Erik.Yuan(a)arm.com>
Sent: Wednesday, November 24, 2021 1:52 PM
To: arm-arch(a)lists.openanolis.cn
Cc: Tony Chen <Tony.Chen(a)arm.com>om>; nd <nd(a)arm.com>
Subject: Some ideas about Arm-Arch SIG running
Hi All,
We all know Arm-Arch SIG was built months ago. It absolutely is a good news for all who
have strong interests on Arm64. But SIG seems a bit too quiet. So I would like to raise
some ideas below to trigger the possible wide discussion.
Because Arm-Arch SIG is just initiated, some general questions probably make sense.
* What is role and objective of Arm-Arch SIG
* To steer the Arm64 based technology directions? To productize some valuable
architectural features based on service scenarios? To stabilize Arm64 based OS as the
cornerstone of OpenAnolis? Or ….
* There are many other SIGs, such as Cloud Kernel, what is the relationship with or
difference from those partner SIGs?
* As the downstream of Linux kernel mainline, how to interact with mainline?
* …
* What is the governance hierarchy or model of this SIG
* Are there any consistent principles about SIG governance?
* Are there any role definitions for this SIG?
* How to keep the balance between efficiency and high quality output based on some
governance rules?
* …
* Are there any facilities or resources needed to support SIG running
* How to improve the cooperation among multiple participators?
* How to make engineering contributions in this SIG?
* How to make the engineers’ life more easier?
* …
* The first step for Arm-Arch
* What can/should we do as the first step?
* Can we discuss everything about Arm-Arch in public channels from now on?
* …
Any comments are welcome! To make Arm-Arch SIG better.
Cheers,
Erik