For May 2018 #71
Comments
|
@cbeams Is there an easy way to get all merged PRs for a release of an user? 😀 |
Sorry, @ripcurlx, when I first read this, I thought it might have been a joke, but now I realize it may have been serious. If the latter is the case, what do you mean by "for a release of a user"? Ah... do you mean all PRs merged that were part of a given release that involved a certain user? That is possible, but to do it via the GitHub interface alone, it would require that all the PRs had the release field set, and we haven't been doing that very consistently (unless something has changed in bisq-desktop lately). |
|
And @ripcurlx, there seems to be a discrepancy with the BSQ requested above. In
but in
Could you clarify? Thanks. |
|
Regarding the release: Yes, it was actually a real question, as I have to do it manually and I guess it will be (hopefully) more and more PRs in the future. But it's fine also to do it manually atm, I just was curious if there is an easier way for it. Regarding the compensation: 9840 BSQ are for the PR's and testing for v0.7.0 release. It was for the work I did for it last month. The remaining 4860 BSQ are for the roles performed this month and communication with contributors,... Does this answer your questions? |
Is this delivered work? I don't think we've addressed it explicitly anywhere. It's a tough call. You could make the argument that it's directly valuable work on its own, and you could make the argument that it's all part of the process of delivering finished work to end users. I tend toward the latter definition. That it is a cost of collaborating effectively, not an end-user good on its own. From a paying and/or stakeholding Bisq user's perspective, I want there to be as little "communicating with contributors" as possible required in order to produce valuable features. I certainly don't want to economically incentivize the act of "communicating with contributors" per se; I want to incentivize the delivery of useful software into my hands. So from this perspective, as a Bisq user, I would want Bisq contributors to bundle their time and effort into their compensation requests in an undifferentiated way. This will allow me to vote consistently for the work that delivers more value at less overall cost, thereby rewarding very efficient contributors who don't require a lot of "communicating", or more precisely, require a minimum of it when compared with other contributors. |
|
Note that I'm not saying that you shouldn't claim this amount of BSQ, but that how we account for it matters. The fact is that you're doing work that is presumably required in order to produce some end result of finished work to users. Should this work be accounted for when that end work gets produced? That might be hard to keep track of which conversations with which contributors led to which work getting done. So that might not be feasible. Should it be accounted for as part of the work of being a 'Maintainer' for different given repositories and projects? That might work well. It's pretty easy, because if we route Slack conversations and GitHub issues well, all the conversations you're having with contributors should already be pretty well aligned with the roles you play, e.g. being one of the @bisq-network/exchange-maintainers. And it would be pretty useful to how much of this kind of cost is going into each of our different roles. We could ask why some are so much more expensive than others, and we could share knowledge about how to transfer information faster, create better onboarding experiences for new contributors, better build dev environment rollouts, whatever helps. |
|
What I wanted to point out with my comment above is, that fulfilling a role has communication efforts as well and is also required in some roles to fulfill it properly. Not every role needs it, but some roles (e.g. forum admin) might be a lot about communication. Would it help if I would split up the BSQ for each role? I could do this for next months if this would help how this value is spread up over each role. |
|
As two didn't vote for my CR this month so far I'd like to talk about the reasons why, so I can answer any open questions. I guess the concerns are about the efforts on my roles performed this month. At the moment I calculate the amount of BSQ for these roles based on the effort/time they consume each month. Coming up with a value of these roles that is not effort based but result based is kind of tricky IMO, but I'm happy to discuss any ideas how we want to do this this month 😄 |
|
I didn't vote at all this month so if you count that as a non vote it was just because I forgot to vote. |
|
Closing as complete, see #70 (comment). |
|
@sqrrm Wasn't about the fact if you haven't voted at all, just for two who voted but not for this CR. I'm happy to talk about everything if someone thinks something is not clear or not justified, that's what this process is all about 😄 |
|
I assume those who did not had the time to validate the request preferred to not vote, which is a good strategy. Otherwise of course its good that they speak up if they disagreed to give feedback.... |
Summary
Contributions delivered
Following PRs have been released with v0.7.0.
bisq-desktop
bisq-core
bisq-common
Including running full test suite for v0.7.0
For these efforts I request 9840 BSQ in total.
Contributions in progress
Release preparations, updates and bug fixes for v0.7.1
Roles performed
The text was updated successfully, but these errors were encountered: