Questions about inconsistencies in the documentation

[Soren Stoutner]

While reading over the documentation I noticed a couple of inconsistencies.

1.
https://salsa.debian.org/python-team/tools/python-modules/blob/master/
policy.rst

"All team members should of course follow the main discussion list:
debian-***@lists.debian.org”

"Team members who have broad interest should subscribe to the mailing list
debian-***@lists.debian.org whereas members who are only interested in some
packages should use the Package Tracking System to follow the packages."

I am already subscribed to the list, so I am not concerned about this
personally. But it seems like we ought to pick one recommendation on this
subject.

2.
https://salsa.debian.org/python-team/tools/python-modules/blob/master/
policy.rst

"debian/master - The Debianized upstream source directory.”

https://wiki.debian.org/Python/GitPackaging

"debian/main (formerly debian/master) - The Debianized upstream source
directory.”

"To prove that all the branches got pushed correctly, in this fresh clone,
checkout the debian/master”

"You will need to push the debian/master branch”

"Set debian-branch value to debian/master in debian/gbp.conf”

"Commit to debian/master branch (use git branch -m master debian/master to
rename the branch).”

"Update .git/config branch debian/master to refer to merge = refs/heads/debian/
master.”

"On Salsa, set the default branch to the new debian/master branch.”

“debian-branch=debian/master”

etc. (there are quite a few other references to debian/master).

I am uncertain whether debian/master or debian/main is recommended.

[Soren Stoutner]

Does anyone have any comments on making the documentation more consistent?

Post by Soren Stoutner
While reading over the documentation I noticed a couple of inconsistencies.
1.
https://salsa.debian.org/python-team/tools/python-modules/blob/master/
policy.rst
"Team members who have broad interest should subscribe to the mailing list
packages should use the Package Tracking System to follow the packages."
I am already subscribed to the list, so I am not concerned about this
personally. But it seems like we ought to pick one recommendation on this
subject.
2.
https://salsa.debian.org/python-team/tools/python-modules/blob/master/
policy.rst
"debian/master - The Debianized upstream source directory.”
https://wiki.debian.org/Python/GitPackaging
"debian/main (formerly debian/master) - The Debianized upstream source
directory.”
"To prove that all the branches got pushed correctly, in this fresh clone,
checkout the debian/master”
"You will need to push the debian/master branch”
"Set debian-branch value to debian/master in debian/gbp.conf”
"Commit to debian/master branch (use git branch -m master debian/master to
rename the branch).”
"Update .git/config branch debian/master to refer to merge =
refs/heads/debian/ master.”
"On Salsa, set the default branch to the new debian/master branch.”
“debian-branch=debian/master”
etc. (there are quite a few other references to debian/master).
I am uncertain whether debian/master or debian/main is recommended.