Skip to content
Browse files

README.rst: shorten it

This is a bit wordy. Let's let the bold text and links stand on their
own; anybody looking at a README on GitHub or in technical
documentation probably knows what these things mean.

Signed-off-by: Marti Bolivar <>
  • Loading branch information...
mbolivar authored and nashif committed Apr 17, 2019
1 parent 95a5f90 commit 8b147cd1b9be8fc2f0d11f6baca5469db4b7a0b9
Showing with 31 additions and 80 deletions.
  1. +31 −80 README.rst
@@ -32,102 +32,53 @@ Intel x86, ARC, Nios II, Tensilica Xtensa, and RISC-V, and a large number of
Getting Started

To start developing Zephyr applications refer to the `Getting Started Guide`_
in the `Zephyr Documentation`_ pages.
A brief introduction to Zephyr can be found in the `Zephyr Introduction`_
Welcome to Zephyr! See the `Introduction to Zephyr`_ for a high-level overview,
and the documentation's `Getting Started Guide`_ to start developing.

Community Support

The Zephyr Project Developer Community includes developers from member
organizations and the general community all joining in the development of
software within the Zephyr Project. Members contribute and discuss ideas,
submit bugs and bug fixes, and provide training. They also help those in need
through the community's forums such as mailing lists and IRC channels. Anyone
can join the developer community and the community is always willing to help
its members and the User Community to get the most out of the Zephyr Project.
.. TODO: add link to Asking for Help doc here when the latest page has it
Welcome to the Zephyr community!
Community support is provided via mailing lists and Slack; see the Resources
below for details.


Here's a quick summary of resources to find your way around the Zephyr Project
support systems:

* **Zephyr Project Website**: The website is the
central source of information about the Zephyr Project. On this site, you'll
find background and current information about the project as well as all the
relevant links to project material.

* **Releases**: Source code for Zephyr kernel releases are available at On this page,
you'll find release information, and links to download or clone source
code from our GitHub repository. You'll also find links for the Zephyr
SDK, a moderated collection of tools and libraries used to develop your

* **Source Code in GitHub**: Zephyr Project source code is maintained on a
public GitHub repository at
You'll find information about getting access to the repository and how to
contribute to the project in this `Contribution Guide`_ document.

* **Samples Code**: In addition to the kernel source code, there are also
many documented `Sample and Demo Code Examples`_ that can help show you
how to use Zephyr services and subsystems.

* **Documentation**: Extensive Project technical documentation is developed
along with the Zephyr kernel itself, and can be found at Additional documentation is maintained in
the `Zephyr GitHub wiki`_.

* **Cross-reference**: Source code cross-reference for the Zephyr
kernel and samples code is available at

* **Issue Reporting and Tracking**: Requirements and Issue tracking is done in
the Github issues system:
You can browse through the reported issues and submit issues of your own.

* **Security-related Issue Reporting and Tracking**: For security-related
inquiries or reporting suspected security-related bugs in the Zephyr OS,
please send email to We will assess and
fix flaws according to our security policy outlined in the Zephyr Project
`Security Overview`_.

Security related issue tracking is done in JIRA. The location of this JIRA

* **Mailing List**: The `Zephyr Development mailing list`_ is perhaps the most convenient
way to track developer discussions and to ask your own support questions to
the Zephyr project community. There are also specific `Zephyr mailing list
subgroups`_ for announcements, builds, marketing, and Technical
Steering Committee notes, for example.
You can read through the message archives to follow
past posts and discussions, a good thing to do to discover more about the
Zephyr project.

* **Chatting**: You can chat online with the Zephyr project developer
community and other users in two ways:

* On `Slack`_: Zephyr has dedicated channels on Slack. To register, use the
following `Slack Invite`_.

* IRC channel #zephyrproject on the IRC server. You can use the web client or use a client-side application such
as pidgin (Note that all discussions have moved to Slack, although we still
have many developers still available on the IRC channel).
Here's a quick summary of resources to help you find your way around:

* **Documentation**: (`Getting Started Guide`_)
* **Source Code**: is the main
repository; contains a
searchable index
* **Releases**:
* **Samples and example code**: see `Sample and Demo Code Examples`_
* **Mailing Lists**: and are the main user and developer mailing lists,
respectively. You can join the developer's list and search its archives at
`Zephyr Development mailing list`_. The other `Zephyr mailing list
subgroups`_ have their own archives and sign-up pages.
* **Chat**: Zephyr's Slack workspace is Use
this `Slack Invite`_ to register. There is also an IRC channel,
``#zephyrproject``, on `freenode`_.
* **Contributing**: see the `Contribution Guide`_
* **Wiki**: `Zephyr GitHub wiki`_
* **Issues**:
* **Security Issues**: Email to report
security issues; also see our `Security`_ documentation. Security issues are
tracked separately at
* **Zephyr Project Website**:

.. _Slack Invite:
.. _Slack:
.. _supported boards:
.. _Zephyr Documentation:
.. _Zephyr Introduction:
.. _Introduction to Zephyr:
.. _Getting Started Guide:
.. _Contribution Guide:
.. _Zephyr GitHub wiki:
.. _Zephyr Development mailing list:
.. _Zephyr mailing list subgroups:
.. _Sample and Demo Code Examples:
.. _Security Overview:
.. _Security:
.. _freenode:

0 comments on commit 8b147cd

Please sign in to comment.
You can’t perform that action at this time.