Changes between Version 222 and Version 223 of WikiStart
- Timestamp:
- Jun 23, 2025, 3:31:15 PM (9 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
WikiStart
v222 v223 79 79 ==== Device Information ==== 80 80 81 If your drive is not in the [source:/smartmontools/src/drivedb.h current version of smartmontools drive database], you can help to improve smartmontools information by [wiki:FAQ#MyATASATAdriveisnotinthesmartctlsmartddatabase sending a report about your drive] to our mailing list [https://listi.jpberlin.de/mailman/listinfo/smartmontools-database smartmontools-database]. 81 If your drive is not in the [source:/src/drivedb.h current version of smartmontools drive database], you can help to add this information. 82 See the [wiki:FAQ#MyATASATAdriveisnotinthesmartctlsmartddatabase FAQ] for details. 82 83 83 84 We collect info about [wiki:Supported_USB-Devices USB devices that have been successfully or unsuccessfully tested with smartmontools]. If you have a device not listed there, please tell us the test result, by editing the wiki page, and/or by sending an email to the [https://listi.jpberlin.de/mailman/listinfo/smartmontools-database smartmontools-database mailinglist]. … … 85 86 ==== Bug Reports ==== 86 87 87 To submit a bug report or propose an enhancement for smartmontools create a [//newticket new ticket here in trac]. Login is needed for that. If you don't want to register an account, you can also send the info to our [https://listi.jpberlin.de/mailman/listinfo/smartmontools-support smartmontools-support] mailing list. 88 To submit a bug report or propose an enhancement, [https://github.com/smartmontools/smartmontools/issues create an issue] at !GitHub. 89 Alternatively [//newticket create a ticket] here in trac. 90 If you don't want to register an account, you can also send the info to our 91 [https://listi.jpberlin.de/mailman/listinfo/smartmontools-support smartmontools-support] mailing list. 88 92 89 93 ==== Patches ==== 90 94 91 Patches are welcome! '''The most convenient way for us is when you attach them to a [//newticket new ticket here in trac]'''. But it's also possible to submit patches for code review to [https://listi.jpberlin.de/mailman/listinfo/smartmontools-devel developers mailing list]. You don't need to be a member of the mailing list for it. Our list moderator will approve posting requests in these cases. Your patches should refer to our recent code base in [wiki:Download#InstalllatestunreleasedcodefromtheGitrepository Git]. You should also have a look at the documents in the [wiki:TocDeveloper developers area here in the wiki]. You will find info about the smartmontools software architecture, tutorials, and guidelines from our developers there. 95 Patches are welcome! 96 '''The most convenient way for us is when you [https://github.com/smartmontools/smartmontools/pulls create a pull request] at !GitHub.''' 97 Alternatively attach the patch to a [//newticket new ticket] here in trac. 92 98 93 99 ==== !GitHub PR-s and Issues 94 100 95 For those who prefer to use git and !GitHub we maintain an [https://github.com/smartmontools/smartmontools/ official mirror] of the smartmontools project. Feel free to fork, submit PRs and issues. Additionally, a GitHub Action CI/CD (Continuous Integration and Deployment) system has been set up; see [https://github.com/smartmontools/smartmontools/blob/main/.github/workflows/build.yml workflow] for details. Every commit to the !GitHub triggers a new build and provides [https://github.com/smartmontools/smartmontools-builds/releases a source tarball and various binaries] as artifacts. 101 The former official R/O mirror at !GitHub is now the [https://github.com/smartmontools/smartmontools/ official upstream repository] of the smartmontools project. 102 Feel free to fork, submit PRs and issues. 103 Please make sure to fork the `main` branch as the `master` branch from former R/O mirroring has been retired. 104 Additionally, a !GitHub Action CI/CD (Continuous Integration and Deployment) system has been set up; see [https://github.com/smartmontools/smartmontools/blob/main/.github/workflows/build.yml workflow] for details. Every commit to the !GitHub triggers a new build and provides [https://github.com/smartmontools/smartmontools-builds/releases a source tarball and various binaries] as artifacts. 96 105 97 106 - !GitHub: ,,[[Image(https://img.shields.io/github/issues/smartmontools/smartmontools?logo=github&label=issues, link=https://github.com/smartmontools/smartmontools/issues, alt="...", title="Open Issues")]] [[Image(https://img.shields.io/github/issues-closed/smartmontools/smartmontools?label=, link=https://github.com/smartmontools/smartmontools/issues?q=is%3Aclosed, alt="...", title="Closed Issues")]] [[Image(https://img.shields.io/github/issues-pr/smartmontools/smartmontools?logo=github&label=pull%20requests, link=https://github.com/smartmontools/smartmontools/pulls, alt="...", title="Open PRs")]] [[Image(https://img.shields.io/github/issues-pr-closed/smartmontools/smartmontools?label=, link=https://github.com/smartmontools/smartmontools/pulls?q=is%3Aclosed, alt="...", title="Closed PRs")]],, 98 107 99 - CodeQL scanning: [[Image( /smartmontools/smartmontools/actions/workflows/codeql.yml/badge.svg, link=https://github.com/smartmontools/smartmontools/security/code-scanning, alt="...", title="CodeQL scanning")]],,108 - CodeQL scanning: [[Image(https://github.com/smartmontools/smartmontools/actions/workflows/codeql.yml/badge.svg, link=https://github.com/smartmontools/smartmontools/security/code-scanning, alt="...", title="CodeQL scanning")]],, 100 109 101 110
