|
| 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 | + |
| 41 | +# Note: |
| 42 | +# - 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. |
| 43 | +# - 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. |
| 44 | +# - Each entry must be sorted in alphabetical order with tag as the keyword. |
| 45 | + |
| 46 | +# Below are existing maintainer entries, divided by module: |
| 47 | + |
| 48 | +tag: bsp_cvitek |
| 49 | +path: bsp/cvitek |
| 50 | +owners: Chen Wang(unicornx)<unicorn_wang@outlook.com> |
| 51 | + |
| 52 | +tag: bsp_k230 |
| 53 | +path: bsp/k230 |
| 54 | +owners: Chen Wang(unicornx)<unicorn_wang@outlook.com> |
| 55 | + |
| 56 | +tag: documentation |
| 57 | +path: documentation |
| 58 | +owners: Chen Wang(unicornx)<unicorn_wang@outlook.com> |
| 59 | + |
| 60 | +tag: libc |
| 61 | +path: components/libc |
| 62 | +owners: Meco Jianting Man(mysterywolf)<920369182@qq.com> |
| 63 | + |
| 64 | +tag: rvlibcpu |
| 65 | +path: libcpu/risc-v |
| 66 | +owners: Shun Wang(Yaochenger)<1516081466@qq.com> |
| 67 | + |
| 68 | +tag: serial_v2 |
| 69 | +path: components/drivers/serial/dev_serial_v2.c |
| 70 | +path: components/drivers/include/drivers/dev_serial_v2.h |
| 71 | +path: examples/utest/testcases/drivers/serial_v2 |
| 72 | +owners: Chen Bei Dou(Ryan-CW-Code)<1831931681@qq.com> |
| 73 | + |
| 74 | +tag: stm32f407-rt-spark |
| 75 | +path: bsp/stm32/stm32f407-rt-spark |
| 76 | +owners: Bingru Zhang(Rbb666)<751061401@qq.com>, Yuqiang Wang(kurisaW)<2053731441@qq.com> |
| 77 | + |
| 78 | +tag: workflow |
| 79 | +path: .github |
| 80 | +owners: supper thomas(supperthomas)<78900636@qq.com>, Bingru Zhang(Rbb666)<751061401@qq.com>, Yuqiang Wang(kurisaW)<2053731441@qq.com> |
| 81 | + |
| 82 | +tag: gd32470z-lckfb-lcd |
| 83 | +path: bsp/gd32/arm/gd32470z-lckfb/board/ports |
| 84 | +owners: Wu Ying Xiang(godmial)<2633967641@qq.com> |
| 85 | + |
| 86 | +tag: bsp_ultrarisc |
| 87 | +path: bsp/ultrarisc/ur_dp1000_evb |
| 88 | +owners: Zhang Jing(zhangjing0303)<zhangjing@ultrarisc.com> |
0 commit comments