maobaolong commented on pull request #921: URL: https://github.com/apache/hadoop-ozone/pull/921#issuecomment-643350226
There are still lots of contributor around me complain with the 80 character per line limitation. So a month past, a vehemently discussion has taken place in the mail-list, i think everyone have many arguments, but everyone try to persuade other, but nobody can persuade other. But we still need a decision, and a reason why, both do nothing and do this change. can be a choice. I think we don't make decision means choose keep 80, it isn't a reasonable result for people who want to change. Now, i found there are 3 choices from the discussion. 1. keep 80 2. change to 120 3. change to 100 It seems we have no better idea than vote, and everyone is equal, i don't think it's a good idea of giving more weight of people who did special contribution for Ozone. For example, founder, member, committer, contributor. In fact, it is too complex, the simple way is everyone is equal, at least voter should be a contributor, majority can be accepted. Finally, my choice is change to 120, or at least 100, so, i want to vote to 2, and 3. I don't know why if we have to keep consistent with the first great people who write the first line of one repository, in fact, i saw a repository was changed from one language into another language, i also saw a repository was changed from gradle to maven, that is what i want to say, keep change, change for great. I write this reply here because i'm not sure all contributors in the ozone-dev mail list, but i believe all the contributor can see this page, we can send this link to mail-list, slack channel or any others to let people vote for this decision. If someone have a better idea than vote, i'm very glad to see any other idea about how to finish this proposal other than vote. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
