[Git][security-tracker-team/security-tracker][master] Clarify LTS tool pointer

[Sylvain Beucler (@beuc)]

Sylvain Beucler pushed to branch master at Debian Security Tracker / security-tracker


Commits:
60471d42 by Sylvain Beucler at 2024-08-01T12:44:20+02:00
Clarify LTS tool pointer

<santiago> thanks for improving the documentation about dla-needed.txt
  with commit 397d4313d893185602fa1d051acb43194b1a5490, but I belive
  this should be part of the freexian paid contributors' documentation

<santiago> I would remove them from dla-needed. LTS is an open
  project, and not everybody has access to the freexian repository nor
  tools

<Beuc> why are you documenting 'freexian available' as the main tool
  to check Xla-needed, and 'find-work' as a "secondary way"? I just
  explained to you that it lacks time-weighing, plus all the changes
  we recently made (lts-do-call-me support, etc.). For all I know
  'freexian available' is left-over code that should be dropped.

- - - - -


1 changed file:

- data/dla-needed.txt


Changes:

=====================================
data/dla-needed.txt
=====================================
@@ -7,20 +7,14 @@ The specific CVE IDs do not need to be listed, they can be gathered in an up-to-
 https://security-tracker.debian.org/tracker/source-package/SOURCEPACKAGE
 when working on an update.
 
-When checking what packages to work on, use:
-$ freexian available
-to list all packages that are not claimed yet, including any important info.
-Then use
-$ freexian claim <packagename>
-to claim this package. The freexian binary is available from [0], it requires
-being part of the freexian gitlab team. The source code is available at [1],
-only available via another team.
-
-The second way to check for packages to work on is:
-$ ./find-work
-from the LTS admin repository [2], available to freexian gitlab team members, to
-sort packages by priority and display important notes about the package (special
-attention, VCS, testing procedures, programming language, etc.).
+A note to Freexian contributors/collaborators: when selecting what
+package to work on first, please use:
+  ./find-work
+  https://freexian.gitlab.io/services/deblts-team/documentation/lts/information-for-lts-contributors.html
+  (private for now)
+to sort packages by priority and display important notes about the
+package (special attention, VCS, testing procedures, programming
+language, maintainers to coordinate with, etc.).
 
 To work on a package, simply add your name behind it. To learn more about how
 this list is updated have a look at
@@ -29,10 +23,6 @@ https://lts-team.pages.debian.net/wiki/Development.html#triage-new-security-issu
 To make it easier to see the entire history of an update, please append notes
 rather than remove/replace existing ones.
 
-[0] https://freexian.gitlab.io/services/deblts-team/documentation/common/pyxian.html
-[1] https://gitlab.com/freexian/code/pyxian/
-[2] https://gitlab.com/freexian/services/deblts-team/debian-lts
-
 NOTE: IMPORTANT: buster->bullseye LTS transition effective 2024-08-15.
 NOTE: IMPORTANT: To work on a bullseye package before that, coordinate with secteam.
 NOTE: IMPORTANT: Last point update planned 2024-08-31 (2 weeks after)



View it on GitLab: https://salsa.debian.org/security-tracker-team/security-tracker/-/commit/60471d4261cc474e36717dae1c76eab537629c39

-- 
View it on GitLab: https://salsa.debian.org/security-tracker-team/security-tracker/-/commit/60471d4261cc474e36717dae1c76eab537629c39
You're receiving this email because of your account on salsa.debian.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/debian-security-tracker-commits/attachments/20240801/b711ad0e/attachment-0001.htm>