Hey @Ivye, Welcome to openEuler Community.
All of the projects in openEuler Community are maintained by @openeuler-ci-bot.
That means the developpers can comment below every pull request or issue to trigger Bot Commands.
Please follow instructions at https://gitee.com/openeuler/community/blob/master/en/command.md to find the details.

Hi @Ivye , the doc link seems need additional access request. Is this as expected?

The same question as imjoey.

I rechecked the permission settings. Please try again，Thank you ：） @imjoey @DozeDoze

I rechecked the permission settings. Please try again，Thank you ：） @imjoey @DozeDoze

@Ivye it's OK for me. Thanks for your efforts.

I rechecked the permission settings. Please try again，Thank you ：） @imjoey @DozeDoze

@Ivye Thanks~

@Ivye The same question as imjoey.

I have left my comments in the doc, and I am fine with it now. Thanks

@imjoey @DozeDoze @zhongjun2 @Fred_Li
Thanks for your review. Version 1.0 of user role definition has been output, including user role definition, data access definition, key indicators and statistical analysis dimensions. Welcome to confirm if v1.0 content is OK.

Hi @Ivye , thanks for your efforts. Only one question, how we classify the action of posting an issue, which is not mentioned in the accessories? Shall we also consider it as a contribution? Thanks.

Hi @Ivye , thanks for your efforts. Only one question, how we classify the action of posting an issue, which is not mentioned in the accessories? Shall we also consider it as a contribution? Thanks.

@imjoey
In https://docs.qq.com/doc/DRmlaYnZSbEViRm5G, I wrote "- 在gitee.com/openeuler、gitee.com/src-openeuler、github.com/openeuler-mirror上有回复其他人的issue或者PR".

You are right, reviewing should be considered as a contribution.
I don't think only posting an issue should be considered ad a contribution. What is your opinion?

@imjoey
In https://docs.qq.com/doc/DRmlaYnZSbEViRm5G, I wrote "- 在gitee.com/openeuler、gitee.com/src-openeuler、github.com/openeuler-mirror上有回复其他人的issue或者PR".

You are right, reviewing should be considered as a contribution.
I don't think only posting an issue should be considered ad a contribution. What is your opinion?

@Fred_Li thanks for your response. From my perspective, a bug report is very helpful for maintainers and contributors, which could be also considered as a contribution. Of course, a simple question is not.

@Ivye @zhongjun2 @DozeDoze Can you join us for sharing your insights? Thanks.

Hi @Ivye , thanks for your efforts. Only one question, how we classify the action of posting an issue, which is not mentioned in the accessories? Shall we also consider it as a contribution? Thanks.

@imjoey

At present,posting a issue is regarded as a behavior characteristics of use.I think it would be more appropriate that the effective reply to the issue is a contribution.

@Fred_Li thanks for your response. From my perspective, a bug report is very helpful for maintainers and contributors, which could be also considered as a contribution. Of course, a simple question is not.
@Ivye @zhongjun2 @DozeDoze Can you join us for sharing your insights? Thanks.

@imjoey

I think you are right.We can classify them according to the issue type. Task-based and demand-based issue are the behavior characteristics of users, while defect based issues are the behavior characteristics of contributors. But in this way,we default that the issue type filled in is accurate.Do you think it's more reasonable?

I want to hear opinion from @zhongjun2 , because I think we need start implementation. Some pending discussion can continue while starting implementation.

@imjoey

I think you are right.We can classify them according to the issue type. Task-based and demand-based issue are the behavior characteristics of users, while defect based issues are the behavior characteristics of contributors. But in this way,we default that the issue type filled in is accurate.Do you think it's more reasonable?

@Ivye thanks, I guess the quality engineers would be glad to see bug report counts. While actually this is not quite a big matter, since we can adjust this strategies along with the implementation accordingly.

@Ivye thanks, I guess the quality engineers would be glad to see bug report counts. While actually this is not quite a big matter, since we can adjust this strategies along with the implementation accordingly.

@imjoey

Thank you for your participation.I have updated the issue classfication in the attachment.

@imjoey

Thank you for your participation.I have updated the issue classfication in the attachment.

@Ivye It totally looks good to me. Thanks for your great efforts.

@Fred_Li thanks for your response. From my perspective, a bug report is very helpful for maintainers and contributors, which could be also considered as a contribution. Of course, a simple question is not.
@Ivye @zhongjun2 @DozeDoze Can you join us for sharing your insights? Thanks.

@imjoey Of course, thanks for the invitation. I have been focusing on content development and will ask questions and suggestions. I also look forward to contributing to the community.