-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refer to specific versions of IL-RFCs #246
Conversation
"Evan Schwartz", | ||
"Stefan Thomas", | ||
"Ben Sharafian" | ||
"Interledger Community" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
would this not be the publisher instead of the author?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@michielbdejong since we have not tracked the editors on these docs directly I have used the committers as the authors list
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you have to name individual community members, then looking at https://github.com/interledger/rfcs/commits/master/0003-interledger-protocol/0003-interledger-protocol.md, for e.g. IL-RFC-3 they would be, in reverse chronological order, Stefan, me, Jason, Andrew, you, Sylvain, and Evan (not Ben).
For IL-RFC-15, looking at https://github.com/interledger/rfcs/commits/master/0015-ilp-addresses/0015-ilp-addresses.md, it would be (again in reverse chronological order): me, you, and Rome (not Stefan, not Evan).
For IL-RFC-26 you would need to look at https://github.com/interledger/rfcs/commits/master/0026-payment-pointers/0026-payment-pointers.md - it would be just you and not Ben.
So which committers did you look at, @adrianhopebailie? I get at least different results than you did. And even then, I think we should not pretend that Interledger was "authored" by whoever updates the RFCs, it sidelines a lot of other people, and doesn't do right to our community spirit?
@marcoscaceres Is it a hard requirement of w3c documents that references name a list of specific humans as authors? Can this document not reference any community-authored documents, in the way I proposed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@michielbdejong as I said, this may be wrong as I haven't updated those for some time.
And even then, I think we should not pretend that Interledger was "authored" by whoever updates the RFCs, it sidelines a lot of other people, and doesn't do right to our community spirit?
I agree with this sentiment, I hadn't really thought about it that way when the committers list was still small.
Let me investigate some options
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it is most correct to leave the names of the authors. These lists may be out of date but they should reflect the list of committers on each spec.
@@ -28,39 +28,33 @@ | |||
localBiblio: { | |||
"interledger-protocol": { | |||
title: "The Interledger Protocol" | |||
, href: "https://interledger.org/rfcs/0003-interledger-protocol/" | |||
, href: "https://interledger.org/rfcs/0003-interledger-protocol/draft-9.html" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
] | ||
, status: "Interledger RFC" | ||
}, | ||
"interledger-addresses": { | ||
title: "Interledger Addresses" | ||
, href: "https://interledger.org/rfcs/0015-ilp-addresses/" | ||
, href: "https://interledger.org/rfcs/0015-ilp-addresses/draft-2.html" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
] | ||
, status: "Interledger RFC" | ||
}, | ||
"payment-pointers": { | ||
title: "Payment Pointers" | ||
, href: "https://interledger.org/rfcs/0026-payment-pointers/" | ||
, href: "https://interledger.org/rfcs/0026-payment-pointers/draft-1.html" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
] | ||
, status: "Interledger RFC" | ||
}, | ||
"simple-payment-setup-protocol": { | ||
title: "Simple Payment Setup Protocol" | ||
, href: "https://interledger.org/rfcs/0009-simple-payment-setup-protocol/" | ||
, href: "https://interledger.org/rfcs/0009-simple-payment-setup-protocol/draft-3.html" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
@michielbdejong this PR will be unnecessary once tobie/specref#436 is merged as I will remove the |
Continuation of w3c/webpayments#246
Continued in interledger/specref#1 |
No description provided.