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

chore(documentation): decision records on Python directory structure and views management #51

Merged
merged 2 commits into from
Jun 9, 2021

Conversation

ace-n
Copy link
Contributor

@ace-n ace-n commented Jun 3, 2021

Decisions related to #37

@engelke @dinagraves FYI

@ace-n ace-n requested a review from grayside June 3, 2021 20:27
@google-cla google-cla bot added the cla: yes This human has signed the Contributor License Agreement. label Jun 3, 2021
@ace-n ace-n linked an issue Jun 4, 2021 that may be closed by this pull request
Copy link
Collaborator

@grayside grayside left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for writing up decisions records on some of our non-obvious Python practices!

I've left the same feedback on both. My higher-level point to clarify is the importance of the decision record is not the "what". What is probably better answered in an architecture doc.

The decision records are here to help us understand the "why", and the terms under which we might reverse or evolve that decision. I think of it as something like a contract the team is making with the software: here's how things can exist as long as these terms are true.

@@ -10,6 +10,41 @@ Decision records should attempt to follow the Y-statement format for consistency
In the context of **<use case/user story u>**, facing **<concern c>** we decided for **<option o>** and neglected <other options>, to achieve <system qualities/desired consequences>, accepting <downside d/undesired consequences>, because <additional rationale>.
```

## Decision: Use a two-folder-level split for Jinja templates

In order to organize our Jinja HTML templates, we decided to **use a two-level folder level split**. This will be combined with Jinja inheritance (i.e. the `extends` clause) for common components where possible.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you clarify the benefit and the trade-off?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added revision criteria - PTAL?


## Decision: Use a one-folder-level split for Flask view functions

In order to organize our Flask view functions, we decided to **use a single folder level split combined with Flask blueprints**, accepting that this may be subject to revision in the future.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All decisions are subject to revision. Could you clarify the benefit/trade-off, or putting it another way, the circumstances under which this might be changed?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added revision criteria - PTAL?

@grayside grayside changed the title chore(documentation): codify decisions agreed to in #37 chore(documentation): decision records on Python directory structure and views management Jun 8, 2021
@grayside grayside added the type: docs Improvement to the documentation for an API. label Jun 8, 2021
@ace-n ace-n requested a review from grayside June 9, 2021 21:16
@grayside grayside merged commit b504201 into main Jun 9, 2021
@grayside grayside deleted the ace-n-patch-2 branch June 9, 2021 21:40
grayside pushed a commit that referenced this pull request Jul 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla: yes This human has signed the Contributor License Agreement. type: docs Improvement to the documentation for an API.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Decision: Folder structure of the website
2 participants