feature: CODEOWNERS help contributors join openkf
cubxxw opened this issue Β· 17 comments
One potential improvement for CODEOWNERS could be to allow for more granular control over ownership of specific files within a directory. Currently, ownership can only be assigned at the directory level, which can be limiting for larger projects with many files. Allowing for file-level ownership would provide more flexibility and allow for more targeted review assistance. Additionally, it may be helpful to allow for multiple owners per file or directory, to distribute ownership responsibilities and ensure timely reviews.
We have members @cubxxw @kubbot @AllianceTing @eurecalulu @StellarisW @linesoft2 @IRONICBo @MC-kanon @hanzhixiao @liumingsongning @Cathay-Chen @charles-chenzz
Their current responsibilities are as follows:
- @cubxxw organizer
- @kubbot automates and operates bots
- @AllianceTing full-stack Engineer
- @eurecalulu full-stack Engineer
- @StellarisW backend development work
- @linesoft2 front-end development
- @IRONICBo core Lead at OpenKF
- @MC-kanon front-end contributor
- @hanzhixiao backend development
- @plutoyty backend developer
- @liumingsongning full stack engineer
- @Cathay-Chen backend development
- @charles-chenzz backend and cloudnative development
If you are looking forward to joining OpenKF, please leave a comment below
- You can edit the file below and then make a PR
https://github.com/OpenIMSDK/OpenKF/edit/main/docs/CODEOWNERS
# This is a comment.
# Each line is a file pattern followed by one or more owners.
# README files
README.md @cubxxw @kubbot @AllianceTing @IRONICBo @MC-kanon @AllianceTing @charles-chenzz @Cathay-Chen @plutoyty
# Contributing guidelines
CONTRIBUTING.md @kubbot @cubxxw @IRONICBo @AllianceTing @plutoyty
# License files
LICENSE @kubbot @cubxxw @IRONICBo
# Makefile
Makefile @kubbot @cubxxw @IRONICBo @Cathay-Chen
# Assets directory
assets/* @AllianceTing @IRONICBo @cubxxw @MC-kanon
# Deploy directory
deploy/* @IRONICBo @cubxxw @kubbot @MC-kanon @charles-chenzz
# Server directory
server/* @AllianceTing @cubxxw @IRONICBo @liumingsongning @Cathay-Chen @charles-chenzz @hanzhixiao @plutoyty
# Web directory
web/* @AllianceTing @MC-kanon @IRONICBo @liumingsongning @plutoyty
# These owners will be the default owners for everything in
# the repo. Unless a later match takes precedence,
# @cubxxw and @kubbot will be requested for
# review when someone opens a pull request.
* @cubxxw @kubbot @AllianceTing @eurecalulu @StellarisW @linesoft2 @IRONICBo @MC-kanon @hanzhixiao @liumingsongning @Cathay-Chen @charles-chenzz
# Order is important; the last matching pattern takes the most
# precedence. When someone opens a pull request that only
# modifies JS files, only @js-owner and not the global
# owner(s) will be requested for a review.
*.js @cubxxw @kubbot @IRONICBo @MC-kanon @AllianceTing @liumingsongning
# You can also use email addresses if you prefer. They'll be
# used to look up users just like we do for commit author
# emails.
*.go 3293172751nss@gmail.com @IRONICBo @AllianceTing @eurecalulu @hanzhixiao @liumingsongning @Cathay-Chen @charles-chenzz @plutoyty
*.py 3293172751nss@gmail.com @IRONICBo @AllianceTing @eurecalulu @liumingsongning @plutoyty
# Teams can be specified as code owners as well. Teams should
# be identified in the format @org/team-name. Teams must have
# explicit write access to the repository. In this example,
# the OpenIMSDK team in the github organization owns all .txt files.
*.txt @cubxxw @kubbot @AllianceTing @IRONICBo @MC-kanon @liumingsongning @charles-chenzz
# In this example, @cubxxw owns any files in the build/
# directory at the root of the repository and any of its
# subdirectories.
build/* @cubxxw @kubbot @IRONICBo @MC-kanon @AllianceTing
# The `docs/*` pattern will match files like
# `docs/getting-started.md` but not further nested files like
# `docs/build-app/troubleshooting.md`.
docs/* 3293172751nss@gmail.com @kubbot @IRONICBo
# In this example, @octocat owns any file in an apps directory
# anywhere in your repository.
api/ @cubxxw @IRONICBo @MC-kanon @AllianceTing @hanzhixiao @charles-chenzz
# In this example, @cubxxw owns any file in the `/docs`
# directory in the root of your repository and any of its
# subdirectories.
/docs/ @cubxxw @kubbot @IRONICBo @liumingsongning
# In this example, any change inside the `/scripts` directory
# will require approval from @cubxxw or @octocat.
/scripts/ @cubxxw @kubbot @MC-kanon @charles-chenzz @plutoyty
scripts/* @cubxxw @kubbot @IRONICBo @charles-chenzz
# In this example, @octocat owns any file in a `/logs` directory such as
# `/build/logs`, `/scripts/logs`, and `/deeply/nested/logs`. Any changes
# in a `/logs` directory will require approval from @octocat.
**/logs @cubxxw @kubbot @IRONICBo @charles-chenzz @plutoyty
# In this example, @octocat owns any file in the `/apps`
# directory in the root of your repository except for the `/apps/github`
# subdirectory, as its owners are left empty.
/apps/ @cubxxw @kubbot @IRONICBo
/apps/githubNote: Looking to join the ranks of developers?
Join the slack and search openkf channel to join
Hi, OpenKF is really cool! I am so excited to be a part of this community. My technology stack is Java, Go and Vue, React, etc. I am more interested in the web section of the community.
me
I'm looking forward to be a part of the community and I'm currently focusing on devops and use golang as my main language
I am happy to be a member of the openkf and I hope to work with everyone to make this project even better.
My technology stack is Go etc. I am interested in this community.
I am a full stack engineer, technical PHP, java, vue, react, flutter, I am interested in the large model of this piece, looking forward to joining
Interested in data processing and large concurrent applications, my technology stack is go php
My technology stack is GoοΌJava etc. I am interested in this community.
happy to be a member of open-im
Glad to join OpenKF. Please give me your guidance in the future.
I am thrilled to be joining this project. I am excited to work with all of you and contribute my skills to the team. Letβs make something great together! π
i want to tryπ
I am thrilled to be joining this project. I am excited to work with all of you and contribute my skills to the team. Letβs make something great together! π