ParticipationSystems/TuringDay
Jump to navigation
Jump to search
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
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