Difference between revisions of "Growth Team"

From Bisq Wiki
Jump to navigation Jump to search
m
(update links and processes to reflect move from wekan to github)
Line 1: Line 1:
The '''Growth Team''''s focus is increasing trading volume through community engagement and outreach efforts, market-making bounties, the website, blog, and translations across the website and software.
+
The '''Growth Team''' focuses on increasing trading volume through community engagement and outreach efforts, market-making bounties, the website, blog, and translations across the website and software.
  
 
== Roles ==
 
== Roles ==
Line 11: Line 11:
  
 
== Infrastructure ==
 
== Infrastructure ==
 
=== Collaboration ===
 
 
{| class="wikitable"
 
|-
 
! Board Name !! Link !! Description
 
|-
 
| Markets || https://grow.bisq.cc/b/jPBBopYuLdGYdDpvF/markets || Covers publicity/outreach, content creation, discrete social media tasks, and other markets-related to-do items.
 
|-
 
| Bitcoin 2020 || https://grow.bisq.cc/b/Ro4TSwKHuYoTwixsz/bitcoin-2020 || Covers all preparations for the Bitcoin 2020 conference in San Francisco on March 27-28.
 
|-
 
| Translations || https://grow.bisq.cc/b/pS7ZjPr2A5oEAvD5D/translations || Covers all translations work for the website and software.
 
|}
 
 
All boards are public, so you can view them by clicking on the links above without without creating an account.
 
  
 
=== GitHub ===
 
=== GitHub ===
Line 32: Line 17:
  
 
[https://github.com/orgs/bisq-network/teams/growth @bisq-network/growth]
 
[https://github.com/orgs/bisq-network/teams/growth @bisq-network/growth]
 +
 +
==== Priorities ====
 +
 +
https://github.com/bisq-network/growth/projects/1
  
 
==== Repositories ====
 
==== Repositories ====
  
* https://github.com/bisq-network/growth (used primarily for market-making bounties and events)
+
* https://github.com/bisq-network/growth
 
* https://github.com/bisq-network/website
 
* https://github.com/bisq-network/website
  
Line 49: Line 38:
 
'''Any effort a contributor expects to be compensated for should be run by the growth team lead to ensure it fits cycle priorities and budget. Failure to do so may result in the contribution being rejected, undercompensated, or uncompensated.'''
 
'''Any effort a contributor expects to be compensated for should be run by the growth team lead to ensure it fits cycle priorities and budget. Failure to do so may result in the contribution being rejected, undercompensated, or uncompensated.'''
  
=== Publicity, Content Creation, Community Engagement, etc ===
+
Please see the priorities board linked above for current objectives.
 
 
All growth efforts (aside from market making and the website) are managed on kanban boards hosted at https://grow.bisq.cc (see [[Collaboration|list of all boards]]).
 
 
 
People interested in contributing to ''existing tasks'' (i.e., tasks already on the board) should:
 
  
# Seek out unassigned tasks on the boards relevant to their skills and interests
+
If you're interested in contributing to an existing priority, please:
# Express interest in the [[#Chat|appropriate Keybase channel]] about taking on a particular task
 
  
People interested in contributing to ''nonexistent tasks'' (i.e., tasks not on the board) should:
+
* Express your interest in the [[#Chat|appropriate Keybase channel]] (or on the corresponding GitHub issue)
  
# Start a discussion on Keybase to outline the merits of their proposed task
+
If you're interested in contributing in a way that's ''not'' currently outlined on the priority board, please:
# If there is potential, growth team lead will get in touch with you to determine specifics
 
  
After agreeing on task details, compensation, and delivery date, the contributor will be assigned to the task and free to begin work.
+
* Start a discussion on Keybase to outline the merits of your proposed task (or open an GitHub issue [[#Repositories|in the appropriate repository]])
 +
* Growth team members will get in touch with you to determine specifics, if warranted
  
 
=== Market Making ===
 
=== Market Making ===
  
Market making bounties are managed in the [https://github.com/orgs/bisq-network/teams/growth growth repository] on GitHub.
+
Occasionally, market making bounties are available for specific markets or regions. These bounties are managed in the [https://github.com/orgs/bisq-network/teams/growth growth repository] on GitHub.
  
 
Interested market makers should:
 
Interested market makers should:
  
# Carefully evaluate the conditions of the bounties they're interested in
+
# Carefully evaluate the conditions of the bounties they're interested in, or propose a new bounty on GitHub or Keybase
 
# Outline a convincing plan of action to deliver the bounty
 
# Outline a convincing plan of action to deliver the bounty
 
# Determine which cycle they would be able to deliver the bounty in
 
# Determine which cycle they would be able to deliver the bounty in
Line 77: Line 61:
 
After agreeing on details and covering any lingering concerns, the market maker will be assigned to the issue and is free to begin work.
 
After agreeing on details and covering any lingering concerns, the market maker will be assigned to the issue and is free to begin work.
  
=== Translations ===
+
{{Admonition_Note|Keep in mind that it's not necessary to be working on an approved bounty in order to do market making—market making should be a profitable activity on its own.}}
 
 
For more information on how translations for Bisq works, please see [[Translation]].
 
  
 
=== Website ===
 
=== Website ===
  
Any website change should be first proposed as an issue in the [https://github.com/bisq-network/bisq-website bisq-network/bisq-website] GitHub repository. The issue should cover the proposed change and how it aligns to current priorities. Estimated delivery date and cost should be included as well, if the issue creator expects to be the one delivering the proposed change.  
+
Any website change should be first proposed as an issue in the [https://github.com/bisq-network/bisq-website bisq-network/bisq-website] GitHub repository or discussed on Keybase in the #website channel. The issue should cover the proposed change and how it aligns to current priorities. Estimated delivery date and cost should be included as well, if the issue creator expects to be the one delivering the proposed change.  
  
 
Website maintainer will then review and advise whether or not to implement the proposal.
 
Website maintainer will then review and advise whether or not to implement the proposal.
  
 
It's highly recommended that the contributor not begin work on the proposed change until reaching agreement on task specifics, compensation, and timeframe with the website maintainer.
 
It's highly recommended that the contributor not begin work on the proposed change until reaching agreement on task specifics, compensation, and timeframe with the website maintainer.
 +
 +
=== Translations ===
 +
 +
For more information on how translations work, please see [[Translation]].
  
 
[[Category:Teams]]
 
[[Category:Teams]]

Revision as of 20:12, 30 June 2020

The Growth Team focuses on increasing trading volume through community engagement and outreach efforts, market-making bounties, the website, blog, and translations across the website and software.

Roles

Infrastructure

GitHub

Team

@bisq-network/growth

Priorities

https://github.com/bisq-network/growth/projects/1

Repositories

Chat

Processes

Any effort a contributor expects to be compensated for should be run by the growth team lead to ensure it fits cycle priorities and budget. Failure to do so may result in the contribution being rejected, undercompensated, or uncompensated.

Please see the priorities board linked above for current objectives.

If you're interested in contributing to an existing priority, please:

If you're interested in contributing in a way that's not currently outlined on the priority board, please:

  • Start a discussion on Keybase to outline the merits of your proposed task (or open an GitHub issue in the appropriate repository)
  • Growth team members will get in touch with you to determine specifics, if warranted

Market Making

Occasionally, market making bounties are available for specific markets or regions. These bounties are managed in the growth repository on GitHub.

Interested market makers should:

  1. Carefully evaluate the conditions of the bounties they're interested in, or propose a new bounty on GitHub or Keybase
  2. Outline a convincing plan of action to deliver the bounty
  3. Determine which cycle they would be able to deliver the bounty in

After agreeing on details and covering any lingering concerns, the market maker will be assigned to the issue and is free to begin work.

Note
Keep in mind that it's not necessary to be working on an approved bounty in order to do market making—market making should be a profitable activity on its own.

Website

Any website change should be first proposed as an issue in the bisq-network/bisq-website GitHub repository or discussed on Keybase in the #website channel. The issue should cover the proposed change and how it aligns to current priorities. Estimated delivery date and cost should be included as well, if the issue creator expects to be the one delivering the proposed change.

Website maintainer will then review and advise whether or not to implement the proposal.

It's highly recommended that the contributor not begin work on the proposed change until reaching agreement on task specifics, compensation, and timeframe with the website maintainer.

Translations

For more information on how translations work, please see Translation.