Re: [che-dev] Github repositories

[Sergii Kabashniuk <skabashnyuk@xxxxxxxxxxx>]

Current plan of migration is here https://github.com/codenvy/che/wiki/Codenvy-Che--to-Eclipse-Che-migration-plan

On Tue, Feb 2, 2016 at 2:33 PM, Tyler Jewell <tyler@xxxxxxxxxxx> wrote:

Sergii - please prepare specification.  You can start by taking your proposal here.  Then florent & others can comment in GitHub, and we can make improvements through edits and pull requests.

1. We need to move specifications into che-specifications repository.

2. Author specs in .MD files, and make available for public to review & comment.

Tyler Jewell | CEO | tyler@​codenvy.​com | 9​78​.8​84​.53​55

On Tue, Feb 2, 2016 at 4:30 AM, Gennady Azarenkov <gazarenkov@xxxxxxxxxxx> wrote:

Let's postpone it to better time.

Gennady Azarenkov - CTO @ codenvy.com

On Tue, Feb 2, 2016 at 2:08 PM, Tyler Jewell <tyler@xxxxxxxxxxx> wrote:

What are the implications of making this change for 4.1 after we get initial contribution done?

1. Significant impact to docs.

2. Numerous videos related to che-on-che that have to be recast.

3. If we make changes to the directory structure then we need to re-define the che assembly

For example:
1. Want to see proposal that includes Florent's ideas.

2. che-swagger & che-terminal should be part of single repository called che-third-party.

3. Tomcat packaging should be part of che-third-party.

4. Che repository would be moved to che/che-assembly

5. We need to re-organize che-assembly to remove src/assembly/ structure and place it at base of assembly folder.  

6. Where does che-dockerfiles go?  We should look at a strategy that combines samples, templates, dockerfiles into a single location.

7. Rename che-depmgt to che-dependencies.

Tyler Jewell | CEO | tyler@​codenvy.​com | 9​78​.8​84​.53​55

On Tue, Feb 2, 2016 at 1:17 AM, Sergii Kabashniuk <skabashnyuk@xxxxxxxxxxx> wrote:

Hello developers.

We are on the last lap with Eclipse Contribution. 

And we are thinking about  structure of our git repositories.

At  this moment we have the following vision for the list of repositories.

1. che-dev-resources

2. che-parent

3. che-depmgt

4. che-swagger

5. che-terminal

  - che-websocket-terminal

  - websocket

  - pty

6. che

   - che-core

   - che-plugins

   - che-dashboard

   - che-tutorials

   - che

Our motivation

1-2. Repositories that contains maven configuration

3. Our dependencies management 

4-5 Repositories with third-party code.

6. Our single source-code repository with dedicated issues management, wiki, pull requests. 

Names of the modules inside of repositories is TBD. This list provides general view about target destination of existed sources.

Sergii Kabashniuk

_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/che-dev

_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/che-dev

_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/che-dev

_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/che-dev