Hi Fabio, Quoting Fabio Fantoni (2024-08-02 14:31:04) > One particular thing noticed in some cases (and I hope they are not > many) is the lack of use or especially updates of the Vcs-* fields in > d/control. I think is important point to packaging repository from the > tracker if present and to update it if moved, this can help > collaboration and reduce possible waste of time doing things that are > perhaps already done by others (or WIP) but which have not yet been > uploaded.
That's tracked as OLD key at https://qa.debian.org/cgi-bin/vcswatch - also included in the Maintainer Dashboard for each package at https://udd.debian.org/dmd.cgi Whenever you stumble upon a package misaligned with its declared Vcs metadata, please file a bugreport, and while doing so consider encouraging the maintainer to use the Maintainer Dashboard. > I think that both email and systems like salsa/github/gitlab etc. are > useful, both with pros and cons. Forcing people to use only one or the > other could be counterproductive at the moment. One thing that I think > would be useful is to have certain, fast and simple information for each > package about which actual collaboration methods it uses and prefers. > > For example seeing a package it would be very useful to know immediately > if it wants a collaboration only through bugtracker and patch, only > through vcs or both are accepted. If managed in a team point more easily > to information about the team and any pages with details (for example on > wiki). I guess that you mean something like this: ```patch --- a/debian/control +++ b/debian/control @@ -60,6 +60,7 @@ Standards-Version: 4.7.0 Homepage: https://github.com/oxigraph/oxigraph Vcs-Git: https://salsa.debian.org/debian/oxigraph.git Vcs-Browser: https://salsa.debian.org/debian/oxigraph +Contact: https://bugs.debian.org/oxigraph Rules-Requires-Root: no Package: oxigraph ``` In principle I find that an interesting suggestion, as I can imagine such information being helpful in understanding if debbugs is used only by "dinosaurs". I see two problems, however: a) Maintainers will be bothered to add that new field to every package (or at least a substantial subset) for it to be of practical use. b) Which other answers exist for that field? I mean, is it ok in Debian for a maintainer to not use Debbugs? Is it ok in Debian for a maintainer to also use another issue tracker and not replicate whatever is collected elsewhere in Debbugs? Or perhaps I am missing the point of your suggestion, and you do not mean where *bug* chatter goes, but instead where *non-bug* conversations go. If that is the case, then I believe we have a field already for that, called "Maintainer:". If you mean neither issue tracking nor the main contact information for a package, then please elaborate what you had in mind, because that's pretty essential to get clarified before discussing any further... > Another thing that seems underestimated and I think it is good to > emphasize is the excessive slowness of the wiki.debian.org, it seems > much worse than salsa to me, and I think it's important to solve. I don't think that the speed of wiki affects the use of Salsa. Please stick to the topic - i.e. if you want to shift to another topic then do so explicitly by changing the Subject: line in your email post. > If someone thinks that these speed/reachabilityare not important because > they are used to even longer times for many operations, for example > regarding the bugtracker, tracker, upload etc., unfortunately we live in > an increasingly frenetic and continuously worsening world (this world > causes more and more stress and less and less time available). If you mean psychological stress, then I find your reasoning flawed, as that is about a *perceived* lack of time (or other pressure), not necessarily actual lack of it. Possibly but not necessarily. If you mean stress on the Earth, then I find it highly unlikely that we can solve that crisis by speeding things up. Instead we need to find ways to *reduce* the *amount* of computing we do, and find ways to time that computing in ways that fit more optimally with the availability of needed resources (e.g. consume less electricity when there is less wind and sunny, to reduce stress on green parts of related electricity grid). Please elaborate what kind of stress you are really talking about, and again please consider the topic of the conversation (see above about changing Subject: line). Thanks for your inspiring input, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: signature
