Contributor checklist - Revision history

Strayorigin: Remove mailing list link; verify YouTube link; add categories & minor cleanup.

2025-05-12T02:39:45Z

Remove mailing list link; verify YouTube link; add categories & minor cleanup.

Pazza at 16:32, 25 August 2024

2024-08-25T16:32:52Z

W000000t: add link to contributor opsec short guide

2022-03-02T22:07:42Z

add link to contributor opsec short guide

W000000t: keybase > matrix

2022-01-22T19:01:31Z

keybase > matrix

M52go: /* Basics */

2021-08-24T03:24:44Z

Basics

M52go: Undo revision 2298 by Willygoldman (talk)

2021-08-24T03:20:35Z

Undo revision 2298 by Willygoldman (talk)

M52go: Undo revision 2300 by Willygoldman (talk)

2021-08-24T03:19:01Z

Undo revision 2300 by Willygoldman (talk)

M52go: Undo revision 2320 by Willygoldman (talk)

2021-08-24T03:17:47Z

Undo revision 2320 by Willygoldman (talk)

Willygoldman: /* Compensation: BSQ tokens */

2021-08-23T01:22:11Z

Compensation: BSQ tokens

Willygoldman: Added parallelism to the major bullet points, various formating consistency changes

2021-08-22T12:05:23Z

Added parallelism to the major bullet points, various formating consistency changes

@@ Line 27: / Line 27: @@
 # To understand Bisq’s commitment to radical transparency and radical honesty, read Part III of [https://www.amazon.com/Principles-Life-Work-Ray-Dalio/dp/1501124021/ Ray Dalio’s Principles].
 # To get inspired about what building software in a non-hierarchical organization can be like (and what it requires of everyone involved), read the [https://steamcdn-a.akamaihd.net/apps/valve/Valve_NewEmployeeHandbook.pdf Valve Employee Handbook].
-# Finally, a few words on [[Contributor_privacy_and_opsec|safeguarding your privacy]]
+# Finally, a few words on [[Contributor_privacy_and_opsec|safeguarding your privacy]].
 == Get connected ==
@@ Line 33: / Line 33: @@
 # Browse and subscribe to the [https://www.youtube.com/c/bisq-network Bisq YouTube channel] to catch up on meetings we hold, tutorials we publish, technical sessions, and more.
 # Follow [https://twitter.com/bisq_network @bisq_network] on Twitter, or on any of the other channels listed [https://bisq.network/#community on the bottom of the website]: forum, Telegram, Matrix, Mastodon, etc.
 If you decide to proceed and start contributing, you'll want to join Bisq's GitHub organization so you can be assigned to issues:
@@ Line 42: / Line 41: @@
 == Do valuable work and get compensated ==
-After browsing GitHub repositories and Matrix discussions, you will start to develop a sense for what's happening, what's needed, and where you can help:
+After Browse GitHub repositories and Matrix discussions, you will start to develop a sense for what's happening, what's needed, and where you can help:
 # '''Find a problem somewhere in Bisq-land''' that (a) needs fixing and (b) is a match for your skills and interests. Browse critical bugs, open bounties, follow chats on Matrix and the forums, and ask around about what other contributors think needs fixing.
 # '''Get assigned to an issue''' or have your initiative acknowledged in some other way. While you don’t strictly need anybody’s permission to do anything for Bisq, you’ll want to make sure there's buy-in from other contributors so your work is received well. Otherwise, there are no guarantees that your work will be merged, reviewed, or eligible for compensation.
 # '''Do work to fix that problem'''. Submit your fix for review with a pull request (for code and documentation changes) or with a GitHub issue (for everything else).
@@ Line 52: / Line 51: @@
 # [[compensation|Submit a compensation request]] toward the end of the cycle.
-{{Admonition Note|As you'll see from browsing the various repositories on GitHub, changes to Bisq are almost always discussed publicly. This helps maintain Bisq's commitment to transparency, invites feedback to improve the quality of contributions, and it helps keep compensation honest. '''Always try to make sure your work is documented somewhere so others can follow its progress and offer feedback.'''}}
+{{Admonition Note|As you'll see from Browse the various repositories on GitHub, changes to Bisq are almost always discussed publicly. This helps maintain Bisq's commitment to transparency, invites feedback to improve the quality of contributions, and it helps keep compensation honest. '''Always try to make sure your work is documented somewhere so others can follow its progress and offer feedback.'''}}
 Ultimately, please remember that all Bisq contributors participate on a voluntary basis, and the more energy and quality you bring to the table, the more existing contributors will be encouraged to pay you attention.
@@ Line 61: / Line 60: @@
 For contributors wanting to receive regular bitcoin payments they may consider becoming performing a role as one of the Bisq [[Burning Men]]. It would be worth Bisq contributors understanding the pros and cons to becoming a burning man to decide if it is something they would like to do.

← Older revision		Revision as of 16:32, 25 August 2024
Line 57:		Line 57:

	Regarding development, keep in mind that reviewing other contributors' work can be highly valuable as well (both to the project, and also to yourself as a way to learn how Bisq works). Quality code reviews are eligible for compensation just like any other contribution.		Regarding development, keep in mind that reviewing other contributors' work can be highly valuable as well (both to the project, and also to yourself as a way to learn how Bisq works). Quality code reviews are eligible for compensation just like any other contribution.
		+
		+	== Consider if you would like to become a Burning Man ==
		+
		+	For contributors wanting to receive regular bitcoin payments they may consider becoming performing a role as one of the Bisq [[Burning Men]]. It would be worth Bisq contributors understanding the pros and cons to becoming a burning man to decide if it is something they would like to do.

@@ Line 27: / Line 27: @@
 # To understand Bisq’s commitment to radical transparency and radical honesty, read Part III of [https://www.amazon.com/Principles-Life-Work-Ray-Dalio/dp/1501124021/ Ray Dalio’s Principles].
 # To get inspired about what building software in a non-hierarchical organization can be like (and what it requires of everyone involved), read the [https://steamcdn-a.akamaihd.net/apps/valve/Valve_NewEmployeeHandbook.pdf Valve Employee Handbook].
 == Get connected ==

@@ Line 11: / Line 11: @@
 Suggestions below are in no particular order. Disregard developer-oriented items if you're not looking to contribute code.
-# Join the [https://keybase.io/team/bisq Keybase team]. In the Keybase software, go to <code>Teams</code> > <code>Join a team</code> then join the one called "Bisq".
+# Join the [https://bisq.chat Matrix space].
-# Introduce yourself in the <code>#introductions</code> channel. Say a bit about your skills and interests. This will help others point you in the right direction.
+# Introduce yourself in the <code>general</code> room. Say a bit about your skills and interests. This will help others point you in the right direction.
-# Explore the other channels on Keybase, and join the ones that are of interest to you. For a start, consider joining <code>#proposals</code>, <code>#dev</code>, <code>#growth</code>, and <code>#dev-onboarding</code> (if you’re a developer).
+# Explore the other rooms on Matrix, and join the ones that are of interest to you. For a start, consider joining <code>dev</code> (if you’re a developer) and <code>growth</code>.
 # Watch the following repositories on GitHub: [https://github.com/bisq-network/bisq core software], [https://github.com/bisq-network/bisq/discussions discussions], [https://github.com/bisq-network/proposals proposals], [https://github.com/bisq-network/growth growth], [https://github.com/bisq-network/roles roles] and [https://github.com/bisq-network/compensation compensation].
 # Read the [https://github.com/bisq-network/bisq/blob/master/docs/README.md developer docs] to set up a Bisq development environment.
@@ Line 36: / Line 36: @@
 If you decide to proceed and start contributing, you'll want to join Bisq's GitHub organization so you can be assigned to issues:
-# Request an invite to the [https://github.com/bisq-network @bisq-network GitHub organization] on Keybase. An admin will get you set up. Doing this makes it possible to add you to the [https://github.com/orgs/bisq-network/teams @bisq-network/contributors] team and to assign you to GitHub issues.
+# Request an invite to the [https://github.com/bisq-network @bisq-network GitHub organization] on Matrix. An admin will get you set up. Doing this makes it possible to add you to the [https://github.com/orgs/bisq-network/teams @bisq-network/contributors] team and to assign you to GitHub issues.
 # After accepting your GitHub invitation, consider changing your [https://github.com/orgs/bisq-network/people membership visibility] from <code>private</code> to <code>public</code>. This helps others know at a glance roughly how many contributors are involved with Bisq.
 == Do valuable work and get compensated ==
-After browsing GitHub repositories and Keybase discussions, you will start to develop a sense for what's happening, what's needed, and where you can help:
+After browsing GitHub repositories and Matrix discussions, you will start to develop a sense for what's happening, what's needed, and where you can help:
-# '''Find a problem somewhere in Bisq-land''' that (a) needs fixing and (b) is a match for your skills and interests. Browse critical bugs, open bounties, follow chats on Keybase and the forums, and ask around about what other contributors think needs fixing.
+# '''Find a problem somewhere in Bisq-land''' that (a) needs fixing and (b) is a match for your skills and interests. Browse critical bugs, open bounties, follow chats on Matrix and the forums, and ask around about what other contributors think needs fixing.
 # '''Get assigned to an issue''' or have your initiative acknowledged in some other way. While you don’t strictly need anybody’s permission to do anything for Bisq, you’ll want to make sure there's buy-in from other contributors so your work is received well. Otherwise, there are no guarantees that your work will be merged, reviewed, or eligible for compensation.
 # '''Do work to fix that problem'''. Submit your fix for review with a pull request (for code and documentation changes) or with a GitHub issue (for everything else).

@@ Line 11: / Line 11: @@
 Suggestions below are in no particular order. Disregard developer-oriented items if you're not looking to contribute code.
-# Join the [https://keybase.io/team/bisq Keybase team].
+# Join the [https://keybase.io/team/bisq Keybase team]. In the Keybase software, go to <code>Teams</code> > <code>Join a team</code> then join the one called "Bisq".
 # Introduce yourself in the <code>#introductions</code> channel. Say a bit about your skills and interests. This will help others point you in the right direction.
 # Explore the other channels on Keybase, and join the ones that are of interest to you. For a start, consider joining <code>#proposals</code>, <code>#dev</code>, <code>#growth</code>, and <code>#dev-onboarding</code> (if you’re a developer).

@@ Line 1: / Line 1: @@
-If you are interested in contributing to Bisq, welcome! This contributor checklist will get you plugged in and productive as quickly as possible.
+If you're interested in contributing to Bisq, welcome! This '''contributor checklist''' will get you plugged in and productive as quickly as possible.
 Bisq is free and open source software, but contributing is not just about writing code. A contributor is any individual who works to improve and add value to the Bisq network and its users.
@@ Line 7: / Line 7: @@
 __TOC__
-== Team Communications: Keybase ==
+== Basics: Communications with team through Keybase ==
 Get communicating with us.
@@ Line 13: / Line 13: @@
 # Keybase is a seperate piece of software we use to communicate. The software supports different teams.  Get the software here: [https://keybase.io/team/bisq Keybase team]. In the Keybase software, join the Bisq team under the "Teams" Tab then "Join a team" and then "Bisq" as the team to join. [[File:BisqTeamsView.jpg||600px|thumb|center|Sucessfully joined the Bisq team]] This is an open community, no permissions needed to join. You will see the Bisq logo when you find the right team.
 # Introduce yourself in the <code>#introductions</code> channel. Say a bit about your skills and interests. This will help others point you in the right direction.
-# Explore the other channels for our team on Keybase, and join the ones that are of interest to you. For a start, consider joining <code>#proposals</code>, <code>#dev</code>, <code>#growth</code>.  There is <code>#dev-onboarding</code> for developers.
+# Explore the other channels for our team on Keybase, and join the ones that are of interest to you. For a start, consider joining <code>#proposals</code>, <code>#dev</code>, <code>#growth</code>, and <code>#dev-onboarding</code> (if you’re a developer).
-== Code: GitHub ==
+== Code: stored in GitHub ==
 Disregard these developer-oriented items if you're not looking to contribute code.
@@ Line 24: / Line 24: @@
 # Get set up to [https://help.github.com/articles/signing-commits-using-gpg/ Sign your Git Commits] with GPG. Any commits to any Bisq repository must be signed.
-== Bisq Project Management ==
+== Learn how we work ==
 # Read about [[Project_management|Bisq’s project management process]].
@@ Line 33: / Line 33: @@
 # To get inspired about what building software in a non-hierarchical organization can be like (and what it requires of everyone involved), read the [https://steamcdn-a.akamaihd.net/apps/valve/Valve_NewEmployeeHandbook.pdf Valve Employee Handbook].
-== Communication Channels ==
+== Get connected social media and e-mail==
 # Browse and subscribe to the [https://www.youtube.com/c/bisq-network Bisq YouTube channel] to catch up on meetings we hold, tutorials we publish, technical sessions, and more.
@@ Line 44: / Line 44: @@
 # After accepting your GitHub invitation, consider changing your [https://github.com/orgs/bisq-network/people membership visibility] from <code>private</code> to <code>public</code>. This helps others know at a glance roughly how many contributors are involved with Bisq.
-== Compansation: BSQ tokens ==
+== Do valuable work and get compensated ==
 After browsing GitHub repositories and Keybase discussions, you will start to develop a sense for what's happening, what's needed, and where you can help: