Thanks, YiKun for the support and input. 1. For specific activities which may belong to a certain area of CoPDoC, I guess we'd better put them in the CONTRIBUTING[1] guide not here. For example, diversity architecture support may need design and discussion being raised in mailing lists, code change via PRs, tech posts through blogs/conferences, documentations, e.t.c. It is inevitable that we will miss something if we try to make it as detailed as we can. This, on the contrary, can lead to some ambiguities and misunderstandings.
2. The second suggestion may be similar to 'Promoting the project by writing articles or holding events.', said Willem. And It will be great if we add this to the CONTRIBUTING guide. BR, Kent Yao [1] https://github.com/apache/incubator-kyuubi/blob/master/CONTRIBUTING.md Yikun Jiang <yikunk...@gmail.com> 于2022年3月12日周六 16:46写道： > > Big no-binding +1 on this charter, I also think this is a good practice for > "community over the code". > > In addition, I think we can add some to encourage contributions in various > fields to make community better. > > -From tech view, we can encourage the improvement of specific fields, such > as diversity architecture (such as, x86 or arm), the deployment of > different OS, security improvement and so on, to make Kyuubi can expand > more application scenarios. > > -From community view, in addition to "you can join us via our mailing list, > issue trackers, discussions page to interact with community members, and > Share vision and knowledge", we might also encourage and help Kyuubi to > speak out in the outside world, including but not limited to development > related, such as share user story, best practices, join/organize the meetup. > > Regards, > Yikun
