330 karma · joined March 16, 2010
Firstly, You don't know for sure what will the client do - with a high probability they will do just like you've said, but I'm not sure it is your obligation to force their hand so to speak, by making that possibility public. Also, if you decide to proceed with telling your coworkers I'd first think whether your employer can accuse you of disclosing what, in their mind, may be confidential information - you're part of the organisation, and "I found it by accident" may not be a strong enough argument to protect yourself from getting reprimended or even fired.
However, I think what's more important in your case is your wife's insistence on you not telling anyone. If I were in your shoes I'd probably try talking to her some more, explaining how not telling your coworkers is affecting your wellbeing, and that will probably become a bigger issue the closer to the April deadline it gets, as your uncertainty grows. I’d even suggest that you together talk with some close and trusted friends, or even a professional, to try and make some sense out of the situation. If you can't reach an agreement, I'd probably suggest siding with your wife - the knowledge you've acquired, while somewhat heavy, is nowhere heavy enough to put it over your own family.
In the end, I can only share my sympathy - It's not an enviable place to find oneself in. I just hope that, whatever you decide, you’ll be able to make peace with that and move on.
It may not be wrong, but it does stand in opposition to the definition of Open Source and Free Software (at least as defined by bodies that RedHat and many others see as authoritative on that subject).
So perhaps we could call MongoDB what it is - a proprietary software with shared code license that lets you run their code for free in some scenarios. I think that wouldn't sell to the investors and VCs as well as open source though, and would make it harder to build a community around.
And then we haven't even touched on the CLA required to make contributions to the project - I have no idea how many people and companies contributed changes or fixes to MongoDB, but they must be pretty happy right now.
Does that mean you can't have a business built around an open source project? It does seem that way to me, especially if we talk about something that scales in a number of employees and revenue. I do think that you could bootstrap a small, consultancy-style business, built around your open source technology, but definitely not something that VCs would drool over.
Also, on a related note, I'd like to add something that's rough around the edges and I'm sure someone else could make a much better case of it, but well, here I go.
There has always been a discussion on Free Software vs. Open Source [1] where the advocates of Free Software are arguing that Open Source does not protect freedom of the users (and communities) while Open Source advocates opposed that view with argument that Open Source is even more free and pure than Free Software. In my opinion, the recent changes made by MongoDB, Redis Labs [2] and even Elastic [3] show that without ethics backing the movement, the movement itself is in danger of having its core believes changed. If some software can't be made in a spirit of Free Software (or even Open Source) then perhaps it should be made as proprietary software with shared code license - it's not as cool, and perhaps will make the adoption harder, but at least it's more sincere.
[1] For example, see Stallman's "Why Open Source misses the point of Free Software" article https://www.gnu.org/philosophy/open-source-misses-the-point....
[2] Calling their non-free licenses "Apache-2 + Common Clause" is a pretty disingenuous move, and the only reason why I see it less bad than what Mongo did being the fact that it only affects a subset of previously-closed extensions IIRC.
[3] Their announcement on x-pack did not call it open source, however the entire press release was full of "open source" this and "open source" - it felt like they tried really hard to ride the Open Source train without actually riding it.
[1] For me issues were mostly interaction with random conference software and screen sharing (e.g. webex), or random hangs when connecting external displays (e.g. doing a presentation before CTO).
[1] at least on 3.1-RCx I have running, where I had to create Firewall VM manually, as installer has failed to deploy those "service VMs".
[1] On the other hand what would be a benefit of investing into getting drivers work with glibc, other than running your classic Linux distribution?
Some people are commenting that ST2 works great for them, and they don't see any bugs, but AFAIR in the ST3 announcement comment thread on HN someone has been writing on how he had to work around crasher in ST2 that has not been fixed after ST2 stable release.
The problem with "it's not the UNIX way" argument is that a lot of people don't care about UNIX that much, they just want a good system. Poettering mentions in that video that all his, and his colleagues' work (pulseaudio, consolekit, udev into udisks/upower) has been done because there was an actual demand for those features. There is a reason why most distributions use their work even as people complain about them.
Is this the reason why some HN comments are displayed using a smaller font than the rest of them? I always thought it had something to do with their score..
EDIT:
> - The edges of the screen are still wasted on the useless unsymmetric tab switching gestures.
Tab switching seems to be affected by your phone case.. when I removed mine from S3 it worked perfectly, but with it I can never reliably switch tabs.
EDIT: clarified a bit