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

Remove redundant items #329

Merged
merged 10 commits into from May 21, 2021
Merged

Remove redundant items #329

merged 10 commits into from May 21, 2021

Conversation

JieXiong9119
Copy link
Contributor

Reference issues #271, #272, #275

Copy link
Member

@nllong nllong left a comment

Choose a reason for hiding this comment

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

This is great, thanks Jie! A couple things:

  1. we need to base the PR against a new develop-v3 branch which I will create today.
  2. Can you add a proposal into the proposal folder so that we know what this change is?
  3. After 2, can we also include Jan and Michael Braunch from CTS on these updates?

@JieXiong9119
Copy link
Contributor Author

This is great, thanks Jie! A couple things:

  1. we need to base the PR against a new develop-v3 branch which I will create today.
  2. Can you add a proposal into the proposal folder so that we know what this change is?
  3. After 2, can we also include Jan and Michael Braunch from CTS on these updates?

Will do!

@JieXiong9119 JieXiong9119 changed the base branch from develop to develop-v3 April 19, 2021 22:07
@JieXiong9119
Copy link
Contributor Author

This is great, thanks Jie! A couple things:

  1. we need to base the PR against a new develop-v3 branch which I will create today.
  2. Can you add a proposal into the proposal folder so that we know what this change is?
  3. After 2, can we also include Jan and Michael Braunch from CTS on these updates?

Hey Nick, please check the added proposals for the changes.
For 3, I don't know how to add Jan and Michael to here. Should I just forward this PR in email to them?

@nllong nllong requested a review from yan130 April 21, 2021 17:51
@nllong
Copy link
Member

nllong commented Apr 21, 2021

Great, thanks! I added Yan as a reviewer. Can you send link to CTS? I'll slack you the email.

Copy link
Member

@nllong nllong left a comment

Choose a reason for hiding this comment

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

Looks good. Let's wait until after meeting with CTS before merging.

Copy link
Contributor Author

@JieXiong9119 JieXiong9119 left a comment

Choose a reason for hiding this comment

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

Make decision and implement the latest proposal: delete Install or upgrade master venting


## Justification

`Install or upgrade master venting` measure repeats in `ChilledWaterHotWaterAndSteamDistributionSystems` and `OtherHVAC`, and we should keep only one of them. This proposal suggests that we remove it under `ChilledWaterHotWaterAndSteamDistributionSystems` and keep it under `OtherHVAC`, as master venting approach could be implemented not only in chilled or hot water system.
Copy link
Contributor Author

Choose a reason for hiding this comment

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

@nllong could we justify whether we should keep it under ChilledWaterHotWaterAndSteamDistributionSystems or OtherHVAC? Any reference to look up?

Copy link
Member

Choose a reason for hiding this comment

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

I would check ASHRAE Standard 100.
image

@JieXiong9119
Copy link
Contributor Author

Two new proposals added. Related issues: #338 , #337

@JieXiong9119 JieXiong9119 requested review from Ryoken and nllong May 4, 2021 17:45
@nllong nllong merged commit 59e7f2d into develop-v3 May 21, 2021
@nllong nllong deleted the CTS-deprecation branch May 21, 2021 21:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment