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

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

Cleaning up the Salsa DPT landing page

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

Contents

  Cleaning up the Salsa DPT landing page Louis-Philippe Véronneau <pollo@debian.org> - 2022-01-17 18:30 +0100
    Re: Cleaning up the Salsa DPT landing page Scott Kitterman <debian@kitterman.com> - 2022-01-17 18:40 +0100
      Re: Cleaning up the Salsa DPT landing page Louis-Philippe Véronneau <pollo@debian.org> - 2022-01-17 19:10 +0100
        Re: Cleaning up the Salsa DPT landing page Scott Kitterman <debian@kitterman.com> - 2022-01-17 20:10 +0100
          Re: Cleaning up the Salsa DPT landing page Sandro Tosi <morph@debian.org> - 2022-01-17 20:40 +0100
        Re: Cleaning up the Salsa DPT landing page Scott Kitterman <sklist@kitterman.com> - 2022-01-17 20:20 +0100

#13882 — Cleaning up the Salsa DPT landing page

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

Hey folks,

The merger between the DPMT and the PAPT into a single entity has been
pretty successful IMO and I think it's time to cleanup the Salsa DPT
landing page.

Looking at https://salsa.debian.org/python-team, I would propose the
following:

1. Delete the empty DPMT sub-group at
https://salsa.debian.org/python-team/modules

2. Delete the empty PAPT sub-group at
https://salsa.debian.org/python-team/applications

3. In the 'tools' sub-group, rename the 'python-modules' sub-sub-group
to 'policy' and delete everything that is not the 'policy.rst' file, as
people now use the 'packages' sub-sub-group for tracking purposes
https://salsa.debian.org/python-team/tools/python-modules

4. Delete the legacy 'python-apps' sub-sub-group
https://salsa.debian.org/python-team/tools/python-apps

Happy to hear what others think of this. I don't have the permissions to
enact this anyway, so if we reach consensus, and admin will have to make
the actual changes :)

Cheers,

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   pollo@debian.org / veronneau.org
  ⠈⠳⣄

[toc] | [next] | [standalone]

#13883

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

On Monday, January 17, 2022 12:20:59 PM EST Louis-Philippe Véronneau wrote:
> Hey folks,
> 
> The merger between the DPMT and the PAPT into a single entity has been
> pretty successful IMO and I think it's time to cleanup the Salsa DPT
> landing page.
> 
> Looking at https://salsa.debian.org/python-team, I would propose the
> following:
> 
> 1. Delete the empty DPMT sub-group at
> https://salsa.debian.org/python-team/modules
> 
> 2. Delete the empty PAPT sub-group at
> https://salsa.debian.org/python-team/applications

I don't have an opinion on #3 and #4.

Might it be better to leave these with a description that explains where they 
went?  There's lots of things that refer to DPMT/PAPT and I don't think all 
the packages have been uploaded with the correct Vcs-* data yet.  It doesn't 
hurt to leave them there and if they explain where to look instead, I think 
the chances of someone being confused later are reduced.

Scott K

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

#13885

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

On 2022-01-17 12 h 31, Scott Kitterman wrote:
> On Monday, January 17, 2022 12:20:59 PM EST Louis-Philippe Véronneau wrote:
>> Hey folks,
>>
>> The merger between the DPMT and the PAPT into a single entity has been
>> pretty successful IMO and I think it's time to cleanup the Salsa DPT
>> landing page.
>>
>> Looking at https://salsa.debian.org/python-team, I would propose the
>> following:
>>
>> 1. Delete the empty DPMT sub-group at
>> https://salsa.debian.org/python-team/modules
>>
>> 2. Delete the empty PAPT sub-group at
>> https://salsa.debian.org/python-team/applications
> 
> I don't have an opinion on #3 and #4.

I mostly care about #3 in #4 :P

> Might it be better to leave these with a description that explains where they 
> went?  There's lots of things that refer to DPMT/PAPT and I don't think all 
> the packages have been uploaded with the correct Vcs-* data yet.  It doesn't 
> hurt to leave them there and if they explain where to look instead, I think 
> the chances of someone being confused later are reduced.

The following lintian tags flag packages using the old Vcs-* data:

https://lintian.debian.org/tags/old-papt-vcs (11 packages)
https://lintian.debian.org/tags/old-dpmt-vcs (431 packages)

Those packages have been fixed in git though, as Ondřej ran a script to
fix all of them a while ago already.

Someone correct me if I'm wrong, but I don't think keeping empty dirs
does anything to the Salsa redirects though.

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   pollo@debian.org / veronneau.org
  ⠈⠳⣄

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

#13886

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

On Monday, January 17, 2022 12:59:53 PM EST Louis-Philippe Véronneau wrote:
> On 2022-01-17 12 h 31, Scott Kitterman wrote:
> > On Monday, January 17, 2022 12:20:59 PM EST Louis-Philippe Véronneau 
wrote:
> >> Hey folks,
> >> 
> >> The merger between the DPMT and the PAPT into a single entity has been
> >> pretty successful IMO and I think it's time to cleanup the Salsa DPT
> >> landing page.
> >> 
> >> Looking at https://salsa.debian.org/python-team, I would propose the
> >> following:
> >> 
> >> 1. Delete the empty DPMT sub-group at
> >> https://salsa.debian.org/python-team/modules
> >> 
> >> 2. Delete the empty PAPT sub-group at
> >> https://salsa.debian.org/python-team/applications
> > 
> > I don't have an opinion on #3 and #4.
> 
> I mostly care about #3 in #4 :P
> 
> > Might it be better to leave these with a description that explains where
> > they went?  There's lots of things that refer to DPMT/PAPT and I don't
> > think all the packages have been uploaded with the correct Vcs-* data
> > yet.  It doesn't hurt to leave them there and if they explain where to
> > look instead, I think the chances of someone being confused later are
> > reduced.
> 
> The following lintian tags flag packages using the old Vcs-* data:
> 
> https://lintian.debian.org/tags/old-papt-vcs (11 packages)
> https://lintian.debian.org/tags/old-dpmt-vcs (431 packages)
> 
> Those packages have been fixed in git though, as Ondřej ran a script to
> fix all of them a while ago already.
> 
> Someone correct me if I'm wrong, but I don't think keeping empty dirs
> does anything to the Salsa redirects though.

I don't know, but I wasn't primarily thinking about people working internal to 
Debian (who might look at lintian output).  I was more thinking about users 
(both ours and downstream).  If they apt source <PKG> their debian/control 
will have the obsolete Vcs-Browser information.  I think there should at least 
be a tombstone there for them to understand where the team went.

I think this is much less relevant for #3 and #4 since they are more 
internally focused so some expectation that people will keep up with changes 
is more reasonable.

Scott K

Scott K

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

#13888

> If they apt source <PKG> their debian/control
> will have the obsolete Vcs-Browser information.  I think there should at least
> be a tombstone there for them to understand where the team went.

since we moved these repos within salsa, they are actually being
redirected to the right repo location. I took a random package that
still uses the all address:

https://salsa.debian.org/python-team/modules/webpy

and if i browse it, i get redirected to

https://salsa.debian.org/python-team/packages/webpy

with a window stating:

Project 'python-team/modules/webpy' was moved to
'python-team/packages/webpy'. Please update any links and bookmarks
that may still have the old path.

so it looks like even if downstreams have the old url, it will be
redirected to the right place and modules|apps can be removed

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

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

#13887

On Monday, January 17, 2022 12:59:53 PM EST Louis-Philippe Véronneau wrote:
> On 2022-01-17 12 h 31, Scott Kitterman wrote:
> > On Monday, January 17, 2022 12:20:59 PM EST Louis-Philippe Véronneau 
wrote:
> >> Hey folks,
> >> 
> >> The merger between the DPMT and the PAPT into a single entity has been
> >> pretty successful IMO and I think it's time to cleanup the Salsa DPT
> >> landing page.
> >> 
> >> Looking at https://salsa.debian.org/python-team, I would propose the
> >> following:
> >> 
> >> 1. Delete the empty DPMT sub-group at
> >> https://salsa.debian.org/python-team/modules
> >> 
> >> 2. Delete the empty PAPT sub-group at
> >> https://salsa.debian.org/python-team/applications
> > 
> > I don't have an opinion on #3 and #4.
> 
> I mostly care about #3 in #4 :P
> 
> > Might it be better to leave these with a description that explains where
> > they went?  There's lots of things that refer to DPMT/PAPT and I don't
> > think all the packages have been uploaded with the correct Vcs-* data
> > yet.  It doesn't hurt to leave them there and if they explain where to
> > look instead, I think the chances of someone being confused later are
> > reduced.
> 
> The following lintian tags flag packages using the old Vcs-* data:
> 
> https://lintian.debian.org/tags/old-papt-vcs (11 packages)
> https://lintian.debian.org/tags/old-dpmt-vcs (431 packages)
> 
> Those packages have been fixed in git though, as Ondřej ran a script to
> fix all of them a while ago already.
> 
> Someone correct me if I'm wrong, but I don't think keeping empty dirs
> does anything to the Salsa redirects though.

I don't know, but I wasn't primarily thinking about people working internal to 
Debian (who might look at lintian output).  I was more thinking about users 
(both ours and downstream).  If they apt source <PKG> their debian/control 
will have the obsolete Vcs-Browser information.  I think there should at least 
be a tombstone there for them to understand where the team went.

I think this is much less relevant for #3 and #4 since they are more 
internally focused so some expectation that people will keep up with changes 
is more reasonable.

Scott K

Scott K

[toc] | [prev] | [standalone]

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

csiph-web