Is the main point that Rackspace has relaxed a restriction that required pre-approval for employees to contribute to OSS _on their own time_ but they still need approval to contribute while at work?
That's not it. Contributions on Rackspace time are also approved. We just need people to understand that the still will need to respect the priorities set by their managers. We don't want them to interpret this policy as allowing them to unilaterally deprioritize their assigned work in favor of hacking on $PROJECT_OF_CHOICE.
If your manager agrees that hacking on $PROJECT is a good idea, go for it.
Comments
Is the main point that Rackspace has relaxed a restriction that required pre-approval for employees to contribute to OSS _on their own time_ but they still need approval to contribute while at work?
That's not it. Contributions on Rackspace time are also approved. We just need people to understand that the still will need to respect the priorities set by their managers. We don't want them to interpret this policy as allowing them to unilaterally deprioritize their assigned work in favor of hacking on $PROJECT_OF_CHOICE.
If your manager agrees that hacking on $PROJECT is a good idea, go for it.
VanL (I wrote the policy)