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


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

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

From c.buhtz@posteo.jp
Newsgroups linux.debian.maint.python
Subject OK to create a new package in "python-team/packages/"
Date 2024-03-15 08:40 +0100
Message-ID <Iiaky-gP4S-11@gated-at.bofh.it> (permalink)
Organization linux.* mail to news gateway

Show all headers | View raw


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>

Back to linux.debian.maint.python | Previous | NextNext in thread | Find similar | Unroll thread


Thread

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

csiph-web