Skip to content

Governance for third party gateways (HIP draft) #66

Closed
philltran wants to merge 4 commits intohelium:masterfrom
philltran:governance-for-third-party-gateways
Closed

Governance for third party gateways (HIP draft) #66
philltran wants to merge 4 commits intohelium:masterfrom
philltran:governance-for-third-party-gateways

Conversation

@philltran
Copy link
Copy Markdown

@philltran philltran commented Oct 29, 2020

Starting a draft of a HIP so the community can flesh out the governance for third party gateways.

Rendered view: https://github.com/philltran/HIP/tree/governance-for-third-party-gateways/00xx-governance-for-third-party-gateways.md

@jamiew jamiew added the draft label Oct 29, 2020
@jamiew
Copy link
Copy Markdown
Contributor

jamiew commented Oct 29, 2020

See also #15 for existing ideas on how to trust DIY hotspots

@philltran
Copy link
Copy Markdown
Author

@jamiew Thanks for that reference to HIP 9. My thought is that this HIP is more focused on establishing the criteria to trust the vendor that is making the gateways / hotspots. By proxy we will need to include ideas from HIP9, but I don't want this to get hung up on trying to solve the "DIY hotspot" problem. I think the solution should still happen in HIP 9. Let me know if you think otherwise.

@jamiew jamiew changed the title Governance for third party gateways (HIP 19 draft) Governance for third party gateways (HIP draft) Nov 4, 2020
@philltran
Copy link
Copy Markdown
Author

@jamiew With PR #86 should I close this PR?

@jamiew
Copy link
Copy Markdown
Contributor

jamiew commented Nov 25, 2020

@philltran yeah I think that makes sense 👍

@jamiew jamiew closed this Nov 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants