<br>
As we mentioned, we are not in a hurry to receive this compensation. We<br>
thought that we had to meet some kind of July deadline, and put<br>
submitted it now.<br>
We will change it to whichever month you wish.<br>
i<br>
CCG<br>
<br>
gpg: B03B 3301 83F3 A497 F433 CCD3 4424 816B 8323 5B37<br>
<br>
On 07/30/2018 06:46 AM, Christoph Atteneder wrote:<br>
> @initCCG <https://github.com/initCCG> Thanks for your detailed<br>
> compensation request and contribution! The only thing I want to discuss<br>
> is, if we should/want to have the same incentive structure as for<br>
> development work. For development, only code that is actually shipped in<br>
> a release is up for compensation. So the pull request might be merged to<br>
> master already, but not shipped and thus not available to the end user.<br>
> The reason for this is, that we only want to compensate anything that<br>
> has direct end user value. If we do it for translations the same, it<br>
> would mean you could do a compensation request after next release, which<br>
> will happen this month. What do you think?<br>
> <br>
> —<br>
> You are receiving this because you were mentioned.<br>
> Reply to this email directly, view it on GitHub<br>
> <https://github.com/bisq-network/compensation/issues/95#issuecomment-408763361>,<br>
> or mute the thread<br>
> <https://github.com/notifications/unsubscribe-auth/Am28qesJQwlK6xsAMjFpaiueo5SbcnTYks5uLqvcgaJpZM4VlVHb>.<br>
> <br>
<br>


<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/compensation/issues/95#issuecomment-409087400">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AkpZtjnf_QPSh-taxu_6hymEfadJwCX_ks5uL9bpgaJpZM4VlVHb">mute the thread</a>.<img src="https://github.com/notifications/beacon/AkpZtll48ZVxzfjtwHSQxXqDJRPihallks5uL9bpgaJpZM4VlVHb.gif" height="1" width="1" alt="" /></p>
<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/bisq-network/compensation","title":"bisq-network/compensation","subtitle":"GitHub repository","main_image_url":"https://assets-cdn.github.com/images/email/message_cards/header.png","avatar_image_url":"https://assets-cdn.github.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/bisq-network/compensation"}},"updates":{"snippets":[{"icon":"PERSON","message":"@initCCG in #95: \nAs we mentioned, we are not in a hurry to receive this compensation. We\nthought that we had to meet some kind of July deadline, and put\nsubmitted it now.\nWe will change it to whichever month you wish.\ni\nCCG\n\ngpg: B03B 3301 83F3 A497 F433 CCD3 4424 816B 8323 5B37\n\nOn 07/30/2018 06:46 AM, Christoph Atteneder wrote:\n\u003e @initCCG \u003chttps://github.com/initCCG\u003e Thanks for your detailed\n\u003e compensation request and contribution! The only thing I want to discuss\n\u003e is, if we should/want to have the same incentive structure as for\n\u003e development work. For development, only code that is actually shipped in\n\u003e a release is up for compensation. So the pull request might be merged to\n\u003e master already, but not shipped and thus not available to the end user.\n\u003e The reason for this is, that we only want to compensate anything that\n\u003e has direct end user value. If we do it for translations the same, it\n\u003e would mean you could do a compensation request after next release, which\n\u003e will happen this month. What do you think?\n\u003e \n\u003e —\n\u003e You are receiving this because you were mentioned.\n\u003e Reply to this email directly, view it on GitHub\n\u003e \u003chttps://github.com/bisq-network/compensation/issues/95#issuecomment-408763361\u003e,\n\u003e or mute the thread\n\u003e \u003chttps://github.com/notifications/unsubscribe-auth/Am28qesJQwlK6xsAMjFpaiueo5SbcnTYks5uLqvcgaJpZM4VlVHb\u003e.\n\u003e \n\n"}],"action":{"name":"View Issue","url":"https://github.com/bisq-network/compensation/issues/95#issuecomment-409087400"}}}</script>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/bisq-network/compensation/issues/95#issuecomment-409087400",
"url": "https://github.com/bisq-network/compensation/issues/95#issuecomment-409087400",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
},
{
"@type": "MessageCard",
"@context": "http://schema.org/extensions",
"hideOriginalBody": "false",
"originator": "AF6C5A86-E920-430C-9C59-A73278B5EFEB",
"title": "Re: [bisq-network/compensation] For July 2018 (#95)",
"sections": [
{
"text": "",
"activityTitle": "**initCCG**",
"activityImage": "https://assets-cdn.github.com/images/email/message_cards/avatar.png",
"activitySubtitle": "@initCCG",
"facts": [

]
}
],
"potentialAction": [
{
"name": "Add a comment",
"@type": "ActionCard",
"inputs": [
{
"isMultiLine": true,
"@type": "TextInput",
"id": "IssueComment",
"isRequired": false
}
],
"actions": [
{
"name": "Comment",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n\"commandName\": \"IssueComment\",\n\"repositoryFullName\": \"bisq-network/compensation\",\n\"issueId\": 95,\n\"IssueComment\": \"{{IssueComment.value}}\"\n}"
}
]
},
{
"name": "Close issue",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n\"commandName\": \"IssueClose\",\n\"repositoryFullName\": \"bisq-network/compensation\",\n\"issueId\": 95\n}"
},
{
"targets": [
{
"os": "default",
"uri": "https://github.com/bisq-network/compensation/issues/95#issuecomment-409087400"
}
],
"@type": "OpenUri",
"name": "View on GitHub"
},
{
"name": "Unsubscribe",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n\"commandName\": \"MuteNotification\",\n\"threadId\": 362107355\n}"
}
],
"themeColor": "26292E"
}
]</script>