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
[email protected]
-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEJKVN2yNUZnlcqOI+wufLJ66wtgMFAmXkIIwACgkQwufLJ66w tgMvJA//WfR/Q2dTwepK4CkKVt/z2zJZMfaTsIuCWH87//0qheO5lFUB+QR+HM+A 9+S8PAss11GOMao4SehJy008ttEXxeK5MOMgl/31xA9oXM3PY1SBnN6XbeL9F5vt O7uVe11Xnu3vMDN74AyehKHEVJNpdmLRhfG7+fcBuOxc0/BmVgIfod86N94OJeGV r0/Pt41e5EzrcRfvGbjnZNiUHb0e/wI3zbGjRXwYCaJ2VEaOtP670f/WqCHUgqTH xgHG5sK+LY/+UUG3TLzkAxUc7RMr1gCjNX4HaurrdCVvFT0IqaCI0bkNy9Lm6BOM esrtoqNZww4z/e3TPuGt0GWv4IFkJ6D+kbeBUu1RlPLqyYjV9bVQUg7W/5BWSmHP YROVIpBlEWzg5DC430j6EhGOPE72WCW9Dq3JYsjkyaPuGX0PavgcucVvigwT7tL8 OUja9UiIMPlmttDgIMW//EJhI7ZWnq+yTFv7q7YXeZ1LGsjDzJ918k9dUfIQ/oQj 1dkYC1Sl6g40kWwBSRL9idCSimQ+kxMhyEfL7TBuQnunTikVj0kWIUnYLkteklat GdMb91uwwTFgyU2vqRf0htOPph79QOvhYmB6ztob69mxO7LpdigqgzIO9QAYn4Nv c19Jcpui4v+mhEDc0KB4R5cDeb149yskGQHdmeqnL8IhFA1828s=
=5iO3
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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
[email protected]

--
Loren M. Lang
[email protected]
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

-----BEGIN PGP SIGNATURE-----

iHUEABEIAB0WIQT3wmbBr9cpdt12HlPMe9wUn2Md1wUCZeTKigAKCRDMe9wUn2Md 18MrAQCXoXShnDePk67G2m906UIDLK2WQUe5PQVYm5CEpBhfvgEAy10fW+p/Otun Q2y4eqzyfPWh0nDYTE68fbJUO8b1/l4=
=gEkk
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Copy: [email protected]

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
[email protected]
-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEJKVN2yNUZnlcqOI+wufLJ66wtgMFAmXmEz0ACgkQwufLJ66w tgPhihAAj8nfxaw+Oq1kekR70cv0py1AP7oRIdLlD6d8/YjM0wePaUWvfcRCWdE5 /ipmOtFrS0vNerOJBykl/e+xN0NBQqEeB3iB6bcIYBJpxsDmd1gr8idglkY6JaBd kQWG9Os2QnCf3hYLhAyaWDjWRR3nJiKm9DoOPHVC5+w2IRUSa8wbXuwhIS0sxjMl XOTZgQ8SdP1lEmZGP7jXPeqd+UPrvRN/CS1thEcLEfMNgPraX6dPYg3VSIgwzFBm jVc2/mkbKWHjMQdlPRaCPzxmMDPdAVjl+P1GzSRm9GHyDPVasLmGp0sN0+4eOy6w 5s++osGTIXna+j5UVUaHdmvNqxHoxWzCPK++S8WS4dXeNidt4ClPErdKwVm1EPwI K8qIsqsaeIwjV8EVPbanZAcmhjzhBIVlcuIfrUPrjeB5mCCVPHS19rqte5OrF5Ep kk42/iszeaVZ/L+KJ/yzvFBKiqrACtx0gCFjO2FCak7CeqfOBzSbR+FEJbixwjuX 6WKISG78+aHroWjanY0tQWiHvRQdusKq++lFbYE6tgSml2UFI+uZYg47R63/FH3C T0Nu3vOPX4XO6VrRWYFbaObso7bLcpBn1/DNe+VrYdQ56cvi6YAOvSgC7WIQj7JX yt9cbDs8ufflbJ1OFh6v6H8Jo0i4fbnJWZqgiqRmt0PpADv9Ub4=
=jadr
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Copy: [email protected]

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
[email protected]
-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEJKVN2yNUZnlcqOI+wufLJ66wtgMFAmXngcoACgkQwufLJ66w tgN9sg//Ymj92d2JOgJO0hoXupZLNPrj+kUM01iRCcRuKpagFXLsJte9/ctmRuH4 RHzw3/qT7yLHZqKhnkhMcQnJHWW1Vaee8VVLjVAL1qOL45d3yg2NwVuQlteOCDhS eOySa0XHTSkodBj0DXozVnd54uB5Z/52ZHC2yZ4Dt4tqHTKj9tzQle6R1kJxLyPO 980Y+MwDj3/lxblb+l02oo4cu73/6lRzx6mAiisZUPJXnV52RqGwuCc4/8Xs8wYv mVHk4IS6vOwl4q/XC9AqbA8NiSUaajbJWPkuT5Wh6/Z3SkCjGmg3ilekqH7o1pbe sgzP3b7yt3HIhgIATrPl7mtL0OdFRYec6VUpEV85D0IkOCQRt2Ya7h9vpsYmZ6m3 P1J9dwEiB5cllVx6EseKwnZLG3pPmrSwZuPnU8neSzwnIxZA3/BnyMmGsutOVYi5 3FYtGqbZlYfv+4oaWaxMQ03K6oPMuuBGRzgidbqJg8RcnffnM0b1wYfcytCAykqR ggjtyJspiZTdjavV6Q04oT6faAg6DJSTq4GSUhVUvLbjkmwdpa8exI7OqoEYDSkJ YD8QzmFg5OcT6rhoN5UT+6NcZKRIftI+2rG1r51dhGNV84+1TxsoRUlhuOPGthug BQlJZYoX1S8q2oFQXJacwy399y0l6OG7BiEg6RxAhzlucW7u4SM=
=RPUe
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)