Linaro Blog

Getting Involved with Linaro

Posted on November 30, 2012 by

Getting Started

Whether you are an individual or an employee of a organization it is easy to get involved with Linaro.  If you or your organization is new to open source, want to know about running Linaro builds with or without your own hardware, using the Linaro Toolchain or the Linaro Linux Kernel we’ll show you how to get started.

You can also find out about how Linaro works live and in-person at our Linaro Connect events. You may also want to take a look at our website, wiki, launchpad, subscribe to the various mailing lists or join our IRC channels.

Staying connected between Linaro events and development cycles is easy as well;  just follow us on Twitter, add us to your circles on Google+ or like us on  Facebook.

Below is a list of the various Linaro teams, what their primary goals are and how to find out more about getting involved with each of them.

Android

The primary goals of the Linaro Android Team is to develop and release tested monthly builds of Android for Galaxy Nexus, Panda, Snowball, Origen, and Versatile Express, collaborate with upstream development efforts and perform monthly toolchain benchmarking.

More information about the Linaro Android Team can be found at: https://wiki.linaro.org/Platform/Android

Developer Platform

The Developer Platform Team’s primary goal is to provide a common platform to use as the basis for Validation test heads and optimized hardware-specific builds. We work with several teams within Linaro to make this happen.

More information about the Linaro Developer Platform Team can be found at: https://wiki.linaro.org/Platform/DevPlatform

LAVA

The goal of the LAVA team is to maintain and develop automated testing tools to be used to test Linaro Platform work. We work with several teams in Linaro to help enable them perform continuos integration testing.

More information about the LAVA Team can be found at: https://wiki.linaro.org/Platform/LAVA

Infrastructure

The scope of the Infrastructure Team is to maintain and develop archive management tools as well as the automated testing, etc. tools to be used to test Linaro platform work.

More information about the Linaro Infrastructure Team can be found at: https://wiki.linaro.org/Platform/Infrastructure

Kernel

The Kernel Consolidation Working Group targets the Linux kernel. Its goals are to consolidate source repositories, unify support across SoCs, develop new kernel infrastructure and features and more. Our acid test: shipping a single source tree that integrates support for multiple modern ARM SoCs.

More information about the Linaro Kernel Team can be found at: https://wiki.linaro.org/WorkingGroups/Kernel

Toolchain

The toolchain working group deals with all aspects of system-level tools – the core development toolchain (compiler, assembler, linker, debugger), emulation, profiling and analysis (oprofile, performance events) and instrumentation (ftrace).

More information about the Linaro Toolchain Team can be found at: https://wiki.linaro.org/WorkingGroups/ToolChain

Power Management

The Power Management WG will look at the entire software stack (kernel, middleware, applications and tools) to help optimize power consumption. The WG is responsible for creating infrastructure, guidelines and tools to enable top-notch power management on multiple ARM SoCs.

More information about the Linaro Power Management Team can be found at: https://wiki.linaro.org/WorkingGroups/PowerManagement

Graphics

The Graphics Working Group is set to improve the Linux graphics stack for current and future GPUs used in modern ARM devices like smart phones, tablets and netbooks.

More information about the Linaro Graphics Team can be found at: https://wiki.linaro.org/WorkingGroups/Middleware/Graphics

Linaro Enterprise Group (LEG)

More information about the Linaro Enterprise Group (LEG)  can be found at: https://wiki.linaro.org/LEG/

*Times and dates to the meetings are subject to change so check the respective wiki pages for any changes and updates.  Also please feel free to email the teams to find out more information. All times are listed in UTC unless otherwise stated.

About Linaro

Linaro is the place where engineers from the world’s leading technology companies define the future of Linux on ARM. The company is a not-for-profit engineering organization with over 120 engineers working on consolidating and optimizing open source software for the ARM architecture, including developer tools, the Linux kernel, ARM power management, and other software infrastructure.

To find out more, please visit http://www.linaro.org.

About Linaro Connect

Over 300 participants, ranging from kernel hackers to integration engineers to ARM SoC industry executives gather during this week long to present, discuss and develop features,  infrastructure and optimizations for the Linux kernel, Android, Ubuntu and beyond.

More information on upcoming Linaro Connect events can be found on the the Linaro Connect Website.

Related posts:

About akgraner

Amber 'akgraner' Graner entered the world of Open Source in 2009, blogging about her experiences. She co-authored the 6th and 7th editions of the Official Ubuntu Book. Articles by Amber can be found in Linux Pro and Ubuntu User Magazines (Linux New Media Publications) as well as InformIT, the Linaro Blog and various other blogging sites. Amber is also a reviewer of the 1st and 2nd editions of Art of Community. Amber is an Open Source use and philosophy advocate. Amber’s interviews with many Linaro and other Open Source personalities can be found on the Linaro and Linaro On Air youtube channels. Amber is constantly looking for ways to grow interest and community participation in Linaro. Ask me about: Linaro Community, Linux, Blogging, Community Building, Google+ Hangouts on Air, Open Souce Advocacy, Women in Open Source, Ubuntu
This entry was posted in Community, Linaro. Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>