Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Codespell report for "libzypp" (on fossies.org) #343

Open
jschleus opened this issue Sep 7, 2021 · 0 comments
Open

Codespell report for "libzypp" (on fossies.org) #343

jschleus opened this issue Sep 7, 2021 · 0 comments

Comments

@jschleus
Copy link

jschleus commented Sep 7, 2021

A bit nitpicky (especially since most of the found misspellings are only in code comments and thus not visible or relevant to users).

The FOSS server fossies.org offers among others a feature named "Source code misspelling reports". Such reports are normally only generated on request, but as Fossies administrator I have created for testing purposes such a codespell based analysis for the GitHub "master" branch of "libzypp". That continuously updated report is generated within a special restricted "test" folder that isn't really integrated into the standard Fossies services and should also not be accessible to search engines:

 https://fossies.org/linux/test/libzypp-master.tar.gz/codespell.html

That version independent URL hopefully always redirects to the report for the latest "master" version identified by the short GitHub commit ID and a year-month-day string (YYMMDD) representing the according git pull date (mostly = commit date). The refresh rate is currently half-hourly.

By the way, the context type of the spelling errors and typos are marked by a single character (within the sortable column "T"): The less interesting, probably not user visible ones (in "comments") are greyed, while the probably more interesting ones are black-colored. If JavaScript is enabled all table columns are sortable.

Although after a first review some obviously wrong matches ("False Positives" = FPs) are already filtered out (ignored) please inform me if you find more of them so that I can force a new improved check if applicable.

Just for information there are also three supplemental pages showing some used "codespell" configuration details, all obvious false positives and an misspelling history (log).

OK, spelling corrections certainly have a low priority, but they may also contribute to the overall quality of a software project. So I hope that the report can nevertheless be a little bit useful.

By the way, a similar issue report was created for the related "zypper" project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant