Thanks Nilesh and Simon for the feedback here, and thanks Maytham and Taavi for posting feedback on the MR!
> About the "Give and get reviews" in your MR: to clarify, that is, in no way, > mandatory right? > I guess that from work "should" instead of "must". The MR text says: "Reviews are recommended as per long-standing Go team principles. Reviews are however not mandatory. Go team members should should feel they want to submit.." My intent was to make a strong recommendation, but not force it. Think "culture" and not "law". This aligned with the current stated team goal. > I personally would not do it. ENOTIME. Would like to take care of my packages > and team > packages as I find time. The page https://go-team.pages.debian.net/ already states "Our goal is that every package is team-maintained and changes are reviewed by at least one other person, in order to keep the standards high." Seems you think code reviews are a time waste? I would argue that while they initially slow down work by introducing pauses where you need to stop work and wait for feedback, in the long run they help us achieve more with less effort. You catch issues earlier and avoid extra work that you might have otherwise, and the collaboration helps grow the team and new contributors and thus there are less packages you have to worry about personally. In believe that things become what you make of them - so single-maintainer work patterns create more single-maintainer work, while collaboration invites more collaboration.
