<p><a class="user-mention" data-hovercard-user-id="29404408" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/marco4444">@marco4444</a> Don't be disheartened, I don't mean to just push the issue around. There is currently quite a lot of reorganization of how we do things around Bisq. There are many new contributors and hopefully more to come and finding a good work flow will help with that. My comment was more to figure out how we handle new issues and not really on topic, sorry for that.</p>
<p>Regarding the implementation. Someone needs to take ownership for it to happen, and since it affects the trading protocol some caution should be taken, even though it seems like a fairly easy thing to do. In my opinion it's best to create an issue in bisq-core and start a discussion on implementation there. I created an issue <a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="317820256" data-permission-text="Issue title is private" data-url="https://github.com/bisq-network/bisq-core/issues/101" href="https://github.com/bisq-network/bisq-core/issues/101">bisq-network/bisq-core#101</a></p>

<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/proposals/issues/17#issuecomment-384458152">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AkpZtoIEhUd1l-tJ2aksXm3PvaZkD3KQks5tsP2jgaJpZM4TWNG1">mute the thread</a>.<img src="https://github.com/notifications/beacon/AkpZtqHxPORp6Dx5ttOBXs0Du7fKWaryks5tsP2jgaJpZM4TWNG1.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/proposals/issues/17#issuecomment-384458152"></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/proposals","title":"bisq-network/proposals","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/proposals"}},"updates":{"snippets":[{"icon":"PERSON","message":"@sqrrm in #17: @marco4444 Don't be disheartened, I don't mean to just push the issue around. There is currently quite a lot of reorganization of how we do things around Bisq. There are many new contributors and hopefully more to come and finding a good work flow will help with that. My comment was more to figure out how we handle new issues and not really on topic, sorry for that.\r\n\r\nRegarding the implementation. Someone needs to take ownership for it to happen, and since it affects the trading protocol some caution should be taken, even though it seems like a fairly easy thing to do. In my opinion it's best to create an issue in bisq-core and start a discussion on implementation there. I created an issue bisq-network/bisq-core#101"}],"action":{"name":"View Issue","url":"https://github.com/bisq-network/proposals/issues/17#issuecomment-384458152"}}}</script>