Thanks for your feedback! To Yu:
1. the top 10 contributors No. I tend not to rank the contributors. We simply acknowledge all contributors to make the release happen. If you'd like to rank the contributors, what's the standard? PR numbers? Patch importance? I believe ranking contributors by PR numbers is the wrong direction. And significant contributions should be already highlighted in the blog if we write it. 2. Contributors page/table I support it can be a good initiative. But it's a different topic - here, we talk about acknowledging contributors _per release_. You can start another thread to discuss it in detail for the contributor page/table. To Dave: > New contributors whose first PR is included. This is a good suggestion. I think GitHub Release already shows the information. I'll investigate how to do it self-driven, or the RM simply copy the info from GitHub Release. > Contributors who are not yet committers. & Committers. I think this is somewhat of the same direction in ranking contributions. Please see my comments above. IMO it's a topic that happened in private@ to identify active contributors. Best, tison. Dave Fisher <w...@apache.org> 于2022年11月22日周二 11:52写道： > To me a contributors list has three levels > > 1. New contributors whose first PR is included. > 2. Contributors who are not yet committers. > 3. Committers. > > As a PMC member I want be on the look out for new committers to grow the > Pulsar community. > > We want the community to see the path to being a committer. > > Best, > Dave > > Sent from my iPhone > > > On Nov 21, 2022, at 6:36 PM, Yu <li...@apache.org> wrote: > > > > Hi tison, > > > > Thanks for raising this up! > > > > Expressing appreciation for contributors is a great way to improve health > > and fitness in our community. > > > > Here are just my two cents: > > > >>>>>>>>>>>>>>>>> > > > > 1. Except for the all-contributors list, does it make sense and is it > > possible to show the top 10 contributors for each release? > > > > Here comes another issue, how to evaluate the top 10? > > > > The simplest way is based on the lines of code (the same as how GitHub > > counts contributions, etc), but it does not make sense to some degree. > > > > At the same time, other factors (e.g. how active a contributor is, how > many > > PR/issues he/she reviews/answers, etc) can be taken into consideration, > but > > this might make things a little complicated. If we do not find a quick > and > > easy way to do this, it might overwhelm release managers. > > > >>>>>>>>>>>>>>>>> > > > > 2. Does it make sense to show contributors for all Pulsar-related repos > > (e.g. pulsar, pulsar-site, pulsar-client-cpp, pulsar-helm-chart) on the > > Pulsar website? > > > > SkyWalking follows this way, see "Contributors" at > > https://skywalking.apache.org/team/. > > > >>>>>>>>>>>>>>>>> > > > > Feel free to correct me if am wrong, thank you! > > > > Yu > > > >> On Mon, Nov 21, 2022 at 2:35 PM tison <wander4...@gmail.com> wrote: > >> > >> Hi, > >> > >> Dave's email about first-time contributions reminds me of the idea to > >> acknowledge contributors for each release. > >> > >> Let's see how the Flink community does it: > >> > >> For each release blog, e.g. [1], in the last section "List of > >> Contributors", > >> explicitly list out contributors and acknowledge their contributions. > >> > >> When it went back to the first time I got listed, I was proud to share > it > >> on social media and it encouraged me a lot to make more contributions. > >> Also, from the community perspective, releasing patches as well as > >> acknowledging the authors are somewhat fundamental rewards we can offer. > >> > >> To generate the list, I adapt the scripts provided by Flink as: > >> > >> 1. For Pulsar v2.10.0 (minor version release): > >> > >> git log --pretty="%an%n%cn" v2.9.0..v2.10.0 | sort | uniq | tr "\n" > "," | > >> sed 's/,/, /g' > >> > >> ... which gives: > >> > >> Addison Higham, Ali Ahmed, Aloys, Amar Prakash Pandey, Andras Beni, > Andrey > >> Yegorov, AnonHxy, Anonymitaet, Arnar, Baozi, Bharani Chadalavada, Bowen > Li, > >> Boyang Jerry Peng, Callum Duffy, Christophe Bornet, Da Xiang Huang, Dave > >> Fisher, David Kjerrumgaard, Devin Bost, Dezhi LIiu, Dianjin Wang, Diego, > >> Enrico Olivelli, Eric Shen, Eron Wright, Fangbin Sun, Frank J Kelly, > >> Frederic Kneier, Gautier DI FOLCO, GitHub, Haaroon Y, Hang Chen, > >> HuangQiang, Huanli Meng, Jagadesh Adireddi, Jason918, JiangHaiting, Jin, > >> Jiwei Guo, Kai, Kai Wang, Koen Rutten, Lakshmi Balu, Lari Hotari, Lars > >> Hvam, Lei Zhiyuan, Li Li, Lishen Yao, Marvin Cai, Masahiro Sakamoto, > >> Massimiliano Mirelli, Matt Fleming, Matteo Merli, Md Mostafijur Rahman, > >> Michael Marshall, Neng Lu, Nicklee007, Nicolò Boschi, Ofek Lev, Paul > Gier, > >> Peter Tinti, Qiang Huang, Qiang Zhao, Rajan Dhabalia, Roc Marshal, Ruguo > >> Yu, Rui Fu, Saumitra Srivastav, Shen Liu, Sijie Guo, Smile, TakaHiro, > Tao > >> Jiuming, Thomas Leplus, Tong, Travis Sturzl, Vincent Royer, WangJialing, > >> Xiangying Meng, Xiaobing Fang, Xiaoyu Hou, YANGLiiN, Yan, Yang Yang, > >> Yannick Koechlin, Yong Zhang, Yunze Xu, Yuri Mizushima, Yuto Furuta, > Zach > >> Walsh, ZhangJian He, Zhanpeng Wu, Zhiwu Wang, Zike Yang, Zixuan Liu, > Ziyao > >> Wei, aarondonwilliams, baomingyu, bentonliang, billowqiu, chenlin, > >> codertmy, congbo, entvex, fengtao1998, feynmanlin, fu-turer, > gaozhangmin, > >> goflutterjava, hanmz, hrsakai, imryao, junqingzh, kaushik-develop, > >> kijanowski, kimula takesi, lightzhao, lin chen, lipenghui, litao, > >> liuchangqing, liudezhi, madhavan-narayanan, ming, mingyifei, momo-jun, > >> penghui, ran, sijia-w, suiyuzeng, wenbingshen, xiaolong ran, youzipi, > >> zhaoyajun2009, 包子, 萧易客 > >> > >> 2. For Pulsar v2.10.1 (patch version release): > >> > >> git log --pretty="%an%n%cn" v2.10.0..v2.10.1 | sort | uniq | tr "\n" > "," > >> | sed 's/,/, /g' > >> > >> ... which gives: > >> > >> Adrian Paul, AlvaroStream, Andrey Yegorov, Baodi Shi, Baozi, Christophe > >> Bornet, Cong Zhao, Dezhi LIiu, Enrico Olivelli, GitHub, JiangHaiting, > Jim > >> Baugh, Jiwei Guo, Kai Wang, Kay Johansen, Lari Hotari, LinChen, Lishen > Yao, > >> Matt-Esch, Matteo Merli, Michael Marshall, Neng Lu, Nicolò Boschi, Qiang > >> Huang, Qiang Zhao, Ruguo Yu, Rui Fu, Shen Liu, Tao Jiuming, Tian Luo, > >> WangJialing, Xiangying Meng, Xiaoyu Hou, Yan Zhao, Yang Yang, Yong > Zhang, > >> Yunze Xu, Yuri Mizushima, ZhangJian He, Zike Yang, Zixuan Liu, > boatrainlsz, > >> codertmy, congbo, dependabot[bot], fengyubiao, gaoran10, gaozhangmin, > >> grayson, lin chen, lipenghui, lixinyang, llIlll, penghui, ran, > wuxuanqicn, > >> 赵延, > >> > >> I think we can integrate such a step into the release process[2] if we > >> reach a consensus. But let me start this thread first to see your > thoughts > >> and suggestions. > >> > >> Looking forward to your feedback! > >> > >> Best, > >> tison. > >> > >> [1] https://flink.apache.org/news/2022/10/28/1.16-announcement.html > >> [2] https://pulsar.apache.org/contribute/release-process > >> > >
