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

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

OK to create a new package in "python-team/packages/"

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

Contents

  OK to create a new package in "python-team/packages/" c.buhtz@posteo.jp - 2024-03-15 08:40 +0100
    Re: OK to create a new package in "python-team/packages/" Carsten Schoenert <c.schoenert@t-online.de> - 2024-03-15 08:50 +0100
      Re: OK to create a new package in "python-team/packages/" Nicholas D Steeves <sten@debian.org> - 2024-03-16 01:20 +0100
        Re: OK to create a new package in "python-team/packages/" <c.buhtz@posteo.jp> - 2024-03-16 13:30 +0100
    Re: OK to create a new package in "python-team/packages/" Stefano Rivera <stefanor@debian.org> - 2024-04-06 09:50 +0200
      Re: OK to create a new package in "python-team/packages/" c.buhtz@posteo.jp - 2024-04-06 09:52 +0200

#15565 — OK to create a new package in "python-team/packages/"

Hi,
for practicing packaging I start again with the docu and stumbled across 
this paragraph:

     
<https://wiki.debian.org/Python/GitPackaging#Creating_new_repositories>

It tells me to create a package in "python-team/packages/". I ask myself 
if I am allowed to and if it is a "good" idea?
Technically I am allowed. And formally also because I am an formally 
accepted member of the DPT. But I wouldn't call me an active member 
despite asking dump questions and wining about the docu. ;)

On the long run it is my goal to make the package [1] ready for official 
upload. But I suspect this is a long way. So on short view that repo 
will be for practicing only. Am I allowed to create such a repo in my 
position?

Kind
Christian

[1] -- <https://codeberg.org/buhtz/hyperorg>

[toc] | [next] | [standalone]

#15566

Am 15.03.24 um 08:31 schrieb c.buhtz@posteo.jp:

> On the long run it is my goal to make the package [1] ready for official
> upload. But I suspect this is a long way. So on short view that repo
> will be for practicing only. Am I allowed to create such a repo in my
> position?

There is no need to start any packaging work within the Salsa group of 
the DPT. You can start any work within your namespace and move the 
package to any other group later if needed and appropriate.

And within your namespace you can e.g. do force pushing if you feel you 
need to, within team space that's a no go.

-- 
Regards
Carsten

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

#15599

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

Carsten Schoenert <c.schoenert@t-online.de> writes:

> Am 15.03.24 um 08:31 schrieb c.buhtz@posteo.jp:
>
>> On the long run it is my goal to make the package [1] ready for official
>> upload. But I suspect this is a long way. So on short view that repo
>> will be for practicing only. Am I allowed to create such a repo in my
>> position?

Christian, have you filed an ITP (intent to package) yet?  If not,
please do so as soon as you can.

  https://wiki.debian.org/ITP

> There is no need to start any packaging work within the Salsa group of 
> the DPT. You can start any work within your namespace and move the 
> package to any other group later if needed and appropriate.
>
> And within your namespace you can e.g. do force pushing if you feel you 
> need to, within team space that's a no go.
>

+1 Carsten, that's my recommendation too, same rationale, and I'd add
that starting a project in personal namespace is zero risk.

  1. You have a remote backup of your work.
  2. You can do whatever you want with it (ie make branches and/or tags
  of experiments that may or may not work out, squash, rebase, force
  push--as noted--etc.)
  3. So it's lower stress and builds confidence faster than working
  directly in a team-managed namespace imho.
  4. Moving the repo during the sponsorship procedure can be a
  reassuring milestone.
  5. Doing Debian development "in the open" is sometimes an
  uncomfortable adjustment, and staging work in personal namespace is a
  more gentle path.

Regards,
Nicholas

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

#15601

Dear Nicholas,

thanks for the reply.

On 2024-03-15 20:13 Nicholas D Steeves <sten@debian.org> wrote:
> Christian, have you filed an ITP (intent to package) yet?  If not,
> please do so as soon as you can.
> 
>   https://wiki.debian.org/ITP

No I have not because it is to much pressure. I am testing and playing
around and doing research about the packaging process. After this I can
decided if I am able doing this and then fill an ITP.

Kind
Christian Buhtz

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

#15705

Hi c.buhtz (2024.03.15_07:31:22_+0000)
> On the long run it is my goal to make the package [1] ready for official
> upload. But I suspect this is a long way. So on short view that repo will be
> for practicing only. Am I allowed to create such a repo in my position?

I don't have a problem with staging an ITP in progress in the git repos.

If you do create a repo and then never upload the package, please
delete/archive the repo when you're done.

Personally, I usually get the package ready to upload before creating a
git repo in the team. I want to be sure that it's something maintainable
that I want to take on, before I commit to it.

The advice for doing it in your own salsa profile seems sensible. For a
complex package that you aren't sure about adding to the team, that
could make sense.

Stefano

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

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

#15740

Dear Stefano,

thanks for the advice.

Am 03.04.2024 16:48 schrieb Stefano Rivera:
> If you do create a repo and then never upload the package, please
> delete/archive the repo when you're done.

Done.

> Personally, I usually get the package ready to upload before creating a
> git repo in the team.

I believe you. But the Wiki states otherwise. There creating the salsa 
repo is the first step.

Kind
Christian

[toc] | [prev] | [standalone]

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

csiph-web