[rfc-i] GitHub references

Bob Hinden bob.hinden at gmail.com
Thu Mar 8 13:46:58 PST 2018


Heather,

> On Mar 8, 2018, at 11:59 AM, Heather Flanagan (RFC Series Editor) <rse at rfc-editor.org> wrote:
> 
> 
> Hello all,
> 
> The RFC Editor is proposing to update the reference format for
> informative references to GitHub repositories (noting that GitHub
> repositories are not currently accepted as normative references).
> Specifically, we propose to standardize on the following:
> 
> 1) No author name(s). A repository may have many contributors, and there
> is no way to easily determine major contributors versus all others.
> 
> 2) The title of the repository will be whatever is in the top left of
> the main repository page.
> 
> 3) The URL will be to the main page of the repository.
> 
> 4) The reference will not include any particular commit hash. It will
> include the date of the last commit at the time the RFC-to-be is edited.
> 
> So:
> 
> OLD
>    [mpingSource]
>               Fan, X., Mathis, M., and D. Hamon, "Git Repository for
>               mping: An IP Level Performance Diagnostic", Sept 2013,
>               <https://github.com/m-lab/mping>.
> 
> NEW
>    [mpingSource]
>               "mping", July 2016, <https://github.com/m-lab/mping>.

Why not also include the full title, for example:

   [mpingSource]
              "mping: An IP Level Performance Diagnostic", July 2016, <https://github.com/m-lab/mping>.

I think that would make the reference more descriptive.

Thanks,
Bob


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 529 bytes
Desc: Message signed with OpenPGP
URL: <http://www.rfc-editor.org/pipermail/rfc-interest/attachments/20180308/89929068/attachment.asc>


More information about the rfc-interest mailing list