B2C2C/B2B2C
(version that also exists in AUP repo)
(content copied to users repo)
Canonical Version
Amended Version
Forked / Cloned
Version
Content Flow
(created by or on behalf of
Arm Education)
Openly accessible content which can be created with and without Arm
endorsement
1. Canonical Version
created by Arm
Education and published
on Arm approved
platforms (materials on
GitHub, marketing pages
on Arm.com)
2. The Arm engineer &
SME agree & create
list of modifications +/
or amends they would
like to see made to
the EdKit, e.g.
additional labs
Yes
6. The content is
reviewed by Arm/
SME, approved &
taken back into the
canonical version
with version history
Decision –
is the content
accepted?
No
8. A new version is added
alongside the canonical
version, e.g., porting to a
different board because the
original board is no longer
available
e.g., lecturer, engineer
+/or hobbyist who
3. EdKit material is
want to make
forked or cloned to a
modifications or add GitHub user’s repo
to content
Decision ‐
content to be
merged back
into canonical
version?
4. Content now
exists on user’s
repo
5. Contributors
modify or add to
content and create
pull request for Arm
to consider merging
changes/updates)
7. Modified/
amended content
now exists on user’s
repo
9. A version exists
alongside the canonical
version. Any subsequent
changes to these versions
are subject to QA &
approval by the owner of
the material (Partner or
Maintainer)
This isn’t necessarily bad
but just not part of the
official version & it exists
independently to the
main version in another
repo