VanL

8 ms·

31.
by VanL 13y ago
DannyBee! Good to see you. Its been a long time. I stand corrected, then. I had thought that Google's policy allowed contributions, but not under the employee's own copyright. I thought there was an additional step to get that app
32.
by VanL 13y ago
This is not true. For example, take a look at DSC Communications Corp. v. Evan Brown, or DDB Tech v. MLB Advanced Media or Medsphere v. Shreeve. In DSC, the court ruled that Alcatel owned the employee's thoughts that had not yet been
33.
by VanL 13y ago
It is a matter of responsibility. Anyone, in any organization, has a responsibility to make sure that the organization's "assets," however defined, are properly handled. Agree or not, intellectual property is one of the asset
34.
by VanL 13y ago
All these points are correct. We are just trying to make it so that the trip to the lawyer is not necessary. The fewer lawyers the better. ;)
35.
by VanL 13y ago
That is the typical corporate America policy, and yes it does stifle contribution. We decided to be different and do better.
36.
by VanL 13y ago
Hi dragonwriter, The scope of employment has historically been interpreted very broadly, usually in terms of any present or possible future business opportunity. You will see how that leads to a broad right of assignment. You may say, that
37.
by VanL 13y ago
What we are saying is that it is our policy that the work for hire doctrine (see http://en.wikipedia.org/wiki/Work_for_hire ) does not apply to OSS contributions at Rackspace, and that we encourage all employees to beco
38.
by VanL 13y ago
Our default policy was (as is the case at most companies) that code written by our employees is copyright Rackspace. This is true just about universally - look on wikipedia about the "work for hire" doctrine. Because employee code
39.
by VanL 13y ago
This is almost precisely the opposite of what we are saying. We are disclaiming ownership of all OSS contributions, inside of work or out. We just want to make sure that while people are on the clock, they do make progress on the tasks as
40.
by VanL 13y ago
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
41.
Rackspace’s Policy On Contributing To Open Source(rackspace.com)
33 points by VanL 13y ago|47 comments
42.
by VanL 13y ago
The control plane is on top of ZeroMQ, to allow for various arrangements of components as well as the ability to observe the flow of inputs/outputs.
43.
by VanL 13y ago
Each container has a single process. Each Individual part is deterministic, so the entire system is composable deterministically.
44.
by VanL 13y ago
We see this as bigger than just Rackspace. Anywhere your data is, we want ZeroVM to be there.
45.
by VanL 13y ago
- It is deterministic based on the inputs. You would need to pass in a seed or read from an external source of randomness to get different values out of a PNRG. - Binaries need to be recompiled. There are two toolchains, a GCC-based one and
46.
by VanL 13y ago
Van Lindberg here from Rackspace. If you have any questions, I am around to answer.
47.
by VanL 13y ago
Glad to see DannyBee here. IAAL too, also specializing in open source. Danny is correct about the prevailing interpretation. I don't see this as an issue.
48.
Rackspace launches “Fanatical Support for Developers”(thewhir.com)
60 points by VanL 13y ago|55 comments
49.
by VanL 13y ago
You are right, we do have some patents. We have never used them against others. Unfortunately, we feel like we need to be prepared for when other patent-holding entities come knocking. We know they will, because they already have. We don'
50.
by VanL 14y ago
We couldn't sue because we didn't know what we would sue on. They wouldn't even tell us the patent numbers - so we didn't have the knowledge necessary to even file a complaint. As for suing because of the forbearance agreement, they try to
51.
by VanL 14y ago
They are claiming the image mark, but the image is the word "Python" with only minimal embellishment. Further, they have added broader rights in private conversation.
52.
by VanL 14y ago
Thank you!
53.
by VanL 14y ago
Great idea - will do.
54.
by VanL 14y ago
Thanks - this is a great thought. Our UK lawyers are going to be receiving a pretty decent Python library. :) Are there similar books in German, Italian, French, and Spanish?
55.
by VanL 14y ago
Do you have any old offers of employment that you could share? The more and the older the better.
56.
by VanL 14y ago
Our main point of contention is that they are claiming that the right to be the sole source of "Python" software, servers, and services. We have reached out to them to try to reach some accommodation (they can be "Python backup services," f
57.
by VanL 14y ago
Thanks for your words - and we would love to get your assistance and advice. Unfortunately, our network of Python-using lawyers is much thinner in Europe than in the US. Feel free to contact me!
58.
by VanL 14y ago
Great thought. We are doing this.
59.
by VanL 14y ago
You can contact me, van@python.org. Thanks!
60.
by VanL 14y ago
I (and probably several other) members of the board will be on this thread to answer any questions. Van Lindberg Chairman, Python Software Foundation Edit: I have been asked what sort of statements would be helpful. I can't tell you exact

More ›