TLDR

Week 2 update, combined with week 1, as I didn't share it yet (due to that, I could not work as much on week 1 and had to push the work from week 1 to week 2):
I'm working on setting up the deb repository for ethereum related nodes/toolchains

• I have been working on setting up the nodes locally with scripts I'm writing and seeing how the various components would work through the package manager when deb packages are used instead of binaries. I will share the scripts repo when it is usable for other platforms and contains enough configuration options for usability; right now, it's nothing more than an implementation done for understanding.
• I have been collecting questions as I still familiarized myself with the process. And now, I have a good grasp of the different elements this project will entail.
• I have created a skeleton of the project tasks I will work on in the following months. Though, this might change at this point.

Tasks I'm doing

• Familiarize myself with Debian-based distros and especially the Linux toolchain
• Set up local nodes that provide binaries, and see how the process works for each consensus and execution client and the requirements of each client. I have created a bash repo, which will ease the installs of such nodes. I will provide the repo in week 3 or week 4. For now, you can ask me for the zip version of it in case of questions.
• Start writing proposal skeleton based on the already existing proposal and based on my understanding of what such project would involve.

Current high-level overview of the plan for the following the months

1. Set up the process of how Debian-based packages should be deployed, which later on could be extended for other platforms (rpm, mac, etc). The process here entails how the teams can integrate their deb releases into one main repo and how the releases should work (automation/manual, push/pull model).
2. To provide a tool that eases the node setups via simple installation. The challenges lie in configuration nuances with various clients and configuration best practices. Some clients offer, and others do not. (various configuration are scattered online). This part the core the part to make running nodes easy, secure, and with best practices. (Note: I might not be able to provide the secure part right away, or own my own, but the project should still aim for it as this will be a community project in the end)
3. Providing additional non-node-related tools in this repo and ensuring seamless integration.