hi Julian:
   I think you have a good idea. In the Calcite community, people can 
know who has made changes by browsing GitHub, the number of PR contributions 
and the activity of the community.And People can know their contributions in 
`https://github.com/apache/calcite/graphs/contributors`.
   I hope the Calcite community will be better.


Xzh


------------------ 原始邮件 ------------------
发件人:                                                                            
                                            "dev"                               
                                                     
<jhyde.apa...@gmail.com&gt;;
发送时间:&nbsp;2021年9月23日(星期四) 晚上10:49
收件人:&nbsp;"dev"<dev@calcite.apache.org&gt;;

主题:&nbsp;Re: [DISCUSS] Remove contributors name from commit summary



A separate but related question: should we give people credit for their 
contributions in the release notes? We could append a contributor’s name to 
each contribution (achieving a similar effect to today). Or we could generate a 
“The following people contributed to this release: …” paragraph per release. Or 
let people’s contributions speak for themselves (if you want to know who did a 
change, browse GitHub).

I lean towards the last of these, but I want to hear what others think. The 
goal, as ever, is to build a strong community.

Julian

&gt; On Sep 23, 2021, at 7:37 AM, Julian Hyde <jhyde.apa...@gmail.com&gt; wrote:
&gt; 
&gt; +1
&gt; 
&gt;&gt; On Sep 23, 2021, at 2:23 AM, Stamatis Zampetakis 
<zabe...@gmail.com&gt; wrote:
&gt;&gt; 
&gt;&gt; Hi all,
&gt;&gt; 
&gt;&gt; Currently we are supposed to append the contributors name to the commit
&gt;&gt; summary when they are not committers of the project. The main reason 
for
&gt;&gt; doing this if I am not mistaken is to give some credit to those people.
&gt;&gt; 
&gt;&gt; I did like this practice in the beginning but I think it adds some 
small
&gt;&gt; overhead to all parties involved (committers and contributors).
&gt;&gt; 
&gt;&gt; The contributor quite often forgets to include the name in the end so 
the
&gt;&gt; burden to find and append the name goes to the committer.
&gt;&gt; 
&gt;&gt; In various cases, I've seen PRs ready to merge which were actually 
missing
&gt;&gt; the name at the end. What usually happens afterwards is one of the
&gt;&gt; following:
&gt;&gt; * the committer merges the PR without amending the name;
&gt;&gt; * the committer rebases the PR, amends the commit, and merges it;
&gt;&gt; * the committer asks the contributor to change the commit message;
&gt;&gt; 
&gt;&gt; I would prefer it if we could avoid this overhead by changing the 
commit
&gt;&gt; guidelines to not append the contributors name at the end.
&gt;&gt; 
&gt;&gt; GitHub does a great job giving credit to contributors. Moreover in most
&gt;&gt; cases the name appears in the log under the author tag so it is very 
easy
&gt;&gt; to exploit if we want to extract information and statistics.
&gt;&gt; 
&gt;&gt; What do you think?
&gt;&gt; 
&gt;&gt; Best,
&gt;&gt; Stamatis

Reply via email to