Skip to content

Add description field to the EIP header#3706

Merged
MicahZoltu merged 6 commits intoethereum:masterfrom
axic:description-header
Aug 17, 2021
Merged

Add description field to the EIP header#3706
MicahZoltu merged 6 commits intoethereum:masterfrom
axic:description-header

Conversation

@axic
Copy link
Member

@axic axic commented Aug 6, 2021

Implementation of #3564 (comment).

The header:
Screenshot

Twitter before:
Screenshot

Twitter after:
Screenshot

Could also render the description prominently after the header.

@axic axic requested review from MicahZoltu and lightclient August 6, 2021 19:58
Copy link

@MicahZoltu MicahZoltu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Recommend removing the Simple Summary from the template and EIP-1, as this would be the new place to put that content.

I generally approve, but would like to see the Simple Summary removed along with the introduction of a description metadata field.

@axic
Copy link
Member Author

axic commented Aug 7, 2021

Recommend removing the Simple Summary from the template and EIP-1, as this would be the new place to put that content.

I generally approve, but would like to see the Simple Summary removed along with the introduction of a description metadata field.

Absolutely, that would be the goal, but decided to keep the first step simple until there's a general agreement on this.

Could also render the description prominently after the header.

My main question right now is how to render it on the page:

  1. only part of the header (as in the PR now)
  2. before the header in large text
  3. after the header in large text
  4. add a new section (like simple summary), but call it Description
  5. both 1) and one of 2) to 4)

@MicahZoltu
Copy link

I care less about answering the "how it is rendered" question right now, as that is something we can pretty easily/freely iterate on after this change I think. I'm fine with starting out with something simple and then improving it later.

@MicahZoltu
Copy link

Absolutely, that would be the goal, but decided to keep the first step simple until there's a general agreement on this.

I would like to see that happen in this PR, not a future PR. I dislike the idea of having a period of time where we have both a description and a ## Simple Summary

@axic
Copy link
Member Author

axic commented Aug 8, 2021

Absolutely, that would be the goal, but decided to keep the first step simple until there's a general agreement on this.

I would like to see that happen in this PR, not a future PR. I dislike the idea of having a period of time where we have both a description and a ## Simple Summary

I planned to do it in this PR, but did not wanted to bring extra work to myself before this field is agreed on.

@axic
Copy link
Member Author

axic commented Aug 10, 2021

Some variations:

image

Screenshot

Screenshot

@MicahZoltu
Copy link

I like 2.

@lightclient
Copy link
Member

I like both 1 and 2. In terms of the actual text in the templates, I don't mind too much. I'm on board with the change in general though (it will be great to not repeat the EIP number a dozen times in the social thumbnail!)

@axic axic force-pushed the description-header branch from a8508b6 to 58af7c5 Compare August 11, 2021 10:55
@axic axic requested a review from MicahZoltu August 11, 2021 10:57
@axic
Copy link
Member Author

axic commented Aug 12, 2021

@MicahZoltu should be ready to merge, but let me know if you want to remove the commit for 2718.

---
eip: 2718
title: Typed Transaction Envelope
description: Defines a new transaction type that is an envelope for future transaction types.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Simple Summary should be removed with the inclusion of description. I think.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right. My question was do you want to touch this file in this PR or not?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm fine with 2718 getting updated as a "first example" in this PR.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, also removed the section.

eip-template.md Outdated
---
eip: <to be assigned>
title: <EIP title>
description: <Provide a simplified and layman-accessible explanation of the EIP.>

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it would be valuable to include this text or similar, but not a hard requirement if others disagree:

Imagine an email subject line, GitHub PR title, or forum post title.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't want to argue too much about it, but what is the title then?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Title is a few words, not a complete sentence.

King Micah

Description is one full (short) sentence.

The benevolent dictator of the EIPs repository.

Abstract is multi-sentence (short paragraph) technical summary.

Micah is the unelected, self assigned dictator of the EIPs repository. They rule by way of blocking an PRs they don't like and merging things they like without waiting for agreement from anyone else. Micah's power can be taken away by someone else volunteering to take on the responsibilities of shepherding the EIP's repository."

Another way to look at it is that a Title is what you would use in a sentence when referring to the EIP. "We should implement the EVM Object Format in Shanghai." The description is what you would use to jog someone's memory as to what the EIP is. "What is the EVM Object Format?" "It is the EIP that Establishes contract versioning by way of a leading bytecode sequence." "Ah, right, I remember that one."

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think actually your description is much better suited as opposed to the examples you gave :)

title: <Title is a few words, not a complete sentence.>
description: <Description is one full (short) sentence.>
abstract: <Abstract is multi-sentence (short paragraph) technical summary.>

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Works for me. :)

@axic axic mentioned this pull request Aug 16, 2021
@axic axic force-pushed the description-header branch from 58af7c5 to 4c91216 Compare August 16, 2021 12:03
@axic axic force-pushed the description-header branch from 7807444 to 27e2844 Compare August 16, 2021 13:41
@axic axic marked this pull request as ready for review August 16, 2021 13:46
@axic axic force-pushed the description-header branch from 27e2844 to 8e80f46 Compare August 16, 2021 13:48
@eth-bot eth-bot enabled auto-merge (squash) August 16, 2021 13:49
@axic
Copy link
Member Author

axic commented Aug 16, 2021

@MicahZoltu this still needs a manual merge from you 😅

@axic
Copy link
Member Author

axic commented Aug 17, 2021

Blocked by ethereum/eipv#28 😭

All eyes are on you @lightclient 🙏

@axic axic force-pushed the description-header branch from 8e80f46 to 3b5cd36 Compare August 17, 2021 19:51
@axic axic force-pushed the description-header branch from 3b5cd36 to 617b06d Compare August 17, 2021 21:24
@axic axic requested review from MicahZoltu and lightclient August 17, 2021 21:25
@axic axic force-pushed the description-header branch from 617b06d to 1de8caf Compare August 17, 2021 21:25
@axic axic force-pushed the description-header branch from 1de8caf to 9e91d4a Compare August 17, 2021 21:43
@axic axic requested a review from lightclient August 17, 2021 21:44
@MicahZoltu MicahZoltu disabled auto-merge August 17, 2021 23:04
@MicahZoltu MicahZoltu merged commit 1bfcf0c into ethereum:master Aug 17, 2021
@axic axic deleted the description-header branch August 17, 2021 23:08
@ethereum ethereum deleted a comment Aug 21, 2021
@ethereum ethereum deleted a comment Aug 21, 2021
@ethereum ethereum deleted a comment Aug 21, 2021
@ethereum ethereum deleted a comment Aug 21, 2021
@ethereum ethereum deleted a comment Aug 21, 2021
@axic axic mentioned this pull request Sep 19, 2021
PhABC pushed a commit to PhABC/EIPs that referenced this pull request Jan 25, 2022
* Add description field to the EIP header

* Update 2718

* Move description rendering to below the title

* Remove the simple summary from the template

This has been removed from EIP-1 on 15-09-2019 in the PR ethereum#2186.

* Update title/description/abstract with new recommendation

* Mention length limit of description
wjmelements added a commit to wjmelements/EIPs that referenced this pull request Mar 24, 2022
eth-bot pushed a commit that referenced this pull request Mar 24, 2022
PowerStream3604 pushed a commit to PowerStream3604/EIPs that referenced this pull request May 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants