GIP-0061: Improvements to the GIP process (WIP) #30
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
PedroMD
reviewed
Sep 29, 2023
PedroMD
reviewed
Sep 29, 2023
PedroMD
reviewed
Sep 29, 2023
|
|
||
| Once a GIP is published on the GitHub repo and the forum, some time should be left for the community to discuss. Some more complex or controversial proposals may require more time and discussion, while others that are more straightforward may be accepted more quickly, always at the Council's discretion. | ||
|
|
||
| After publishing, the authors are encouraged to present the GIPs in one or many of the relevant community calls, for instance, Indexer Office Hours that happen weekly on Discord, or the monthly core developer calls. To request a speaking slot in one of these calls, you can use this form (TODO: add form link) to get in touch with organizers from core dev teams and The Graph Foundation. |
There was a problem hiding this comment.
@pcarranzav, @dmachotka and I will propose a form link for people to get in touch
PedroMD
reviewed
Sep 29, 2023
PedroMD
reviewed
Sep 29, 2023
PedroMD
reviewed
Nov 28, 2023
|
|
||
| **To avoid conflicts in GIP numbers, proposals should be posted as a Pull Request on GitHub with a GIP number _before_ being posted to the forum**. | ||
|
|
||
| After creating the Pull Request, post a thread in the GIPs and Governance category with a link to the Pull Request. The post should have the same title as the GIP, and include the Abstract and Motivation sections but linking to GitHub for the full GIP text. (Older GIPs may include the full proposal text in the forum post, but this is now discouraged as it is hard to keep the forum and GitHub versions in sync). |
There was a problem hiding this comment.
@pcarranzav with the new GIP Tracker, we're considering having a GPT-powered TLDR/Summary for all GIPs, so people can quickly understand what the whole proposal is all about without having to read the entire thing (after clicking a link from the forum). It might make sense for us to do the same in the Forum discussion for all subsequent GIPs, with some automation. Do you see any problem with this?
There was a problem hiding this comment.
I think that'd be pretty cool! I would just suggest adding a disclaimer noting this is a GPT-powered summary so it might be biased
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Early draft of some proposed changes to GIP-0001 and GIP-0001, with an accompanying GIP-0061 explaining the rationale for the changes.