Ludovic Courtès <l...@gnu.org> writes: > Hi Chris, > > Christopher Baines <m...@cbaines.net> skribis: > >> Regarding this change specifically though, I'm unclear how it would >> impact the things I push for others. I pushed some patches today, would >> this mean that I'd have to look at what team/teams are involved >> (according to /etc/teams.scm.in) for each commit/series, and then either >> continue if I'm a member of that team, or skip it if I'm not? >> >> If I'm going to not be pushing stuff I would have previously pushed >> because I'm not in the relevant teams, maybe I should just add myself to >> every team? I guess this is not a serious question, but I'm more making >> the point that if teams become a formal part of patch review, then some >> formalities over membership of a team is probably a prerequsite. >> > [...] > > Good questions. > > For teams like ‘core’ or ‘home’, there should be no overlap, so it’s > quite easy to see who’s in charge. > [...] > For “random packages”, I’m fine with the status quo.
Hello, I'd like to know if I'm working fine according to the status quo.. I usually push patches for others who don't have commit access, while most packages don't have a team at all, and some with me as the only team member. Should I wait for another commiter's approvol under this new policy or can I push "random packages" (eg: jwm) solo under the status quo? For packages I as the only team member (eg: fcitx), should I looking for another commiter for other's patches and my patches? Thank you!