Closed staheri14 closed 1 year ago
Thank you @rymnc and @s1fr0 for your comments, please see the revised version of the post based on the comments in https://github.com/vacp2p/research/pull/143/commits/cd6791e42a20acc866589d3fb87a0e13ca95e4ea and https://github.com/vacp2p/research/pull/143/commits/985457aef8aaf4554fe62c5c21750ddc4edaf5a8.
Given that:
1) We didn't get this out before Devcon 2) We have my talk at Devcon that'll be up as a write-up soon, as well as Franck's https://github.com/vacp2p/vac.dev/pull/78/ being out soon 3) We are gonna "rebrand" as RLNP2P
Perhaps we should save this write-up until we've done some work on RLNP2P?
I think what s1fr0 is getting at is that this should be mentioned in the text. A question in a PR review of a text is usually feedback on the text itself, and just answering the PR comment doesn't actually improve the text...
I agree and that is what I do, but this question didn't seem to require an update on the text as the separation of the two articles is pretty evident as the publication venues and links are not the same. Will stress on this more by putting the title of the articles. Please check https://github.com/vacp2p/research/pull/143/commits/5528be68422ff1dba89134cd2d8453f58c326d26.
Perhaps we should save this write-up until we've done some work on RLNP2P?
Fine for me, then going to close this PR and keep the write-up locally until the due time comes.
This is to address the last part of the second testnet tasks list i.e.,
The relation to operator outreach will be clarified separately in the operator outreach document.
This post can be published as a forum post or a research post. Open to suggestions. I opened it as a PR here to ease the review process, once the decision reached about where to publish this doc, I'll move it to the relevant repo accordingly.