# 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)`. # - **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: # path: # owners: , , ... # # 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), Jane Smith(janesmith) # 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. # Below are existing maintainer entries, divided by module: tag: bsp_cvitek path: bsp/cvitek owners: Chen Wang(unicornx) tag: bsp_k230 path: bsp/k230 owners: Chen Wang(unicornx) tag: documentation path: documentation owners: Chen Wang(unicornx) tag: libc path: components/libc owners: Meco Jianting Man(mysterywolf)<920369182@qq.com> tag: rvlibcpu path: libcpu/risc-v owners: Shun Wang(Yaochenger)<1516081466@qq.com> tag: serial_v2 path: components/drivers/serial/dev_serial_v2.c path: components/drivers/include/drivers/dev_serial_v2.h path: examples/utest/testcases/drivers/serial_v2 owners: Chen Bei Dou(Ryan-CW-Code)<1831931681@qq.com> tag: stm32f407-rt-spark path: bsp/stm32/stm32f407-rt-spark owners: Bingru Zhang(Rbb666)<751061401@qq.com>, Yuqiang Wang(kurisaW)<2053731441@qq.com> tag: workflow path: .github owners: supper thomas(supperthomas)<78900636@qq.com>, Bingru Zhang(Rbb666)<751061401@qq.com>, Yuqiang Wang(kurisaW)<2053731441@qq.com> tag: gd32470z-lckfb-lcd path: bsp/gd32/arm/gd32470z-lckfb/board/ports owners: Wu Ying Xiang(godmial)<2633967641@qq.com> tag: bsp_ultrarisc path: bsp/ultrarisc/ur_dp1000_evb owners: Zhang Jing(zhangjing0303)