dblock

Note on the ossinsights data point, there are 115 public repos in https://github.com/opensearch-project, including, as an example https://github.com/opensearch-project/k-nn where all vector search is written, or https://github.com/opensearch-project/neural-search.

OpenSearch only requires DCO.

https://github.com/opensearch-project/.github/blob/main/CONT...

You're right about documentation and tooling. There's some good momentum in the OpenSearch community around it though, and I am really excited by things like https://github.com/opensearch-project/documentation-website/....

"Elasticsearch" seems to be often referred to as a technology, as in ELK stack, rather than as in "Elastic" the company.

Connects Strava in Discord and reposts athlete and club activities into Discord channels, including time, distance, pace, map and weather. Open-source at https://github.com/dblock/discord-strava.

Artsy absolutely borrowed its cultural elements from the USSR, товарищ Стаханов! :)

I am sorry you had this experience. No approach, closed or open, will ever substitute better leaders that aren’t taking advantage of you. Your experience is likely and sadly very common.

Yikes. I was being sarcastic to make my point. And if highlight the “jokes aside” in the second paragraph, you’ll tell me I wasn’t funny?

I worked at artsy in my 30s, and participated in many hackathons.

My daughter (second child) was born 4 days after I started at Artsy. Some of the best new ideas came from hackathons.

Joey who opened https://github.com/artsy/README/issues/427 is one of the best 10x engineers I’ve ever had the privilege to work with. If it’s important to him to rename all branches from “master” to “joey” I’d add my plus 1.

Jokes aside, please read Ash’s (another artsy alumni) post on psychological safety, hope it changes your mind: https://ashfurrow.com/blog/building-compassionate-software/

Thanks orta for the links!

On not having to ask permission.

We failed early. Had a wonderful demo day. Tons of sign ups. It started getting a bit long. Someone decided to shorten each session (max 2 minutes) and choose which ones were worth demoing. So you basically asked for permission to demo. Sign ups stopped. Nobody wanted to demo anymore. Demo day died and took a year to restart properly.

In general, establish “how”. Everything is in writing and GitHub workflow. When someone says “can I?” the answer is “why are you asking and haven’t done it (submit PR) yet”? This moves permission to a public discussion.

Think in terms of must have, should have, nice to have, not allow/disallow.

Managers already have the power to veto, so they don’t need to approve, allow or disallow. Managers need to say that to everyone all the time - “you have an idea, why haven’t you done it yet?”.

Everyone needs to do things very visibly and over communicate to enable gentle redirects and avoiding getting to veto.

Losing control is hard. Communications team wanted to review and control the engineering blog. I said hard no multiple times with every new comms leader. Asked them to comment on PRs.

Don’t fix problems that don’t exist. If someone wants a knob that looks like permission, ask them what problem they are trying to solve.

(I was CTO of Artsy then.)

tl;dr The README became possible because Artsy is open-source by default, and someone just decided one day to create a repo and some content, and didn't need permission to do so. It's also the repo that most new hires read before they even apply to the job, and they don't need permission to make changes either. GitHub workflow is how everything gets done.

More practically, check out https://github.com/artsy/meta/pull/1, which is one of the repos that merged into the handbook via https://github.com/artsy/README/pull/1. Also note that Artsy was founded in 2010. This handbook in its current iteration is 7-8 years in, but its content goes back to ~2011 in some kind of evolution. You'll want to check out https://artsy.github.io/blog/archives/ as well.

As someone who works on an open-source fork of the open-source software mentioned in the post, I am now exclusively referring to the open-source version of it as Apache (APLv2) -licensed. Maybe that's how we fix this confusion?

I work at AWS on opensearch.org, literally to do this as described.

Or your entre website can be the FAQ.

https://www.drawingwithrussians.com/faq.html

Time to (re)watch Brazil!

I think so. But if anything I learned to be wary of propaganda on both sides.

This is extremely shortsighted. Educated people are a lot harder to exploit. One of these students might one day lead the kind of change we’ve seen in numerous examples through history.

I grew up in the USSR. There were multiple layers of the system. I was somewhere in the middle with my father being a well known poetry translator and grandfather writing propaganda. We listened to the BBC and Voice of America without reprimand, because of our status. Neighbors would face serious consequences for this. At 12 I was sent to the US to understand how capitalism is harmful. I think North Korea is making the same bet of creating a system in which some know all the truth and still work for the regime.

(I’m Swiss)

This was a question of money. The Swiss were asked to be taxed (even more than they already are). They voted against the costs.

Cool. Ironically, not open-source. +1 on wanting Ruby.

Possibly my bad, it may require being a member of one of the orgs.

A better URL to look at is https://github.com/enterprises/amazon.

This is important, +1.

If you want an example of what successful OSS looks like for over 10 years now, https://github.com/artsy, MIT license.