💠 Background

Klaudiusz has shared that his availability for JSG from 3rd of October (today) will be reduced and expressed the intention of moving to a part-time working schedule, for circa 20 hours per week. JSG is committed to offering the flexible working schedule for the service providers, and support such cases in circumstances deemed favourable for the overall business operations. On that basis, JSG executive team has made a decision to support Klaudiusz in this transition.

Following a consultation with Klaudiusz, the new schedule, working the first half of the week (Monday, Tuesday and first half of Wednesday) will be adopted for the foreseeable future. As part of this change, there will be a significant impact on the current operations, as he has a set of key technical of operational responsibilities which are not shared by other members of the team. I will be working on handling this change and during the transition time we need to ensure that impact on the overall operations is minimised.

💠 Goal

1️⃣ Empower: Give greater autonomy and ownership of large pieces of Atlas product and infrastructure to remainder of the team, to increase overall productivity, quality of work and initiative.

2️⃣ De-risk: There is a risk that the rest of the engineering team and project overall is left with large technical and operational blind spots during his absences, which will inevitably impact our ability to maintain the current velocity of product development and speed of decision making.

3️⃣ Unblock: With reduced working hours, he will have less time to serve tasks which enable other team members: Atlas dev team, Design Team, Query Node and marketing website developers.

💠 Proposal

Here is the attempt to summarise the changes which are believed to achieve the described goals within the constraints we have.

PR Reviews

Everyone in the Atlas dev team will receive write access, effectively having maintainer status, and reviewers can and should autonomously merge PRs they believe are completed.

Klaudiusz will provide a reviewer guideline which outlines best practices for what a reviewer should keep in mind before merging.

Whenever a mistake occurs in production, effort will be made to back track to original review process to ensure best practices are being followed, and understand how we possibly are falling short in systematic ways.

Maintaining Playgrounds

Every developer on the Atlas team will receive maintainer access to the playground, so they have the ability to redeploy QN, debug infra failures, etc.

Designs

Everyone on the Atlas team does design reviews specifically in order to provide feedback on how upcoming designs may need to be adjusted or changed to respect certain technical constraints imposed by infrastructure they are responsible for.

When required anyone should participate in ad-hoc calls to explain technical feasibility or constraints to design team. This would be done on the basis of proximity to the context of the issue in question.

@Dima is specifically responsible for doing copy editing.

Query Node

@bartosz, with support from Klaudiusz, will transition into the role of QN technical owner for Atlas stream and have primary responsibility for:- writing schemas+mappings