You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Specify the amount of BSQ you are requesting, and the BSQ address that amount should be paid to:
BSQ amount requested: 11,000
BSQ address: B1Dj1kAGDs4AGh83cPFJBQC7pDubtuZV2ZS
Details
Provide links to the work you are requesting compensation for, along with any comments or explanations that will help stakeholders understand its value.
Development
While getting more and more comfortable with the current UI codebase, I've made some little clean-up tasks on the way.
Setup of Bisq Test Scenarios document and participation in testing for release v0.6
UX
Setup of Bisq Use Cases document as an entry point for every UX/UI person who wants to contribute to Bisq (work in progress).
General moderation of #ux channel.
Growth Hacking
Kickstarted structured process to find the most efficient ways to grow the Bisq platform.
General moderation of #growthhacking channel (https://bisq.network/slack-invite).
Analytics
Google Analytics:
Changed configuration of Google Analytics and Bisq website to be able to monitor conversion goal (Download Bisq client). This analytics will be the baseline for our first #growthhacking (https://bisq.network/slack-invite) experiments. Continuous monitoring of metrics to react to certain issues.
Reporting Spreadsheet:
Added daily volume chart and did some clean-ups on Google Finance live feed. Changed estimation calculation of TV grouped by 19th to 18th sheet and our public Bisq Trading Volume so it will keep up-to-date for a whole month without manual updates.
A full monthly reporting sheet containing our current key metrics and will follow beginning of next month.
Communication and Investigation on volume number discrepancy issue with coin.dance bisq-network/analytics#1 Should be solved soon, if coin.dance applies handling of trades data as from dan-da suggested.
General moderation of #analytics channel.
Other
Setup and maintenance of full core node btc.christophatteneder.com:8333
Communication with contributors
The text was updated successfully, but these errors were encountered:
ripcurlx
changed the title
[DRAFT] For November 2017
For November 2017
Nov 30, 2017
Basic information
Details
Development
While getting more and more comfortable with the current UI codebase, I've made some little clean-up tasks on the way.
[1] bisq-network/bisq#1029
[2] bisq-network/bisq#1024
[3] bisq-network/bisq#1020
Testing
Setup of Bisq Test Scenarios document and participation in testing for release v0.6
UX
Setup of Bisq Use Cases document as an entry point for every UX/UI person who wants to contribute to Bisq (work in progress).
General moderation of #ux channel.
Growth Hacking
Kickstarted structured process to find the most efficient ways to grow the Bisq platform.
General moderation of #growthhacking channel (https://bisq.network/slack-invite).
Analytics
Google Analytics:
Changed configuration of Google Analytics and Bisq website to be able to monitor conversion goal (Download Bisq client). This analytics will be the baseline for our first #growthhacking (https://bisq.network/slack-invite) experiments. Continuous monitoring of metrics to react to certain issues.
Reporting Spreadsheet:
Added daily volume chart and did some clean-ups on Google Finance live feed. Changed estimation calculation of
TV grouped by 19th to 18th
sheet and our public Bisq Trading Volume so it will keep up-to-date for a whole month without manual updates.A full monthly reporting sheet containing our current key metrics and will follow beginning of next month.
Communication and Investigation on volume number discrepancy issue with coin.dance bisq-network/analytics#1 Should be solved soon, if coin.dance applies handling of trades data as from dan-da suggested.
General moderation of #analytics channel.
Other
Setup and maintenance of full core node btc.christophatteneder.com:8333
Communication with contributors
The text was updated successfully, but these errors were encountered: