<p>Feedback:</p>
<p>I'm not sure how valuable it is just to list the growth calls we did. I think the value of a monthly report is also to recap how our growth efforts went over the month. At a high level, what did we do, how did things go? What worked, what didn't? If we grew, why did we grow? What should we focus on in the month to come? I don't mean to suggest you need to write volumes in each of these reports, they can remain as concise as you like, but I'd like to suggest that we try to impart insight where we can. If you were brand new to Bisq, and wanted to help it grow, and all you read was the last few months of the Growth Maintainer's monthly reports, would you walk away with any insight, ideas about how you might be able to help? I don't want these to be mere, perfunctory "TPS reports", but rather an opportunity to share with each other what we're learning and what we think we need over time.</p>
<p>Nits:</p>
<ul>
<li>Please use <code>2018.04 report</code> title formatting in the future for consistency with other reports.</li>
<li>Please consider back-referencing your compensation request e.g. with "/cc <a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="318833530" data-permission-text="Issue title is private" data-url="https://github.com/bisq-network/compensation/issues/59" href="https://github.com/bisq-network/compensation/issues/59">bisq-network/compensation#59</a>". This kind of round-tripping makes everything that much more discoverable / navigable.</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/42#issuecomment-387311455">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AkpZtq_4Yh8mIawg5sAmJ4DmWpV4Z2zUks5twUlpgaJpZM4QycXj">mute the thread</a>.<img src="https://github.com/notifications/beacon/AkpZtpxj9ggABv_AJK_rrVYslSDp75MIks5twUlpgaJpZM4QycXj.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/42#issuecomment-387311455"></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 #42: Feedback:\r\n\r\nI'm not sure how valuable it is just to list the growth calls we did. I think the value of a monthly report is also to recap how our growth efforts went over the month. At a high level, what did we do, how did things go? What worked, what didn't? If we grew, why did we grow? What should we focus on in the month to come? I don't mean to suggest you need to write volumes in each of these reports, they can remain as concise as you like, but I'd like to suggest that we try to impart insight where we can. If you were brand new to Bisq, and wanted to help it grow, and all you read was the last few months of the Growth Maintainer's monthly reports, would you walk away with any insight, ideas about how you might be able to help? I don't want these to be mere, perfunctory \"TPS reports\", but rather an opportunity to share with each other what we're learning and what we think we need over time.\r\n\r\nNits:\r\n\r\n - Please use `2018.04 report` title formatting in the future for consistency with other reports.\r\n - Please consider back-referencing your compensation request e.g. with \"/cc bisq-network/compensation#59\". This kind of round-tripping makes everything that much more discoverable / navigable.\r\n\r\n"}],"action":{"name":"View Issue","url":"https://github.com/bisq-network/roles/issues/42#issuecomment-387311455"}}}</script>