| Summary: | https://check.mageia.org/ should contain a link to the source code that is used to generate it | ||
|---|---|---|---|
| Product: | Websites | Reporter: | Shlomi Fish <shlomif> |
| Component: | Other | Assignee: | Sysadmin Team <sysadmin-bugs> |
| Status: | NEW --- | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | filip.komar, olav, tmb |
| Version: | trunk | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | https://check.mageia.org/ | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
| Attachments: | Untest patch to add a link to the source repo. | ||
|
Description
Shlomi Fish
2020-03-21 11:34:43 CET
Why would that be "important" ? We are using youri-check CC:
(none) =>
tmb I don't even know where the repo is. But IIRC Pascal contribute some of it. CC:
(none) =>
filip.komar (In reply to Thomas Backlund from comment #1) > Why would that be "important" ? > > We are using youri-check What if it goes down and someone needs to set it up again? The knowledge how to do it should be properly documented and accessible See e.g. http://gitweb.mageia.org/software/build-system/mga-youri-core/tree/lib/Youri/Check I think it makes sense. The one time I wanted to fix a bug it took quite a long time to figure out where the stuff was. CC:
(none) =>
olav Created attachment 11581 [details]
Untest patch to add a link to the source repo.
Ping! Can the patch be reviewed, tested, and applied? |