[ 
https://issues.apache.org/jira/browse/HDDS-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16877933#comment-16877933
 ] 

Eric Yang commented on HDDS-1661:
---------------------------------

{quote}What do you mean? "brain wash current developers with odd behaviors" I 
do not even understand what you are trying to insinuate here. If you cannot 
communicate respectfully, please stop trolling and go away. {quote}

My definition of odd behavior in this case is firmly believe in something that 
will not happen and also prevent people from making code changes to make the 
project better.  I am not trolling, and happy to provide patch to make this 
happen.  However, if no Ozone developer agree with me, then you are exactly on 
my point that you like to build Ozone on your own, and you don't want new Ozone 
developer adoption.  I think this is an odd behavior for open source 
development.  I respect your reasons to keep the status quote, but it is awful 
for people who like to contribute, but can't.

> Consolidate hadoop-hdds and hadoop-ozone into hadoop-ozone-project
> ------------------------------------------------------------------
>
>                 Key: HDDS-1661
>                 URL: https://issues.apache.org/jira/browse/HDDS-1661
>             Project: Hadoop Distributed Data Store
>          Issue Type: Bug
>            Reporter: Eric Yang
>            Priority: Major
>
> Ozone source code is some what fragmented in Hadoop source code.  The current 
> code looks like:
> {code}
> hadoop/pom.ozone.xml
> ├── hadoop-hdds
> └── hadoop-ozone
> {code}
> It is helpful to consolidate the project into high level grouping such as:
> {code}
> hadoop
> └── hadoop-ozone-project/pom.xml
> └── hadoop-ozone-project/hadoop-hdds
> └── hadoop-ozone-project/hadoop-ozone
> {code}
> This allows user to build ozone from hadoop-ozone-project directory.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to