roles
roles copied to clipboard
bisq-network
Bisq Maintainer
Docs: https://bisq.wiki/Bisq_Maintainer Team: @bisq-network/bisq-maintainers
I've assigned @ripcurlx to this role, reflecting the work that he is already doing on Bisq's UI. This is still a role that we'd like additional developers to take on, though. There is plenty of work to be done!
I've renamed this role from JavaFX Developer => Bisq Desktop Maintainer. @ripcurlx, as the primary role owner here, please report monthly as you see fit.
2018.05 report
Reviewing and merging of PRs and release preparations for v0.7.0
/cc https://github.com/bisq-network/compensation/issues/71
2018.06 report
Reviewing and merging of PRs and release preparations for v0.7.1
/cc bisq-network/compensation#84
2018.06 report
Nothing to report. Note that I plan to remove myself from the set of desktop maintainers.
/cc bisq-network/compensation#89
@ripcurlx wrote
Reviewing and merging of PRs
I think it's important that we account separately for maintainer work and PR review work. I've written about this in the WIP Roles doc, see https://deploy-preview-46--bisq-docs.netlify.com/roles.html#maintainer. I'm +1'ing your compensation request as-is, but something to keep in mind as you review that doc.
I've updated the @bisq-network/desktop-maintainers team and the description of this issue to reflect that @ManfredKarrer and @ripcurlx are Bisq Desktop maintainers now, and that I've removed myself.
@cbeams Regarding PR reviewer work. Should this be part of the general contributions delivered section in a compensation request referencing PRs reviewed?
@ripcurlx wrote:
Regarding PR reviewer work. Should this be part of the general contributions delivered section in a compensation request referencing PRs reviewed?
Yes. Please see the new https://docs.bisq.network/roles.html#maintainer-duties and https://docs.bisq.network/roles.html#compensation documentation, and provide any feedback in the related proposal at https://github.com/bisq-network/proposals/issues/30, thanks.
Renamed to "Bisq Maintainer" to reflect the monorepo reconsolidation in bisq-network/bisq#1650 and added @cbeams as a member of @bisq-network/bisq-maintainers (which has also been renamed) to reflect his maintainer role over the assets subproject.
2018.09 report
This month we reconsolidated all code repositories into one mono repo to make it easier for developers to work across modules and switched to Java 10. No release this month.
/cc bisq-network/compensation#126
2018.10 report
We've created a release branch for 0.9.0 this time before merging to master to make it easier to cooperate and developer test the work happening in the redesign and DAO in parallel.
/cc bisq-network/compensation#148
2018.11 report
We've been working on and syncing the release branch for 0.9.0 to make it easier to cooperate and developer test the work happening in the redesign and DAO in parallel. This month also release preparations and testing for v0.9.0 is part of my Desktop Maintainer contribution.
/cc bisq-network/compensation#177
2018.12 report
We had a busy December with two releases (v0.9.0 and v0.9.1). Release preparations and testing is part of my Desktop Maintainer contribution this month.
/cc bisq-network/compensation#195
2019.01 report
We had again a busy month with two releases (v0.9.2 and v0.9.3). We also added the stale app to help cleaning up our issue repository. It will mark issues that are inactive for 90 days as stale and close it without activity 7 days later. Excluded from becoming stale are issues with following labels:
- a:bug
- re:security
- re:privacy
- re:Tor
- in:dao
- $BSQ bounty
- good first issue
- Epic
Release preparations and testing is part of my Desktop Maintainer contribution this month.
/cc bisq-network/compensation#206
2019.02 report
We released v0.9.4. Release preparations and testing is part of my Desktop Maintainer contribution this month.
/cc bisq-network/compensation#224
2019.03 report
We released v0.9.5. Release preparations and testing is part of my Desktop Maintainer contribution this month.
/cc bisq-network/compensation#247
2019.04 report
We released v1.0.0 and v1.0.1. Release preparations and testing is part of my Desktop Maintainer contribution this month.
/cc bisq-network/compensation#269
Cycle 2 report
Took over as secondary Bisq maintainer. I have merged PRs and done minor git admin.
https://github.com/bisq-network/compensation/issues/293
Cycle 2 report
We released v1.1.2.
Release preparations and testing is part of my Desktop Maintainer contribution for this cycle.
Cycle 3 report
No release this cycle as we are still working on the account signing feature. Probably we'll release one more version before this feature as a couple of PRs already piled up.
Cycle 3 report
All maintainer work is included under other posts for compensation, as appropriate.
https://github.com/bisq-network/compensation/issues/311
I just added @freimair as a Bisq maintainer to increase the issue and PR throughput.
Cycle 4 report
All maintainer work is included under other posts for compensation, as appropriate.
@ripcurlx handled releases, helped with testing and preparation.
bisq-network/compensation#325
Cycle 4 report
We released v1.1.3 and v1.1.4.
Release preparations and testing is part of my Desktop Maintainer contribution for this cycle.
/cc https://github.com/bisq-network/compensation/issues/269
Cycle 5 report
We released v1.1.5.
Release preparations and testing is part of my Desktop Maintainer contribution for this cycle.
/cc https://github.com/bisq-network/compensation/issues/269
Cycle 5 report
All maintainer work is included under other posts for compensation, as appropriate.
Didn't help much with the latest release, thanks to @ripcurlx for all the work
https://github.com/bisq-network/compensation/issues/356