Thai sounds an odd move to me.
If this is logically a subteam of the science team, why not use a subteam
in the science team?...

Also, if people are giving you power permission for your new account, just
ask them to correct the permissions?  Surely it's an overlook as they
didn't check the previous status...
And if you need higher permissions to do something somewhere, just ask if
somebody could grant you new rights?

I read your mail as a random rant on how evil and stingy is the world,
which I don't think it's a useful thought to have...


On Fri, 31 Aug 2018, 8:28 a.m. Mo Zhou, <[email protected]> wrote:

> I need the FULL permission on all the deep learning related packages
> maintained by myself,


Incidentally, you may want to be more precise in what you mean by "FULL"
here.  Even if you are a "maintainer" and not an owner the only thing that
you would lack is the ability to delete and rename the projects, which is
not too much IMHO.  So I'd find it useful if you describe what rights you
lack now that is hindering your work.

at the same time I don't bother to create
> another team mail address because the team will be very tiny or even
> only myself.
>
> In many Salsa teams my new DD account permission is lower than my DM
> account (with -guest postfix) such that I've quickly lost my interest
> and patience to do the boring account migration (lumin-guest -> lumin).
>
> As a result, I created a new namespace [1] for "Debian Deep Learning
> Team" and assigned all my accounts as the Owner role. This team is not
> an independent team but logically a subteam of the Debian Science team.
> I'll maintain all my future deep leanring packages in this subteam.
>
> So the last thing I need to confirm with the science team is:
> May I use science team's mail address for this subteam? i.e.
>
> > Maintainer: Debian Deep Learning Team <
> [email protected]>
> > Vcs-*: https://salsa.debian.org/deeplearning-team/*
>
> P.S. the subteam inherits science team's poicy.
>
> [1] https://salsa.debian.org/deeplearning-team
>
>

Reply via email to