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

[Fred]

PLEASE REMOVE ME FROM ALL LISTS!

I tried to remove myself. It didn't work.

I tried to contact the list admin. I did not get an answer.

I'M GONNA SPAM YOUR LISTS UNTIL YOU REMOVE ME!



On 05.03.24 21:34, Soren Stoutner wrote:

Peter,

That’s a good point.  When I granted the access I actually selected
Maintainer, but for some reason I wrote Developer in the email.

On Tuesday, March 5, 2024 5:44:51 AM MST Peter B wrote:

On 01/03/2024 04:12, Soren Stoutner wrote:

I have created a repository named planner under debian and have granted

you

Developer access.  :)

F.Y.I.   'Developer' access on Salsa does not allow to Manage CI/CD
settings.

If required, 'Maintainer' or 'Owner' is needed to do that.
https://docs.gitlab.com/ee/user/permissions.html

BTDTGTTS,
Peter

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

[Soren Stoutner]

Peter,

That’s a good point.  When I granted the access I actually selected 
Maintainer, but for some reason I wrote Developer in the email.

On Tuesday, March 5, 2024 5:44:51 AM MST Peter B wrote:
> On 01/03/2024 04:12, Soren Stoutner wrote:
> > I have created a repository named planner under debian and have granted 
you
> > Developer access.  :)
> 
> F.Y.I.   'Developer' access on Salsa does not allow to Manage CI/CD
> settings.
> 
> If required, 'Maintainer' or 'Owner' is needed to do that.
> https://docs.gitlab.com/ee/user/permissions.html
> 
> BTDTGTTS,
> Peter


-- 
Soren Stoutner
so...@debian.org

signature.asc
Description: This is a digitally signed message part.

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

[Peter B]

On 01/03/2024 04:12, Soren Stoutner wrote:

I have created a repository named planner under debian and have granted you
Developer access.  :)


F.Y.I.   'Developer' access on Salsa does not allow to Manage CI/CD 
settings.


If required, 'Maintainer' or 'Owner' is needed to do that.
https://docs.gitlab.com/ee/user/permissions.html

BTDTGTTS,
Peter

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

[Soren Stoutner]

On Sunday, March 3, 2024 12:08:00 PM MST Loren M. Lang wrote:
> > 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

Done.

-- 
Soren Stoutner
so...@debian.org

signature.asc
Description: This is a digitally signed message part.

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

[Loren M. Lang]

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
> so...@debian.org



-- 
Loren M. Lang
lor...@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


signature.asc
Description: PGP signature

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

[Soren Stoutner]

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.

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
so...@debian.org

signature.asc
Description: This is a digitally signed message part.

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

[Soren Stoutner]

Generally you should create the repository under the debian namespace unless 
you really don’t want anyone else making any changes to it, even if the 
changes are urgent and you are AFK for some reason.

I have created a repository named planner under debian and have granted you 
Developer access.  :)

On Thursday, February 29, 2024 7:28:59 AM MST Shriram Ravindranathan wrote:
> Dear mentors,
> 
> I'm curious about the guidelines for putting a package under the debian 
> namespace on Salsa . I wasn't able to 
> find much discourse about this online.
> 
> This package didn't have a salsa repository created for it, I am unsure 
> whether I should create a repository under my own namespace or if the 
> package should be placed under the debian namespace.
> 
> Thank you,
> 
> -- 
> Shriram Ravindranathan
> 


-- 
Soren Stoutner
so...@debian.org

signature.asc
Description: This is a digitally signed message part.

Bug#1065078: Question about the debian group on Salsa

[Shriram Ravindranathan]

Dear mentors,

I'm curious about the guidelines for putting a package under the debian 
namespace on Salsa . I wasn't able to 
find much discourse about this online.


This package didn't have a salsa repository created for it, I am unsure 
whether I should create a repository under my own namespace or if the 
package should be placed under the debian namespace.


Thank you,

--
Shriram Ravindranathan



OpenPGP_0xFC7E951A7BEF0836.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature