Changeset f170947 in rtems-docs


Ignore:
Timestamp:
Aug 5, 2019, 1:06:01 PM (3 weeks ago)
Author:
Sebastian Huber <sebastian.huber@…>
Branches:
master
Children:
7c89bd6
Parents:
8037cbb
git-author:
Sebastian Huber <sebastian.huber@…> (08/05/19 13:06:01)
git-committer:
Sebastian Huber <sebastian.huber@…> (08/06/19 05:04:27)
Message:

user: Move support sections to top level

This is a preparation step to move the bug reporting procedure from the
wiki to the user manual and to add a contributing section.

Location:
user
Files:
5 added
2 edited

Legend:

Unmodified
Added
Removed
  • user/index.rst

    r8037cbb rf170947  
    3030    overview/index
    3131    start/index
     32    support/index
    3233    hosts/index
    3334    installation/index
  • user/overview/index.rst

    r8037cbb rf170947  
    270270fill this role for the community. The :ref:`RTEMS Source Builder <RSB>`
    271271provides some aid to :ref:`build and deploy tool binaries <RSBDeployment>`.
    272 
    273 Support
    274 =======
    275 .. index:: Support
    276 
    277 RTEMS offers a variety of support options.
    278 
    279 This section covers all options available to both users and developers.  If you
    280 believe this is a bug report please submit it to the bug tracker otherwise the
    281 developers mailing list is the default location to send the report.
    282 
    283 RTEMS Project Support
    284 ---------------------
    285 .. index:: RTEMS Project Support
    286 
    287 The following support channels are provided by the RTEMS Project and provide
    288 direct access to the RTEMS community.
    289 
    290 Bug Tracker
    291 ~~~~~~~~~~~
    292 .. index:: Bugs
    293 .. index:: Reporting bugs
    294 
    295 The bug tracker can be found at the :r:url:`bugs`.
    296 
    297 See the `Submission Guidelines <http://devel.rtems.org/wiki/NewTicket/>`_ for
    298 details on submitting a ticket.
    299 
    300 Be sure to do a cursory search for any tickets that may be relevant to your
    301 problem.
    302 
    303 If you are unsure about your issue status submit a ticket and we will help you
    304 sort it out.
    305 
    306 Documentation
    307 ~~~~~~~~~~~~~
    308 
    309 The latest user documentation can always be found at the :r:url:`docs`.
    310 
    311 .. _support-mailing-lists:
    312 
    313 Mailing Lists
    314 ~~~~~~~~~~~~~
    315 .. index:: Community
    316 .. index:: Mailing lists
    317 
    318 We have several mailing lists for RTEMS users and developers.
    319 
    320         * :r:list:`announce`
    321                 * Announcements for major and other project-related issues.
    322 
    323         * :r:list:`bugs`
    324                 * Bugs email from :r:url:`bugs`.
    325 
    326         * :r:list:`devel`
    327                 * Developers list, this is for developers of RTEMS itself.
    328 
    329 
    330         * :r:list:`build`
    331                 * Results from the testing and building of RTEMS.
    332 
    333         * :r:list:`users`
    334                 * Users of RTEMS.
    335 
    336         * :r:list:`vc`
    337                 * Commits to the RTEMS master repository.
    338 
    339 
    340 IRC
    341 ~~~
    342 .. index:: Community
    343 .. index:: IRC
    344 
    345 RTEMS IRC is available on the Freenode network. See the `Freenode
    346 <http://www.freenode.net/>`_ web site for details on connecting, selecting a
    347 nickname, and general usage tips. If you are new to IRC it is recommended
    348 reading.
    349 
    350 These are the current IRC channels.
    351 
    352   **#rtems**
    353 
    354 This is a general channel for all things RTEMS. You can just hang out with
    355 other RTEMS users and developers to talk about RTEMS, using RTEMS or to make
    356 contact with other RTEMS users.
    357 
    358 The ``#rtems`` channel is logged. You can find the logs at
    359 http://www.rtems.org/irclogs/. You can search the logs using Google by adding:
    360 
    361   **site:rtems.org inurl:irclogs**
    362 
    363 to your search terms.
    364 
    365 Developers
    366 ~~~~~~~~~~
    367 .. index:: Community
    368 .. index:: Developers
    369 
    370 Developers can find help and support on the mailing lists, see
    371 :ref:`support-mailing-lists`.
    372 
    373 Technical documents including design, :r:url:`gsoc`, :r:url:`socis` can be
    374 found on the :r:url:`devel`.
    375 
    376 Commercial Support Services
    377 ---------------------------
    378 
    379 The wider RTEMS community has developers and organizations who can provide
    380 commercial support services. These services range from training, implementing
    381 new features in RTEMS, deployment of RTEMS< helping establish a new project
    382 environment for a team, to application and system design.
    383 
    384 The RTEMS Project does not endorse or promote any provider of these services
    385 and we recommend you use a search engine to locate a suitable provider. If you
    386 are unsure please contact a provider and see what is available.
    387 
    388 If you develop a new feature or you have someone do this for you we recommend
    389 you have the work submitted to the project and merged. Once accepted into the
    390 project the work will be maintained as part of the development process within
    391 the project and this is a benefit for.
    392272
    393273Real-time Application Systems
Note: See TracChangeset for help on using the changeset viewer.