Skip to content

Conversation

@lidel
Copy link
Member

@lidel lidel commented Aug 13, 2022

@yiannisbot @willscott ok to add the more recent paper to https://docs.ipfs.tech/concepts/further-reading/academic-papers/?
Any preference with regard to ordering?
Anything else that should be added?

@lidel lidel requested review from 2color and johnnymatthews August 13, 2022 02:33
Copy link
Contributor

@willscott willscott left a comment

Choose a reason for hiding this comment

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

Sounds good. This order looks good. Maybe worth noting that this one has been peer-reviewed / published at SIGCOMM '22?

@2color
Copy link
Member

2color commented Aug 15, 2022

I think the current order makes sense, having the original IPFS paper at the top. Since the papers are not ordered by date, I would add in brackets the publication year.

Copy link
Contributor

@johnnymatthews johnnymatthews left a comment

Choose a reason for hiding this comment

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

Looks good!

@filecorgi
Copy link
Contributor

  • Image optimization came back clean!
  • Vuepress build was successful!

Copy link
Contributor

@TMoMoreau TMoMoreau left a comment

Choose a reason for hiding this comment

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

Looks good.

@yiannisbot
Copy link
Member

Yup, looks good to me as well! Thanks @lidel for catching this. A couple of thoughts (non-blocking for this PR):

  • The order looks good.
    • It makes sense to have the original whitepaper always on top.
    • It makes sense to have our Sigcomm paper second as it's the most related to IPFS itself and is also from our team.
  • It's a good idea to add (in parentheses at the end of the paper title?) where the paper was published together with the year. For the whitepaper, this can be "Original IPFS Whitepaper" or something similar.

@TMoMoreau
Copy link
Contributor

@yiannisbot Good suggestions, could you open up a separate issue for it? Just in an attempt to keep this PR as clean and simple as possible :)

@lidel lidel merged commit 671ed5b into main Aug 17, 2022
@lidel lidel deleted the add-trautwein2022a.pdf branch August 17, 2022 15:07
@lidel
Copy link
Member Author

lidel commented Aug 17, 2022

Let's continue in #1247

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.

8 participants