Replies: 3 comments
-
|
Got some good feedback about formally assigning people to take lead on certain parts of Electra. We should expand this method to ensure that we have adequate coverage on the codebase and ensuring engineers are developing in topics that peak their interest. Discussing this in a synchronized meeting since async doesn't necessarily ensure we're all on the same page. Some people didn't even indicate their topic interests in this previous document: https://hackmd.io/BCJAtJ_zTq6q4Uz7dbz9qA 😛 Current specialties are easy to identify. It's hard to understand where everybody would like to expand their knowledge in and whether it's done in a way to maximize coverage on specific parts of the codebase. Please think about what areas of development you have a preference in and signal your preference to move in this direction. We can start having a "primary maintainer" for specific areas of the codebase and then encouraging interested devs to become "secondary maintainers" to give coverage and potentially takeover the responsibility sometime in the future. It's also ok to stay put in an area that interests you - no pressure to move around. We just need to ensure adequate coverage in all things to prevent knowledge gaps. Some examples of high level areas of responsibility:
|
Beta Was this translation helpful? Give feedback.
-
|
Please take a look at metrics for |
Beta Was this translation helpful? Give feedback.
-
|
Closing for #6716 |
Beta Was this translation helpful? Give feedback.
-
Meeting Info
Apr 16, 2024, 14:00-15:00 UTC
Zoom: shared on #lodestar-general ChainSafe Discord channel at 14:00 UTC
Agenda
Instructions
Please post here any topics to be added for Standup discussions. Examples of agenda items are issues, discussions, proposals which require feedback, consensus from the team and/or community members.
Beta Was this translation helpful? Give feedback.
All reactions