Revert 'contributingAtWork'to Revision Number '3'

Meta data of item revision to be reverted:

  • Action: SAVE
  • Address: 127.0.0.1
  • Comment: ''
  • Content Type: Moinmoin 1.9 [text/x.moin.wiki;format=1.9;charset=utf-8]
  • Data ID: 4ad433ef8acd47cebf185f0705a554dd
  • External Links: (None)
  • Item ID: cf1ec122b4e54107a35cc71cf72aff79
  • Item Links: (None)
  • Item Transclusions: (None)
  • Item Type: default
  • Language:
  • Modified Time: 2011-09-21 01:46:22z
  • Name: contributingAtWork
  • Old Name: (None)
  • Namespace: ''
  • Parent Revision ID: 014e079c969c4fddafcef20a0cb64d04
  • Revision ID: 2fbf74a7732d4b2cae37d4ba90b9eed6
  • Revision Number: 3
  • SHA1: 713dc5067f0ac283a9a1d29acae65031651554ee
  • Size: 1.0 kB
  • Summary: ''
  • Tags: (None)
  • Trash: False
  • User ID: de0a5c52eff7499980f2de73bc1f18fe
  • Wiki Name: My MoinMoin

Content of item revision to be reverted:

Contributing back code at your workplace

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)