Folks, I appreciate everyone’s comments and support. I have resubmitted the proposal with the appropriate link to the forum post describing. The new proposal is https://dashboard.internetcomputer.org/proposal/135829.
The original post is still intact. Original Forum Post is here
Who looks after your Houston servers by the way? Is he part of this forum?
Yes, @charles_witte:matrix.org
Hello borovan! Yes sir, I look after the HU1 servers. 
Proposal 135829 – Louise | Aviate Labs
Vote: ADOPT
Review:
The proposal increases the type1.1 rewardable_nodes of Node Operator fthz3 from 0 to 14 in order to include 14 nodes in the HU1 DC.
type1.1 reward configuration is used Vote: ADOPT
The proposal increases the type1.1 rewardable_nodes of Node Operator eikix from 0 to 28 in order to include 3 more nodes in the sj2 DC.
The node’s Node Operator matches the one from the proposal and the NO has 28 nodes which match the ones mentioned in the proposal.
Vote: REJECT
The proposal increases the type1.1 rewardable_nodes of Node Operator yngfj from 0 to 14 in order to include 14 nodes in the hu1 DC.
The node’s Node Operator matches the one from the proposal and the NO has 14 nodes which match the ones mentioned in the proposal.
Bad proposal summary, not providing either a forum link, relevant discussion neither the wiki profile for further verification of ownership.
Vote: ADOPT
The proposal increases the type1.1 rewardable_nodes of Node Operator gl27f from 0 to 28 in order to include 28 nodes in the lj1 DC.
The node’s Node Operator matches the one from the proposal and the NO has 28 nodes which match the ones mentioned in the proposal.
Vote: ADOPT
The proposal increases the type1.1 rewardable_nodes of Node Operator 3xiew from 0 to 14 in order to include 14 nodes in the mb1 DC.
The node’s Node Operator matches the one from the proposal and the NO has 14 nodes which match the ones mentioned in the proposal.
Vote: ADOPT
The proposal increases the type1.1 rewardable_nodes of Node Operator byspq from 0 to 1 in order to include node a2e7m in the zh2 DC.
The both the node and the node’s Node Operator matches the ones from the proposal.
Vote: ADOPT
The proposal increases the type1.1 rewardable_nodes of Node Operator db7fe from 0 to 5 in order to include 5 nodes in the zh2 DC.
The node’s Node Operator matches the one from the proposal and the NO has 5 nodes which match the ones mentioned in the proposal.
Vote: ADOPT
The proposal increases the type1.1 rewardable_nodes of Node Operator pi3wm from 0 to 1 in order to include node hgbum in the zh2 DC.
The both the node and the node’s Node Operator matches the ones from the proposal.
Vote: ADOPT
The proposal increases the type1.1 rewardable_nodes of Node Operator rzskv from 0 to 1 in order to include node y7vmg in the zh2 DC.
The both the node and the node’s Node Operator matches the ones from the proposal.
Vote: ADOPT
The proposal increases the type1.1 rewardable_nodes of Node Operator s7dud from 0 to 2 in order to include 2 more nodes in the zh2 DC.
The node’s Node Operator matches the one from the proposal and the NO has 2 nodes which match the ones mentioned in the proposal.
Vote: ADOPT
The proposal increases the type1.1 rewardable_nodes of Node Operator vqe65 from 0 to 1 in order to include node gtc2a in the zh2 DC.
The both the node and the node’s Node Operator matches the ones from the proposal.
Vote: ADOPT
The proposal increases the type1.1 rewardable_nodes of Node Operator wqyl3 from 0 to 1 in order to include node 6hkcx in the zh2 DC.
The both the node and the node’s Node Operator matches the ones from the proposal.
Vote: ADOPT
The proposal increases the type1.1 rewardable_nodes of Node Operator xcne4 from 0 to 1 in order to include node gd2vp in the zh2 DC.
The both the node and the node’s Node Operator matches the ones from the proposal.
Vote: ADOPT
The proposal increases the type1.1 rewardable_nodes of Node Operator y4c7z from 0 to 1 in order to include node 45huy in the zh2 DC.
The both the node and the node’s Node Operator matches the ones from the proposal.
Vote: ADOPT
The proposal increases the type1.1 rewardable_nodes of Node Operator gv77f from 27 to 28 in order to include node cfvmx in the aw1 DC.
The both the node and the node’s Node Operator matches the ones from the proposal.
Vote: ADOPT
The proposal increases the type1.1 rewardable_nodes of Node Operator fthz3 from 0 to 14 in order to include 14 nodes in the hu1 DC.
The node’s Node Operator matches the one from the proposal and the NO has 14 nodes which match the ones mentioned in the proposal.
Vote: ADOPT
The proposal increases the type1.1 rewardable_nodes of Node Operator 4kxqv from 0 to 1 in order to include node qnfu3 in the st1 DC.
The both the node and the node’s Node Operator matches the ones from the proposal.
CodeGov has a team of developers who review and vote independently on the following proposal topics: IC-OS Version Election, Protocol Canister Management, Subnet Management, Node Admin, and Participant Management. The CodeGov NNS known neuron is configured to follow our reviewers on these technical topics. We also have a group of Followees who vote independently on the Governance and the SNS & Neuron’s Fund topics. We strive to be a credible and reliable Followee option that votes on every proposal and every proposal topic in the NNS. We also support decentralization of SNS projects such as WaterNeuron, KongSwap, and Alice with a known neuron and credible Followees.
Learn more about CodeGov and its mission at codegov.org.
Proposal 135790
Vote: Adopt
This proposal sets rewardable_nodes for node operator gv77f to 28, corresponding to the number of nodes now deployed under this node operator ID.
Proposal 135829
Vote: Adopt
This proposal sets rewardable_nodes for node operator fthz3 to 14, corresponding to the number of nodes now deployed under this node operator ID.
Proposal 135832
Vote: Adopt
This proposal sets rewardable_nodes for node operator 4kxqv to 1, corresponding to the number of nodes now deployed under this node operator ID.
CodeGov has a team of developers who review and vote independently on the following proposal topics: IC-OS Version Election, Protocol Canister Management, Subnet Management, Node Admin, and Participant Management. The CodeGov NNS known neuron is configured to follow our reviewers on these technical topics. We also have a group of Followees who vote independently on the Governance and the SNS & Neurons’ Fund topics. We strive to be a credible and reliable Followee option that votes on every proposal and every proposal topic in the NNS. We also support decentralisation of SNS projects such as WaterNeuron, KongSwap, and Alice with a known neuron and credible Followees.
Learn more about CodeGov and its mission at codegov.org.
