GIP-0001 and Getting Started with GIPs, GRPs, GRCs, etc

The Graph community recently adopted a GIP Process that uses a git repo that is hosted on Radicle, a decentralized code collaboration tool.

This post explains the high-level steps for downloading the repo and submitting a GIP, GRC, GRP, etc. More detailed explanations of how the GIP process works can be found in the GIP repo itself under “GIP-0001.”

Steps for accessing the GIPs repo:

  1. Download the Radicle Upstream Client
  2. Add The Graph’s Custom Radicle Seed: hyn98iuryyotyt8aarux16mqeh7k5sbznot8wpgaqt4nhue5fekqqa@radicle.thegraph.com:7001
  3. Fork the GIP repo from one of the editors’ copies (my copy has the following project ID: rad:git:hnrkrhnth6afcc6mnmtokbp4h9575fgrhzbay ).

Once you have the repo locally, you can follow the instructions in GIP-0001 for creating one of the following proposal types:

  • Graph Improvement Proposal (GIP) - Describes a protocol improvement.
  • Graph Request for Comment (GRC) - Describes an application-layer community standard.
  • Graph Request for Proposal (GRP) - Specifies the requirements for basic research, ecosystem tooling, or a possible protocol improvement. Focuses on the problem rather than the solution.

Once you have written your proposal, you will need to push it to your Radicle repo.

Once you’ve pushed your changes, then create a post under either the “GIPs”, “GRCs” or “GRPs” sub-categories in this forum, depending on the type of your proposal. Your post should include:

  • Your Radicle Device ID
  • The branch you have deployed your proposal to.
  • A link to any thread where discussion for this proposal is already happening.
  • A forum post title in the following format: <GIP | GRC | GIP>:<Proposal Title>.

Posting the proposal in The Graph’s Discourse forum will help it to get the attention of the GIP editors and provide a place for discussion if there isn’t already an active thread.

Eventually, as Radicle builds out their Ethereum-based features such as decentralized pull requests and issues, this workflow may change, but for now, this is the informal “pull request” process for getting a proposal included in the repo.

Feel free to ask questions or post suggestions below!

9 Likes

@Brandon thanks for setting this up – i have a radicle-seed node running as well and happy to add it here for others to leverage

My Radicle Seed node is:
hynigj3cxods3uairkx143icaroxzetggbpgui5e8zhex4zggpo9wg@seed.w3m.one:12345

Tried to fork the GIP repo from you copy but looks it is unable to see it for some reason – let me know if you have any tips?

2 Likes

@pkr I have the same problem now. How did you resolve it?

@xarborial there is some problem w/ prior versions of Radicle Upstream …try upgrading your client to the most current version 0.1.12 and it should work.

It is working for me now, here is a screenshot

1 Like

In response to another forum discussion on arbitration ( An Arbitration Charter to clarify Arbitrator behavior - Research & Protocol Improvements - The Graph), I am struggling to find the specified branch “zerim/arbitration-charter”, maybe someone can provide helpful tips.

Here is what I’m seeing:

The left dropdown box only shows GIP branches, not the specified arbitration chapter:
Screen Shot 2021-04-25 at 8.15.28 AM

The top dropdown box only shows the maintainer selection:
Screen Shot 2021-04-25 at 8.16.37 AM

Curious whether I somehow need to add the arbitration chapter branch, but have not found a way to do that. Thanks for any help in advance!

Thanks for following up on this @Oliver. Looks like the new branch made it to my Radicle Upstream client but the client is failing to connect to any peers.

I’m going to try updating to the latest version, restarting, and seeing if that fixes. Stay tuned.

Update: updating my client didn’t seem to fix things, even though I can see the branch in my Radicle client and I can see that my client is connected to The Graph’s community seed. I’ve reached out to the Radicle team to troubleshoot.

2 Likes

Update: Radicle team says many of the replication issues will be solved in the upcoming 0.2 release, which is a breaking lease. Documentation for upgrading will be available coinciding with the release.

There is some additional troubleshooting steps involving our Radicle Seed we can try out that we’ve blocked out some time tomorrow to work through.

In the meantime, @Oliver I’ll post the full contents of the Arbitration Charter in the post you’ve linked.

Update: Radicle released a new minor version, 0.2.X, which is supposed to be far more stable for replication.

Can read more about the release here.

This was a breaking change for all clients and seed nodes. We have upgraded our seed node and I’ve confirmed (w/ @Oliver 's help) that the GIP repo is now propagating correctly again.

As part of the breaking change, project IDs have to be recreated. The new one for the GIP repo is: rad:git:hnrkrhnth6afcc6mnmtokbp4h9575fgrhzbay (I have also updated this in the OP).

Thanks everyone for you patience as we dogfood the bleeding edge of decentralized tech! :globe_with_meridians:

3 Likes

It appears that Radicle is only available for Mac and Linux. What route should someone using windows take to interact with the repo?

Btw, on my Mac, it also doesn’t work, at least for new users. Or maybe I do something wrong. If someone could check Radicle and help me with getting access to it, it will be super nice :slight_smile:

1 Like

Still no luck to connect to this project. Radicle keeps saying: "This project haven't been found yet", while one of the connected peers is ..qqa@radicle.thegraph.com:7001