[che-dev] Community meeting minutes, 2018-08-20

[Dave Neary <dneary@xxxxxxxxxx>]

Hi all,

We had the regular Che community meeting today. Here are the meeting
notes (included below):
https://docs.google.com/document/d/1OODjdZXMM4TKb9-2GCMHBQTs-pYjTkXjJ_TNzUC-PcM/edit#

The next meeting will be at 11am Eastern Standard Time, September 3rd,
at the same place.

Thanks,
Dave.

Topics
* Che 6.x timeline - Jason Levine/Software Ag
* Workspace restart strategy - Sergey/SAP
* Accessibility (Section 508 compliance), Localization,
Internationalization - Jason Levine/Software AG


Notes
=====

1. Che 6.x timeline

 - Question: When will Che 7 release?
 - Answer: Continue to work on 6.x for the next number of releases,
while working on Che 7 related features and merging them as they are
ready. When all Che 7 prerequisite features are “ready”, we will jump
versions to Che 7.0 - no dates announced or targeted yet.

2. Accessibility

 - Software AG needs to ensure that Che is accessible for its customers.
Is there interest in accessibility related improvements?
 - Absolutely! Dave summarises what accessibility means - allowing
products to be used by the blind, visually impaired, and physically
impaired - can you use the project without a screen, in text only mode,
without a mouse, or with a high contrast theme and very large font size?
 - Any accessibility features will be welcomed.

3. Internationalization and localization

 - Are there plans to have language packs in non-English languages?
 - Do we support non-Latin scripts, RTL languages?
 - Answer from Sergii: There is currently support in GWT for
localisation, but no plans to improve it - the goal is to focus support
for l10n and i18n in Theia

4. Workspace restart strategy

 - Workspaces are currently in a pod, rather than being a deployment -
when a workspace fails, Kubernetes can’t restart it. What are our plans
in this area?
 - Oleksander answers that we already have deployment workspaces in the
tip of master, as an option. Right now our installer process prevents us
from leveraging this for workspace restarts, we plan to address this
issue. In workspace.next, workspaces will be run in separate containers,
and this will make workspace restarts much easier.
 - Asaf also interested in workspace management, and would like to know
when it will be available to use. Sergii explained that it is already
available but considered experimental - we are not developing 7.x
separately, features like this are merged as they are ready.
 - Oleksander suggests that we need to raise awareness of experimental
work which has merged as an option or has not yet merged b/c still work
in progress, and suggests that we should publish our demo videos for
experimental features.
 - Asaf asked whether it would be possible to use sidecar flow for Che 6.x
 - Oleksandr answered that our current experimental builds supports
current GWT based IDE as sidecar, but we won’t make sidecar flow default
in Che 6.x because it is major incompatibility with the current flow and
we would rather have such an incompatibility in a new major version of
the product.


Actions
=======

 - Post demos from Che core teams to che-dev mail list to engage
community to provide feedback and spread information about the most
recent changes. Demos of Theia based Che flow might also be interesting
for the community.


-- 
Dave Neary - Open Source and Standards team
Red Hat - http://community.redhat.com
Ph: +1-978-399-2182 / Cell: +1-978-799-3338