[
https://issues.apache.org/jira/browse/OFBIZ-7788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15375115#comment-15375115 ]
Pierre Smits edited comment on OFBIZ-7788 at 7/13/16 2:35 PM:
--------------------------------------------------------------
It all has to do with recognition of the contribution done by the community member. When the original issue is closed as a duplicate, the perception can grow that contributions of that contributor are mediocre and thus he/she won't build the merit necessary to gain privileges within the project. Because his/her contribution won't show up when the (code) change resulting from that is implement, and thus won't be communicated to the community.
was (Author: pfm.smits):
It all has to do with recognition of the contribution done by the community member. When the original issue is closes as a duplicate, the perception can grow that contributions of that contributor are mediocre and thus he/she won't build the merit necessary to gain privileges within the project. Because his/her contribution won't show up when the (code) change resulting from that is implement, and thus won't be communicated to the community.
> Update to 'OFBiz Contributors Best Practices'
> ---------------------------------------------
>
> Key: OFBIZ-7788
> URL:
https://issues.apache.org/jira/browse/OFBIZ-7788> Project: OFBiz
> Issue Type: Improvement
> Components: Confluence
> Reporter: Pierre Smits
>
> Please add the following to the *When to create a Jira issue* section of the document:
> {quote}
> When you find a duplicate of a JIRA issue, please close the newer one with the resolution 'Duplicate', and state what the original issue is. Closing the older issue is not respectful to the creator of the first issue, and can be perceived as an insult with respect to his/her good intentions.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Locked
