*_Updates:_*
KASPARNET:
* Changes to windows provisioning scripts and tests (to no longer rely
on the node process): https://github.com/GPII/windows/pull/107
* Pull request against michelle's gpii-app branch:
https://github.com/michelled/gpii-app/pull/2
* Work on MM - harrassing antranig with stupid questions
Ale
* Merged Michelle and Kasper work around GPII-App in my own HST branch
where I'm working https://github.com/gloob/gpii-app/tree/HST
* Playing with electron-packager and GPII-App, created successfully
two flavours of win32 electron bundle for ia32 and x64. WICKED!
* Create new script for the creation of the installer automatically
based on GPII-App.
* Helping JJ to investigate how Learning tools are implemented and how
to onboard them.
Alfredo
* Building VMs for testing
* Working on the vagrant plugin
* Testing Gitlab-CI
* Testing Jenkins role
Antranig
* https://github.com/GPII/universal/pull/497/files is in review for
GPII-2160 - allow journalling system to continue restores with failures
* Some minor dependency updates for GPII-2259
* Merged in Steve Grundell's
https://github.com/GPII/universal/pull/498 for GPII-2235, ensure a
single instance of the GPII
* Merged in ADTKIN's
https://github.com/fluid-project/infusion/pull/761 transforms
inherited from gpii-binder
* Various code review for ADTKIN's group of projects
* Continued work on P4A Nexus demo
Avtar:
* APCP infra call
* GPII-2205 - becoming familiar with gpii-webdriver and webdriver,
have a somewhat working example that loads the Infusion
keyboard-a11y demo and runs aXe checks THIS IS GOING TO BE SO COOL
Cindy
* Working on
https://wiki.gpii.net/w/Continued_Researches_on_Possible_Approaches_for_Protecting_Communication_btw_LFM_and_CBFM
o Collecting and updating feedback and ideas from Simon and Steve
* Refactoring and adding tests for data loaders:
https://issues.gpii.net/browse/GPII-1987
Colin
* Helping with ops team
* Planning next steps for UI Options improvements and integration with
GPII
* Writing P4A deliverable for SP3
* Writing something about our training requirements
* Still need to review Javi's work on API for PCP (I haven't forgotten!)
Giovanni
* Various discussions and meetings about our infrastructure and future
direction
* Lots of minor improvements and cleanups in the inclusivedesign/ops
repo, pfSense, etc
* Working on assessing risks to moving away from OCAD's gateway and
using our pfSense firewall as the VM's gateway
* Updated Jenkins instances to latest LTS release due to security
advisory released today (please report issues, if any)
* Testing CentOS updates (and specially Docker latest update) before
continuing with the work that failed on the 20th
Han:
* Finished Windows 10 instruction documents for HST Script 1.5
* Resolved GPII-2232/2199/2240/2239
Javi
* Updated the chrome extension pull request
* Updated https://github.com/GPII/universal/pull/494 - Use the dynamic
device reporter when running tests
o Will appreciate any feedback on my last question here ->
https://github.com/GPII/universal/pull/494#issuecomment-276714696
o something's going wrong with the web tests, will take a look at
it later
* Also, sent a mail to the architecture list about the PCP API - Will
appreciate any feedback on it ->
http://lists.gpii.net/pipermail/architecture/2017-January/004488.html
* Reviewed pull requests from Ale and Joseph, pedantically.
* HST meetings
* Being a rubber duck for Ale and his work on packaging gpii-app for
HST - Haired and stylish rubber duck.!!
* Also, and as part of the HST testing plan, just started playing
around with the gpii-app - yay!!
JJ: _[GPII-2238]_
_[GPII-2249]_: Research how Microsoft Learning Tools are implemented
o Actual research is done in [GPII-2258] or [GPII-2257].
o Initial report for this issue is almost complete.
_[GPII-2258]_: Implement a PoC of an Add-in that controls the settings
and running state of other Add-ins
o It has been empirically confirmed by PoC that we are able to
reload a OneNote Addin at ‘on-the-fly’. In this case ‘Learning
Tools’.
o The process of detecting that Microsoft Internal runtime has
free the resources in order to reload the Addin is a bit hacky,
because there isn’t any standard way of doing it. (Introspection
API).
o Next step will be, to be totally sure that there isn’t any
standard way of doing it before proceeding with this
implementation, but it requires more "investigate" Learning
Tools and insides Microsoft API. It should take so much time,
until be totally sure of its limitations.
o We have been also started a kind of wiki, with the procedures,
tools and resources used for the deconstruction of this
Microsoft product. In order to increase the speed for next items.
_[GPII-2257]_: Evaluate differences of Learning Tools between several
Windows products.
o Just after finishing point 3 of [GPII-2258] this investigation
would be resumed.
Joseph
* GPII-8: GSettings handler core dumps on non-existent key.
o Addressed Javi's (pedantic) comments, and pushed -- ready for
more review.
o https://github.com/GPII/linux/pull/90
* FLUID-6090: model-ized the StateTracker component.
o will revisit to use IoC testing framework.
Sandra:
- Work continues to support hardware sensitivity testing.
- Should have new installer from Ale today or tomorrow, which
includes Michelle's new GPII-app.
- Listening to Udacity course on Intro to DevOps.
Simon:
* Continuing with Nexus work
* Security chats with Cindy
* Reviewing Antranig's https://github.com/GPII/universal/pull/497
Steve Grundell
1. HST stuff:
1. Detection of the gpii instance is in - Ale says he'll continue
it - Oh no, I said that? :P "mañana" - for the record, "mañana"
in this context may be tomorrow, or in 2 months :P classic spaniards
2. Started GPII-2248: port 8081 in use
Tony: :P
1. Completed the last of the import scripts to bring in GARI data for
the UL user testing.
2. After consultation with Alfredo, fleshed out a plan for deploying
the new UL website. After initial hilarity with libvips and
Centos, have completed all the preparation that can safely be done
in parallel, will make the full switch tomorrow.
3. After long consultation with Antranig, gpii-binder was just merged.
Notably, I figured out a key problem that resulted in spurious
failures at the end of each browser's testem run.
4. Working on the PR for gpii-launcher, will likely take a bit longer,
but looks promising.
5. Based on feedback from the OAuth2 team, will work on the cleanup
cycle for parts of gpii-pouchdb later this week:
https://issues.gpii.net/browse/GPII-2267
6. Will start working on the "live solutions registry" using the
"documentation driven design" method, i.e. writing the docs first to
get the craziest ideas out of the way before I write any code.
7. Super excited that people are using gpii-webdriver in anger, send
links to branches, etc. if you encounter problems, happy to give
advice or pair.
Tyler:
* AWS cost estimating
* Learning what constitutes a GPII Demo
* Resurrect IDRC Grafana (metrics collection and visualization)
* Poke at running Ansible continuously
(https://issues.gpii.net/browse/GPII-2261)
<https://issues.gpii.net/browse/GPII-2261%29>
*_Agenda:_*
* *Update on MatchMaker to Simon Bates and Steve Githens*
o https://pad.gpii.net/p/201612-washington-f2f-effectology-mockup-1z1h4n35
* *Source code line length* (let's keep the discussion short :)) like
80 characters short? HA I got this hot new computer with a nice 80
character display:
https://upload.wikimedia.org/wikipedia/commons/thumb/7/71/IBM_3277_Display.jpg/1280px-IBM_3277_Display.jpg
(Ale is jealous of the keyboard) That keyboard is nice and clean but
those arrow keys are giving me a migraine already."keep sessions as
short as possible" - Do they sold that keyboard?
o GitHub 'Unified' diff view is 980px, for me this works out to ~
120 chars +1 +1 122 now? yeah! or perhaps 123, just
because...Oddly, all the different text colours here in the
comments make me think "painting the bikeshed".
+ This varies depending on browser/platform - but generally
120 chars seems to fit into most/all environments
o DECISION:
+ As a starting point, we will use 120 characters for all
javascript files
+ This will be enforced in eslint
# We will do this in iterations (ie. first modify the
.eslint in infusion and fix things there, then next
repo, etc) rather than doing it with our shared
eslint'ing rules.
+ We will not have any enforced length limit in .json files.
--
Kasper Galschiot Markus
Lead Research Engineer,
Raising the Floor - International,
www.raisingthefloor.org
_______________________________________________
Architecture mailing list
[email protected]
http://lists.gpii.net/mailman/listinfo/architecture
