Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [che-dev] Eclipse Che initial contribution plan
Merging of "che" branches postponed until the end of "che" weekly meeting

On Wed, Apr 1, 2015 at 8:07 PM, Tyler Jewell <tyler@xxxxxxxxxxx> wrote:
Once we convert over to this new repository structure, is someone going to update the various places where we referenc the old the repository names?

1. In the sdk readme, it has old references.
2. In the codenvy docs / downloads, do we have links to the right place to clone source (I think we have a downloads page, and eclipse che page on where to get these repositories).
3. in the marketing site, there are references to che - does it point to the right repository?

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


On Wed, Apr 1, 2015 at 9:53 AM, Sergii Kabashniuk <skabashnyuk@xxxxxxxxxxx> wrote:
The good news: SDK and hosted enviroment is working.
Tomorrow Apr 2 at 10:30 Kiev time. I will start merging "che" branches in

plugins
plugin-hosted
plugin-contribution
plugin-gae
plugin-svn
hosted-infrastructure
odyssey
factory
user-dashboard
cloud-ide

After that I will send one more mail and welcome you to contribute to our new project structure.

Sergii Kabashnniuk


P.S.
plugin-svn will be moved to che-plugin next week.



On Wed, Apr 1, 2015 at 5:32 PM, Sergii Kabashniuk <skabashnyuk@xxxxxxxxxxx> wrote:
Hello

Here is the current status.
che-parent
che-depmgt 
che-core
che-plugins
Is ready to go.


che-sdk - Vitaly in progress. Hope will be today. It's compiling,  but not tested.

For projects that are the part of Hosted version
plugins
plugin-hosted
plugin-contribution
plugin-gae
plugin-svn
hosted-infrastructure
odyssey
factory
user-dashboard
cloud-ide
I've created branch "che" with changes for the che migration.

cloud-ide - is not compiling yet. Vitaly and me is working now. Expected to fix it today


What next?
Today or tomorrow when hosted and sdk version will be ready I will send one more mail.
It mean "go" for new commits in new structure.
Old projects will remain public for 1 month + ~6 month they will be private. 
Then we will backup and remove from codenvy organization on github.

Also not accepted PR and old branches except master have to be moved manually. Projects that are not part of hosted version have to be adopted to new che dependencies by owners.
That is responsibility of branches owners, pull request owners or project owners.
So keep an eye


plugin-svn will be moved to che-plugin next week.

One more time remind list of old projects.

maven-parent-pom
maven-depmgt-pom
commons
platform-api
platform-api-client-gwt
ide
vfs-impl
test-framework
plugin-java
plugin-editor-codemirror
plugin-editor-orion
plugin-php
plugin-git
plugin-datasource
plugin-angularjs
plugin-bower
plugin-gulp
plugin-grunt
plugin-npm
plugin-yeoman
plugin-cpp
plugin-ruby
plugin-go
plugin-python
plugin-tour
plugin-sdk
plugin-runner


On Mon, Mar 30, 2015 at 6:20 PM, Sergii Kabashniuk <skabashnyuk@xxxxxxxxxxx> wrote:
Hello

Current progress.
We moved all expected artifacts to che-* structured. 
We setup maven build.
We renamed all groupId to org.eclipse.che.*
We are about 40% of renaming artifactId.
We also expect to do some cleanup in 
che-core/security
che-core/ide
che-plugin/plugin-git
che-sdk/*
We alson need to rename orgId and artifactId in all plugins what are the part of Hosted-IDE


We expect to finish this work till the end of Apr 1. 
Then you will be able to start migration of your branches to che-* projects

Sergii Kabashniuk




On Fri, Mar 27, 2015 at 8:51 PM, Dmitry Kuleshov <dkuleshov@xxxxxxxxxxx> wrote:
Hi,

As I understand we can continue development using new structure on our github account until initial contribution is accepted by Eclipse.
Is that correct, Dmitry?

Yes, that is correct. 

With regards,
Dmitry

2015-03-27 18:43 GMT+02:00 Sergey Kryzhny <skryzhny@xxxxxxxxxxx>:
Write access to these repositories removed.


maven-parent-pom
maven-depmgt-pom
commons
platform-api
platform-api-client-gwt
ide
vfs-impl
security
test-framework

plugin-java
plugin-editor-codemirror
plugin-editor-orion
plugin-php
plugin-git
plugin-datasource
plugin-angularjs
plugin-bower
plugin-gulp
plugin-grunt
plugin-npm
plugin-yeoman
plugin-cpp
plugin-ruby
plugin-go
plugin-python
plugin-tour
plugin-runner

plugin-sdk
assembly-che


On 27 March 2015 at 17:52, Sergii Kabashniuk <skabashnyuk@xxxxxxxxxxx> wrote:
I'm pretty confident in the way we choose to go to Eclipse Che
Right now 
Are set up and building with maven. 
I have some work to do with artifact renaming

On the way

In nearest hour write access to  such projects


maven-parent-pom
maven-depmgt-pom
commons
platform-api
platform-api-client-gwt
ide
vfs-impl
security
test-framework

plugin-java
plugin-editor-codemirror
plugin-editor-orion
plugin-php
plugin-git
plugin-datasource
plugin-angularjs
plugin-bower
plugin-gulp
plugin-grunt
plugin-npm
plugin-yeoman
plugin-cpp
plugin-ruby
plugin-go
plugin-python
plugin-tour
plugin-runner

plugin-sdk
assembly-sdk

will be removed 

Stay tuned for future instructions
 

On Fri, Mar 27, 2015 at 12:25 PM, Gennady Azarenkov <gazarenkov@xxxxxxxxxxx> wrote:
Sounds good, thanks

As I understand we can continue development using new structure on our github account until initial contribution is accepted by Eclipse.
Is that correct, Dmitry?

Gennady Azarenkov - CTO @ codenvy.com


On Fri, Mar 27, 2015 at 12:10 PM, Sergii Kabashniuk <skabashnyuk@xxxxxxxxxxx> wrote:
We have following plan to make initial Eclipse Che contribution.

1. Today Mar 27. We experimenting with project structure that we will contribute to eclipse in such projects

che-parent
che-depmgt
che-core
che-plugins 
сhe-sdk

in codenvy organization on github.

2. Approximately in one or two working days Mar 27-Apr 1 We will remove write access for the following projects.
Or maybe we gently asked to not to push in master. I haven't decided yet ))


maven-parent-pom
maven-depmgt-pom
commons
platform-api
platform-api-client-gwt
ide
vfs-impl
security
test-framework
plugin-java
plugin-editor-codemirror
plugin-editor-orion
plugin-php
plugin-git
plugin-datasource
plugin-angularjs
plugin-bower
plugin-gulp
plugin-grunt
plugin-npm
plugin-yeoman
plugin-cpp
plugin-ruby
plugin-go
plugin-python
plugin-tour
plugin-runner
plugin-sdk
assembly-sdk

In this time I will move content of this project to che-*
+ I will change groupId and artifactId of this projects

3. Until the end of working day  April 1 we will 
know when we can give write access to all developers in che-*
either open write access for the existed projects

4. After opening write access  to codenvy/che-* projects
developers have to manually migrate their branches to the new structure.

5. We will provide Eclipse our codenvy/che-* code as initial contribution.

6. After eclipse accept this contribution and host on their git infrastructure
   we will have to migrate our codenvy/che-* to their git hosting.
 Details of this procedure will  be provided later.

Sergii Kabashniuk







--
Best regards,
Sergey






Back to the top