Update hip-1.md in preparation to Hiero migration #1062

sergmetelin · 2024-10-16T21:12:05Z

Adding Hiero TSC entity
Updating the process to reflect Hiero TSC
Grammar and styling fixes

- Adding Hiero TSC entity - Updating the process to reflect Hiero TSC - Grammar and styling fixes Signed-off-by: Serg Metelin <[email protected]>

netlify · 2024-10-16T21:12:21Z

✅ Deploy Preview for hedera-hips ready!

Name	Link
🔨 Latest commit	`c8845b4`
🔍 Latest deploy log	https://app.netlify.com/sites/hedera-hips/deploys/6770b4fc95919c0008fc3276
😎 Deploy Preview	https://deploy-preview-1062--hedera-hips.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Signed-off-by: Michael Garber <[email protected]>

HIP/hip-1.md

hendrikebbers

Some suggested changes

hendrikebbers · 2024-12-17T07:48:53Z

HIP/hip-1.md


-## HIP Workflow
+### Hiero Governing Council


Suggested change

### Hiero Governing Council

### Herdera Governing Council

hendrikebbers · 2024-12-17T07:53:24Z

HIP/hip-1.md


 ### Hedera Core Developers

 Hedera Core Developers or "core developers" include those who are tasked with the development of any part of the Hedera platform or ecosystem; this includes employees of Hedera, contractors hired by Hedera directly, and community developers who have received grants to develop and maintain a project.

 ### HIP Editors

-The HIP editors or "editors" are individuals responsible for managing the administrative and editorial aspects of the HIP workflow. HIP editorship is by invitation of the current editors or by assignment by the Council.
+The HIP editors or "editors" are individuals responsible for managing the administrative and editorial aspects of the HIP workflow. HIP editorship is by invitation of the current editors or by assignment by the Hiero TSC.


Suggested change

The HIP editors or "editors" are individuals responsible for managing the administrative and editorial aspects of the HIP workflow. HIP editorship is by invitation of the current editors or by assignment by the Hiero TSC.

The HIP editors or "editors" are individuals responsible for managing the administrative and editorial aspects of the HIP workflow. HIP editorship is by invitation of the current committers and maintainers of the HIP project.

We have defined roles for committers and maintainers in the charter:

Contributors include anyone in the community that contributes code, documentation, or other technical artifacts to the Project;

Committers are Contributors who have earned the ability to modify (“commit”) source code, documentation or other technical artifacts in a project’s repository; and

Maintainers are Committers who have earned the right to vote on (1) promotion of Contributors to Committers; (2) promotion of Committers to Maintainers; (3) the removal of any Committer or Maintainer; (4) representation on the TSC; (5) other scenarios that require a vote for good governance of the sub-project.

hendrikebbers · 2024-12-17T07:53:51Z

HIP/hip-1.md


-The HIP process begins with a new idea for Hedera. It is highly recommended that a single HIP contain a single key proposal or new idea. The more focused the HIP, the more successful it tends to be. Hedera collaborators and maintainers reserve the right to reject a HIP if it appears too unfocused or too broad. If in doubt, split your HIP into several well-focused ones.
+The HIP process begins with a new idea for Hiero. It is highly recommended that a single HIP contain a single key proposal or new idea. The more focused the HIP, the more successful it tends to be. Hiero collaborators and maintainers reserve the right to reject a HIP if it appears too unfocused or too broad. If in doubt, split your HIP into several well-focused ones.


Suggested change

The HIP process begins with a new idea for Hiero. It is highly recommended that a single HIP contain a single key proposal or new idea. The more focused the HIP, the more successful it tends to be. Hiero collaborators and maintainers reserve the right to reject a HIP if it appears too unfocused or too broad. If in doubt, split your HIP into several well-focused ones.

The HIP process begins with a new idea for Hiero. It is highly recommended that a single HIP contain a single key proposal or new idea. The more focused the HIP, the more successful it tends to be. Hiero committers and maintainers reserve the right to reject a HIP if it appears too unfocused or too broad. If in doubt, split your HIP into several well-focused ones.

hendrikebbers · 2024-12-17T07:56:07Z

HIP/hip-1.md


-Each HIP must have a champion -- someone who writes the HIP using the style and format described below, shepherds the discussions in the appropriate forums, and attempts to build community consensus around the idea. The HIP champion (a.k.a. Author) should first attempt to ascertain whether the idea is HIP-able. Circulating the idea in Hedera's Discord server (https://hedera.com/discord) or in an issue in the Hedera HIP GitHub Repository (https://github.com/hashgraph/hedera-improvement-proposal) is the best way to do so.
+Each HIP must have a champion -- someone who writes the HIP using the style and format described below, shepherds the discussions in the appropriate forums, and attempts to build community consensus around the idea. The HIP champion (a.k.a. Author) should first attempt to ascertain whether the idea is HIP-able. Circulating the idea in Hiero's Discord server (https://hedera.com/discord) or in an issue in the Hiero HIP GitHub Repository (https://github.com/hashgraph/hedera-improvement-proposal) is the best way to do so.


Suggested change

Each HIP must have a champion -- someone who writes the HIP using the style and format described below, shepherds the discussions in the appropriate forums, and attempts to build community consensus around the idea. The HIP champion (a.k.a. Author) should first attempt to ascertain whether the idea is HIP-able. Circulating the idea in Hiero's Discord server (https://hedera.com/discord) or in an issue in the Hiero HIP GitHub Repository (https://github.com/hashgraph/hedera-improvement-proposal) is the best way to do so.

Each HIP must have a champion -- someone who writes the HIP using the style and format described below, shepherds the discussions in the appropriate forums, and attempts to build community consensus around the idea. The HIP champion (a.k.a. Author) should first attempt to ascertain whether the idea is HIP-able. Circulating the idea in Hederas Discord server (https://hedera.com/discord), our GitHub Discussions (https://github.com/hashgraph/hedera-improvement-proposal/discussions) or in an issue in the HIP GitHub Repository (https://github.com/hashgraph/hedera-improvement-proposal) is the best way to do so.

For Hiero we want to use GitHub discussions more that why I added it here

hendrikebbers · 2024-12-17T07:58:54Z

HIP/hip-1.md


 HIPs can also be superseded by a different HIP, rendering the original obsolete. This is intended for Informational HIPs, where version 2 of an API can replace version 1.

-Some HIPs will have to be approved by the Governing Council before getting a `Accepted` status'. This is usually the case for HIPs in the `Standards Track` type and `Core`, `Service` and `Mirror` categories, but can expand to other HIPs as well. The HIPs editors will double-check if the `Yes` flag on `needs-council-approval` header field needs to be set. If HIP needs Governing Council approval, it will have to go through a 'Council Review' status and be reviewed at the next Technical Committee meeting of the Governing Council.
+Some HIPs will have to be reviewed by the Hiero Technical Steering Committee (TSC) before getting an `Accepted` status. This is usually the case for HIPs in the `Standards Track` type and `Core`, `Service`, and `Mirror` categories, but can expand to other HIPs as well, including `Process` HIPs. The HIP editors will double-check if the `Yes` flag on the `needs-tsc-approval` header field needs to be set. If a HIP needs TSC approval, it will have to go through a `TSC Review` status and be reviewed by the Hiero TSC.


Suggested change

Some HIPs will have to be reviewed by the Hiero Technical Steering Committee (TSC) before getting an `Accepted` status. This is usually the case for HIPs in the `Standards Track` type and `Core`, `Service`, and `Mirror` categories, but can expand to other HIPs as well, including `Process` HIPs. The HIP editors will double-check if the `Yes` flag on the `needs-tsc-approval` header field needs to be set. If a HIP needs TSC approval, it will have to go through a `TSC Review` status and be reviewed by the Hiero TSC.

Some HIPs will have to be reviewed by the Hiero TSC before getting an `Accepted` status. This is usually the case for HIPs in the `Standards Track` type and `Core`, `Service`, and `Mirror` categories, but can expand to other HIPs as well, including `Process` HIPs. The HIP editors will double-check if the `Yes` flag on the `needs-tsc-approval` header field needs to be set. If a HIP needs TSC approval, it will have to go through a `TSC Review` status and be reviewed by the Hiero TSC.

hendrikebbers · 2024-12-17T08:01:14Z

HIP/hip-1.md


 #### `discussions-to` header

-While a HIP is a draft, a discussions-to header will indicate the URL where the HIP is being discussed. Examples of places to discuss your HIP include an issue in this repo or in a fork of this repo, the Hedera Developer Discord, or Reddit r/hashgraph.
+While a HIP is a draft, a discussions-to header will indicate the URL where the HIP is being discussed. Examples of places to discuss your HIP include an issue in this repo or in a fork of this repo, the Hiero Developer Discord, or Reddit r/hashgraph.


Suggested change

While a HIP is a draft, a discussions-to header will indicate the URL where the HIP is being discussed. Examples of places to discuss your HIP include an issue in this repo or in a fork of this repo, the Hiero Developer Discord, or Reddit r/hashgraph.

While a HIP is a draft, a discussions-to header will indicate the URL where the HIP is being discussed. Examples of places to discuss your HIP include an issue in this repo or in a fork of this repo, the Hedera Developer Discord, or Reddit r/hashgraph.

Today nobody use the Hiero Discord and based on that we should not change it at the moment. We will discuss in future what tooling we use for the community

hendrikebbers · 2024-12-17T09:34:00Z

HIP/hip-1.md


 #### `release` header

-The release header indicates when the HIP was implemented on the network (vX.Y.Z), e.g. 0.29.0.
+The `release` header indicates when the HIP was implemented in the codebase (vX.Y.Z), e.g., `v0.29.0`.


Maybe it makes sense to mention that Hiero release numbers are used here and not Hedera release numbers.
In future Hedera mainnet version A will be build based on Hiero version B.

hendrikebbers · 2024-12-17T09:34:55Z

HIP/hip-1.md

@@ -355,24 +359,25 @@ For each new HIP that comes in, an editor does the following:

 - Read the HIP to check if it is ready: sound and complete. The ideas must make technical sense, even if they don't seem likely to get to Final status.
 - The title should accurately describe the content.
- Check the HIP for language (spelling, grammar, sentence structure, etc.), markup (GitHub flavored Markdown), and code style.
+- Check the HIP for language (spelling, grammar, sentence structure, etc.), markup (GitHub-flavored Markdown), and code style.


Suggested change

- Check the HIP for language (spelling, grammar, sentence structure, etc.), markup (GitHub-flavored Markdown), and code style.

- Check the HIP for language (spelling, grammar, sentence structure, etc.), markup ([GitHub-flavored Markdown](https://github.github.com/gfm/)), and code style.

hendrikebbers · 2024-12-17T09:35:53Z

HIP/hip-1.md


 ## Style Guide

 When referring to a HIP by number, it should be written in the hyphenated form HIP-X where X is the HIP number.

 ## History

-This document was derived from Bitcoin's BIP-0001 written by Amir Taaki, Ethereum's EIP-1 written by Martin Becze and Hudson Jameson, and Python's PEP-0001 written by Barry Warsaw, Jeremy Hylton, David Goodger, and Nick Coghlan. In many places text was simply copied and modified. The authors of the text from which this document was derived are not responsible for this document's use in the Hedera Improvement Proposal process, and should not be bothered with technical questions specific to Hedera or the HIP.
+This document was derived from Bitcoin's BIP-0001 written by Amir Taaki, Ethereum's EIP-1 written by Martin Becze and Hudson Jameson, and Python's PEP-0001 written by Barry Warsaw, Jeremy Hylton, David Goodger, and Nick Coghlan. In many places text was simply copied and modified. The authors of the text from which this document was derived are not responsible for this document's use in the Hiero Improvement Proposal process, and should not be bothered with technical questions specific to Hedera or the HIP.


Suggested change

This document was derived from Bitcoin's BIP-0001 written by Amir Taaki, Ethereum's EIP-1 written by Martin Becze and Hudson Jameson, and Python's PEP-0001 written by Barry Warsaw, Jeremy Hylton, David Goodger, and Nick Coghlan. In many places text was simply copied and modified. The authors of the text from which this document was derived are not responsible for this document's use in the Hiero Improvement Proposal process, and should not be bothered with technical questions specific to Hedera or the HIP.

This document was derived from Bitcoin's BIP-0001 written by Amir Taaki, Ethereum's EIP-1 written by Martin Becze and Hudson Jameson, and Python's PEP-0001 written by Barry Warsaw, Jeremy Hylton, David Goodger, and Nick Coghlan. In many places text was simply copied and modified. The authors of the text from which this document was derived are not responsible for this document's use in the Hiero Improvement Proposal process, and should not be bothered with technical questions specific to Hiero, Hedera or the HIP.

Co-authored-by: Hendrik Ebbers <[email protected]> Signed-off-by: Michael Garber <[email protected]>

Update hip-1.md in preparation to Hiero migration

5e3a23a

- Adding Hiero TSC entity - Updating the process to reflect Hiero TSC - Grammar and styling fixes Signed-off-by: Serg Metelin <[email protected]>

sergmetelin requested a review from mgarbs as a code owner October 16, 2024 21:12

mgarbs and others added 7 commits October 22, 2024 16:34

Update hip-1.md to reflect Hiero process

f98e66f

Signed-off-by: Michael Garber <[email protected]>

Update Hedera with Hiero

7f41048

Support for Hiero TSC Approval

7b9795e

Support for Hiero TSC in about

5b0dcda

pull latest merge resolve

1cc013c

update header validation script

7798e58

remove uneeded workflows

eee0bbe

mgarbs requested a review from a team as a code owner December 2, 2024 15:31

mgarbs requested a review from rbarkerSL December 2, 2024 15:31

fix type category table on hip 1

fdc471c

hendrikebbers reviewed Dec 17, 2024

View reviewed changes

HIP/hip-1.md Outdated Show resolved Hide resolved

hendrikebbers reviewed Dec 17, 2024

View reviewed changes

Update HIP/hip-1.md

c8845b4

Co-authored-by: Hendrik Ebbers <[email protected]> Signed-off-by: Michael Garber <[email protected]>

rbarkerSL approved these changes Jan 16, 2025

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update hip-1.md in preparation to Hiero migration #1062

Update hip-1.md in preparation to Hiero migration #1062

sergmetelin commented Oct 16, 2024

netlify bot commented Oct 16, 2024 •

edited

Loading

hendrikebbers left a comment

hendrikebbers Dec 17, 2024

hendrikebbers Dec 17, 2024

hendrikebbers Dec 17, 2024

hendrikebbers Dec 17, 2024

hendrikebbers Dec 17, 2024

hendrikebbers Dec 17, 2024

hendrikebbers Dec 17, 2024

hendrikebbers Dec 17, 2024

hendrikebbers Dec 17, 2024

hendrikebbers Dec 17, 2024

	The HIP editors or "editors" are individuals responsible for managing the administrative and editorial aspects of the HIP workflow. HIP editorship is by invitation of the current editors or by assignment by the Hiero TSC.
	The HIP editors or "editors" are individuals responsible for managing the administrative and editorial aspects of the HIP workflow. HIP editorship is by invitation of the current committers and maintainers of the HIP project.


		The HIP process begins with a new idea for Hedera. It is highly recommended that a single HIP contain a single key proposal or new idea. The more focused the HIP, the more successful it tends to be. Hedera collaborators and maintainers reserve the right to reject a HIP if it appears too unfocused or too broad. If in doubt, split your HIP into several well-focused ones.
		The HIP process begins with a new idea for Hiero. It is highly recommended that a single HIP contain a single key proposal or new idea. The more focused the HIP, the more successful it tends to be. Hiero collaborators and maintainers reserve the right to reject a HIP if it appears too unfocused or too broad. If in doubt, split your HIP into several well-focused ones.


		Each HIP must have a champion -- someone who writes the HIP using the style and format described below, shepherds the discussions in the appropriate forums, and attempts to build community consensus around the idea. The HIP champion (a.k.a. Author) should first attempt to ascertain whether the idea is HIP-able. Circulating the idea in Hedera's Discord server (https://hedera.com/discord) or in an issue in the Hedera HIP GitHub Repository (https://github.com/hashgraph/hedera-improvement-proposal) is the best way to do so.
		Each HIP must have a champion -- someone who writes the HIP using the style and format described below, shepherds the discussions in the appropriate forums, and attempts to build community consensus around the idea. The HIP champion (a.k.a. Author) should first attempt to ascertain whether the idea is HIP-able. Circulating the idea in Hiero's Discord server (https://hedera.com/discord) or in an issue in the Hiero HIP GitHub Repository (https://github.com/hashgraph/hedera-improvement-proposal) is the best way to do so.

	While a HIP is a draft, a discussions-to header will indicate the URL where the HIP is being discussed. Examples of places to discuss your HIP include an issue in this repo or in a fork of this repo, the Hiero Developer Discord, or Reddit r/hashgraph.
	While a HIP is a draft, a discussions-to header will indicate the URL where the HIP is being discussed. Examples of places to discuss your HIP include an issue in this repo or in a fork of this repo, the Hedera Developer Discord, or Reddit r/hashgraph.

	- Check the HIP for language (spelling, grammar, sentence structure, etc.), markup (GitHub-flavored Markdown), and code style.
	- Check the HIP for language (spelling, grammar, sentence structure, etc.), markup ([GitHub-flavored Markdown](https://github.github.com/gfm/)), and code style.

Update hip-1.md in preparation to Hiero migration #1062

Are you sure you want to change the base?

Update hip-1.md in preparation to Hiero migration #1062

Conversation

sergmetelin commented Oct 16, 2024

netlify bot commented Oct 16, 2024 • edited Loading

✅ Deploy Preview for hedera-hips ready!

hendrikebbers left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

netlify bot commented Oct 16, 2024 •

edited

Loading