Open Source Culture Log: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| 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. | ||
Latest revision as of 18:56, 3 August 2015
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 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.