Minutes: July, 17 2017
- Gennady Azarenkov
- Florent Benoit
- Gorkem Erkan
- Roman Iuvshyn
- Eugene Ivantsov
- Alexander Garagatyi
- Stevan LeMeur
- Mario Loriedo
- Vitalii Parfonov
- Anna Shumilova
- Release of 5.15.0
- Remaining work on new workspace details pages
- Next sprint plans?
- Strat work on Command Palette https://github.com/eclipse/che/issues/4993
- Freesia train planning objectives - results of Dev BU management meeting last week
- Codenvy customer support and business plan
- Review the development process document
- Multi-tenant Che on OSIO
- Build centos-based image of Che server
- Brno face to face agenda (doc)
- Call for papers from EclipseCon Europe 2017
TOPICS FOR DISCUSSING:
4 open issues, any blockers. Looks like we are ready for release 5.15
Ann propose move to 5.17
Propose for sprint are ready. Tomorrow (18/07/2017) will be estimate meetings
IDE team will start work on it. It will be POC. Issue is to big for one sprint.
-
Core Objective: Ship Che 6 w/ SPI, OpenShift, keycloak, IDE re-design, workspace loading
-
Core Objective: Dogfooding objectives … various IDE improvements to support dogfooding
-
Core Objective: Complete specification (and maybe reference implementation) of JavaScript API for plugins (moving Florent’s investigations into a full markdown specification with various APIs and samples that can be shared with community for discussion and also presented at CheConf 2017)
-
Stretch Objective: improvements to IDE for Try It Now experience. I started this thread with Stevan, but needs thought + investigation. Basic idea is whether we can improve how new users to a technology learn that technology by re-configuring the views of the IDE when an action is executed - change the project tree, which files are open, which lines are highlighted, and which panel / popup is displayed (with HTML help)
-
Stretch Objective: exploration to have Che bundled within the DevSuite / CDK bundle that is shipped by RHT. There are not a lot of thinking on this yet, but RHT’s standard bundle is installing their own Docker daemon, configuring it, and the thinking is why not have Che installed and running as well?
* Core Objective - clear for team * Stretch Objective - any comments for now
Brad can walk through specifics and offer any Q&A. There is no action item here - just a discussion so that everyone is on the same page.
Current Codenvy customer support: Proposal: Support Codenvy 5 for at least one more renewal cycle. When Che 6 / OSIO are good enough to support enterprise teams, we will work with each customer to move them to Che 6 / OSIO. Eugene commented that it will be very hard to move customers to Che 6 or OSIO, it’s basically a reinstall and re-implement. For customers like TIAA this could be a long process. Brad replied that we need the long support timeline for this reason and that we won’t start looking at moving customers until Jan 2018 at the earliest.
Have we concluded the analysis of maintainers? Is the language in the dev process document finalized? If not finalized, we need another review cycle and then once finished, update the wiki.
Looks like we done this task. Roman add special command pr-test for testing PR on our CI. Core concepts are complete. Needs another top-to-bottom review of language before posting by PM.
KC support is a pre-req for multi-tenant Che on OSIO. Do we have an idea about when this will be available? Are there any risk?
Sergii will have more info end of this week. Will organize meeting for agreement status
Mario will create issue for Roman for this task
Team will review add comment and discus next few weeks
Sergii will send mail with description of problem
Che 6 needs to be able to run on OSIO. Needs to be added to Freesia goals.
Stevan and Florent have submitted two talks:
- Chefiles talk from EclipseCon France which was very well received;
- Che 6 features.
Brad is submitting a talk on the current and future state of the IDE market which will touch on Che 6