ParticipationSystems/TuringDay

Turing Day

In late November 2016 the Participation Systems team started a Small Uncontrolled Experiment: Turing Day

We aim to have a Turing day every second Friday. During these days we:

• Sharpen the saw to increase efficiency and reduce maintenance effort
• Hack stuff, fail safely, learn new things, share insights
• Leverage the Internet we build

On Turing Day we try to be as distraction free as possible, so please apologize for delay on email and chat responses.

Inventory of Turing Days

2017-04-017

Session Proposals

• (Nikos) Learn about ReactJS
• (Viorela) Auth0 rules + session information
• (Tasos)
• (Nemo)

2016-11-25

Session Proposals

• (Nemo) Implement OIDC in AWS lambda
• (Nemo) Prometheus time series and logs
• (Yousef, Nemo) FOSDEM infrastructure talk proposal/preparation
• (Tasos) Progressive web apps: add service workers to Moderator
• (Nikos) Bugzilla REST API fun: build a dashboard similar to Bugs Ahoi
• (Viorela, Yousef) Access emails via python for automated testing (reuse for SSL certificates)
• (Henrik) Beautify the TuringDay page
• (Henrik) 1-minute story on why Henrik refers to a particular person's microphone as "Heal the World mike"

What we did/learned/hacked

• (Henrik) Collapsing content on a Wiki page is not trivial. Failed miserably.
• (Henrik) Heal the World --> We Are The World ... Mission completed. Check out the background story to that "microphone laugh".
• (Nikos) Mentored bugs dashboard gets initial shape.
• (Nemo) Learned about AWS Lambda, AWS ALB and how restrictive AWS is :)
• (Nemo) Investigated how we can implement the authentication part of the automated tests (using auth0 API, by parsing emails, by automating the process with AWS Lambda + AWS SES)
• (Viorela) Imaplib (python library) seems to be a good option for accessing and getting email content. I created a python script that was able to access gmail and zoho accounts and get content from emails with different parameters.
• (Tasos) Played around with service workers. First take on caching assets for offline access. Next steps: Full offline access + sync functionality

ROTI

4.8

2016-12-02

Session Proposals

• (Nikos) Finalize Mentored Bugs dashboard UI and push it on Github pages
• (Tasos) Make moderator installable in a mobile device.

2017-01-13

Session Proposals

• (Henrik) Iterate the Google Data Studio ParSys Dashboard
• (Yousef) AWS per-tag billing metrics
• (Yousef) Per-app metrics with linkerd-viz
• (nemo) Try to build a load balancer (how hard could it be)
• (Viorela) Investigate and fix stale element reference exceptions caused by switching to latest Firefox driver version
• (Tasos) Continue work on service workers in moderator app.

What we did/learned/hacked

• (Henrik) Google Data Studio is still cool. Data source debugging sucks (especially if you are trying to identify a PEBCAK typo). The "share without requiring a login" function does not work. Curious to see if we get any feedback on the Discourse post.
  PS: I also put together a quick Equal Rating Innovation Challenge Data Studio report.
• (Viorela) New Firefox driver versions (>48) don't have support for implicit wait checks on click that causes another page load. Github issue were there are discussions regarding this topic: https://github.com/mozilla/geckodriver/issues/308. Bugzilla bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1309231