Otto Kekäläinen <[email protected]> writes: > Hi, > >> When I started working on Go packages I found this historically >> motivated framing confusing and unhelpful, and this slowed me down. >> Nothing has changed in 2-3 years. > > I am sure everyone shares this pain. I think the biggest problem is > that we are supposedly a team, but we haven't defined what a team > means, how one officially becomes a member or stops being a member, or > how members make joint decisions. Everytime I try to do some change > because people don't vote at all, or don't vote in a unified way, and > there is no way to "count" what the "team" wants, or that there is one > person who comes and reverts all my work two months later stating it > wasn't decided upon in the "correct" way. I also say some suggesting > that decisions can only be made after meeting in person at a Debconf. > Having so many opinions on how to make decisions does not help in > making actual decisions. > > Can we agree on something simple to begin with like what we already > did a couple weeks ago, that for a MR to be accepted in the policy we > need 5x +1 and then the submitter can merge it?
Hopefully yes, although I'm not confident that we'll be able to agree on anything substantial. What I suggest instead is to propose small incremental changes that each can be discussed and is hopefully non-controversial (or it establish a question that needs more discussion). > I suggest you make now the editorial changes you want, and then we see > if you get 5x +1 on it, and if so, you can merge it. It was easier than I thought: the new workflow file did not seem to duplicate content in the first file from what I could tell. It is hard to review, but I did not make any edits of the text other than removing the document heading and locating what I thought was a good place to paste it -- how about this: https://salsa.debian.org/go-team/go-team.pages.debian.net/-/merge_requests/26 /Simon
signature.asc
Description: PGP signature
