<p>Thanks, <a class="user-mention" data-hovercard-user-id="36703333" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/alfsbs">@alfsbs</a>. A couple minor nits:</p>
<ul>
<li>
<p>Please use <code>2018.04 report</code> title formatting for these report comments for consistency with everyone else's reports.</p>
</li>
<li>
<p>Please backreference your your compensation report issue with a mentioning like the following: <a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="319341808" data-permission-text="Issue title is private" data-url="https://github.com/bisq-network/compensation/issues/67" href="https://github.com/bisq-network/compensation/issues/67">bisq-network/compensation#67</a>. I and other do this with a <code>/cc bisq-network/compensation#67</code> at the bottom of the report comment. Doing this ensures bi-directional linkage between compensation request issues and role report comments, which is quite helpful for voting stakeholders as they review everyone's requests. Have a look at the timeline of your compensation request issue now, and you'll see the effect that the issue reference I just created has on its timeline.</p>
</li>
</ul>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/bisq-network/roles/issues/38#issuecomment-387371388">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AkpZtl2xdxpVZ5gnikgGvtM2XR0ubgwvks5twYCAgaJpZM4PMLHK">mute the thread</a>.<img src="https://github.com/notifications/beacon/AkpZtlMCnLdRQUNZinMYZWu0hFtp2Jitks5twYCAgaJpZM4PMLHK.gif" height="1" width="1" alt="" /></p>
<div itemscope itemtype="http://schema.org/EmailMessage">
<div itemprop="action" itemscope itemtype="http://schema.org/ViewAction">
  <link itemprop="url" href="https://github.com/bisq-network/roles/issues/38#issuecomment-387371388"></link>
  <meta itemprop="name" content="View Issue"></meta>
</div>
<meta itemprop="description" content="View this Issue on GitHub"></meta>
</div>

<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/bisq-network/roles","title":"bisq-network/roles","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/bisq-network/roles"}},"updates":{"snippets":[{"icon":"PERSON","message":"@cbeams in #38: Thanks, @alfsbs. A couple minor nits:\r\n\r\n - Please use `2018.04 report` title formatting for these report comments for consistency with everyone else's reports.\r\n\r\n - Please backreference your your compensation report issue with a mentioning like the following: bisq-network/compensation#67. I and other do this with a `/cc bisq-network/compensation#67` at the bottom of the report comment. Doing this ensures bi-directional linkage between compensation request issues and role report comments, which is quite helpful for voting stakeholders as they review everyone's requests. Have a look at the timeline of your compensation request issue now, and you'll see the effect that the issue reference I just created has on its timeline.\r\n"}],"action":{"name":"View Issue","url":"https://github.com/bisq-network/roles/issues/38#issuecomment-387371388"}}}</script>