You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the file CONTRIBUTING.md "What contributions can I make?" section.
"please comment on the issue to notify the team." What content should we comment on, where can we find it, or is it better to use the issue label?
"Describe the intended feature and discuss the design and implementation with the team and community. Once the team agrees on the plan, you can follow the Contributing code to implement it." If I understand the current process correctly. I think if a new feature is needed, a new issue should be opened and described in the issue like feature_request.md. But who is the team that decides whether this feature is approved? How and how often does the team decide?
I wonder if it would be better to explain all of this.
The text was updated successfully, but these errors were encountered:
Thank you for the input. For the questions you have:
If you find the issue urgent, you can comment on the issue and explain your reasoning in detail. Milvus committer will add the label if he sees fit.
The team is basically the Milvus committers who are active contributors in the Milvus community. You can check out the membership ladder here: https://github.com/milvus-io/community/blob/master/community-membership.
There is no set schedule for the review, it is done in an ad hoc basis.
In the file CONTRIBUTING.md "What contributions can I make?" section.
I wonder if it would be better to explain all of this.
The text was updated successfully, but these errors were encountered: