[bisq-network/dev] Dev Team Announcements (#1)

[Christoph Atteneder]

As @cbeams announced in our recent [Q1 2020 Update](https://youtu.be/oImSdIAsywA), Bisq is improving management of the DAO by organizing into teams, and dev is one of the 5 new teams. I'll be serving as the ops team lead to help coordinate the budget, compensation, roles, etc..

## Mission

The mission of the dev team is to provide tools that enable all Bisq network participants to execute their use cases easy, fast and reliable.

## TODOs

To accomplish our mission, we will need to:

1. Create actionable metrics that provide a baseline and can be revisited to measure success of our actions
2. Define development priorities that are reflected in issues and PRs making it clear what kind of contribution is up for compensation and which isn’t
3. Plan a budget that supports maintenance of existing tools and allows development of new features/tools that are in line with our current priorities
4. Create a process to reassign roles if role owners do not reliably operate or communicate

### Metrics

We plan to collect (by app version) for the Bisq desktop app:
- Number of active nodes (nodes that are part of the network)
- Number of available offers
- Number of trades

Based on these numbers we can create actionable KPIs that are discussed in detail in https://github.com/bisq-network/bisq/issues/3916.

Of course it won’t be a perfect solution with control groups, but it is as good as it gets without violating our user’s privacy in any way.

### Priorities

As mentioned in our mission statement above Bisq should be:
1. Easy-to-use (Usability, UI)
2. Fast (Trade process, performance,…)
3. Reliable (Critical bug fixes, privacy issues)

We will focus in a first step on our most critical „core use cases“. A „core use case“ is any set of actions that a user must be able to complete in order to successfully trade and/or manage funds using Bisq.

A "critical bug" is any bug or other issue that:
- impedes users from completing a core use case in Bisq, and/or
- repeatedly lands users in support, and/or
- puts user funds or privacy at risk

As it won’t be possible to come up with a bulletproof description of what falls within our priorities, it is advised that if you are seeking for compensation, you should contact me upfront before committing to any work. I’ll label PRs and issues that fall within our priorities with a label `is:priority`. This means any work on this will be up for compensation. 

### Budget

After analyzing previous compensation requests and talking to active dev contributors I came up with following numbers.

| Item | Amount |
|:------|---------:|
|Development| $20000|
|Review|$5000|
|Testing|$1000|
|Release|$1000|
|Support|$2000|
|**Total**|**$29000**|

As it is very hard to estimate development efforts up-front it will be a learning process from cycle to cycle how to balance the budget.  We’ll have a fixed total budget of $29k per cycle. If compensation requests that are within our current priorities exceed our budget in a cycle it will be decided based on upfront communication and timing which will be moved to the next cycle and which will be compensated in the current one. If we spend less we'll have more budget available in the next cycle.

## Assigned Roles

Initially the assigned roles will mostly stay the same:

* @ripcurlx (bisq-dev, bisq-maintainer, design-maintainer, markets-maintainer)
* @wiz (bisq-dev, android-maintainer, markets-maintainer)
* @sqrrm (bisq-dev, bish-maintainer, explorer-maintainer)
* @freimair (arch-linux-maintainer
* @pedromvpg (design-maintainer) 
* Remaining bisq-devs: @cbeams, @devinbileck, @dmos62, @freimair, @niyid, @rafaelpac, @stejbac, @beingindot, @chimp1984

Unassigned roles: bitcoinJ-maintainer, netlayer-maintainer

The current up-to-date list will be maintained at https://github.com/orgs/bisq-network/teams/dev/teams 

## Keybase dev channels

We do have already an existing _#dev_ channel for development related discussions and a _#dev-onboarding_ channel for new Bisq devs.

## Thank you

Thanks everyone who participated already in making Bisq such a great tool! 

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/orgs/bisq-network/teams/dev/discussions/1
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20200211/add28c9b/attachment.html>