Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding Scope and Motivation Fields and Defining the Role of the What Section in README Files #3948

Closed
Xinlu-Y opened this issue Aug 28, 2024 · 1 comment · Fixed by #3950
Closed

Comments

@Xinlu-Y
Copy link
Collaborator

Xinlu-Y commented Aug 28, 2024

This issue relates to both issue #3159 and #3248. Based on the comments above, generating a comprehensive software review isn't feasible for us at the moment. The main goal is to ensure that the scope and motivation are available in both the SystemInformation and in the README files.

  • We can update the following sections in the generated README files for each example's src directory:
    • Example name
    • Authors
    • Motivation
    • Purpose
    • Scope
    • Making Examples
    • ...
  • For instance, taking the Projectile example, the README could look like this, where Purpose, Motivation, and Scope are optional subsections under introInfo:
    • Projectile
    • Authors: Samuel J. Crawford, Brooks MacLachlan, W. Spencer Smith
    • Motivation: Projectile motion is a common problem in physics.
    • Purpose: Predict whether a launched projectile hits its target.
    • Scope: The scope of the requirements includes the analysis of a two-dimensional (2D) projectile problem with constant acceleration.
    • Making Examples
      How to Run the Program: In your terminal command line, enter the same directory as this README file.
    • ...
  • Additionally, a What section has already been created in the current code, but currently, it holds no information in the generated README file.
    -- | 'What' section in generated README file, does not display if empty
    whatInfo :: Maybe String -> Doc
    whatInfo = maybe empty (regularSec (text "What") . text)
  • I'm considering whether we could use this section to include relevant background information. If so, the What section might look like this:
    • ...
    • Scope: The scope of the requirements includes the analysis of a two-dimensional (2D) projectile problem with constant acceleration.
    • What: Common examples of projectile motion include ballistics problems (missiles and bullets) and the flight of the balls in various sports (baseball, golf, football, etc.).
    • Making Examples
    • ...

We need to decide whether it's necessary to keep the What section and, if so, what information should be included in it. One possibility is to move some of the content from introInfo to whatInfo. For example, we could have introInfo focus on answering the "why" questions (motivation, purpose), while whatInfo could address the "what" questions (background, scope).

@JacquesCarette
Copy link
Owner

This is an excellent proposal! Yes, please start designing exactly this.

JacquesCarette added a commit that referenced this issue Oct 2, 2024
Implement Proposal #3948: Enhance README Generation
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants