[bisq-network/compensation] For January - April 2018 (#61)

Chris Beams notifications at github.com
Mon Apr 30 14:25:15 UTC 2018


Thanks @blabno, great to see your first compensation request after all this time!

Not sure whether you've caught up with bisq-network/proposals#19 yet, but most of the PRs above have not yet actually been _delivered_ per the definition of that term in the proposal.

We can see, for example, that bisq-network/bisq-desktop#1302 _was_ delivered in v0.6.5:

```
$ git log --grep 'Merge pull request #1302' --pretty=format:%H | xargs git tag --contains
v0.6.5
v0.6.6
v0.6.7
```

But other bisq-desktop PRs listed above have not shipped in any release yet, and thus have _not_ been delivered, e.g.:

```
$ git log --grep 'Merge pull request #1311' --pretty=format:%H | xargs git tag --contains
[no tags listed]
```

So, in keeping with the proposal, could you create a second compensation request, titled `[WIP] For May 2018` and move `bisq-desktop` PR entries 1311–1416 to it? These will all be delivered with the forthcoming v0.7.0, which will surely ship by the time we do our May voting.

With regard to the `bisq-core` / `bisq.asset` PRs, these are an interesting case, because while the software itself has not been delivered in a release, the _value_ of these changes has indeed been delivered in the sense that the target users (people who want to list an asset) have been able to use this new infrastructure and documentation, and indeed they have in fact been using it. So I'd say keep these PRs in for this month if you like. A bit of an unusual scenario, this one, but an interesting exploration of what it means to deliver value to users in any case. You can also feel free to move these to the May PR, too. Just wanted to walk through the thinking a bit.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/compensation/issues/61#issuecomment-385413796
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20180430/13c72d81/attachment-0002.html>


More information about the github mailing list