Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.python > #13021 > unrolled thread

Joining the team

Back to article view | Back to linux.debian.maint.python

Contents

  Joining the team nicoo <nicoo@debian.org> - 2020-11-23 14:20 +0100
    Re: Joining the team Thomas Goirand <zigo@debian.org> - 2020-11-23 22:10 +0100
      Re: Joining the team Sandro Tosi <morph@debian.org> - 2020-11-23 22:20 +0100
        Re: Joining the team Thomas Goirand <zigo@debian.org> - 2020-11-24 01:00 +0100
          Re: Joining the team Sandro Tosi <morph@debian.org> - 2020-11-24 01:40 +0100
          Re: Joining the team Brian May <bam@debian.org> - 2020-11-24 22:30 +0100
    Re: Joining the team Ondrej Novy <novy@ondrej.org> - 2020-11-30 12:50 +0100
      Re: Joining the team nicoo <nicoo@debian.org> - 2021-01-31 18:00 +0100
        Re: Joining the team Stefano Rivera <stefanor@debian.org> - 2021-01-31 19:20 +0100
          Re: Joining the team nicoo <nicoo@debian.org> - 2021-01-31 21:40 +0100
            Re: Joining the team Louis-Philippe Véronneau <pollo@debian.org> - 2021-01-31 22:50 +0100
              Re: Joining the team Stefano Rivera <stefanor@debian.org> - 2021-01-31 23:30 +0100
            Re: Joining the team Sandro Tosi <morph@debian.org> - 2021-02-01 00:40 +0100
              Re: Joining the team nicoo <nicoo@debian.org> - 2021-02-02 10:10 +0100
        Re: Joining the team nicoo <nicoo@debian.org> - 2021-02-01 01:20 +0100

#13021 — Joining the team

[Multipart message — attachments visible in raw view] — view raw

Hi everyone!

First, an apology: it seems I misremembered being in the team, and uploaded to
NEW a bunch of packages with the team in `Uploaders`.  While I guess that's
technically valid (I'm fine with the Python team uploading to them), I am not
exactly comfortable with having done so without being a team member or clearing
it first with you all.

I... guess that's what I get for packaging and dput-ing when sleep deprived >_>'
(I was trying to deal with insomnia by packaging a new tool, multiplex.)

Anyhow, sorry about that, I will fix it with the next source upload if you
do not with for those modules to be in the Python team.


Second, I would like to join the team  ^.^

- I'm maintaining a couple other Python things, which I would be interested in
  maintaining within the team, incl. aiostream, ansicolors, easy-ansi, and
  multiplex, that I packaged last night.

- I'm interested in using click-man to generate the manpages of some of my
  packages, and even opened the RFP bug for it, but there seem to be issues with
  running it during the package build, so I'd be interested in working on that
  too. (Presumably collaborating with Ryan, who packaged it?)

- I'm mentoring my friend Guiness, who expressed interest in adopting a couple
  of modules (currently orphaned) and contributing bugfixes etc. to existing
  packages, so she might want to join the team at some point.

- I already maintain a couple of Python modules and applications inside auth-team,
  which I might keep there, as they are tightly coupled to C libraries which are
  also packaged there.


Please do poke me on IRC (I am nicoo on OFTC, and am in #d-python) as I have
trouble keeping up with all the mailing lists  :)


Best,

  nicoo

[toc] | [next] | [standalone]

#13022

On 11/23/20 2:15 PM, nicoo wrote:
> Hi everyone!
> 
> First, an apology: it seems I misremembered being in the team, and uploaded to
> NEW a bunch of packages with the team in `Uploaders`.

Please put the team as Maintainer, and yourself as Uploaders.

Cheers,

Thomas Goirand (zigo)

[toc] | [prev] | [next] | [standalone]

#13023

> > First, an apology: it seems I misremembered being in the team, and uploaded to
> > NEW a bunch of packages with the team in `Uploaders`.
>
> Please put the team as Maintainer, and yourself as Uploaders.

why? that's not a requirement:
https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst#maintainership

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

[toc] | [prev] | [next] | [standalone]

#13024

On 11/23/20 10:10 PM, Sandro Tosi wrote:
>>> First, an apology: it seems I misremembered being in the team, and uploaded to
>>> NEW a bunch of packages with the team in `Uploaders`.
>>
>> Please put the team as Maintainer, and yourself as Uploaders.
> 
> why? that's not a requirement:
> https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst#maintainership

Because joining a team, putting packages in them, and enforcing strong
ownership, is not logic at all. I know you like to do this way, but this
shouldn't be what we advise for new comers.

Cheers,

Thomas Goirand (zigo)

[toc] | [prev] | [next] | [standalone]

#13025

On Mon, Nov 23, 2020 at 6:50 PM Thomas Goirand <zigo@debian.org> wrote:
>
> On 11/23/20 10:10 PM, Sandro Tosi wrote:
> >>> First, an apology: it seems I misremembered being in the team, and uploaded to
> >>> NEW a bunch of packages with the team in `Uploaders`.
> >>
> >> Please put the team as Maintainer, and yourself as Uploaders.
> >
> > why? that's not a requirement:
> > https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst#maintainership
>
> Because joining a team, putting packages in them, and enforcing strong
> ownership, is not logic at all.

that's your opinion, and the policy disagrees with you. this team
welcomes everyone that is willing to follow our policies and its
rules.

> I know you like to do this way, but this
> shouldn't be what we advise for new comers.

that's also what nicoo prefers, given he chose exactly that way for
maintaining his packages.

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

[toc] | [prev] | [next] | [standalone]

#13026

Thomas Goirand <zigo@debian.org> writes:

> Because joining a team, putting packages in them, and enforcing strong
> ownership, is not logic at all. I know you like to do this way, but this
> shouldn't be what we advise for new comers.

Agreed. In my opinion what the policy allows and what is best practise
are two different things.

If you want strong ownership, you can get that already by not having the
package part of the team. To invite people to do so as part of the
Debian policy just makes the policy more complicated (and confusing)
then it needs to be. And creates needless conflicts within our team.

Depending on what you want, You are also free to follow the packaging
guidelines, policies, etc, even if the package isn't formally part of
the team. You could even join this group
https://wiki.debian.org/LowThresholdNmu and allow others to make changes
to your packages without going through the slow NMU process.
-- 
Brian May <bam@debian.org>

[toc] | [prev] | [next] | [standalone]

#13034

[Multipart message — attachments visible in raw view] — view raw

Hi nicoo,

po 23. 11. 2020 v 14:15 odesílatel nicoo <nicoo@debian.org> napsal:

> First, an apology: it seems I misremembered being in the team, and
> uploaded to
> NEW a bunch of packages with the team in `Uploaders`.  While I guess that's
> technically valid (I'm fine with the Python team uploading to them), I am
> not
> exactly comfortable with having done so without being a team member or
> clearing
> it first with you all.
>

it's up to you to choose if you want to have strong or weak team
maintenance.
If you are fine with the Python team members uploading, use strong -
use team in the Maintainer field.

Second, I would like to join the team  ^.^
>

cool! Please follow our policy:
https://salsa.debian.org/python-team/tools/python-modules/-/blob/master/policy.rst
to join the team.

Thanks.

-- 
Best regards
 Ondřej Nový

[toc] | [prev] | [next] | [standalone]

#13154

[Multipart message — attachments visible in raw view] — view raw

Hi Ondrej!

Sorry for the super-late reply, I've been pretty broken in the last couple
of months, unfortunately. I'm trying to take care of myself, though, and
things seem to be looking up over the last few days :3


On Mon, Nov 30, 2020 at 12:32:04PM +0100, Ondrej Novy wrote:
> it's up to you to choose if you want to have strong or weak team
> maintenance.  If you are fine with the Python team members uploading,
> use strong - use team in the Maintainer field.

Yes, my intent was to go for strong team maintenance (teamwork makes the
dream work!) but my sleep-deprived self thought I was in the team already.


> po 23. 11. 2020 v 14:15 odesílatel nicoo <nicoo@debian.org> napsal:
> > Second, I would like to join the team  ^.^
>
> cool! Please follow our policy:
> https://salsa.debian.org/python-team/tools/python-modules/-/blob/master/policy.rst
> to join the team.

I've read and accepted the policy, my login is nicoo, and I mentionned in
the previous emails my motivation for joining the team.


Best,

  nicoo  <3

[toc] | [prev] | [next] | [standalone]

#13155

Hi nicoo (2021.01.31_16:39:43_+0000)
> > cool! Please follow our policy:
> > https://salsa.debian.org/python-team/tools/python-modules/-/blob/master/policy.rst
> > to join the team.
> 
> I've read and accepted the policy, my login is nicoo, and I mentionned in
> the previous emails my motivation for joining the team.

Added!

Happy package maintenance :)

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

[toc] | [prev] | [next] | [standalone]

#13156

[Multipart message — attachments visible in raw view] — view raw

Hi Stefano,

On Sun, Jan 31, 2021 at 06:19:00PM +0000, Stefano Rivera wrote:
> Hi nicoo (2021.01.31_16:39:43_+0000)
> > > cool! Please follow our policy:
> > > https://salsa.debian.org/python-team/tools/python-modules/-/blob/master/policy.rst
> > > to join the team.
> > 
> > I've read and accepted the policy, my login is nicoo, and I mentionned in
> > the previous emails my motivation for joining the team.
> 
> Added!
> 
> Happy package maintenance :)

Thanks  <3


Speaking of the policy, are there conventions about repository setup,
beyond complying with DEP-14? In particular the CI setup (the usual
pipeline?), whether it's fine to enable branch/tag protection and require
working through MRs, adding webhooks to tag BTS bugs as pending when a fix
is merged, ...


Best,

  nicoo

[toc] | [prev] | [next] | [standalone]

#13157

[Multipart message — attachments visible in raw view] — view raw

On 2021-01-31 15 h 25, nicoo wrote:
> In particular the CI setup (the usual pipeline?)

Nothing on that, since the Salsa Team has asked us not to use CI
systematically because Salsa CI apparently cannot take the load.

> whether it's fine to enable branch/tag protection

Nothing on that either.

> working through MRs

You're free to ask for MRs, no team policy on this.

> adding webhooks to tag BTS bugs as pending when a fix is merged

AFAIK, you don't need to add webhooks for that to work, something (I
don't know what) scans through all new commits on Salsa and checks for
relevant BTS info.

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   pollo@debian.org / veronneau.org
  ⠈⠳⣄

[toc] | [prev] | [next] | [standalone]

#13158

Hi Louis-Philippe (2021.01.31_21:43:48_+0000)
> > whether it's fine to enable branch/tag protection
> 
> Nothing on that either.

When we imported packages we set this up. But haven't automated managing
it on all / new packages, yet. (The tools for automation didn't exist at
the time)

> > adding webhooks to tag BTS bugs as pending when a fix is merged
> 
> AFAIK, you don't need to add webhooks for that to work, something (I
> don't know what) scans through all new commits on Salsa and checks for
> relevant BTS info.

As I understood it, that's the tagpending webhook, which we have set up
on all our repos, at import time.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

[toc] | [prev] | [next] | [standalone]

#13159

> > Added!
> >
> > Happy package maintenance :)
>
> Thanks  <3

please name the project as the source package name, not "Easy Ansi"
https://salsa.debian.org/python-team/packages/easy-ansi; also
src:python-easy-ansi, the python- prefix is not strictly required --
anyhow, the salsa project name should match what source package name
you decide to set. please fix Easy Ansi

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

[toc] | [prev] | [next] | [standalone]

#13161

[Multipart message — attachments visible in raw view] — view raw

On Sun, Jan 31, 2021 at 06:32:14PM -0500, Sandro Tosi wrote:
> > > Added!
> please name the project as the source package name, not "Easy Ansi"

Thanks for the catch; I didn't realise Gitlab was “smart” about turning the
repository's path stub into a project name.

Now fixed.

[toc] | [prev] | [next] | [standalone]

#13160

[Multipart message — attachments visible in raw view] — view raw

On Sun, Jan 31, 2021 at 05:39:49PM +0100, nicoo wrote:
> Yes, my intent was to go for strong team maintenance (teamwork makes the
> dream work!) but my sleep-deprived self thought I was in the team already.

I just noticed I originally did exactly the reverse of what I meant to,
but it will be fixed shortly (merging and uploading tonight or tomorrow)

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.maint.python

csiph-web