[Pkg-privacy-maintainers] Moving Go packages to the go team

[Antoine Beaupré]

On 2025-12-13 16:38:40, Simon Josefsson wrote:
> Antoine Beaupré <anarcat at debian.org> writes:
>
>> On 2025-12-13 11:23:30, Simon Josefsson wrote:
>>> Hi again.
>>>
>>> Seeing some support and no opposition to the suggestion below, I have
>>> made an upload of 'golang-goptlib' moving Maintainer to the Go team.
>>>
>>> Could someone grant me 'Maintainer' role for the pkg-privacy-team on
>>> Salsa and I will move the Salsa repo to the Go team too, so it gains the
>>> Go team pipeline checking and some naming consistency.
>>
>> I lost track of who's on the privacy team and who's not, so for now I've
>> just moved the project myself, as I have access to both teams!
>
> Thank you!  I hope to do another upload fixing Vcs-* URLs.
>
>> let me know if you really feel you should be on the team in salsa!
>
> No worries.  Unless there are objections, could you also move the Salsa
> projects for 'golang-siphash-dev', 'obfs4proxy' and 'snowflake' to the
> Go team?  Then I will make an upload of that with the right Vcs-* URL
> from the start.
>
> I think these are all the Go-related packages in pkg-privacy, and I
> think they are better maintained by the Go team, as they often end up
> being involved in Go library transitions.
>
> I'm not familiar with the pkg-privacy team origins, but it seems like a
> small team and I wonder if there is anything substantial that sets it
> apart from the bigger pkg-security team these days.  Winding down
> pkg-auth-maintainers and moving packages to pkg-security felt like the
> right thing.

That SGTM as well.

I don't have time to handle the other transitions right now, but i'm
happy to do so soon.

a.
-- 
Evil exists to glorify the good. Evil is negative good.
It is a relative term. Evil can be transmuted into good.
What is evil to one at one time,
becomes good at another time to somebody else.
                        - Sivananda