1 | .. comment SPDX-License-Identifier: CC-BY-SA-4.0 |
---|
2 | |
---|
3 | Support |
---|
4 | ******* |
---|
5 | .. index:: Support |
---|
6 | |
---|
7 | RTEMS offers a variety of support options. |
---|
8 | |
---|
9 | This chapter covers all options available to both users and developers. If you |
---|
10 | believe this is a bug report please submit it to the bug tracker otherwise the |
---|
11 | developers mailing list is the default location to send the report. |
---|
12 | |
---|
13 | RTEMS Project Support |
---|
14 | ===================== |
---|
15 | .. index:: RTEMS Project Support |
---|
16 | |
---|
17 | The following support channels are provided by the RTEMS Project and provide |
---|
18 | direct access to the RTEMS community. |
---|
19 | |
---|
20 | Bug Tracker |
---|
21 | ----------- |
---|
22 | .. index:: Bugs |
---|
23 | .. index:: Reporting bugs |
---|
24 | |
---|
25 | The bug tracker can be found at the :r:url:`bugs`. |
---|
26 | |
---|
27 | See the `Submission Guidelines <http://devel.rtems.org/wiki/NewTicket/>`_ for |
---|
28 | details on submitting a ticket. |
---|
29 | |
---|
30 | Be sure to do a cursory search for any tickets that may be relevant to your |
---|
31 | problem. |
---|
32 | |
---|
33 | If you are unsure about your issue status submit a ticket and we will help you |
---|
34 | sort it out. |
---|
35 | |
---|
36 | Documentation |
---|
37 | ------------- |
---|
38 | |
---|
39 | The latest user documentation can always be found at the :r:url:`docs`. |
---|
40 | |
---|
41 | .. _support-mailing-lists: |
---|
42 | |
---|
43 | Mailing Lists |
---|
44 | ------------- |
---|
45 | .. index:: Community |
---|
46 | .. index:: Mailing lists |
---|
47 | |
---|
48 | We have several mailing lists for RTEMS users and developers. |
---|
49 | |
---|
50 | * :r:list:`announce` |
---|
51 | * Announcements for major and other project-related issues. |
---|
52 | |
---|
53 | * :r:list:`bugs` |
---|
54 | * Bugs email from :r:url:`bugs`. |
---|
55 | |
---|
56 | * :r:list:`devel` |
---|
57 | * Developers list, this is for developers of RTEMS itself. |
---|
58 | |
---|
59 | |
---|
60 | * :r:list:`build` |
---|
61 | * Results from the testing and building of RTEMS. |
---|
62 | |
---|
63 | * :r:list:`users` |
---|
64 | * Users of RTEMS. |
---|
65 | |
---|
66 | * :r:list:`vc` |
---|
67 | * Commits to the RTEMS master repository. |
---|
68 | |
---|
69 | |
---|
70 | IRC |
---|
71 | --- |
---|
72 | .. index:: Community |
---|
73 | .. index:: IRC |
---|
74 | |
---|
75 | RTEMS IRC is available on the Freenode network. See the `Freenode |
---|
76 | <http://www.freenode.net/>`_ web site for details on connecting, selecting a |
---|
77 | nickname, and general usage tips. If you are new to IRC it is recommended |
---|
78 | reading. |
---|
79 | |
---|
80 | These are the current IRC channels. |
---|
81 | |
---|
82 | **#rtems** |
---|
83 | |
---|
84 | This is a general channel for all things RTEMS. You can just hang out with |
---|
85 | other RTEMS users and developers to talk about RTEMS, using RTEMS or to make |
---|
86 | contact with other RTEMS users. |
---|
87 | |
---|
88 | The ``#rtems`` channel is logged. You can find the logs at |
---|
89 | http://www.rtems.org/irclogs/. You can search the logs using Google by adding: |
---|
90 | |
---|
91 | **site:rtems.org inurl:irclogs** |
---|
92 | |
---|
93 | to your search terms. |
---|
94 | |
---|
95 | Developers |
---|
96 | ---------- |
---|
97 | .. index:: Community |
---|
98 | .. index:: Developers |
---|
99 | |
---|
100 | Developers can find help and support on the mailing lists, see |
---|
101 | :ref:`support-mailing-lists`. |
---|
102 | |
---|
103 | Technical documents including design, :r:url:`gsoc`, :r:url:`socis` can be |
---|
104 | found on the :r:url:`devel`. |
---|
105 | |
---|
106 | Commercial Support Services |
---|
107 | =========================== |
---|
108 | |
---|
109 | The wider RTEMS community has developers and orgainizations who can provide |
---|
110 | commercial support services. These services range from training, implementing |
---|
111 | new features in RTEMS, deployment of RTEMS< helping establish a new project |
---|
112 | environment for a team, to application and system design. |
---|
113 | |
---|
114 | The RTEMS Project does not endorse or promote any provider of these services |
---|
115 | and we recommend you use a search engine to locate a suitable provider. If you |
---|
116 | are unsrue please contact a provider and see what is available. |
---|
117 | |
---|
118 | If you develop a new feature or you have someone do this for you we recommend |
---|
119 | you have the work submitted to the project and merged. Once accepted into the |
---|
120 | project the work will be maintained as part of the development process within |
---|
121 | the project and this is a benefit for. |
---|