sdesol

27 ms·

391.
by sdesol 5y ago
> anything involving multiple commits in a single PR results in the diff more or less lying to you: you get diffs of something, but it's not clear what, and even less clear how to get what I want to actually diff. I'm trying to
392.
by sdesol 5y ago
Yeah if you look at only changes to Java files in OpenSearch (OpenSearch + Security) and Elasticsearch, the number of contributors is growing at a steady pace and who knows, it may well surpass Elasticsearch in a year or two. month
393.
by sdesol 5y ago
This is true, but it is a huge proxy for investment and survivability. In the beginning, it was hard to tell how much Amazon would invest in OpenSearch, but it appears now (based on activity) that Amazon is committed to OpenSearch.
394.
by sdesol 5y ago
Based on my latest analysis, OpenSearch is very active as the following shows: https://oss.gitsense.com/insights/github?q=pull-age%3A%3C%3D... but it is still not as active as Elasticsearch, which is to be expected giv
395.
by sdesol 5y ago
Trade secret and PII are two different things. Trade secret is something you can risk. PII is not something most governments will allow you to risk.
396.
by sdesol 5y ago
> I'm spending over $200 per week just to stand up the service as it is What are using if you don't mind me asking? Not trying to criticize or anything. I have a Heztner box that gives me 1TB SSD in RAID 0 mode and 64 GB of R
397.
by sdesol 5y ago
> How about starting with mean time to merge a code change? I'm currently experimenting with using "Mode time" as I think it is less susceptible to data skew from outliers. See example below: https://oss.gitsen
398.
by sdesol 5y ago
This appears to be the repo that the copyright originated from https://github.com/mwshinn/forceatlas2-python bhargavchippa also contributed to this repo, so this doesn't seem like one of those random "fork an
399.
by sdesol 5y ago
My product ( https://gitsense.com ) moves most of Git's history into a relational database and then I do indexing on top of that to produce things like code churn (lines added, changed and deleted), which is also stored in th
400.
by sdesol 5y ago
When this project made it to the front page of HackerNews, they (grist-core owners) mentioned most things were open-source. Their process flow (which involves Phabricator and a mono-repo) hides a lot of the development activity but based o
401.
by sdesol 5y ago
> he’s still 30+ yo and has many many years ahead I know where you are going with this, but I'm not sure his age is relevant as somebody 50+ yo could have many years ahead of them. Having said all of that, here's his contribut
402.
by sdesol 5y ago
Yeah I can see what you mean. There are currently 20 open pull requests [1] that hasn't changed in over 28 days, which accounts for 53% of all open pulls that are less than 4 months old. 1) https://oss.gitsense.com/ins
403.
by sdesol 5y ago
My product ( https://gitsense.com ) moves most of Git's history into a Postgres database and from there, you can execute the following SQL statement: select commit_ym AS month, count(distinct(author_emai
404.
by sdesol 5y ago
I've never heard of Calcite before and dug a bit deeper into this project and found it to be quite active. Only taking into consideration changes to Java files, this is the repo activity for the last 12 months: month | authors
405.
by sdesol 5y ago
Hey thanks for the insights! I've added all timescale repos for indexing and should have the bigger picture in a few hours. Thanks again for catering to my curiosity.
406.
by sdesol 5y ago
Congrats and I was wondering if you can comment on the current team size? I'm looking at the number of contributors that have created pull requests within the last four months and it is shockingly low (in a good way). Based on the fo
407.
by sdesol 5y ago
Here are some development stats for yjs and automerge for the last 4 months. Ignoring bots, 15 people created pull requests for yjs. 7 people created pull requests for automerge. https://oss.gitsense.com/insights/gith
408.
by sdesol 5y ago
> I don't think it has anything to do with the fact that Git is distributed. I think it does since meta-data increases merge complexity, which is probably a headache when dealing with a distributed system. With a centralized system
409.
by sdesol 5y ago
I do agree that renaming/moving files isn't great but I guess that is one of the downsides of having a distributed version control system. With Subversion, ClearCase, and others, they were centralized and very much meta-data driv
410.
by sdesol 5y ago
Thanks for the insights! I'm trying to support different workflows and hearing about yours helps.
411.
by sdesol 5y ago
Hey great product! Wondering if you can provide some development insights. I'm looking at the activity for the grist-core repo https://oss.gitsense.com/insights/github?q=pull-age%3A%3C%3D... and it looks like no
412.
by sdesol 5y ago
Looking at pull requests that had commits in the last 14 days in 30 OpenSearch repositories, there were 90 authors, which isn't insignificant. https://oss.gitsense.com/insights/github?q=pull-age%3A%3C%3D...
413.
by sdesol 5y ago
> I think part of the challenge looking at these metrics is the project versus repo structure For my tool, I can analyze any combination of repositories so getting the bigger picture isn't challenging. Out of curiosity, I decided t
414.
by sdesol 5y ago
I was curious to see what the monthly contribution pattern was for both Elasticsearch and OpenSearch and this is was what I got: repo | month | commits | authors ------------+---------+---------+--------- elastic |
415.
by sdesol 5y ago
Here's the activity difference for the last year repo | commits | authors ------------+---------+--------- elastic | 2719 | 179 opensearch | 265 | 54 Here's a breakdown based on co
416.
by sdesol 5y ago
Somebody that does consulting work with Elasticsearch mentioned that they had some pretty innovative features in the pipeline and these are the things that can really pull people away from OpenSearch. It could also be that, people only rea
417.
by sdesol 5y ago
It was announced by elastic and I'm not sure it is in their best interest to advertise their competitor.
418.
by sdesol 5y ago
Full disclosure: This is my tool that I'm using to generate the insights. When OpenSearch was announced, I shared some insights into how both Elasticsearch and OpenSearch were evolving, and I'll share some more up to date insights
419.
by sdesol 5y ago
> Volume doesn't mean shit though, that's the trick. Based on having studied lots and lots of open source projects, I can say volume has a very strong correlation with experience. The more people contribute, the more likely th
420.
by sdesol 5y ago
Full disclosure: I'm trying to find a way to use development insights to help us develop software better, together. I tried a lot and I mean a lot of ways to see if we could use git commits to help us better understand productivity, bu

More ›