1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
|
# List of maintainers of the RT-Thread open-source community
#
# This file manages the maintainers and their associated sections in the repository.
# Developers should update this file according to project needs.
# The following are explanations of each field and guidelines for adding new
# maintainer entries.
#
# When adding new entries, please follow the format:
#
# 1. **tag** - Assign a unique tag to each entry for identifying the code module
# or functionality.
# - The tag should be concise and descriptive, such as `workflow`, `libc`...
# - **Rule for Adding**: Use a new tag when adding a new functionality or
# module to ensure it clearly describes the area of responsibility.
#
# 2. **path** - Specify the directory or file path that the maintainer is responsible for.
# - The path must be relative to the repository's root directory and can
# refer to either a single file or a folder.
# - If the maintainer is responsible for all files in a directory, use the
# directory path; if it's for a specific file, provide the full file path.
# - **Rule for Adding**: Ensure that the path correctly points to the relevant
# code location. Please note that a tag should correspond to only one path.
# Currently, multiple paths are not supported.
#
# 3. **owners** - List the maintainers responsible for the section, including
# their GitHub usernames and contact information.
# - The owners should be listed as a comma-separated list if there are multiple
# maintainers.
# - Format: `Name(GitHub username)<email address>`.
# - **Rule for Adding**: Ensure that the listed GitHub usernames are correct,
# and the maintainers are aware of their responsibilities and duties.
#
# Example: How to Add a Maintainer Entry
#
# The following is a template for adding new entries in the MAINTAINER file:
#
# tag: <module-name>
# path: <file-or-directory-path>
# owners: <maintainer1>, <maintainer2>, ...
#
# When adding entries, please follow these guidelines:
# - Ensure the `tag` is unique and descriptive.
# - Ensure the `path` points to the correct location in the repository.
# - Ensure the `owners` are accurate and that all new maintainers are aware of
# their responsibilities.
#
# Example Entry:
# tag: example-module
# path: example/module/path
# owners: John Doe(johndoe)<[email protected]>, Jane Smith(janesmith)<[email protected]>
# Note:
# - Each entry includes a `tag` that identifies the module or functionality, a
# `path` that points to the relevant code location, and `owners` who are the
# maintainers for that part of the codebase.
#
# - If there are multiple entries, each entry should be separated by a blank line.
# Within a single entry, there is no need to insert blank lines between the
# tag, path, and owners.
#
# - Each entry must be sorted in alphabetical order with tag as the keyword.
# It is recommended that the tag naming method follow the directory path in
# the code tree. For example, if the entry path is 'bsp/cvitek', then the tag
# name is 'bsp_cvitek'. It is recommended to use all lowercase letters and not
# mix uppercase and lowercase letters.
# Below are existing maintainer entries, divided by module:
tag: bsp_cvitek
path: bsp/cvitek
owners: Chen Wang(unicornx)<[email protected]>
tag: bsp_esp32_c3
path: bsp/ESP32_C3/builtin_imgs
path: bsp/ESP32_C3/drivers
owners: Damoshed_Xu(xu18838022837)<[email protected]>
tag: bsp_gd32105c-eval
path: bsp/gd32/arm/gd32105c-eval
owners: Xiansong Cao(CXSforHPU)<[email protected]>
tag: bsp_gd32470z-lckfb
path: bsp/gd32/arm/gd32470z-lckfb
owners: Wu Ying Xiang(godmial)<[email protected]>
tag: bsp_gd32e503v-eval
path: bsp/gd32/arm/gd32e503v-eval
owners: 蒙蒙plus(meng-plus)<[email protected]>
tag: bsp_hc32
path: bsp/hc32
owners: Levi Zhang(levizh)<[email protected]>
tag: bsp_k230
path: bsp/k230
owners: Chen Wang(unicornx)<[email protected]>
tag: bsp_lpc4088
path: bsp/nxp/lpc/lpc408x
owners: 蒙蒙plus(meng-plus)<[email protected]>
tag: bsp_mcxa
path: bsp/nxp/mcx/mcxa
owners: 下里巴人(hywing)<[email protected]>
tag: bsp_mcxn
path: bsp/nxp/mcx/mcxn
owners: 下里巴人(hywing)<[email protected]>
tag: bsp_mm32f526x
path: bsp/mm32f526x
owners: Huanyi Mai(Maihuanyi)<[email protected]>
tag: bsp_nrf5x
path: bsp/nrf5x
owners: Xiaowei Swenson(ReviewSun)<[email protected]>
tag: bsp_rt-spark
path: bsp/stm32/stm32f407-rt-spark
owners: Bingru Zhang(Rbb666)<[email protected]>, Yuqiang Wang(kurisaW)<[email protected]>
tag: bsp_ultrarisc
path: bsp/ultrarisc/ur_dp1000_evb
owners: Zhang Jing(zhangjing0303)<[email protected]>
tag: bsp_renesas
path: bsp/renesas
owners: Yuqiang Wang(kurisaW)<[email protected]>
tag: bsp_stm32
path: bsp/stm32
owners: Han Lv(hamburger-os)<[email protected]>, Liya Huang(wdfk-prog)<[email protected]>, Liang He(Liang1795)<[email protected]>
tag: bsp_stm32f103-blue-pill
path: bsp/stm32/stm32f103-blue-pill
owners: Liang He(Liang1795)<[email protected]>
tag: bsp_stm32f412-st-nucleo
path: bsp/stm32/stm32f412-st-nucleo
owners: Liang He(Liang1795)<[email protected]>
tag: bsp_stm32f429-armfly-v6
path: bsp/stm32/stm32f429-armfly-v6
owners: wenguang Dong(Knowbie-dwg)[email protected]
tag: bsp_stm32f429-atk-apollo
path: bsp/stm32/stm32f429-atk-apollo
owners: lizhen9880(lizhen9880)<[email protected]>
tag: bsp_stm32h723-st-nucleo
path: bsp/stm32/stm32h723-st-nucleo
owners: 下里巴人(hywing)<[email protected]>
tag: bsp_stm32g030-tiny-board
path: bsp/stm32/stm32g030-tiny-board
owners: 下里巴人(hywing)<[email protected]>
tag: bsp_stm32h743-st-nucleo
path: bsp/stm32/stm32h743-st-nucleo
owners: PengXu(LittleGreyG)<[email protected]>
tag: bsp_stm32h750-artpi
path: bsp/stm32/stm32h750-artpi
owners: PengXu(LittleGreyG)<[email protected]>
tag: bsp_wch
path: bsp/wch
owners: Huanyi Mai(Maihuanyi)<[email protected]>
tag: components
path: components
owners: Huanyi Mai(Maihuanyi)<[email protected]>
tag: components_driver_can
path: components/drivers/can
owners: Liya Huang(wdfk-prog)<[email protected]>
tag: components_driver_i2c
path: components/drivers/i2c
owners: Liya Huang(wdfk-prog)<[email protected]>
tag: components_driver_pm
path: components/drivers/pm
owners: Liya Huang(wdfk-prog)<[email protected]>
tag: components_driver_serial_v2
path: components/drivers/serial/dev_serial_v2.c
path: components/drivers/include/drivers/dev_serial_v2.h
path: components/drivers/serial/utest/v2
owners: Chen Beidou(Ryan-CW-Code)<[email protected]>
tag: components_driver_spi
path: components/drivers/spi
owners: Liya Huang(wdfk-prog)<[email protected]>, Liang He(Liang1795)<[email protected]>
tag: components_fal
path: components/fal
owners: Yucai Liu(illustriousness)<[email protected]>
tag: components_libc
path: components/libc
owners: Meco Jianting Man(mysterywolf)<[email protected]>, Guorui Li(GorrayLi)<[email protected]>
tag: components_lwp
path: components/lwp
owners: Damoshed_Xu(xu18838022837)<[email protected]>
tag: components_net_at
path: components/net/at
owners: Chen Beidou(Ryan-CW-Code)<[email protected]>, lizhen9880(lizhen9880)<[email protected]>
tag: components_utilities_ymodem
path: components/utilities/ymodem
owners: Liya Huang(wdfk-prog)<[email protected]>
tag: documentation
path: documentation
owners: Chen Wang(unicornx)<[email protected]>, Guorui Li(GorrayLi)<[email protected]>, Lian Wang(lianux-mm)<[email protected]>, Xiansong Cao(CXSforHPU)<[email protected]>
tag: kernel
path: src
owners: Damoshed_Xu(xu18838022837)<[email protected]>, Guorui Li(GorrayLi)<[email protected]>, Han Lv(hamburger-os)<[email protected]>, Lian Wang(lianux-mm)<[email protected]>, Liya Huang(wdfk-prog)<[email protected]>, Xiaowei Swenson(ReviewSun)<[email protected]>
tag: libcpu_riscv
path: libcpu/risc-v
owners: Shun Wang(Yaochenger)<[email protected]>
tag: maintainers
path: MAINTAINERS
owners: Bingru Zhang(Rbb666)<[email protected]>, Yuqiang Wang(kurisaW)<[email protected]>
tag: workflow
path: .github
owners: supper thomas(supperthomas)<[email protected]>, Bingru Zhang(Rbb666)<[email protected]>, Yuqiang Wang(kurisaW)<[email protected]>
|
