Hackers & Designers Coop - Revision history

Karl at 16:33, 24 January 2020

2020-01-24T16:33:49Z

← Older revision		Revision as of 18:33, 24 January 2020
Line 32:		Line 32:
	Maintenance: Will be wrapped in the an activity for overall H&D technical infrastructure.		Maintenance: Will be wrapped in the an activity for overall H&D technical infrastructure.

	Try it yourself:		== Try it yourself ==

	<tool user="hackersanddesigners" repo="coop" file="README.md" />		<tool user="hackersanddesigners" repo="coop" file="README.md" />

	[[Category:Tools]]		[[Category:Tools]]

Karl at 16:33, 24 January 2020

2020-01-24T16:33:27Z

← Older revision		Revision as of 18:33, 24 January 2020
Line 34:		Line 34:
	Try it yourself:		Try it yourself:

	<tool user="hackersanddesigners" repo="coop" file="~~readme~~.md" />		<tool user="hackersanddesigners" repo="coop" file="README.md" />

	[[Category:Tools]]		[[Category:Tools]]

Karl at 16:33, 24 January 2020

2020-01-24T16:33:05Z

← Older revision		Revision as of 18:33, 24 January 2020
Line 32:		Line 32:
	Maintenance: Will be wrapped in the an activity for overall H&D technical infrastructure.		Maintenance: Will be wrapped in the an activity for overall H&D technical infrastructure.

			Try it yourself:

			<tool user="hackersanddesigners" repo="coop" file="readme.md" />

	[[Category:Tools]]		[[Category:Tools]]

Hd-onions at 15:00, 12 January 2020

2020-01-12T15:00:10Z

← Older revision		Revision as of 17:00, 12 January 2020
Line 1:		Line 1:
	== The Hackers & Designers Coop is a proposed model of collaborative organization based on fiscal democracy. ==		== The Hackers & Designers Coop is a proposed model of collaborative organization based on fiscal democracy. ==

			[[File:coop1.png]]
	# Funds will be divided equally between all members of the cooperative.		# Funds will be divided equally between all members of the cooperative.
	# Projects will be proposed to the cooperative by one or more members of the cooperative. Projects broadly consist of a description, budget, and participants, but can include any relevant information to funding cooperative members.		# Projects will be proposed to the cooperative by one or more members of the cooperative. Projects broadly consist of a description, budget, and participants, but can include any relevant information to funding cooperative members.

Hd-onions at 19:36, 9 January 2020

2020-01-09T19:36:38Z

← Older revision		Revision as of 21:36, 9 January 2020
Line 30:		Line 30:

	Maintenance: Will be wrapped in the an activity for overall H&D technical infrastructure.		Maintenance: Will be wrapped in the an activity for overall H&D technical infrastructure.


			[[Category:Tools]]

JBG at 18:42, 10 February 2018

2018-02-10T18:42:50Z

← Older revision		Revision as of 20:42, 10 February 2018
Line 27:		Line 27:
	== Cost ==		== Cost ==

	Technical platform construction: ~~2160~~ (12 half days for 1 month x 40 EUR per hour)		Technical platform construction: 1920 (12 half days for 1 month x 40 EUR per hour)

	Maintenance: Will be wrapped in the an activity for overall H&D technical infrastructure.		Maintenance: Will be wrapped in the an activity for overall H&D technical infrastructure.

JBG at 18:41, 10 February 2018

2018-02-10T18:41:37Z

← Older revision		Revision as of 20:41, 10 February 2018
Line 27:		Line 27:
	== Cost ==		== Cost ==

	Technical platform construction: 2160 (12 half days for 1 month x 45 EUR per hour)		Technical platform construction: 2160 (12 half days for 1 month x 40 EUR per hour)

	Maintenance: Will be wrapped in the an activity for overall H&D technical infrastructure.		Maintenance: Will be wrapped in the an activity for overall H&D technical infrastructure.

JBG at 16:15, 10 February 2018

2018-02-10T16:15:40Z

← Older revision		Revision as of 18:15, 10 February 2018
Line 20:		Line 20:

	Project management platforms should be evaluated.		Project management platforms should be evaluated.

			== Technical ==

			The rules should be codified into a smart contract and deployed on to a private Ethereum blockchain.

			== Cost ==

			Technical platform construction: 2160 (12 half days for 1 month x 45 EUR per hour)

			Maintenance: Will be wrapped in the an activity for overall H&D technical infrastructure.

JBG at 11:32, 7 January 2018

2018-01-07T11:32:54Z

← Older revision		Revision as of 13:32, 7 January 2018
Line 6:		Line 6:
	# Funding members, cooperative members outside a project's participant list, consider the project proposal, and then return a promise to fund the project (a promise), a rejection to fund (a rejection), or suggestions as to how the project could be modified to be evaluated for funding again (a modification).		# Funding members, cooperative members outside a project's participant list, consider the project proposal, and then return a promise to fund the project (a promise), a rejection to fund (a rejection), or suggestions as to how the project could be modified to be evaluated for funding again (a modification).
	# Projects can not be funded by it's participating members, except for the case where all members of the cooperative are participating in a single project.		# Projects can not be funded by it's participating members, except for the case where all members of the cooperative are participating in a single project.
	# Projects that receive enough promises, even in the case ~~they my~~ also receive modifications, can be executed without fulfilling modification requests.		# Projects that receive enough promises, even in the case it may also receive modifications, can be executed without fulfilling modification requests.
	# If a project does not receive enough promises, and does fulfil modification requests, it must be re-evaluated by the whole non-participating collective for funding again.		# If a project does not receive enough promises, and does fulfil modification requests, it must be re-evaluated by the whole non-participating collective for funding again.
	# Everything the cooperative does should be included in or described as a project including administration and organization activities including: book keeping, communication, external funding applications, etc..		# Everything the cooperative does should be included in or described as a project including administration and organization activities including: book keeping, communication, external funding applications, etc..

JBG at 09:45, 7 January 2018

2018-01-07T09:45:16Z

← Older revision		Revision as of 11:45, 7 January 2018
Line 3:		Line 3:
	# Funds will be divided equally between all members of the cooperative.		# Funds will be divided equally between all members of the cooperative.
	# Projects will be proposed to the cooperative by one or more members of the cooperative. Projects broadly consist of a description, budget, and participants, but can include any relevant information to funding cooperative members.		# Projects will be proposed to the cooperative by one or more members of the cooperative. Projects broadly consist of a description, budget, and participants, but can include any relevant information to funding cooperative members.

	# Project can contain participants outside of the cooperative, but participants outside the cooperative can not participate in cooperative funding.		# Project can contain participants outside of the cooperative, but participants outside the cooperative can not participate in cooperative funding.

	# Funding members, cooperative members outside a project's participant list, consider the project proposal, and then return a promise to fund the project (a promise), a rejection to fund (a rejection), or suggestions as to how the project could be modified to be evaluated for funding again (a modification).		# Funding members, cooperative members outside a project's participant list, consider the project proposal, and then return a promise to fund the project (a promise), a rejection to fund (a rejection), or suggestions as to how the project could be modified to be evaluated for funding again (a modification).

	# Projects can not be funded by it's participating members, except for the case where all members of the cooperative are participating in a single project.		# Projects can not be funded by it's participating members, except for the case where all members of the cooperative are participating in a single project.

	# Projects that receive enough promises, even in the case they my also receive modifications, can be executed without fulfilling modification requests.		# Projects that receive enough promises, even in the case they my also receive modifications, can be executed without fulfilling modification requests.

	# If a project does not receive enough promises, and does fulfil modification requests, it must be re-evaluated by the whole non-participating collective for funding again.		# If a project does not receive enough promises, and does fulfil modification requests, it must be re-evaluated by the whole non-participating collective for funding again.

	# Everything the cooperative does should be included in or described as a project including administration and organization activities including: book keeping, communication, external funding applications, etc..		# Everything the cooperative does should be included in or described as a project including administration and organization activities including: book keeping, communication, external funding applications, etc..

	# It is possible to participate in the cooperative and never propose or participate in a project. Such members, however, will not receive funds.		# It is possible to participate in the cooperative and never propose or participate in a project. Such members, however, will not receive funds.

	# It is possible to continue with a self-initiated project which was rejected by all cooperative funding, and use the "Hackers & Designers" non-financial assets (name, communication, web, wiki, whatever). Such assets are perks of being part of the cooperative. Self-initiated projects can also happen completely outside of the Hackers & Designers umbrella. It is completely up to the project executor.		# It is possible to continue with a self-initiated project which was rejected by all cooperative funding, and use the "Hackers & Designers" non-financial assets (name, communication, web, wiki, whatever). Such assets are perks of being part of the cooperative. Self-initiated projects can also happen completely outside of the Hackers & Designers umbrella. It is completely up to the project executor.

	# Projects which receive required promises and are executed must include Hackers & Designers in project communications, etc..		# Projects which receive required promises and are executed must include Hackers & Designers in project communications, etc..

	# Individual project management need not concern the cooperative once funded and began. Any external funding received by an individual project is to be handled at the project level. The project can decided to contribute such funding wholly or partially back to the cooperative, but it is not mandatory. Any funding contributed back to the cooperative is again split evenly to cooperative members.		# Individual project management need not concern the cooperative once funded and began. Any external funding received by an individual project is to be handled at the project level. The project can decided to contribute such funding wholly or partially back to the cooperative, but it is not mandatory. Any funding contributed back to the cooperative is again split evenly to cooperative members.