2017-09:day-2017-09-28
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision Last revision Both sides next revision | ||
|
2017-09:day-2017-09-28 [2017/09/28 13:45] h1 created |
2017-09:day-2017-09-28 [2017/09/28 18:36] mikedep333 Add "Mike#2 contributing on behalf of his day job" |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ==== 6th ΞX2Go Development Meeting ==== | + | ===== 6th ΞX2Go Development Meeting |
| - | ===== Who is taking part? ===== | + | ==== Who is taking part? ==== |
| * <todo @all>h1, Mike#1, Mike#2, Mihai, Stefan, Alex</ | * <todo @all>h1, Mike#1, Mike#2, Mihai, Stefan, Alex</ | ||
| - | === Research | + | ==== Topics ==== |
| - | * FIXME | + | * X2GoServer code updates in preparation of the upcoming release |
| + | * release is scheduled for early December 2017, but the sooner, the better | ||
| + | * We need a " | ||
| + | * Who will file these bugs, and who will mark them as blockers? | ||
| + | * Who is working on what? | ||
| + | * New release will bring changes on server and client side | ||
| + | * mostly regarding xinerama | ||
| + | * keyboard handling (" | ||
| + | * " | ||
| + | * server-side changes must come first, client-side changes could be delayed into early 2018 if we're low on resources | ||
| + | * Upcoming X2GoClient stable release | ||
| + | * any questions, vetos, ...? | ||
| + | * What needs to be done? | ||
| + | * Mike#2 will be available for Q&A | ||
| + | * Move of bugtracker to self-hosted " | ||
| + | * after the upcoming release? | ||
| + | * who can do it? | ||
| + | * how do we migrate bugs? | ||
| + | * Date for Next DevMeeting | ||
| + | * Regular schedule: Once per quarter | ||
| + | * Might need to take place more often in the next few months, due to the release schedule | ||
| + | * Mike#2 contributing on behalf of his day job | ||
| + | * [[https:// | ||
| + | * Use different git name like "Mike DePaulo (Work)" | ||
| + | * Would rather not make his work email address public | ||
| - | === Retrospective | + | ==== " |
| - | * FIXME | + | (will be moved to a different Wiki page later) |
| - | + | < | |
| - | === Planning === | + | X2Go Next Major Release |
| - | * FIXME | + | |
| - | === Out-of-band Topic === | + | Server-Side: |
| - | * <todo @orkun?> | + | Phase that allows 3.5 && 3.6 |
| + | 3.6 is in experimental, | ||
| + | Xinerama is not done | ||
| + | Needs Server-side and Client-Side changes | ||
| - | ====== Raw Chat Log ====== | + | New Servers need to be able to function with older Clients |
| + | and vice versa | ||
| + | |||
| + | Current (old) approach: xinerama.conf is generated on the client | ||
| + | file gets copied to server regularly | ||
| + | |||
| + | Mode 1: NXagent is in fullscreen - xinerama.conf shows geometry of your output device layout | ||
| + | |||
| + | Mode 2: X2Go session is in windowed mode and there is a multi-device layout on the client | ||
| + | -> | ||
| + | -> that's why on each resize/move event, xinerama.conf needs to be updated when using the " | ||
| + | |||
| + | Now, with current X2Go-Libs and X2GoClient, xinerama.conf gets pushed to the server -> if file is present, we enable xinerama mode. | ||
| + | |||
| + | When does that happen? Before or after the xgostartagent call? | ||
| + | |||
| + | New Client, New Server: | ||
| + | ->Idea: keep creating xinerama.conf, | ||
| + | -> " | ||
| + | * present -> xinerama.conf with " | ||
| + | not present -> xinerama.conf with required values | ||
| + | |||
| + | New Client, Old Server: | ||
| + | -> x2gofeaturelist / x2gofeature < | ||
| + | -> " | ||
| + | | ||
| + | * not present -> xinerama.conf with required values | ||
| + | |||
| + | Old Client, New Server: | ||
| + | Old clients will generate a xinerama.conf and upload it to the server | ||
| + | New Server should check file | ||
| + | -> If file exists, enable xinerama | ||
| + | -> If not, do not enable xinerama | ||
| + | --> Won't work because xinerama.conf is created too late | ||
| + | --> New Client | ||
| + | |||
| + | Old Client, Old Server: Unchanged | ||
| + | |||
| + | ->Idea: Have New X2Go *Client* report its list of features *to the Server* | ||
| + | --> Empty list = old client | ||
| + | ->This info should be stored in a file on the server (in the session directory) | ||
| + | --> x2gosuspend-/ | ||
| + | |||
| + | -- | ||
| + | |||
| + | Keyboard: | ||
| + | |||
| + | (Uli) | ||
| + | Plan: Change NX so keyboard handling works out of the box. | ||
| + | Unsure if this works. | ||
| + | Future NX-libs should block keyboard changes within sessions. | ||
| + | But: X2Go is currently changing keyboard settings within sessions. | ||
| + | |||
| + | -->New Feature " | ||
| + | |||
| + | (Mike#1) | ||
| + | Plan: Keep old behavior in the code, but switch the default: | ||
| + | - New way of handling things becomes default | ||
| + | - command line parameter/ | ||
| + | |||
| + | -- | ||
| + | |||
| + | Auto-Grab: | ||
| + | X2GoClient needs a checkbox to enable/ | ||
| + | |||
| + | Same goes for Input-Lock | ||
| + | |||
| + | -- | ||
| + | |||
| + | Focus on Server-Side implementation first | ||
| + | (Timing/ | ||
| + | |||
| + | |||
| + | Step-by-step plan, dependencies, | ||
| + | |||
| + | If we do a " | ||
| + | ESR instead of LTS? | ||
| + | Remove LTS/ESR packages from download servers if there is no support contract | ||
| + | |||
| + | ->Mihai will introduce snapshot archives for heuler | ||
| + | --> | ||
| + | |||
| + | required Documentation for testers -> Should be as simple as updating sources.list to a heuler+timestamp entry and running update, upgrade, dist-upgrade | ||
| + | </ | ||
| + | ==== Raw Chat Log ==== | ||
| FIXME | FIXME | ||
| < | < | ||
| ...log... | ...log... | ||
| </ | </ | ||
2017-09/day-2017-09-28.txt · Last modified: 2017/09/28 20:53 by ionic
Imprint & Legal Disclaimer -
Data Protection & Privacy Statement
Except where otherwise noted, content on this wiki is licensed under the following license: GNU Free Documentation License 1.3