anuengineer commented on pull request #921:
URL: https://github.com/apache/hadoop-ozone/pull/921#issuecomment-648364625


   >    https://accessibility.digital.gov/ is about accessible websites 
(layout, navigation, etc.). It does not talk about making the source of these 
websites accessible.
   
   But which part of the write up gave you the impression that written text on 
a screen shouldn't follow this recommendation. For a website like 
https://www.gutenberg.org/ would this hold? It is just text, some novels on the 
web. I think it does; Again, what is missing in the whole conversation is what 
is the data point to move when a certified government body, designed to deal 
with only this issue is giving a set of recommendations and why would we not 
follow it? Why are we insisting that source code is some how not text? I am not 
able to comprehend this stretch of argument. In my mind, Source code is text. 
And I am assuming that these recommendations hold for all romantic languages.
   
   
   >  Even if we accept the specific line length recommendation as applicable 
to our sources, why should it apply only to Java code? Why not, most 
importantly, to our Markdown docs, which have much longer lines than 80 chars? 
What about Javascript, CSS, bash scripts, POM files, etc?
   This is a good point. I agree, to the extend possible, we should make this 
binding on all sources. Including for sure, on MArkdown and CSS and Bash 
scripts. I was not aware of this oversight. Thank you for bringing this to my 
attention.
   
   
   > What about log files and configuration? Those affect a (hopefully) much 
wider audience.
   
   Log files generally have no carriage return and therefor formats to whatever 
size you want. Configuration, I do feel that we should follow the 80 lines 
limit.
   


----------------------------------------------------------------
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]

Reply via email to