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

ECD/PMC/Meeting Minutes

< ECD‎ | PMC
Revision as of 15:58, 13 August 2015 by John arthorne.ca.ibm.com (Talk | contribs)

Minutes of the Eclipse Cloud Development PMC

August 13, 2015 - John, Tyler, Martin, Nedelcho, Simon

  • Some problems were noted with the Che project infrastructure:
    • Bugzilla entry appears under Technology rather than ECD
    • The che-dev mailing list archive view shows no activity since April, however it is active
    • Tyler sent note to webmaster to resolve it
  • Projects are encouraged to have development discussions on the mailing list so there are public signs of the project's activity level and community.
  • Discussion of the proposed Cloud Foundry Tools project:
    • The PMC did not reach agreement that this project fit within the current project charter
    • The current charter is to build a Cloud developer environment that runs on cloud, not just traditional desktop tools that happen to deploy to cloud
    • If the proposed project widened its scope to also include CF tooling for Cloud Developer Environments it would be a more natural fit (e.g, CF deployment support for Orion or Che).
    • The PMC was open to discussing a widening of the charter to include a broader variety of cloud-related tools such as this one, but this process will take some time.
    • We need to decide if ECD will be a project focused on a cohesive, tightly integrated set of Cloud-based developer environments, or simply a technology umbrella with no attempt at internal consistency or cohesion.

June 18, 2015 - John, Tyler, Martin

June 4, 2015 - John, Tyler, Simon, Nedelcho

Project updates:

  • Orion wrapping up 9.0 release, doing final polish, thinking about Orion 10
  • Che:
    • 3.10.0 is released
    • 3.10.1 is planned to release in a couple days
    • 4.0 later in 2015
    • Che has completed their switch to Orion editor
  • Dirigible
    • Waiting on clearance of initial contribution CQ
    • Question: can we keep working while waiting for clearance? Answer: Yes, keep committing on top of initial contribution

Had a discussion of integration examples or reference applications that illustrate how to consume or connect Cloud project technologies. Where should such samples/integrations be hosted? GitHub or within the Eclipse project? It can be either, depending on whether you intend to release it, whether there are IP issues, etc. However there are wider issues of how these integrations are packaged/installed into the different cloud tools. How do users discover them? Is there a marketplace of integrations/plugins where users can discover new stuff to install? It was an interesting discussion, but more questions than answers at this stage.

Discussed ability to change UI layout in the browser. Want to be able to change UI layout by drag and drop as a user. It's very hard on the web. This is a common request in Che. Orion and Dirigible not currently looking at anything for changing view orientation.

May 21, 2015 - John, Martin, Tyler and Simon

IP issues for cloud PMC

  • Weekly releases don't fit with Eclipse release processes
  • CQ process for 3rd party library, incremental updates to fast moving libraries

Marketing around 3Q/fall releases for Che and Orion

  • Meet with project leads

Orion-Che bridge

  • Prototype has been built to dig into details of how to connect Orion client to Che server API
  • Two approaches: Che server extension that exposes Orion-compatible API so Orion client can

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 development in the cloud, and where cloud-based development has overlaps with local desktop tools it is reasonable to include them. For example a local development tool that connects to a cloud-based development service is in scope (as exemplified by Flux), but a local tool that simply deploys to cloud is not (for example a local FTP client).
    • We discussed representation for the Cloud PMC on the Eclipse Planning Council. We generally agreed that there is currently little overlap with the planning council's work given our current technology and deliverables. The planning council's primary focus is on the simultaneous release, which the cloud projects largely don't participate in. If we were looking to do aligned releases across multiple cloud-based technologies in the future then it could be a useful venue for that. For now John Arthorne will be the Cloud PMC representative on the planning council, but we don't anticipate a very active role in the short term.

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
Retrieved from "https://wiki.eclipse.org/index.php?title=ECD/PMC/Meeting_Minutes&oldid=389798"

Back to the top