Changeset c4da705 in rtems-docs


Ignore:
Timestamp:
Jan 11, 2019, 11:45:30 AM (5 months ago)
Author:
Sebastian Huber <sebastian.huber@…>
Branches:
master
Children:
c098290
Parents:
b5014fe
git-author:
Sebastian Huber <sebastian.huber@…> (01/11/19 11:45:30)
git-committer:
Sebastian Huber <sebastian.huber@…> (01/14/19 06:15:27)
Message:

user: Move "Support" to "Introduction"

New users may find it useful to get this information in the
introduction.

Location:
user
Files:
1 deleted
2 edited

Legend:

Unmodified
Added
Removed
  • user/index.rst

    rb5014fe rc4da705  
    4343    rsb/index
    4444
    45     support/index
    46 
    4745    glossary/index
    4846
  • user/overview/index.rst

    rb5014fe rc4da705  
    22
    33Introduction
    4 ============
     4************
    55
    66Overview
    7 --------
     7========
    88
    99You are someone looking for a real-time operating system.  This document
     
    1818
    1919Features
    20 --------
     20========
    2121
    2222The Real-Time Executive for Multiprocessor Systems (:ref:term:`RTEMS`) is a
     
    183183    - Support to stay in synchronization with FreeBSD
    184184
     185Support
     186=======
     187.. index:: Support
     188
     189RTEMS offers a variety of support options.
     190
     191This section covers all options available to both users and developers.  If you
     192believe this is a bug report please submit it to the bug tracker otherwise the
     193developers mailing list is the default location to send the report.
     194
     195RTEMS Project Support
     196---------------------
     197.. index:: RTEMS Project Support
     198
     199The following support channels are provided by the RTEMS Project and provide
     200direct access to the RTEMS community.
     201
     202Bug Tracker
     203~~~~~~~~~~~
     204.. index:: Bugs
     205.. index:: Reporting bugs
     206
     207The bug tracker can be found at the :r:url:`bugs`.
     208
     209See the `Submission Guidelines <http://devel.rtems.org/wiki/NewTicket/>`_ for
     210details on submitting a ticket.
     211
     212Be sure to do a cursory search for any tickets that may be relevant to your
     213problem.
     214
     215If you are unsure about your issue status submit a ticket and we will help you
     216sort it out.
     217
     218Documentation
     219~~~~~~~~~~~~~
     220
     221The latest user documentation can always be found at the :r:url:`docs`.
     222
     223.. _support-mailing-lists:
     224
     225Mailing Lists
     226~~~~~~~~~~~~~
     227.. index:: Community
     228.. index:: Mailing lists
     229
     230We have several mailing lists for RTEMS users and developers.
     231
     232        * :r:list:`announce`
     233                * Announcements for major and other project-related issues.
     234
     235        * :r:list:`bugs`
     236                * Bugs email from :r:url:`bugs`.
     237
     238        * :r:list:`devel`
     239                * Developers list, this is for developers of RTEMS itself.
     240
     241
     242        * :r:list:`build`
     243                * Results from the testing and building of RTEMS.
     244
     245        * :r:list:`users`
     246                * Users of RTEMS.
     247
     248        * :r:list:`vc`
     249                * Commits to the RTEMS master repository.
     250
     251
     252IRC
     253~~~
     254.. index:: Community
     255.. index:: IRC
     256
     257RTEMS IRC is available on the Freenode network. See the `Freenode
     258<http://www.freenode.net/>`_ web site for details on connecting, selecting a
     259nickname, and general usage tips. If you are new to IRC it is recommended
     260reading.
     261
     262These are the current IRC channels.
     263
     264  **#rtems**
     265
     266This is a general channel for all things RTEMS. You can just hang out with
     267other RTEMS users and developers to talk about RTEMS, using RTEMS or to make
     268contact with other RTEMS users.
     269
     270The ``#rtems`` channel is logged. You can find the logs at
     271http://www.rtems.org/irclogs/. You can search the logs using Google by adding:
     272
     273  **site:rtems.org inurl:irclogs**
     274
     275to your search terms.
     276
     277Developers
     278~~~~~~~~~~
     279.. index:: Community
     280.. index:: Developers
     281
     282Developers can find help and support on the mailing lists, see
     283:ref:`support-mailing-lists`.
     284
     285Technical documents including design, :r:url:`gsoc`, :r:url:`socis` can be
     286found on the :r:url:`devel`.
     287
     288Commercial Support Services
     289---------------------------
     290
     291The wider RTEMS community has developers and organizations who can provide
     292commercial support services. These services range from training, implementing
     293new features in RTEMS, deployment of RTEMS< helping establish a new project
     294environment for a team, to application and system design.
     295
     296The RTEMS Project does not endorse or promote any provider of these services
     297and we recommend you use a search engine to locate a suitable provider. If you
     298are unsure please contact a provider and see what is available.
     299
     300If you develop a new feature or you have someone do this for you we recommend
     301you have the work submitted to the project and merged. Once accepted into the
     302project the work will be maintained as part of the development process within
     303the project and this is a benefit for.
     304
    185305Real-time Application Systems
    186 -----------------------------
     306=============================
    187307
    188308Real-time application systems are a special class of computer applications.
     
    219339
    220340Real-time Executive
    221 -------------------
     341===================
    222342
    223343Fortunately, real-time operating systems, or real-time executives, serve as a
Note: See TracChangeset for help on using the changeset viewer.