@Julian,
(copy my reply from another thread and paste it as below)
Just copy your comments here and adding my comments. Thank you for the
suggestions.
[Julian] - Also, make the disclaimer more prominent on the front page. It
is buried at the bottom of a very long page. I think it should appear i
Sure, Julian, I'll take notice of your reminding. Thank you very much!
Michael
On Mon, Jul 18, 2016 at 4:16 PM, Julian Hyde wrote:
> Thanks for the explanation. But I hope you took note of my main point:
> code changes should be accompanied by sufficient explanation so that the
> community can
@Julian,
Just copy your comments here and adding my comments. Thank you for the
suggestions.
[Julian] - Also, make the disclaimer more prominent on the front page. It
is buried at the bottom of a very long page. I think it should appear in
the first screen-full.
[Michael] - a find an example from
Thanks for the explanation. But I hope you took note of my main point: code
changes should be accompanied by sufficient explanation so that the community
can review/understand them. We shouldn’t have to ask for an explanation.
Making code changes transparent helps to build community.
> On Jul 1
I added the following comments to the JIRA case:
* Also, make the disclaimer more prominent on the front page. It is buried at
the bottom of a very long page. I think it should appear in the first
screen-full.
* Apply these guidelines throughout the site, in particular to the docs,
https://eag
[
https://issues.apache.org/jira/browse/EAGLE-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15381860#comment-15381860
]
Julian Hyde commented on EAGLE-380:
---
Also, make the disclaimer more prominent on the fron
