[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#1065078: Question about the debian group on Salsa



On Sun, Mar 03, 2024 at 12:02:36AM -0700, Soren Stoutner wrote:
> Loren,
> 
> Yes, I would say that is generally correct.  If you have a package that is 
> team maintained, it is best under the team namespace.  If it is not team 
> maintained, it is generally best under the debian namespace (which is the team 
> of all Debian Developers).  It makes it easier for others to pick up if 
> something happens to you.
> 
> However, there may be specific cases where you do want to keep it in your own 
> namespace.  I maintain one package where I am also the upstream developer.  I 
> keep the Debian packaging in my own namespace because I want to have a very 
> high threshold for other people making changes to it.  At this stage, if 
> something were to happen to me, both the Debian package and the upstream 
> project would need to be adopted by someone else, which would probably 
> necessitate a renaming of the project.  Down the road, I would like to get 
> more people involved in both the upstream development and the Debian 
> packaging.  When that happens I will probably move the Salsa project to a team 
> namespace.
> 
> There is certainly nothing wrong with keeping your project under your own 
> namespace, but if you would like to move it to the debian namespace, grant me 
> full access to it (my Salsa username is soren) and I can then move it to the 
> debian namespace and grant you full access to the project there.

Thanks! I've granted you full access to

https://salsa.debian.org/penguin359/tiv

-Loren

> 
> Soren
> 
> On Saturday, March 2, 2024 11:34:14 PM MST Loren M. Lang wrote:
> > On Sat, Mar 02, 2024 at 01:11:46AM +0100, Salvo Tomaselli wrote:
> > > In data venerdì 1 marzo 2024 05:12:51 CET, Soren Stoutner ha scritto:
> > > > Generally you should create the repository under the debian namespace
> > > 
> > > You need to ask a DD to do that. Non DD don't have permissions for this.
> > 
> > So is having all packages (at least those not maintained by a team)
> > under the debian/ namespace considered a best practice for all but the
> > most sensitive of packages? Should I actually have my own package
> > transfered to this namespace?
> > 
> > I just have a small, CLI package that I maintain alone and, since I
> > don't have DD permissions, just assumed that I should put it under my
> > own namespace. Is it recommended to just keep it under the neutral
> > debian namespace just in case I am no longer able to keep it maintained
> > in the future?
> > 
> > My current package is https://salsa.debian.org/penguin359/tiv
> > 
> > -Loren
> 
> -- 
> Soren Stoutner
> soren@debian.org



-- 
Loren M. Lang
lorenl@north-winds.org
http://www.north-winds.org/


Public Key: http://www.north-winds.org/lorenl_pubkey.asc
Fingerprint: 7896 E099 9FC7 9F6C E0ED  E103 222D F356 A57A 98FA

Attachment: signature.asc
Description: PGP signature


Reply to: