[bisq-network/compensation] For Cycle 15 (#627)

[elkimek]

<!--
Compensation requests have a specific format that enables them to be evaluated by a bot for more efficient budgeting. Please make sure you stick to the template. A linter will evaluate your request after you remove [WIP] from the issue title and notify you of any issues.

See the following link for details:
https://bisq.wiki/Making_a_compensation_request

Feel free to browse other requests if you're not sure about something, or reach out in #compensation on Keybase (https://keybase.io/team/bisq).
-->


## Summary

> _Specify the total amount of BSQ you are requesting, along with the USD total and BSQ/USD rate (don't include the brackets!):_

- **BSQ requested**: **`76.92`** <!-- [BSQ amount] should be: USD amount / BSQ rate -->
- USD requested: 50 <!-- [USD amount] should be: total of all contributions listed in "contributions delivered" table below -->
- BSQ rate: 0.65 USD per BSQ <!-- [rate] should be the rate used to determine the BSQ amount above, as specified in the cycle's rate announcement (https://bisq.wiki/Compensation_Maintainer#Announce_BSQ-USD_rate) -->
- Previous compensation request (if applicable): #  <!-- Link to last compensation request submitted -->


## Contributions delivered

> _Add contributions you have [delivered](https://github.com/bisq-network/proposals/issues/19) and roles you have performed here as new rows in the table below. Role line-items should include an asterisk (*) in the team column._

| Title | Team | USD | Link | Notes |
| --- | --- | --- | --- | --- |
| Writer | Growth | 50 | https://www.alzashop.com/p2p-exchange-bisq-how-to-buy-and-sell-bitcoin-guide | EN version |
| Writer | Growth | 0 | https://www.alza.cz/burza-bisq-jak-nakoupit-a-prodat-bitcoin-navod | CZ version (original) |
| Writer | Growth | 0 | https://www.alza.sk/burza-bisq-ako-nakupit-a-predat-bitcoin-navod | SK version |

- **About the work**:

I strongly believe bitcoin was never ment to be a KYC coin and that its main value proposition is sovereignty. I'm constantly seeing stronger and stronger informational asymmetry between using Bitcoin as it was designed and as it is marketed by the banking layer in favor of the latter. 

Unfortunately custodial and KYC services are driven by FUD convincing the majority of users that sovereignty is hard and dangerous and the majority is parroting it to the new users. This was my motivation to do a comprehensive write up on Bisq but I realized just a step by step guide would be boring and not many users would really read it. I came up with a concept of wrapping the core in sovereignty nudge (chapters 1, 11 and 12) and it seems to be working. According to GA the czech version has ~38 minutes average reading time which tells me the readers are actually reading it and not just scrolling it through or skipping from start to the end.

You may wonder why ( and this is not an add) an e-tailer would produce such an article. Alza is very progressive company in all directions and we produce ton of content on everything be it our own hardware reviews (that's my main job there) or guides how to _____ . Beside that, we are Bitcoin enthusiasts and we accept bitcoin payments. I'm the main editor of the Bitcoin Alza section and I took it under my wing because I saw it as an interesting asymmetric channel to approach different kind of people who would not be looking for high quality articles this way.

Sidenote: If anyone would like to translate it to HU/DE, we also have  domains where we could publish that. Feel free to contact me.

**This request is a claim for the [hat-tip bounty]**
 
<!-- 


Each contribution should be a new line-item in the table above. 

Title - optional, string.
Team - optional, must one of the following: admin, dev, growth, ops, support (case-insensitive). If the line-item is for a role, please add a `*`. See Example 2 below.
USD - optional, number. Please do not specify 'USD', as the column title makes units clear.
Link - optional, string.
Notes - optional, string.

Example 1 - typical contribution:

| Add local Bitcoin node configuration detection | dev | 240 | https://github.com/bisq-network/bisq/pull/3982

Example 2 - role (note the asterisk):

| Community manager | growth* | 400 | https://github.com/bisq-network/roles/issues/95#issuecomment-628431613

Example 3 - list of minor contributions, such as reviews:

| | | | https://github.com/bisq-network/bisq/pull/3968 | This and PRs below too small to be valued separately. See total at bottom.
| | | | https://github.com/bisq-network/bisq/pull/4040
| | | | https://github.com/bisq-network/bisq/pull/4044
| | | | https://github.com/bisq-network/bisq/pull/4048
| | | | https://github.com/bisq-network/bisq/pull/4066
| | dev | 400 | https://github.com/bisq-network/bisq/pull/4062 | Total for items above.

-->


## Contributions in progress

> _Provide links to work you're involved with that is still [in progress](https://github.com/bisq-network/proposals/issues/19). **This section is optional (the linter ignores it),** and is for your own benefit in keeping track of what you're doing and keeping other contributors up to date with the same._


-- 
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/627
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20200720/054d81cf/attachment.html>