_msw_

11 ms·

61.
by _msw_ 5y ago
The defects in SSPLv1 were raised by the community during the review process when it was submitted by MongoDB for comment. It would be redundant to re-enumerate them in a blog post like Bradley's, which already tend to be on the long s
62.
by _msw_ 5y ago
Disclosure: I work for AWS, but I am not paid by AWS to comment on HN on Free Software matters, on which I have my own personal opinions. SSPLv1 is not a free software license. It is constructed to have unsatisfiable obligations that, in pr
63.
by _msw_ 5y ago
It is pretty clear to me that Elastic is planning to build their ANN features differently than OpenDistro's k-NN implementation, or other plugins modules that extend Easticsearch in similar ways. They now will build on the Apache Lucen
64.
by _msw_ 5y ago
It is totally reasonable to expect for-profit corporations to be good stewards of shared resources, such as the public goods that make up the Free and Open Source Software (FOSS) commons. I think it is important to all users of FOSS that
65.
by _msw_ 5y ago
Disclosure: I work for AWS where I build infrastructure services that sit low in the stack. I am a relative novice when it comes to Java-heavy codebases like Apache Lucene, Elasticsearch, or OpenSearch. But I know a thing or two about Open
66.
by _msw_ 5y ago
Earlier post: https://news.ycombinator.com/item?id=28237443
67.
by _msw_ 5y ago
Disclosure: I work for AWS where I build infrastructure services The license to Redis never changed. See his blog post [1] around the time when his _employer_ announced some license changes on modular extensions to Redis. See also threads o
68.
by _msw_ 6y ago
Disclosure: I work for AWS building cloud infrastructure. I wouldn't assume that VM migration does not exist in AWS. The overall design and implementation of Google's infrastructure somewhat mandated the development live migration
69.
by _msw_ 6y ago
Disclosure: I work for AWS, but I am not speaking for the company. The Redis case study is a nuanced one. The core Redis code is BSD-3 licensed, and adopted a lightweight community governance model in June of 2020 [1]. This model includes a
70.
by _msw_ 6y ago
Disclosure: I work for AWS, but I am not speaking for my employer. This post is based on my personal workplace experience. The policy exists to enable collaboration and contribution, not to restrict it. These types of policies are common at
71.
by _msw_ 6y ago
It is interesting to think about this in the abstract, but I think that Peter is right. The real collaboration only comes with getting the code published, design proposals on extension points in the core engine, and so on. This isn't t
72.
by _msw_ 6y ago
Which company are you thinking of?
73.
by _msw_ 6y ago
I think we are trying to establish the brand of this project in these early days, and to have that brand distinct from AWS. I see this like "Mozilla" was separate from "Netscape" in their early days [1] (note, this link
74.
by _msw_ 6y ago
I am not reciting corporate PR. As I said, I'm not speaking for AWS. I only speak for myself, and I'm not saying anything that I don't believe. You'll find elsewhere in the comments [1] that on actions, not words, I agre
75.
by _msw_ 6y ago
Personally, I try to keep a "curious" outlook, and to regularly try to disprove my beliefs. To me, one way to do this is to listening closely to criticism from viewpoints and perspectives that are different than mine. Based on my
76.
by _msw_ 6y ago
NB: it is not "AWS Babelfish". It is (currently) "Babelfish for PostgreSQL". https://babelfish-for-postgresql.github.io/babelfish-for-pos... Can the title of this post be changed to remove "AWS&quot
77.
by _msw_ 6y ago
I take it as no disrespect. I can understand why you would have this point of view. :-)
78.
by _msw_ 6y ago
Disclosure: I work for Amazon where I build AWS infrastructure, but these opinions are mine alone. Personally, I think that the word "fork" has a lot of historical meaning in the world of Free and Open Source Software. To me, &quo
79.
by _msw_ 6y ago
Disclosure: I work for Amazon, where I build AWS infrastructure. But these are my own opinions and experiences at work, and I am not speaking for my employer. "Embrace, extend, extinguish" has never been uttered in any conversatio
80.
by _msw_ 6y ago
Got it. Thank you for mentioning it here. Comments are getting a bit unwieldy to stay on top of.
81.
by _msw_ 6y ago
That's counting emails. Unlike other Git-based projects like the Linux kernel, it seems a lot of commits are made with users.noreply.github.com email addresses. For example. commit 8e413f85e8978da83db107aae51e5543d4779dba Author:
82.
by _msw_ 6y ago
Disclosure: I work at Amazon on AWS infrastructure. And sometimes I have exchanges with ahmetb on Twitter. I cannot dispute the fact that Google has more developers working on k8s than AWS does. And that AWS developers have been focused mor
83.
by _msw_ 6y ago
Disclosure: I work at Amazon on cloud infrastructure, but not on the codebase in question. I helped with parts of the blog post to try to explain some of the nuance about how things are set up with Elasticsearch as an "upstream".
84.
by _msw_ 6y ago
Disclosure: I work at Amazon on cloud infrastructure, but not directly on the codebase being discussed here. Someone pointed out elsewhere: *Correction after looking a bit closer, I think Amazon has submitted at least 600 PRs, they only
85.
by _msw_ 6y ago
Disclosure: I work for Amazon, but not directly on search related technology. Some information about Amazon's investments in upstream Apache Lucene can be found here: https://aws.amazon.com/blogs/opensource/am
86.
by _msw_ 6y ago
I didn't say that non-Elastic employees could not contribute. I said that they cannot become maintainers . Non-elastic pull requests are merged, as I mentioned in [1]. [1] https://twitter.com/_msw_/status/134
87.
by _msw_ 6y ago
Disclosure: I work for AWS, but I do not work directly on Elasticsearch related services. Elasticsearch is/was an "upstream" for Open Distro for Elasticsearch (which is a distribution / collection of software). As an &qu
88.
by _msw_ 6y ago
Disclosure: I work for AWS Free for some to use under certain restrictions. Therefore not Open Source (which is totally OK, I just want to make sure there's no confusion).
89.
by _msw_ 6y ago
From my perspective, the size of the companies has little to do with the relative risk of outcomes that are not the best for the common good. I've seen folks at small companies try to control or unduly influence open-source software, a
90.
by _msw_ 6y ago
Disclosure: I work at Amazon where I build AWS infrastructure This is where I think mindful investments in building and maintaining a diverse community of developers and users is especially important for a system component like a programmin

More ›