Find a way to split maintenance burden

[laurentS]

Issues

• I have checked existing issues and there are no existing ones with the same request.

Feature description

We should find a way to split up the maintenance burden of the repo to keep things manageable.
Based on the archival announcement issue, there are several problems with the code base, one of them being the number of builtins it tracks.

One thought could be to rely on code owners per section, for instance:

• core functionality
• builtins for javascript
• builtings for python
• ...

and enforce a process of PR review by said code owners.

Help

Yes

Implementation help

No response