Path: csiph.com!newsfeed.xs4all.nl!newsfeed8.news.xs4all.nl!bofh.it!news.nic.it!robomod From: Scott Kitterman Newsgroups: linux.debian.maint.python Subject: Re: DPT repositories checks/"violations" report Date: Sat, 27 Nov 2021 10:50:01 +0100 Message-ID: References: X-Original-To: debian-python@lists.debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Sat Nov 27 09:47:10 2021 Old-Return-Path: X-Amavis-Spam-Status: No, score=-7.2 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, LDO_WHITELIST=-5] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate:hard: -5.5 X-Greylist: delayed 488 seconds by postgrey-1.36 at bendel; Sat, 27 Nov 2021 09:46:54 UTC MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Mailing-List: archive/latest/19534 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/318988FB-253F-499D-9B9F-385634035A28@kitterman.com Approved: robomod@news.nic.it Lines: 56 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Sat, 27 Nov 2021 09:38:41 +0000 X-Original-Message-ID: <318988FB-253F-499D-9B9F-385634035A28@kitterman.com> X-Original-References: Xref: csiph.com linux.debian.maint.python:13731 On November 27, 2021 6:01:08 AM UTC, Sandro Tosi wrot= e: >Hello, >while working on something else[1], i noticed how many of the >repositories in the DPT salsa group are in poor shape: > >* missing branches >* changes not pushed to salsa >* general misalignment in configuration/setup/organization >* many other small nuances > >[1] https://github=2Ecom/sandrotosi/debian-python-team-tracker > >That makes it hard to make mass work as in [1], so I thought it would >be interesting to have a tool to evaluate the amount of issues our >repos have, and identify such "violations" so that they can be >addressed=2E > >That information is now available at [2]=2E > >[2] https://github=2Ecom/sandrotosi/dpt-repos-check/blob/main/violations= =2Etxt > >please take the content with caution, as it's still an early, raw >draft (i spot-checked some of the reported issues, but there could be >bugs/issues) and it contains data that can be outdated (see below re >caching); the fact that the report indicates only 43 repos are without >violations is a bit disarming, but i think the tool tries to err on >the side of verbosity and pedantry, with 2 level of violations (ERROR >and WARNING) to mark which ones are the most important that require >immediate attention vs the nice-to-have ones=2E > >The checks are under-documented, although they should be somehow >self-explanatory=2E While the current format is just a text file, I plan >on getting it converted to markdown, although I'm still not sure how >to convey that amount of information effectively=2E > >The report is extremely intensive to generate, as it needs to make 10+ >API calls to salsa=2Ed=2Eo for each repository, and it gets throttled >quite early in the run (i got away in dev by installing a cache, so >that i could test it without hitting salsa every time, but that makes >some info stale); for that reason, and if we decide is valuable to >generate it periodically, i don't expect to be able to run it more >than once a month (maybe once a week? TBD)=2E > >Comments, critics and improvements are welcome=2E I don't think the pypi tarball "issue" should be presumed to be a problem = at all=2E I wasn't paying attention to Debian when that discussion happene= d, but in my experience there was a lot wrong with the idea=2E A properly = constructed sdist is exactly what we want to build a package from=2E That'= s almost never found on GitHub=2E Scott K