View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001568 | Community.cacert.org | misc | public | 2024-10-02 23:21 | 2026-01-18 23:05 |
| Reporter | L10N | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | needs work | Resolution | open | ||
| Platform | Main CAcert Website | OS | N/A | OS Version | stable |
| Summary | 0001568: Add link to community centre to main page | ||||
| Description | At the AGM it was asked to add the link to the community centre to the main page. | ||||
| Tags | community | ||||
|
|
@L10N do you have specific wishes where the community page should be linked? We could put it in a) the Text "For CAcert Community Members" on the start page b) in the page footer c) somewhere in the sidebar menu or a combination of these options. Is there any preference? |
|
|
a) "For CAcert Community Members" looks good for me b) is a good place as well - if there is enough space left. (maybe both places) c) I do not know where in the sidebar would be a good place |
|
|
Do you need any other information or any help? Or is there a place, where I could create a draft (e.g. github)? |
|
|
https://code.cacert.org/cacert/cacert-webdb/src/branch/main/pages/index/0.php is the code for the start page the footer is defined in multiple places that can be found by the following search https://code.cacert.org/cacert/cacert-webdb/search/branch/main?path=includes&q=function+showfooter%28%29&mode=exact same for the sidebar which can be found by https://code.cacert.org/cacert/cacert-webdb/search/branch/main?path=includes&q=pageNav&mode=exact The preferred way of change would be a pull request in https://code.cacert.org/cacert/cacert-webdb/pulls from a branch that addresses all places where the link would make sense. I think just adding a link on the start page would be the quickest/easiest solution. https://code.cacert.org/cacert/cacert-webdb/src/branch/main/CONTRIBUTING.md contains a guide how to contribute these changes. We do not use Github for code deployments, all code that will eventually go into the production systems need to be merged into the main branch of https://code.cacert.org/cacert/cacert-webdb Maybe it would be a good idea to link the CONTRIBUTING.md somewhere visible in the bug tracker. I don't know whether Mantis (the software behind bugs.debian.org) can do this. |
|
|
https://code.cacert.org/cacert/cacert-webdb/pulls/40 adds a link to the footer. I think this is sufficient. @L10N would that pull request fix this bug in your opinion too? |
|
|
@jandd I addressed this issue by making the cacert-webdb changes in 1585 ( incorrectly, since that is listed as a Wiki bug ). How do you want me to correct this? |
|
|
@jandd I see that you have merged all of the outstanding ( except one ) PRs, so my question above, is moot. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-10-02 23:21 | L10N | New Issue | |
| 2024-10-02 23:21 | L10N | Tag Attached: community | |
| 2024-10-02 23:25 | L10N | Relationship added | related to 0001567 |
| 2024-10-03 11:13 | jandd | Assigned To | => jandd |
| 2024-10-03 11:13 | jandd | Status | new => needs feedback |
| 2024-10-03 11:13 | jandd | Note Added: 0006270 | |
| 2024-10-03 21:12 | L10N | Note Added: 0006274 | |
| 2024-10-03 21:12 | L10N | Status | needs feedback => needs work |
| 2026-01-17 21:43 | L10N | Note Added: 0006337 | |
| 2026-01-18 14:50 | jandd | Note Added: 0006343 | |
| 2026-01-18 14:52 | jandd | Assigned To | jandd => |
| 2026-01-18 15:06 | jandd | Note Added: 0006344 | |
| 2026-01-18 23:00 | bdmc | Note Added: 0006345 | |
| 2026-01-18 23:05 | bdmc | Note Added: 0006346 |
