Teams - Revision history

Pazza at 17:39, 25 August 2024

2024-08-25T17:39:41Z

Pazza: /* Control and Recruitment */

2024-08-25T17:37:46Z

Control and Recruitment

Pazza: /* Limits on growth */

2024-08-25T17:35:12Z

Limits on growth

Pazza at 17:34, 25 August 2024

2024-08-25T17:34:15Z

Flix21: /* Limits on growth */

2024-02-02T13:23:42Z

Limits on growth

Flix21: /* Control and Recruitment */

2024-02-02T13:11:20Z

Control and Recruitment

Flix21: /* Control and Recruitment */

2024-01-05T19:32:00Z

Control and Recruitment

Flix21: /* List of Teams */

2024-01-05T19:06:42Z

List of Teams

Flix21: /* Control and Recruitment */

2024-01-05T18:43:30Z

Control and Recruitment

Flix21: /* Recruitment */

2024-01-05T18:37:14Z

Recruitment

← Older revision		Revision as of 17:39, 25 August 2024
Line 30:		Line 30:

	Experienced team members should take responsibility for control of new team members, external contributors and outsourced workers. They can exercise this control by commenting on and approving (or not) their compensation requests every cycle.		Experienced team members should take responsibility for control of new team members, external contributors and outsourced workers. They can exercise this control by commenting on and approving (or not) their compensation requests every cycle.
		+
		+	== Recruitment ==
		+
		+	There are no recruiters for Bisq. People interested in contributing for Bisq should check out the [[Contributor checklist\|Contributor Checklist]].

@@ Line 27: / Line 27: @@
 Anonymity and pseudonymity are welcome at Bisq. Bisq is global and many countries have unfriendly regulations for Bitcoin, exchanges, DEX, FOSS, etc. Many countries do not respect [[Free Speech]] or [[Private Property]]. Contributors should be able to work for the Bisq DAO without requiring to endanger their privacy. This is another important reason to decentralise work and rely on external contributors that can complete a project, get paid and leave. [[Proof of work]] should be the standard for compensation and merit.
-== Control and Recruitment ==
+== Control ==
-Team leads are responsible for control of team members, external contributors and outsourced workers. They can exercise this control by approving their compensation requests every cycle (see [[Compensation|Team Lead review]]). They can also recruit more members and greenlight projects, subject to final DAO approval. Team leads are controlled horizontally by their peers and by the DAO.
+Experienced team members should take responsibility for control of new team members, external contributors and outsourced workers. They can exercise this control by commenting on and approving (or not) their compensation requests every cycle.

@@ Line 21: / Line 21: @@
 == Limits on growth ==
-To avoid the bureaucratic decay that many startups and FOSS projects fall into once they exceed the '''Dunbar Number''' (~150) and horizontal communications become difficult, Bisq will limit the number of teams to a maximum of 12 and will make efforts to outsource as much work as possible to external contributors. This can be done on a per-project basis for some types of work, through bounties for one-off tasks or by opening it up to the market in an automatic way following the model of Bitcoin miners. Ideally 90% of work will require only in-team coordination and only a small part will require team leads to coordinate between them. In theory each team could behave as an external contractor, being assigned work by the DAO and then presenting a compensation request when the work is completed, just as an external contractor would present the bill for services rendered.
+To avoid the bureaucratic decay that many startups and FOSS projects fall into once they exceed the '''Dunbar Number''' (~150) and horizontal communications become difficult, Bisq will limit the number of teams to a maximum of 12 and will make efforts to outsource as much work as possible to external contributors. This can be done on a per-project basis for some types of work, through bounties for one-off tasks or by opening it up to the market in an automatic way following the model of Bitcoin miners. Ideally 90% of work will require only in-team coordination. In theory each team could behave as an external contractor, being assigned work by the DAO and then presenting a compensation request when the work is completed, just as an external contractor would present the bill for services rendered.
 == Privacy and security ==

← Older revision		Revision as of 17:34, 25 August 2024
Line 1:		Line 1:
	[[File:Teams.jpg\|thumb]]		[[File:Teams.jpg\|thumb]]

−	Bisq is a [[FOSS]] project. Governance is decentralised through the [[DAO]]. Work is coordinated through a number of teams with some core members and other external contributors working with a particular team on a project basis~~. A Team Lead coordinates, assigns work and proposes new projects, always subject to DAO approval and funding. Horizontal control means that each Team Lead is controlled by his peers and the DAO~~. There is no CEO. True Names are not required. Anonymous and pseudonymous contributors are welcome.	+	Bisq is a [[FOSS]] project. Governance is decentralised through the [[DAO]]. Work is coordinated through a number of teams with some core members and other external contributors working with a particular team on a project basis. There is no CEO. True Names are not required. Anonymous and pseudonymous contributors are welcome.

@@ Line 21: / Line 21: @@
 == Limits on growth ==
-To avoid the bureaucratic decay that many startups and FOSS projects fall into once they exceed the Dunbar Number (~150) and horizontal communications become difficult, Bisq will limit the number of teams to a maximum of 12 and will make efforts to outsource as much work as possible to external contributors. This can be done on a per-project basis for some types of work, through bounties for one-off tasks or by opening it up to the market in an automatic way following the model of Bitcoin miners. Ideally 90% of work will require only in-team coordination and only a small part will require team leads to coordinate between them. In theory each team could behave as an external contractor, being assigned work by the DAO and then presenting a compensation request when the work is completed, just as an external contractor would present the bill for services rendered.
+To avoid the bureaucratic decay that many startups and FOSS projects fall into once they exceed the '''Dunbar Number''' (~150) and horizontal communications become difficult, Bisq will limit the number of teams to a maximum of 12 and will make efforts to outsource as much work as possible to external contributors. This can be done on a per-project basis for some types of work, through bounties for one-off tasks or by opening it up to the market in an automatic way following the model of Bitcoin miners. Ideally 90% of work will require only in-team coordination and only a small part will require team leads to coordinate between them. In theory each team could behave as an external contractor, being assigned work by the DAO and then presenting a compensation request when the work is completed, just as an external contractor would present the bill for services rendered.
 == Privacy and security ==

← Older revision		Revision as of 13:11, 2 February 2024
Line 32:		Line 32:

	When a new team lead position has multiple candidates the recruitment process must adhere to Bisq principles being open and public.		When a new team lead position has multiple candidates the recruitment process must adhere to Bisq principles being open and public.
−
−	~~For example:~~
−
−	1. Contributor interested in Team Lead position formally applies on the relevant github issue (https://github.com/bisq-network/roles/issues/100), detailing their plan for the team, the work they expect to do, how many hours a day they can work on this, the compensation they will ask for, the goals that they hope to achieve. Links to previous work. Details of BSQ bond if bonded role.
−
−	~~2. Other contributors and team leads give feedback, ask questions, demand more details from candidates.~~
−
−	~~3. If decision is clear (contributor consensus on preferred candidate) this should be obvious on github issue.~~
−
−	~~4. If doubt persists, ask for an explicit vote on github.~~
−
−	~~5. If there is a tie or issues with voting (sybil attack?), put it to a DAO vote.~~

@@ Line 29: / Line 29: @@
 == Control and Recruitment ==
-Team leads are responsible for control of team members, external contributors and outsourced workers. They can exercise this control by approving their compensation requests every cycle. They can also recruit more members and greenlight projects, subject to final DAO approval. Team leads are controlled horizontally by their peers and by the DAO.
+Team leads are responsible for control of team members, external contributors and outsourced workers. They can exercise this control by approving their compensation requests every cycle (see [[Compensation|Team Lead review]]). They can also recruit more members and greenlight projects, subject to final DAO approval. Team leads are controlled horizontally by their peers and by the DAO.
 When a new team lead position has multiple candidates the recruitment process must adhere to Bisq principles being open and public.

@@ Line 15: / Line 15: @@
 * 8. [[UX Team]] responsible for improving user experience and making Bisq easy to use.
 * 9. [[Projects Team]] coordinates projects developed by external contributors, creates bounties, etc.
-* 10. [[Decentralization Team]] guides the DAO to be more decentralised, guards against risks of corporate capture.
+* 10. [[Decentralization Team]] guides the DAO to be more decentralised, guard against corporate capture, automate governance.
 * 11. [[Defense Team]] focused on legal, regulatory, privacy and other risks to contributors and the DAO.
 * 12. [[Financial Team]] is responsible for keeping the DAO profitable and markets liquid.

@@ Line 35: / Line 35: @@
 For example:
-. Contributor interested in Team Lead position formally applies on the relevant github issue (https://github.com/bisq-network/roles/issues/100), detailing their plan for the team, the work they expect to do, the compensation they expect to ask for, the goals that they hope to achieve. Links to previous work. Details of BSQ bond if bonded role.
+. Contributor interested in Team Lead position formally applies on the relevant github issue (https://github.com/bisq-network/roles/issues/100), detailing their plan for the team, the work they expect to do, how many hours a day they can work on this, the compensation they will ask for, the goals that they hope to achieve. Links to previous work. Details of BSQ bond if bonded role.
 . Other contributors and team leads give feedback, ask questions, demand more details from candidates.