Open Source Culture Log - Revision history

Dorkmo at 18:56, 3 August 2015

2015-08-03T18:56:58Z

← Older revision		Revision as of 18:56, 3 August 2015
Line 2:		Line 2:

	=Mon Aug 3, 2015=		=Mon Aug 3, 2015=
	If you publish early and often, collaborators can join in the process. Otherwise, they nag you for results (because the results are not published) and don't contribute to the process. This is the current state of Koruza-OSE collaboration, where OSE is the nag. The limit in such a case is resources on the part of the lead developer to document - that is the part that is always missing without a running Google Presentation, CAD repo, Hangouts, and dev platform. Perhaps a technical development FB group. Instead of Gmail, use FB to publish so it's open.		If you publish early and often, collaborators can join in the process. Otherwise, they nag you for results (because the results are not published) and don't contribute to the process. This is the current state of [[Koruza]]-OSE collaboration, where OSE is the nag. The limit in such a case is resources on the part of the lead developer to document - that is the part that is always missing without a running Google Presentation, CAD repo, Hangouts, and dev platform. Perhaps a technical development FB group. Instead of Gmail, use FB to publish so it's open.

Marcin at 16:14, 3 August 2015

2015-08-03T16:14:14Z

← Older revision		Revision as of 16:14, 3 August 2015
Line 2:		Line 2:

	=Mon Aug 3, 2015=		=Mon Aug 3, 2015=
	If you publish early and often, collaborators can join in the process. Otherwise, they nag you for results (because the results are not published) and don't contribute to the process. This is the current state of Koruza-OSE collaboration, where OSE is the nag. The limit in such a case is resources on the part of the developer to ~~collaborate in~~ the ~~process~~.		If you publish early and often, collaborators can join in the process. Otherwise, they nag you for results (because the results are not published) and don't contribute to the process. This is the current state of Koruza-OSE collaboration, where OSE is the nag. The limit in such a case is resources on the part of the lead developer to document - that is the part that is always missing without a running Google Presentation, CAD repo, Hangouts, and dev platform. Perhaps a technical development FB group. Instead of Gmail, use FB to publish so it's open.

Marcin: Created page with "Aka Collaborative Literacy Log. =Mon Aug 3, 2015= If you publish early and often, collaborators can join in the process. Otherwise, they nag you for results (because the resu..."

2015-08-03T16:11:47Z

Created page with "Aka Collaborative Literacy Log. =Mon Aug 3, 2015= If you publish early and often, collaborators can join in the process. Otherwise, they nag you for results (because the resu..."

New page

Aka Collaborative Literacy Log.

=Mon Aug 3, 2015=
If you publish early and often, collaborators can join in the process. Otherwise, they nag you for results (because the results are not published) and don't contribute to the process. This is the current state of Koruza-OSE collaboration, where OSE is the nag. The limit in such a case is resources on the part of the developer to collaborate in the process.