Peer Feedback Response to #218: Supervisor's SRS Review Pitfall

Open
#236 0 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@Andreas-Sideris is already working on this.

Since Nov 7, 2026.

Assessment

This issue has not been assessed yet.

Description

documentation Feedback Response Revision

Description of the Feedback

The following feedback was provided:

In lecture, Dr. Smith explicitly mentioned that having a supervisor review an SRS document is a bad idea because it is very lengthy and contains a bunch of technical jargon the supervisor may not understand. While Dr. Welch is a CAS professor who could probably understand it after a refresher on requirements, such unpaid work is burdensome. I suggest limiting his "review" of the SRS to validating assumptions and advice about feasibility in his areas of expertise (natural language processing (and by extension AI), personalization, computing methodologies; see (https://www.eng.mcmaster.ca/cas/faculty/dr-charles-welch/).

While it is true that you mentioned limiting his review to "critical sections", this is unsatisfactory. The term "critical sections" is undefined, and the sole reason you provided was respect for his time.

Actions to be taken

  • Clarify the critical sections that will be reviewed by Dr. Welch. These are meant to be focused slices of certain critical sections, he will not have to read through or comment on large swaths of the document.
Dominant language
TeX
Stars
0
Forks
0
Avg merge
1d 7h
Merged PRs (30d)
52

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Aeolus-Software/RealmForge

All issues in Aeolus-Software/RealmForge

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.