Diff for 'contributingAtWork'

Revert to Revision 2 - 2011-09-21 01:45:35z
Revision: 1
Size: 953:
Time: 2011-09-21 01:45:08z
Comment: Notes from SFD 2011 workshop
Revision: 2
Size: 970:
Time: 2011-09-21 01:45:35z
Comment: Wikify
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
* offload maintenance
* central competence
* consortium (positive vocabulary)
* colaboration
* social consience
* build or existing tool		  * offload maintenance
 * central competence
 * consortium (positive vocabulary)
 * colaboration
 * social consience
 * build or existing tool
Line 12: Line 12:
* test the water first
* multiple-sourcing, no vendor lock in
* how to manage risk
* OSIA, paid support
* mitigate risk: bus factor and burden of maintenance
* user acceptance and testing
* wider/expert code review
* success stories
* attribution		  * test the water first
 * multiple-sourcing, no vendor lock in
 * how to manage risk
 * OSIA, paid support
 * mitigate risk: bus factor and burden of maintenance
 * user acceptance and testing
 * wider/expert code review
 * success stories
 * attribution
Line 24: Line 24:
* look for an existing guide
* legal clause/addendum on contributing back code (on engagement contract)		  * look for an existing guide
 * legal clause/addendum on contributing back code (on engagement contract)
Revert to Revision 2 - 2011-09-21 01:45:35z

The following are notes from the Software Freedom Day 2011 workshop on contributing to free software in your workplace. The ultimate goal is to produce an agreement between employees and their employer to allow upstream contribution to free software projects.

  • offload maintenance
  • central competence
  • consortium (positive vocabulary)
  • colaboration
  • social consience
  • build or existing tool

Output: Set of arguments to convince employers that contributing upstream is a good idea. Some points relate more generally to encouraging use of free software.

  • test the water first
  • multiple-sourcing, no vendor lock in
  • how to manage risk
  • OSIA, paid support
  • mitigate risk: bus factor and burden of maintenance
  • user acceptance and testing
  • wider/expert code review
  • success stories
  • attribution

Action items:

  • look for an existing guide
  • legal clause/addendum on contributing back code (on engagement contract)