2,808 karma · joined November 13, 2008
I run a game company developing http://fracturedveil.com and help governments, film/tv productions and companies worldwide on issues related to technology, open source and manufacturing.
Also, it is not as simple as you think, government code isn't always pd. If written by a contractor, the contractor/contracting organization can decide to not release code/work to the public.
Finally, if this code was written by Macon's team, and not by contractors, then you could maybe make an argument that the parts of the code that came from original gpl parts would be gpl'd, but not the code written by the wh team that doesn't depend on the gpl'd parts, as the code isn't distributed to end users the way the gpl mandates sharing.
Anyhow, I'm trying to simplify a lot here, but thought I'd chime in.
This whole situation is very sketchy, honestly.
Nasa can basically call the local navy detachment and ask them to swoop in. It's not clear that is accounted for in the NASA budget vs. the normal operating budget of that battle group.
Similarly, when NASA says something costs 20k to get to orbit, they're saying that because that's what they told someone it would cost when justifying the program. The real cost of things like a shuttle recovery are never as easy to track as one might think.
(wow, this is a lot longer than I expected it to be)
1) Who are the investors?
Before I joined VA Linux in 1998, I knew they were super close to closing the Intel Capital deal, so I knew (to a certain degree of accuracy) that they were close to having money in the bank. I agreed to take less salary for equity and a promise from the CEO that salary would improve as the company got more solid funding. The CEO was good to his word, too. I might have taken the job without the vc funding, but knowing what was up there was really helpful.
There is more knowledge now about the equity picture of a private technology company today than ever before in history. It's very easy to get an idea of a companies valuations and then if you agree with those values and if you think they'll increase.
Some VCs also have a reputation for screwing early employees and pancaking out those that might leave before an exit. This is very important to know if you're going to be valuing a potential equity stake. So, your equity could disappear without any regard for your feelings on the matter.
2) How far along are they towards going public/another exit.
I joined Google the week before it went public (in 2004), meaning my initial strike was the ipo opening price. Considering that made Google more stable than competing offers from younger startups, and more fun than some of the other companies I had offers from. The former was important as I had just come out of a failed startup and some time consulting, and I wanted stable more than I wanted fun. I got both, but that's pretty rare in companies of Google's vintage (I still have it, which is one of the reasons why I stay).
The point of this is to understand what the future of a company looks like. I knew what Google looked like, and for other companies when considering/working with them, I asked myself what do similar 'exits' look like. That leads to understanding of what an equity position means.
You can look at an offer and ask yourself: Will the company actually increase in value before an exit that makes this equity worth it?
3) Is there an established bonus system?
A lot of companies have no bonus and weaker benefits/salaries pre-ipo. They have the equity stake offer and so these other considerations are sidelined until they become larger and those equity offers stop attracting good people by themselves. These differences can mean 70 to 80k less per year for a senior employee. So, know what you're worth and decide if it is worth the risk.
4) Are the people running the company any good? Are they ethical?
This is actually hard to answer, but I've seen plenty of acquisitions become less lucrative than a similar job in an established company. I won't mention the company, but I've seen large companies (not Google that I know of) end up giving less in financial terms to acquired employess than they give a new hire wrt equity participation. It's kind of sad how little people know about the companies they join.
I'll say it again: I often see companies on HN get acquired, but for many of the employees, and not a few founders , of startups, this is a much worse deal financially than taking a job with an established firm. Your mileage may vary, and take it with a grain of salt, but remember you are trading money now for the chance of much more money later.
There's so much more I'd like to tell people here about considering offers, but I've already blathered on a bit much on this. I also readily admit I have a different approach to risk as a husband and father (2004) than I did as a single developer (1998)...
There really isn't another solution out there right now (at least not anything open source) for very large single repositories.
Gas + Truck Rental = 100$/day. Parking/tickets in front of embassy: Free? Costly?
3 people (or 4? The article says they have 2 mandarin speakers on tap) in said truck for 8 hours + back and forth time splitting the remainder and you have a bit under 12.5/hour.
That said, they're not being up front about how much they make, and given its probably largely a cash business ...
We make it easy for companies to comply with the notice requirements (via build scripts that populate inside the about phone section of the OS) and we often advocate for what we consider to be our high level of compliance wrt code mirroring.
If you review the manufacturers of devices that actually make it into people's pockets, you'll find that they are fairly decent about compliance (notification and providing source on request) and a few are very good and doing more than the licenses actually require (posting mirrored code online at time of shipment, like we do).
Some are not as fast about code provision. In those cases, I suggest joining gpl-violations and starting there. Email me too and I'll pass word along if they are one of the manufacturers that we have a decent relationship with.
For most of the small run manufacturers, we have little or no relationship and gpl-violations might be a better place to start.
We aren't the world's linux cop and I know from experience it's the last thing people want Google to be.
There are some companies that don't care about doing compliance right, and they'll take what is in my opinion a long time to comply with the license, or work certain corners of the license (like sveasoft did many years ago) to wiggle out from under the code provision requirements of the gpl. It's actually quite difficult to see what could productively done about these bad actors.
I take umbrage from people who say crap like 'Google makes money off other peoples violation of the gpl' . It isn't true and It shows a lack of thoughtfulness on the part of MJG on this issue.
Finally; As one of the people who contacts developers and manufacturers using our software outside of the provisions of the apache, bsd, lgpl and gpl licenses, compliance is almost always about education and not about malice.
I'd ask this question to the developers at CarrierIQ though....those guys should be ashamed.
Edited to add: No, no one seems anymore ashamed to work at Zynga than one does at any game company.
Stand by :-)
The real problem is that I could point you to source.google.com and you could download the kernel and other gpl components from honeycomb right this second, but kernel.org and the osuosl site is recovering from a nasty hack. When those machines are back up, I invite you to go get the code you seem to be interested in.