Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "ECD/PMC/Meeting Minutes"

< ECD‎ | PMC
Line 20: Line 20:
 
* Flux:
 
* Flux:
 
** No updates
 
** No updates
 +
* General discussion:
 +
** We revisited the subject of whether Eclipse desktop-based tools related to development '''for cloud''' are appropriate for ECD. There is some concern this will dilute the focus of the project and it will not be clear how/when to draw the line since many technologies and tools can touch on cloud deployment. We agreed the main focus of ECD is on cloud-based development, and since this style of development still has some overlaps with local development tools it would not be helpful to be too rigid about excluding desktop-based tools as long as they are part of a cloud-focused workflow.
  
  

Revision as of 09:01, 11 May 2015

Minutes of the Eclipse Cloud Development PMC

May 7, 2015 - John, Martin, Tyler and Nedelcho

  • Orion:
    • Tern
    • Dark theme
    • Split editors
    • Editor consumability
  • Dirigible:
    • Working through IP process for dependencies
    • Now consuming Orion editor
    • Working on debug tools, integration with editor
  • Che:
    • Working on both 3.10 and 4.0 releases
    • 3.10 is focused on stabilizing SDK
    • Being able to launch an SDK instance via a URL
    • Bundling docker capability in SDK so Docker can be used for local runners
    • Events infrastructure, project types have associated events, events can trigger commands which run inside a runner
  • Flux:
    • No updates
  • General discussion:
    • We revisited the subject of whether Eclipse desktop-based tools related to development for cloud are appropriate for ECD. There is some concern this will dilute the focus of the project and it will not be clear how/when to draw the line since many technologies and tools can touch on cloud deployment. We agreed the main focus of ECD is on cloud-based development, and since this style of development still has some overlaps with local development tools it would not be helpful to be too rigid about excluding desktop-based tools as long as they are part of a cloud-focused workflow.



April 23, 2015 - John, Martin, with notes sent from Tyler and Nedelcho

  • Che
    • We have submitted the Che initial contribution CQ
    • We are releasing 3.9 next week which will be a monster release.
    • We are almost done packaging up our docker runner system into Che itself for reuse.
    • Submitted a few different Che + Orion talks at various conferences
  • Flux
    • Submitted move review documentation to move Flux to the ECD project
  • Orion
    • Submitted move review documentation to move Orion to ECD project
    • Orion 9 planning: focus on JavaScript tools, UX improvements, performance, and Docker investigation
  • Dirigible
    • We managed to refactor Dirigible in way to depend only to already approved libraries in Orbit
    • About 40 dependencies are already approved by John and Martin and respectively by Jason. Thanks a lot for that!
    • Currently pending is only the CQ with the sources of Dirigible itself
    • Meanwhile we introduced and integrated Orion editor (client side only) as alternative to the ACE. It can open, save, change dirty state, highlighting for some languages, code completion for HTML and CSS as of now. The remaining major features is integration with the debugger and code completion for JavaScript.

General discussion:

We discussed whether desktop-based tooling for Cloud, such as Cloud Foundry tools, would be a good fit under ECD. We agreed that we are not limited to only browser-based tools so it is ok to welcome desktop-based tooling projects with a strong cloud focus. Such projects can also fit under Web Tools, for example there was a WTP talk at EclipseCon 2015 about WTP and cloud. To be vendor neutral, such tools would need to be pluggable to enable an open-ended set of cloud providers where applicable.


April 2, 2015 - John, Martin, Tyler, Nedelcho, Simon

  • Future meetings:
    • Need to establish PMC meeting time/cadence
    • Start with 1 hour slot, every two weeks
    • Can keep it to 30 minutes most of the time
  • Orion
    • John to draft move review docs
    • Doing exploration on Docker containers
  • Flux
    • John to draft move review docs
  • Dirigible
    • Preparing CQ's
    • 60 dependencies, mostly Java libraries
    • Plan to host directly on GitHub
    • Then make initial code contribution
    • Groovy dependency may need to be factored out to allow bulk of legal review to proceed
  • Che
    • Not showing up as a sub-project of ECD, need to check with EMO on why
    • Refactoring repositories into 4 repos
    • Changing build infrastructure to match refactoring
    • Focused on initial contribution
    • Talking to other companies about bringing their technology to ECD

Back to the top