[
https://issues.apache.org/jira/browse/HBASE-25183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17215586#comment-17215586
]
Andrew Kyle Purtell edited comment on HBASE-25183 at 10/16/20, 6:19 PM:
------------------------------------------------------------------------
bq. If I just want to keep politeness I could just leave the issue there, and
reply a single sentence every week with very positive words but no actual
action. Everyone will think I’m a good person but what is the value to the
project?
Ok, but I will say this: I think one can be polite and still stick to one's
opinions. For example, let's say I want to separate out the balancer to a
separate module. Someone else on the project has concerns, but I don't agree,
so I say "Yes I hear your concerns and here is why I disagree: ..." . No more
no less. And then I would put up my patch to split the balancer out to its own
module. :-) During patch review the community will either accept it or not,
there may be a technical veto, the technical veto may be judged to be valid. So
I would then choose to abide by the rationale for the technical veto and update
my patch, or abandon the work and move on to another issue. Or maybe I would
succeed in getting the technical veto lifted through continuing polite
communication and technical rationale, and all would be good that way. I think
this is the Apache model of handling disagreement over code.
was (Author: apurtell):
bq. If I just want to keep politeness I could just leave the issue there, and
reply a single sentence every week with very positive words but no actual
action. Everyone will think I’m a good person but what is the value to the
project?
Ok, but I will say this: I think one can be polite and still stick to one's
opinions. For example, let's say I want to separate out the balancer to a
separate module. Someone else on the project has concerns, but I don't agree,
so I say "Yes I hear your concerns and here is why I disagree: ..." . No more
no less. And then I would put up my patch to split the balancer out to its own
module. :-)
> Move more balancer related classes to hbase-balancer
> ----------------------------------------------------
>
> Key: HBASE-25183
> URL: https://issues.apache.org/jira/browse/HBASE-25183
> Project: HBase
> Issue Type: Umbrella
> Components: Balancer
> Reporter: Duo Zhang
> Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
