Difference between revisions of "Growth Team"
Plebeian9000 (talk | contribs) (overhaul to match other team pages) |
(Fix link typo) |
||
| Line 74: | Line 74: | ||
=== Website === | === Website === | ||
| − | Any website change should be first proposed as an issue in the [https://github.com/bisq-network/bisq-website bisq-network/bisq] 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. 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. | ||
Revision as of 06:29, 5 March 2020
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.
Contents
Roles
Infrastructure
Collaboration
| 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
Team
Repositories
- https://github.com/bisq-network/growth (used primarily for market-making bounties and events)
- https://github.com/bisq-network/website
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.
Publicity, Content Creation, Community Engagement, Translations, etc
All growth efforts (aside from market making and the website) are managed on kanban boards hosted at https://grow.bisq.cc (see 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
- Express interest in the appropriate Keybase channel about taking on a particular task
People interested in contributing to nonexistent tasks (i.e., tasks not on the board) should:
- Start a discussion on Keybase to outline the merits of their proposed task
- 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.
Market Making
Market making bounties are managed in the growth repository on GitHub.
Interested market makers should:
- Carefully evaluate the conditions of the bounties they're interested in
- Outline a convincing plan of action to deliver the bounty
- 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.
Website
Any website change should be first proposed as an issue in the 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.
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.
