> The https://go-team.pages.debian.net/ pages may have some flaws, but one > key social function is that it establishes the group as a team effort. > That goal is something to take after. I'm trying migrate my
+1 > pkg-auth-maintainers packages to pkg-security just because > https://wiki.debian.org/Teams/pkg-security establish the same social > function, that we never managed to create within pkg-auth-maintainers. > > I'm now learning Python team conventions -- > https://wiki.debian.org/Python/LibraryStyleGuide -- too, and find > similar elements. > > These policies are mutually incompatible and each is opinonated about > its own technical choices, but I find adapting to a set of consistency > rules helps collaborative work, regardless of what those technical > choices are. I am active both in the Python and Go teams, and both teams work relatively well and efficiently thanks to having certain minimum common denominator in the packaging workflows. While preparing DEP-18 I reviewed all packaging team policies I could find, and the majority seems to be converging on using git, hosted on salsa.debian.org, built with with git-buildpackage, most of the time also using pristine-tar, and branches and tags following DEP-14. Many also advocate using gbp pq instead of quilt. The Go and Python teams have all these in common, although they adopted DEP-14 at a different time, so one ended up using `debian/master`[1] and the other `debian/sid`[2] as the branch, which in DEP-14 nowadays should be called `debian/latest`[3]. The places these teams diverge I think are *not* actually intentional design decisions, but just a function of when the team had momentum to renew and agree on workflows. Hopefully these discussions will lead to elevated interest and agreement among DDs that we should project-wide a recommended base workflow, and support teams to each update their workflows at the same time to have the same generation of advice in their docs. [1] https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst#id5 [2] https://go-team.pages.debian.net/workflow-changes.html#wf-2017-11-dep14 [3] https://github.com/Debian/dh-make-golang/pull/225
