MAINTAINERS 6.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199
  1. # List of maintainers of the RT-Thread open-source community
  2. #
  3. # This file manages the maintainers and their associated sections in the repository.
  4. # Developers should update this file according to project needs.
  5. # The following are explanations of each field and guidelines for adding new maintainer entries.
  6. #
  7. # When adding new entries, please follow the format:
  8. #
  9. # 1. **tag** - Assign a unique tag to each entry for identifying the code module or functionality.
  10. # - The tag should be concise and descriptive, such as `workflow`, `libc`...
  11. # - **Rule for Adding**: Use a new tag when adding a new functionality or module to ensure it clearly describes the area of responsibility.
  12. #
  13. # 2. **path** - Specify the directory or file path that the maintainer is responsible for.
  14. # - The path must be relative to the repository's root directory and can refer to either a single file or a folder.
  15. # - 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.
  16. # - **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.
  17. #
  18. # 3. **owners** - List the maintainers responsible for the section, including their GitHub usernames and contact information.
  19. # - The owners should be listed as a comma-separated list if there are multiple maintainers.
  20. # - Format: `Name(GitHub username)<email address>`.
  21. # - **Rule for Adding**: Ensure that the listed GitHub usernames are correct, and the maintainers are aware of their responsibilities and duties.
  22. #
  23. # Example: How to Add a Maintainer Entry
  24. #
  25. # The following is a template for adding new entries in the MAINTAINER file:
  26. #
  27. # tag: <module-name>
  28. # path: <file-or-directory-path>
  29. # owners: <maintainer1>, <maintainer2>, ...
  30. #
  31. # When adding entries, please follow these guidelines:
  32. # - Ensure the `tag` is unique and descriptive.
  33. # - Ensure the `path` points to the correct location in the repository.
  34. # - Ensure the `owners` are accurate and that all new maintainers are aware of their responsibilities.
  35. #
  36. # Example Entry:
  37. # tag: example-module
  38. # path: example/module/path
  39. # owners: John Doe(johndoe)<johndoe@example.com>, Jane Smith(janesmith)<janesmith@example.com>
  40. # Note:
  41. # - 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.
  42. # - 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.
  43. # - Each entry must be sorted in alphabetical order with tag as the keyword.
  44. # Below are existing maintainer entries, divided by module:
  45. tag: at
  46. path: components/net/at
  47. owners: Chen Beidou(Ryan-CW-Code)<1831931681@qq.com>, lizhen9880(lizhen9880)<lizhen9880@126.com>
  48. tag: bsp_cvitek
  49. path: bsp/cvitek
  50. owners: Chen Wang(unicornx)<unicorn_wang@outlook.com>
  51. tag: bsp_gd32105c-eval
  52. path: bsp/gd32/arm/gd32105c-eval
  53. owners: Xiansong Cao(CXSforHPU)<19511928573@163.com>
  54. tag: bsp_gd32470z-lckfb
  55. path: bsp/gd32/arm/gd32470z-lckfb
  56. owners: Wu Ying Xiang(godmial)<2633967641@qq.com>
  57. tag: bsp_gd32e503v-eval
  58. path: bsp/gd32/arm/gd32e503v-eval
  59. owners: 蒙蒙plus(meng-plus)<chengmeng_2@outlook.com>
  60. tag: bsp_k230
  61. path: bsp/k230
  62. owners: Chen Wang(unicornx)<unicorn_wang@outlook.com>
  63. tag: bsp_lpc4088
  64. path: bsp/nxp/lpc/lpc408x
  65. owners: 蒙蒙plus(meng-plus)<chengmeng_2@outlook.com>
  66. tag: bsp_mcxa
  67. path: bsp/nxp/mcx/mcxa
  68. owners: 下里巴人(hywing)<hywing.sir@qq.com>
  69. tag: bsp_mcxn
  70. path: bsp/nxp/mcx/mcxn
  71. owners: 下里巴人(hywing)<hywing.sir@qq.com>
  72. tag: bsp_mm32f526x
  73. path: bsp/mm32f526x
  74. owners: Huanyi Mai(Chasel)<m19825309307@163.com>
  75. tag: bsp_nrf5x
  76. path: bsp/nrf5x
  77. owners: Xiaowei Swenson(ReviewSun)<Sxw1204814381@outlook.com>
  78. tag: bsp_rt-spark
  79. path: bsp/stm32/stm32f407-rt-spark
  80. owners: Bingru Zhang(Rbb666)<751061401@qq.com>, Yuqiang Wang(kurisaW)<2053731441@qq.com>
  81. tag: bsp_ultrarisc
  82. path: bsp/ultrarisc/ur_dp1000_evb
  83. owners: Zhang Jing(zhangjing0303)<zhangjing@ultrarisc.com>
  84. tag: bsp_ESP32_C3
  85. path: bsp/ESP32_C3/builtin_imgs
  86. path: bsp/ESP32_C3/drivers
  87. owners: Damoshed_Xu(xu18838022837)<496121493@qq.com>
  88. tag: bsp_renesas
  89. path: bsp/renesas
  90. owners: Yuqiang Wang(kurisaW)<2053731441@qq.com>
  91. tag: bsp_stm32
  92. path: bsp/stm32
  93. owners: Liya Huang(wdfk-prog)<1425075683@qq.com>
  94. tag: bsp_stm32f429-atk-apollo
  95. path: bsp/stm32/stm32f429-atk-apollo
  96. owners: lizhen9880(lizhen9880)<lizhen9880@126.com>
  97. tag: bsp_stm32h723-st-nucleo
  98. path: bsp/stm32/stm32h723-st-nucleo
  99. owners: 下里巴人(hywing)<hywing.sir@qq.com>
  100. tag: bsp_stm32g030-tiny-board
  101. path: bsp/stm32/stm32g030-tiny-board
  102. owners: 下里巴人(hywing)<hywing.sir@qq.com>
  103. tag: bsp_stm32h743-st-nucleo
  104. path: bsp/stm32/stm32h743-st-nucleo
  105. owners: PengXu(LittleGreyG)<18825981694@163.com>
  106. tag: bsp_stm32h750-artpi
  107. path: bsp/stm32/stm32h750-artpi
  108. owners: PengXu(LittleGreyG)<18825981694@163.com>
  109. tag: bsp_wch
  110. path: bsp/wch
  111. owners: Huanyi Mai(Chasel)<m19825309307@163.com>
  112. tag: components
  113. path: components
  114. owners: Huanyi Mai(Chasel)<m19825309307@163.com>
  115. tag: documentation
  116. path: documentation
  117. owners: Chen Wang(unicornx)<unicorn_wang@outlook.com>, Guorui Li(GorrayLi)<liguorui1213@163.com>, Lian Wang(lianux-mm)<lianux.mm@gmail.com>, Xiansong Cao(CXSforHPU)<19511928573@163.com>
  118. tag: driver_can
  119. path: components/drivers/can
  120. owners: Liya Huang(wdfk-prog)<1425075683@qq.com>
  121. tag: driver_i2c
  122. path: components/drivers/i2c
  123. owners: Liya Huang(wdfk-prog)<1425075683@qq.com>
  124. tag: driver_pm
  125. path: components/drivers/pm
  126. owners: Liya Huang(wdfk-prog)<1425075683@qq.com>
  127. tag: driver_spi
  128. path: components/drivers/spi
  129. owners: Liya Huang(wdfk-prog)<1425075683@qq.com>
  130. tag: driver_ymodem
  131. path: components/utilities/ymodem
  132. owners: Liya Huang(wdfk-prog)<1425075683@qq.com>
  133. tag: fal
  134. path: components/fal
  135. owners: Yucai Liu(illustriousness)<1486344514@qq.com>
  136. tag: kernel
  137. path: src
  138. owners: Damoshed_Xu(xu18838022837)<496121493@qq.com>, Guorui Li(GorrayLi)<liguorui1213@163.com>, Lian Wang(lianux-mm)<lianux.mm@gmail.com>, Liya Huang(wdfk-prog)<1425075683@qq.com>, Xiaowei Swenson(ReviewSun)<Sxw1204814381@outlook.com>
  139. tag: libc
  140. path: components/libc
  141. owners: Meco Jianting Man(mysterywolf)<920369182@qq.com>, Guorui Li(GorrayLi)<liguorui1213@163.com>
  142. tag: lwp
  143. path: components/lwp
  144. owners: Damoshed_Xu(xu18838022837)<496121493@qq.com>
  145. tag: maintainers
  146. path: MAINTAINERS
  147. owners: Bingru Zhang(Rbb666)<751061401@qq.com>, Yuqiang Wang(kurisaW)<2053731441@qq.com>
  148. tag: rvlibcpu
  149. path: libcpu/risc-v
  150. owners: Shun Wang(Yaochenger)<1516081466@qq.com>
  151. tag: serial_v2
  152. path: components/drivers/serial/dev_serial_v2.c
  153. path: components/drivers/include/drivers/dev_serial_v2.h
  154. path: examples/utest/testcases/drivers/serial_v2
  155. owners: Chen Beidou(Ryan-CW-Code)<1831931681@qq.com>
  156. tag: workflow
  157. path: .github
  158. owners: supper thomas(supperthomas)<78900636@qq.com>, Bingru Zhang(Rbb666)<751061401@qq.com>, Yuqiang Wang(kurisaW)<2053731441@qq.com>