Skip to content

EIP editors should explain the external link policy to new authors #5597

@xinbenlv

Description

@xinbenlv

Proposed Change

Dear editors, here is an example of comment that I like to suggest against:

No external links

There is nothing personal, I am just trying to voice suggestion against such editorial practice.

I suggest EIP editors avoid leaving a simple comment like this above, especially towards new authors who don't necessarily know how to challenge editorial comment.

Please note that, per
EIP-1 shows the current policy in EIP-1

Links to external resources SHOULD NOT be included. External resources may disappear, move, or change unexpectedly.

Which is "SHOULD NOT" but not "MUST NOT" pursuant to RFC 2729
Please kindly allow authors to understand it's ok for them to include links when necessary given the current policy.

I am making it a EIP issue so I can easily reference in other of my comments.

I also think it's good for an Editor to set a good example about following EIP-1, and about understanding of "SHOULD" vs "MUST" in their editorial contributions

FYI: @axic, @Pandapip1, @gcolvin, @lightclient, @SamWilsn if my understanding of the current policy is incorrect.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions