| Variable | Value |
|---|
Edit count of the user (user_editcount) | 2884 |
Name of the user account (user_name) | 'MGorny' |
Age of the user account (user_age) | 419623573 |
Page ID (page_id) | 62124 |
Page namespace (page_namespace) | 510 |
Page title (without namespace) (page_title) | 'ARM' |
Full page title (page_prefixedtitle) | 'Project:ARM' |
Action (action) | 'edit' |
Edit summary/reason (summary) | 'remove nerdboy' |
Old content model (old_content_model) | 'wikitext' |
New content model (new_content_model) | 'wikitext' |
Old page wikitext, before the edit (old_wikitext) | '{{Project
|Name=ARM Development
|Description=The ARM Development Project is devoted to keeping Gentoo in good shape on the ARM architecture.
|Email=arm@gentoo.org
|Bug assignment=Yes
|Packages=Yes
|IRC=#gentoo-arm
|ParentProject=Project:Gentoo
|PropagatesMembers=No
|Members={{Project Member
|Developer=User:Zero Chaos
|IsLead=No
}}{{Project Member
|Developer=User:Ago
|Role=Security bugs primarily
|IsLead=No
}}{{Project Member
|Developer=User:Blueness
|IsLead=No
}}{{Project Member
|Developer=User:Dilfridge
|Role=Release engineering
|IsLead=No
}}{{Project Member
|Developer=User:Dlan
|IsLead=No
}}{{Project Member
|Developer=User:Maekke
|IsLead=No
}}{{Project Member
|Developer=User:Vapier
|IsLead=No
}}{{Project Member
|Developer=User:Alicef
|Role=Kernel
|IsLead=No
}}{{Project Member
|Developer=User:Nerdboy
|Role=Kernel
|IsLead=No
}}{{Project Member
|Developer=User:Sam
|IsLead=Yes
}}{{Project Member
|Developer=User:Ajak
|IsLead=No
}}{{Project Member
|Developer=User:GYakovlev
|Role=installcd maintainer, misc helper
|IsLead=No
}}
{{Project Member
|Developer=User:Viorel
|IsLead=No
}}
}}
The Gentoo/ARM Project works to keep Gentoo the most up to date and fastest ARM distribution available. We are responsible for the maintenance of all ARM specific metadata and the testing of all other non ARM specific meta-data on the ARM architecture to ensure portability. Portability implies reusable metadata.
Bugs are tracked and resolved from the [http://bugs.gentoo.org Gentoo bug tracker] and correspondence is maintained on the various ARM related mailinglists. ({{IRC|gentoo-arm}} and those belonging to the sub-projects).
__TOC__
== Key facts ==
* ARM is 32-bit.
* ARM is little-endian.
* <= ARMv5te lacks proper hardware atomics, see {{Bug|721344}}.
Gentoo at the moment does not have any 32bit ARM development hardware. Most development and testing is done in
containers on a 80 core Neoverse arm64 machine that supports 32bit mode; stages are built quasi-natively on
that machine itself.
== Goals ==
The goal of the Gentoo ARM development project is to guarantee that the ARM packages build using Gentoo metadata are up to date. By continuously enhancing the metadata, we provide the ARM user with the Gentoo community feeling, performance, freedom and up-to-dateness. The meta-distribution notion allows for a user to to be as bleeding edge as he/she wants:
Gentoo is unique because of its interpretation of the Meta-Distribution notion: all architectures share the same 'generic' metadata (information about how to build packages - how to build a distribution). The ARM developers are responsible for building and testing packages using this meta-data. The meta-data gets marked 'tested' or 'stable' afterwards, depending on the building and testing experience. Our users can use (but don't have to use) this information to build a system that suits their needs.
=== Stabilization policy ===
{{Note|Users do '''not''' have to test themselves with FEATURES{{=}}test, although it's nice if they do. Please file a bug if a package works for you in stable and your system is stable. We want to mark it as such in Gentoo!}}
The Gentoo ARM development project supports various flavors of the 32-bit ARM architecture (to be precise: armv4/armv5/armv6/armv7) but the workload to test all packages on these platforms is excessive. So, successfully testing on armv7 is adequate.
Team members or developers must run <code>FEATURES=test</code> for all packages and ensure each package passes the test phase. This is '''not''' required just to simply file a bug and request keywording or stabilisation though - it is the responsibility of the arch teams to test, not the person requesting.
* vanilla-sources and gentoo-sources should be stabilized per the Kernel Project stabilization policy [[Project:Kernel#Kernel_stabilization]]
== Keywording ==
{{Tip|We want both stable <code>arm</code> '''and''' keywording <code>~arm</code> requests. File them!}}
See [[Project:ARM64#Keywording]].
== How to participate ==
Can you make computers do amazing things? Are you excited about exploring areas of computing never explored before? We are continuously looking for volunteers willing to spend some of their free time on this project. In return for your work, you get the respect of the ARM community.
If you are interested in helping, but don't have a niche that you are interested in filling, you can always look through [http://bugs.gentoo.org bugs.gentoo.org]. There are many many bugs waiting to be found and fixed and many enhancements looking to find someone to code them. Figure out a fix, implement it, test it, and then keep trying to make the patch smaller. Post it for review on [http://bugs.gentoo.org bugs.gentoo.org], and keep working on it. If it seems ignored, make a new comment in the bug and/or mention it in {{IRC|gentoo-arm}}.
Finally, feel free to add yourself with your IRC handle to our [[Embedded systems/ARM hardware list|ARM hardware list]] on the wiki. It's always nice to know what gadgets are out there!' |
New page wikitext, after the edit (new_wikitext) | '{{Project
|Name=ARM Development
|Description=The ARM Development Project is devoted to keeping Gentoo in good shape on the ARM architecture.
|Email=arm@gentoo.org
|Bug assignment=Yes
|Packages=Yes
|IRC=#gentoo-arm
|ParentProject=Project:Gentoo
|PropagatesMembers=No
|Members={{Project Member
|Developer=User:Zero Chaos
|IsLead=No
}}{{Project Member
|Developer=User:Ago
|Role=Security bugs primarily
|IsLead=No
}}{{Project Member
|Developer=User:Blueness
|IsLead=No
}}{{Project Member
|Developer=User:Dilfridge
|Role=Release engineering
|IsLead=No
}}{{Project Member
|Developer=User:Dlan
|IsLead=No
}}{{Project Member
|Developer=User:Maekke
|IsLead=No
}}{{Project Member
|Developer=User:Vapier
|IsLead=No
}}{{Project Member
|Developer=User:Alicef
|Role=Kernel
|IsLead=No
}}{{Project Member
|Developer=User:Sam
|IsLead=Yes
}}{{Project Member
|Developer=User:Ajak
|IsLead=No
}}{{Project Member
|Developer=User:GYakovlev
|Role=installcd maintainer, misc helper
|IsLead=No
}}{{Project Member
|Developer=User:Viorel
|IsLead=No
}}
}}
The Gentoo/ARM Project works to keep Gentoo the most up to date and fastest ARM distribution available. We are responsible for the maintenance of all ARM specific metadata and the testing of all other non ARM specific meta-data on the ARM architecture to ensure portability. Portability implies reusable metadata.
Bugs are tracked and resolved from the [http://bugs.gentoo.org Gentoo bug tracker] and correspondence is maintained on the various ARM related mailinglists. ({{IRC|gentoo-arm}} and those belonging to the sub-projects).
__TOC__
== Key facts ==
* ARM is 32-bit.
* ARM is little-endian.
* <= ARMv5te lacks proper hardware atomics, see {{Bug|721344}}.
Gentoo at the moment does not have any 32bit ARM development hardware. Most development and testing is done in
containers on a 80 core Neoverse arm64 machine that supports 32bit mode; stages are built quasi-natively on
that machine itself.
== Goals ==
The goal of the Gentoo ARM development project is to guarantee that the ARM packages build using Gentoo metadata are up to date. By continuously enhancing the metadata, we provide the ARM user with the Gentoo community feeling, performance, freedom and up-to-dateness. The meta-distribution notion allows for a user to to be as bleeding edge as he/she wants:
Gentoo is unique because of its interpretation of the Meta-Distribution notion: all architectures share the same 'generic' metadata (information about how to build packages - how to build a distribution). The ARM developers are responsible for building and testing packages using this meta-data. The meta-data gets marked 'tested' or 'stable' afterwards, depending on the building and testing experience. Our users can use (but don't have to use) this information to build a system that suits their needs.
=== Stabilization policy ===
{{Note|Users do '''not''' have to test themselves with FEATURES{{=}}test, although it's nice if they do. Please file a bug if a package works for you in stable and your system is stable. We want to mark it as such in Gentoo!}}
The Gentoo ARM development project supports various flavors of the 32-bit ARM architecture (to be precise: armv4/armv5/armv6/armv7) but the workload to test all packages on these platforms is excessive. So, successfully testing on armv7 is adequate.
Team members or developers must run <code>FEATURES=test</code> for all packages and ensure each package passes the test phase. This is '''not''' required just to simply file a bug and request keywording or stabilisation though - it is the responsibility of the arch teams to test, not the person requesting.
* vanilla-sources and gentoo-sources should be stabilized per the Kernel Project stabilization policy [[Project:Kernel#Kernel_stabilization]]
== Keywording ==
{{Tip|We want both stable <code>arm</code> '''and''' keywording <code>~arm</code> requests. File them!}}
See [[Project:ARM64#Keywording]].
== How to participate ==
Can you make computers do amazing things? Are you excited about exploring areas of computing never explored before? We are continuously looking for volunteers willing to spend some of their free time on this project. In return for your work, you get the respect of the ARM community.
If you are interested in helping, but don't have a niche that you are interested in filling, you can always look through [http://bugs.gentoo.org bugs.gentoo.org]. There are many many bugs waiting to be found and fixed and many enhancements looking to find someone to code them. Figure out a fix, implement it, test it, and then keep trying to make the patch smaller. Post it for review on [http://bugs.gentoo.org bugs.gentoo.org], and keep working on it. If it seems ignored, make a new comment in the bug and/or mention it in {{IRC|gentoo-arm}}.
Finally, feel free to add yourself with your IRC handle to our [[Embedded systems/ARM hardware list|ARM hardware list]] on the wiki. It's always nice to know what gadgets are out there!' |
Unified diff of changes made by edit (edit_diff) | '@@ -33,8 +33,4 @@
}}{{Project Member
|Developer=User:Alicef
-|Role=Kernel
-|IsLead=No
-}}{{Project Member
-|Developer=User:Nerdboy
|Role=Kernel
|IsLead=No
@@ -49,6 +45,5 @@
|Role=installcd maintainer, misc helper
|IsLead=No
-}}
-{{Project Member
+}}{{Project Member
|Developer=User:Viorel
|IsLead=No
' |
Old page size (old_size) | 5052 |
Lines added in edit (added_lines) | [
0 => '}}{{Project Member'
] |
Lines removed in edit (removed_lines) | [
0 => '|Role=Kernel',
1 => '|IsLead=No',
2 => '}}{{Project Member',
3 => '|Developer=User:Nerdboy',
4 => '}}',
5 => '{{Project Member'
] |
New page text, stripped of any markup (new_text) | '
ARM Development
Description
The ARM Development Project is devoted to keeping Gentoo in good shape on the ARM architecture.
Project email
arm@gentoo.org
Packages
p.g.o/arm@gentoo.org
IRC channel
#gentoo-arm (webchat)
Bugs
Related bugs
Lead(s)
Sam James
(sam) No lead election date set
Member(s)
Agostino Sarubbo
(ago)Security bugs primarilyJohn Helmert III
(ajak)Arisu Tachibana
(arisut)KernelAnthony G. Basile
(blueness)Andreas K. Hüttel
(dilfridge)Release engineeringYixun Lan
(dlan)Georgy Yakovlev
(gyakovlev)installcd maintainer, misc helperMarkus Meier
(maekke)Steve Arnold
(nerdboy)KernelMike Frysinger
(vapier)Viorel Munteanu
(ceamac)Rick Farina
(zerochaos)
Subproject(s)(and inherited member(s))
(none)
Parent Project
Gentoo
Project listing
The Gentoo/ARM Project works to keep Gentoo the most up to date and fastest ARM distribution available. We are responsible for the maintenance of all ARM specific metadata and the testing of all other non ARM specific meta-data on the ARM architecture to ensure portability. Portability implies reusable metadata.
Bugs are tracked and resolved from the Gentoo bug tracker and correspondence is maintained on the various ARM related mailinglists. (#gentoo-arm (webchat) and those belonging to the sub-projects).
Contents
1 Key facts
2 Goals
2.1 Stabilization policy
3 Keywording
4 How to participate
Key facts[edit]
ARM is 32-bit.
ARM is little-endian.
<= ARMv5te lacks proper hardware atomics, see bug #721344.
Gentoo at the moment does not have any 32bit ARM development hardware. Most development and testing is done in
containers on a 80 core Neoverse arm64 machine that supports 32bit mode; stages are built quasi-natively on
that machine itself.
Goals[edit]
The goal of the Gentoo ARM development project is to guarantee that the ARM packages build using Gentoo metadata are up to date. By continuously enhancing the metadata, we provide the ARM user with the Gentoo community feeling, performance, freedom and up-to-dateness. The meta-distribution notion allows for a user to to be as bleeding edge as he/she wants:
Gentoo is unique because of its interpretation of the Meta-Distribution notion: all architectures share the same 'generic' metadata (information about how to build packages - how to build a distribution). The ARM developers are responsible for building and testing packages using this meta-data. The meta-data gets marked 'tested' or 'stable' afterwards, depending on the building and testing experience. Our users can use (but don't have to use) this information to build a system that suits their needs.
Stabilization policy[edit]
NoteUsers do not have to test themselves with FEATURES=test, although it's nice if they do. Please file a bug if a package works for you in stable and your system is stable. We want to mark it as such in Gentoo!
The Gentoo ARM development project supports various flavors of the 32-bit ARM architecture (to be precise: armv4/armv5/armv6/armv7) but the workload to test all packages on these platforms is excessive. So, successfully testing on armv7 is adequate.
Team members or developers must run FEATURES=test for all packages and ensure each package passes the test phase. This is not required just to simply file a bug and request keywording or stabilisation though - it is the responsibility of the arch teams to test, not the person requesting.
vanilla-sources and gentoo-sources should be stabilized per the Kernel Project stabilization policy Project:Kernel#Kernel_stabilization
Keywording[edit]
TipWe want both stable arm and keywording ~arm requests. File them!
See Project:ARM64#Keywording.
How to participate[edit]
Can you make computers do amazing things? Are you excited about exploring areas of computing never explored before? We are continuously looking for volunteers willing to spend some of their free time on this project. In return for your work, you get the respect of the ARM community.
If you are interested in helping, but don't have a niche that you are interested in filling, you can always look through bugs.gentoo.org. There are many many bugs waiting to be found and fixed and many enhancements looking to find someone to code them. Figure out a fix, implement it, test it, and then keep trying to make the patch smaller. Post it for review on bugs.gentoo.org, and keep working on it. If it seems ignored, make a new comment in the bug and/or mention it in #gentoo-arm (webchat).
Finally, feel free to add yourself with your IRC handle to our ARM hardware list on the wiki. It's always nice to know what gadgets are out there!' |
Parsed HTML source of the new revision (new_html) | '<div class="mw-parser-output"><table class="table table-condensed" style="width: 30em; font-size: 95%; border: 1px solid #ddd; background-color: #f9f9f9; color: black; margin-bottom: 0.5em; margin-left: 1em; padding: 0.2em; float: right; clear: right; text-align:left;">
<tbody><tr>
<th style="text-align: center; background-color:#3E355A; color: white;" colspan="2"><big>ARM Development</big>
</th></tr>
<tr valign="top">
<th>Description
</th>
<td style="text-align: justify;">The ARM Development Project is devoted to keeping Gentoo in good shape on the ARM architecture.
</td></tr>
<tr>
<th><span title="Mails to member(s) listed below.">Project email</span>
</th>
<td><a rel="nofollow" class="external text" href="mailto:arm@gentoo.org">arm@gentoo.org</a>
</td></tr>
<tr>
<th><span title="Link to packages.g.o for ebuilds maintained in gentoo.git.">Packages</span>
</th>
<td><span class="fa fa-cubes fa-fw"></span> <a rel="nofollow" class="external text" href="https://packages.gentoo.org/maintainer/arm@gentoo.org">p.g.o/arm@gentoo.org</a>
<p><br />
</p><p><br />
</p>
</td></tr>
<tr>
<th><span title="The link opens an IRC client to libera.chat IRC channel.">IRC channel</span>
</th>
<td><span style="font-family: monospace; font-size: 95%;"><a rel="nofollow" class="external text" href="ircs://irc.libera.chat/#gentoo-arm">#gentoo-arm</a></span> (<span style="font-family: monospace; font-size: 95%;"><a rel="nofollow" class="external text" href="https://web.libera.chat/#gentoo-arm">webchat</a></span>)
</td></tr>
<tr>
<th><span title="The link opens to a bugs.gentoo.org search based on the projects email address.">Bugs</span>
</th>
<td><span class="fa fa-bug fa-fw"></span> <a rel="nofollow" class="external text" href="https://bugs.gentoo.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=CONFIRMED&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=PLEASETEST&bug_status=IN_PROGRESS&email1=arm@gentoo.org&emailassigned_to1=1&order=bug_id%20DESC">Related bugs</a>
</td></tr>
<tr valign="top">
<th>Lead(s)
</th>
<td><ul><li><a href="/wiki/User:Sam" title="User:Sam">Sam James</a>
(sam)</li></ul> <br />No lead election date set
</td></tr>
<tr valign="top">
<th>Member(s)
</th>
<td><ul><li><a href="/wiki/User:Ago" title="User:Ago">Agostino Sarubbo</a>
(ago)<br /><i>Security bugs primarily</i></li><li><a href="/wiki/User:Ajak" title="User:Ajak">John Helmert III</a>
(ajak)</li><li><a href="/wiki/User:Alicef" title="User:Alicef">Arisu Tachibana</a>
(arisut)<br /><i>Kernel</i></li><li><a href="/wiki/User:Blueness" title="User:Blueness">Anthony G. Basile</a>
(blueness)</li><li><a href="/wiki/User:Dilfridge" title="User:Dilfridge">Andreas K. Hüttel</a>
(dilfridge)<br /><i>Release engineering</i></li><li><a href="/wiki/User:Dlan" title="User:Dlan">Yixun Lan</a>
(dlan)</li><li><a href="/wiki/User:GYakovlev" title="User:GYakovlev">Georgy Yakovlev</a>
(gyakovlev)<br /><i>installcd maintainer, misc helper</i></li><li><a href="/wiki/User:Maekke" title="User:Maekke">Markus Meier</a>
(maekke)</li><li><a href="/wiki/User:Nerdboy" title="User:Nerdboy">Steve Arnold</a>
(nerdboy)<br /><i>Kernel</i></li><li><a href="/wiki/User:Vapier" title="User:Vapier">Mike Frysinger</a>
(vapier)</li><li><a href="/wiki/User:Viorel" title="User:Viorel">Viorel Munteanu</a>
(ceamac)</li><li><a href="/wiki/User:Zero_Chaos" title="User:Zero Chaos">Rick Farina</a>
(zerochaos)</li></ul>
</td></tr>
<tr valign="top">
<th>Subproject(s)<br /><small style="font-weight: normal;">(and inherited member(s))</small>
</th>
<td>(none)
</td></tr>
<tr>
<th>Parent Project
</th>
<td><a href="/wiki/Project:Gentoo" title="Project:Gentoo">Gentoo</a>
</td></tr>
<tr>
<td colspan="2" style="border-top: 1px solid #ddd; font-size: smaller; text-align: center;"><a href="/wiki/Project:Gentoo" title="Project:Gentoo">Project listing</a>
</td></tr></tbody></table>
<p>The Gentoo/ARM Project works to keep Gentoo the most up to date and fastest ARM distribution available. We are responsible for the maintenance of all ARM specific metadata and the testing of all other non ARM specific meta-data on the ARM architecture to ensure portability. Portability implies reusable metadata.
</p><p>Bugs are tracked and resolved from the <a rel="nofollow" class="external text" href="http://bugs.gentoo.org">Gentoo bug tracker</a> and correspondence is maintained on the various ARM related mailinglists. (<span style="font-family: monospace; font-size: 95%;"><a rel="nofollow" class="external text" href="ircs://irc.libera.chat/#gentoo-arm">#gentoo-arm</a></span> (<span style="font-family: monospace; font-size: 95%;"><a rel="nofollow" class="external text" href="https://web.libera.chat/#gentoo-arm">webchat</a></span>) and those belonging to the sub-projects).
</p>
<div id="toc" class="toc" role="navigation" aria-labelledby="mw-toc-heading"><input type="checkbox" role="button" id="toctogglecheckbox" class="toctogglecheckbox" style="display:none" /><div class="toctitle" lang="en" dir="ltr"><h2 id="mw-toc-heading">Contents</h2><span class="toctogglespan"><label class="toctogglelabel" for="toctogglecheckbox"></label></span></div>
<ul>
<li class="toclevel-1 tocsection-1"><a href="#Key_facts"><span class="tocnumber">1</span> <span class="toctext">Key facts</span></a></li>
<li class="toclevel-1 tocsection-2"><a href="#Goals"><span class="tocnumber">2</span> <span class="toctext">Goals</span></a>
<ul>
<li class="toclevel-2 tocsection-3"><a href="#Stabilization_policy"><span class="tocnumber">2.1</span> <span class="toctext">Stabilization policy</span></a></li>
</ul>
</li>
<li class="toclevel-1 tocsection-4"><a href="#Keywording"><span class="tocnumber">3</span> <span class="toctext">Keywording</span></a></li>
<li class="toclevel-1 tocsection-5"><a href="#How_to_participate"><span class="tocnumber">4</span> <span class="toctext">How to participate</span></a></li>
</ul>
</div>
<h2><span class="mw-headline" id="Key_facts">Key facts</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:ARM&action=edit&section=1" title="Edit section: Key facts">edit</a><span class="mw-editsection-bracket">]</span></span></h2>
<ul><li>ARM is 32-bit.</li>
<li>ARM is little-endian.</li>
<li><= ARMv5te lacks proper hardware atomics, see <span class="plainlinks" style="color: MidnightBlue; font-family: monospace; font-size: 95%;" title="External link to https://bugs.gentoo.org."><a rel="nofollow" class="external text" href="https://bugs.gentoo.org/show_bug.cgi?id=721344"><span style="color: MidnightBlue;">bug #721344</span></a><span style="color: grey; margin-left: 0.1em; font-size: 70%;" class="fa fa-bug fa-fw"></span></span>.</li></ul>
<p>Gentoo at the moment does not have any 32bit ARM development hardware. Most development and testing is done in
containers on a 80 core Neoverse arm64 machine that supports 32bit mode; stages are built quasi-natively on
that machine itself.
</p>
<h2><span class="mw-headline" id="Goals">Goals</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:ARM&action=edit&section=2" title="Edit section: Goals">edit</a><span class="mw-editsection-bracket">]</span></span></h2>
<p>The goal of the Gentoo ARM development project is to guarantee that the ARM packages build using Gentoo metadata are up to date. By continuously enhancing the metadata, we provide the ARM user with the Gentoo community feeling, performance, freedom and up-to-dateness. The meta-distribution notion allows for a user to to be as bleeding edge as he/she wants:
</p><p>Gentoo is unique because of its interpretation of the Meta-Distribution notion: all architectures share the same 'generic' metadata (information about how to build packages - how to build a distribution). The ARM developers are responsible for building and testing packages using this meta-data. The meta-data gets marked 'tested' or 'stable' afterwards, depending on the building and testing experience. Our users can use (but don't have to use) this information to build a system that suits their needs.
</p>
<h3><span class="mw-headline" id="Stabilization_policy">Stabilization policy</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:ARM&action=edit&section=3" title="Edit section: Stabilization policy">edit</a><span class="mw-editsection-bracket">]</span></span></h3>
<div class="alert alert-info gw-box" style="padding-top: 8px; padding-bottom: 8px;"><strong><i class="fa fa-sticky-note-o fa-rotate-180"></i> Note</strong><br />Users do <b>not</b> have to test themselves with FEATURES=test, although it's nice if they do. Please file a bug if a package works for you in stable and your system is stable. We want to mark it as such in Gentoo!</div>
<p>The Gentoo ARM development project supports various flavors of the 32-bit ARM architecture (to be precise: armv4/armv5/armv6/armv7) but the workload to test all packages on these platforms is excessive. So, successfully testing on armv7 is adequate.
</p><p>Team members or developers must run <code>FEATURES=test</code> for all packages and ensure each package passes the test phase. This is <b>not</b> required just to simply file a bug and request keywording or stabilisation though - it is the responsibility of the arch teams to test, not the person requesting.
</p>
<ul><li>vanilla-sources and gentoo-sources should be stabilized per the Kernel Project stabilization policy <a href="/wiki/Project:Kernel#Kernel_stabilization" title="Project:Kernel">Project:Kernel#Kernel_stabilization</a></li></ul>
<h2><span class="mw-headline" id="Keywording">Keywording</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:ARM&action=edit&section=4" title="Edit section: Keywording">edit</a><span class="mw-editsection-bracket">]</span></span></h2>
<div class="alert alert-success gw-box" style="padding-top: 8px; padding-bottom: 8px;"><strong><i class="fa fa-check-circle"></i> Tip</strong><br />We want both stable <code>arm</code> <b>and</b> keywording <code>~arm</code> requests. File them!</div>
<p>See <a href="/wiki/Project:ARM64#Keywording" title="Project:ARM64">Project:ARM64#Keywording</a>.
</p>
<h2><span class="mw-headline" id="How_to_participate">How to participate</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:ARM&action=edit&section=5" title="Edit section: How to participate">edit</a><span class="mw-editsection-bracket">]</span></span></h2>
<p>Can you make computers do amazing things? Are you excited about exploring areas of computing never explored before? We are continuously looking for volunteers willing to spend some of their free time on this project. In return for your work, you get the respect of the ARM community.
</p><p>If you are interested in helping, but don't have a niche that you are interested in filling, you can always look through <a rel="nofollow" class="external text" href="http://bugs.gentoo.org">bugs.gentoo.org</a>. There are many many bugs waiting to be found and fixed and many enhancements looking to find someone to code them. Figure out a fix, implement it, test it, and then keep trying to make the patch smaller. Post it for review on <a rel="nofollow" class="external text" href="http://bugs.gentoo.org">bugs.gentoo.org</a>, and keep working on it. If it seems ignored, make a new comment in the bug and/or mention it in <span style="font-family: monospace; font-size: 95%;"><a rel="nofollow" class="external text" href="ircs://irc.libera.chat/#gentoo-arm">#gentoo-arm</a></span> (<span style="font-family: monospace; font-size: 95%;"><a rel="nofollow" class="external text" href="https://web.libera.chat/#gentoo-arm">webchat</a></span>).
</p><p>Finally, feel free to add yourself with your IRC handle to our <a href="/wiki/Embedded_systems/ARM_hardware_list" class="mw-redirect" title="Embedded systems/ARM hardware list">ARM hardware list</a> on the wiki. It's always nice to know what gadgets are out there!
</p>
' |
Unix timestamp of change (timestamp) | 1737895980 |
Wiki