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