Bug 269892 - website/content/en/status/report-2023-01-2023-03/ does not exist
Summary: website/content/en/status/report-2023-01-2023-03/ does not exist
Status: Closed FIXED
Alias: None
Product: Documentation
Classification: Unclassified
Component: Website (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: Lorenzo Salvadore
URL: https://lists.freebsd.org/archives/fr...
Keywords:
Depends on:
Blocks:
 
Reported: 2023-03-01 07:24 UTC by Graham Perrin
Modified: 2023-03-14 10:03 UTC (History)
4 users (show)

See Also:
salvadore: maintainer-feedback+


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Graham Perrin freebsd_committer freebsd_triage 2023-03-01 07:24:20 UTC
From this morning's call: 

> … You should put your reports in the directory
> doc/website/content/en/status/report-2023-01-2023-03/ ;
> 
> …

Nonexistent at the time of writing: 

<https://github.com/freebsd/freebsd-doc/tree/main/website/content/en/status/report-2023-01-2023-03/>

<https://reviews.freebsd.org/source/doc/browse/main/website/content/en/status/report-2023-01-2023-03/>
Comment 1 Li-Wen Hsu freebsd_committer freebsd_triage 2023-03-01 07:31:31 UTC
Because there is no report merged yet.
Comment 2 Graham Perrin freebsd_committer freebsd_triage 2023-03-01 07:45:26 UTC
salvadore@ please, is the intention for each submitter to create the folder in their fork?
Comment 3 Li-Wen Hsu freebsd_committer freebsd_triage 2023-03-01 07:53:21 UTC
(In reply to Graham Perrin from comment #2)
Only the first few people need to create that file in their branch. That won't be an issue, and even will not cause any conflict.
Comment 4 Lorenzo Salvadore freebsd_committer freebsd_triage 2023-03-01 10:36:04 UTC
As lwhsu explained, the fact that the directory is missing should not be a problem. However if we believe that this is not very "report submitter"-friendly we can improve it. I had some doubts myself.

Two possible solutions are:

- edit the call for status reports message adding a note about this: "You should put your reports in the directory doc/website/content/en/status/report-2023-01-2023-03/ (create it if does not exist yet)" ;

- create an empty file in the report-2023-01-2023-03. I believe git does not allow to to track empty directories: some content must be put in there. I could touch intro.adoc, which we will write later.
Comment 5 Pau Amma 2023-03-01 10:55:54 UTC
(In reply to Lorenzo Salvadore from comment #4)
Or that placeholder file could be the per-report Makefile.
Comment 6 Lorenzo Salvadore freebsd_committer freebsd_triage 2023-03-01 11:00:07 UTC
(In reply to Pau Amma from comment #5)

That was indeed what we were doing in the now archived GitHub repository. However unfortunately the import into the doc repository comes with some conditions on tools that prevent us from continuing using per-report Makefiles, so this is not an option anymore.
Comment 7 commit-hook freebsd_committer freebsd_triage 2023-03-14 09:55:22 UTC
A commit in branch main references this bug:

URL: https://cgit.FreeBSD.org/doc/commit/?id=d4c1222325530ac30ff11db5fd97085137963f26

commit d4c1222325530ac30ff11db5fd97085137963f26
Author:     Lorenzo Salvadore <salvadore@FreeBSD.org>
AuthorDate: 2023-03-14 09:49:02 +0000
Commit:     Lorenzo Salvadore <salvadore@FreeBSD.org>
CommitDate: 2023-03-14 09:54:51 +0000

    Status reports: Improve call for reports email

    Specify that if the directory where it is asked to put status reports
    does not exist yet, then it should be created, as it is already done in
    https://docs.freebsd.org/en/articles/freebsd-status-report-process/#_submit_your_report

    PR:             269892
    Reported by:    grahamperrin
    Approved by:    debdrup (status blanket)

 tools/sendcalls/call.txt.template | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)