nomulus

My guess is because it just doesn't bring in enough profits. Most domain registrars make money through volume by either having a relatively small team (porkbun etc.), having most of the team located in a low CoL jurisdiction (Namecheap and eastern Europe/formerly Ukraine), or from value added services/the registrar acting as a loss leader (pretty much every service do this to an extent, CloudFlare, GoDaddy etc.) For a company like Google that pays top tier salary, there is no way that selling domains (especially not in bulk, their targets are mostly consumers and businesses, domain traders use other services) make enough money. If you take a look at the commiters on https://github.com/google/nomulus That's at least 10 engineers maintaining one component. Add in SRE and product executives, you are looking at expenses in the two digit mill

I don't know what to say other than that my experience here is precisely the opposite of yours. Different areas of the company? I use a LOT of third party libraries in the course of my employment, and third_party in my experience is full of legitimate third party libraries, not ones that are developed by Google. Anyway, here's the list of dependencies for my project. There's a lot of third-party stuff in it: https://github.com/google/nomulus/blob/master/dependencies.g...

You can escalate to legal for edge cases, but you should be able to handle base cases yourself. As an example, I work at Google on an Apache 2.0-licensed open source project, and we have dozens of third party dependencies: https://github.com/google/nomulus/blob/master/core/build.gra... It wouldn't remotely scale across Google if we had to escalate to legal every single time we pulled in a new dependency. Instead, there's a company-wide allowlist of accepted software licenses, and you only need legal help for exceptions beyond that. So yes, we do have to know some basics of software licensing. It's just part of being a SWE.

There were a lot of people who thought like you and thought they could just whip up some perl scripts to do it. Then they all got hacked, and since when you hack a domain registry, you hack every domain it manages too, they'd usually snag a google.whatever domain and say haha we hacked google. Eventually Google got so angry about this happening that they sent a crack team of security experts to build a top-level domain registry the right way, and made it open source. https://github.com/google/nomulus It wasn't easy.

If you give me your email I can send you a message from my _lastname_@ work address, which you can then match up with published media I've done under my name, e.g. https://www.youtube.com/watch?v=kBkX30Cj7Bw and https://security.googleblog.com/2017/09/broadening-hsts-to-s... Or you can look at the matching username on GitHub ( https://github.com/CydeWeys ) and see that I'm a member of the Google org and owner of the Nomulus repo ( https://github.com/google/nomulus/graphs/contributors ), the software running our TLD registry and which was announced here: https://opensource.googleblog.com/2016/10/introducing-nomulu... Or I could just dig out my GPG key and sign a message. So I respect your healthy skepticism, but I promise I'm really me, and not just someone pretending to be me! And I'll also note that, in all my time on HN, I've never onc

Yeah, it's the same advice, just Chris Beams did it over 4 years earlier. This is the article I always link people to on my team when explaining how to write commit messages. My company doesn't have a style guide for this exact thing, so this article is what I've been using. And the results are here: https://github.com/google/nomulus/commits/master

Tech Lead of Google Registry ( https://registry.google ) here. We run on GCP. You definitely don't want to check secrets into the repo for the same reason you don't set them as environment variables: It's not secure. The solution is to use Cloud Key Management Service. More info here: https://cloud.google.com/kms/ We use that to either store secrets directly, or to decrypt encrypted entities in a DB (e.g. Datastore). You can see how we use it here (our project is open source): https://github.com/google/nomulus/tree/master/java/google/re...

It's definitely true that putting the burden of consistency on developers (instead of on the DB) results in a lot more tricky work for developers. On my project, which started six years ago, we use Cloud Datastore, because Cloud Spanner hadn't come out yet. It results in complicated, painful code that would be completely unnecessary with stronger transactional guarantees. Some examples: https://github.com/google/nomulus/blob/master/java/google/re... https://github.com/google/nomulus/blob/master/java/google/re... https://github.com/google/nomulus/blob/master/java/google/re... It's no surprise that we're currently running screaming to something with stronger transactional guarantees.

Yes. I don't recall the details but I think it's required by ICANN. We (Google Registry) support extended Latin and Japanese codebases, and since the registry software that we've written is Free Software, you can see our implementation, e.g. here's extended Latin: https://github.com/google/nomulus/blob/master/java/google/re...

We've been using this format on our project for over a year now. Our commit history looks nice as a result: https://github.com/google/nomulus/commits/master

Here's the top-level Bazel BUILD file of the open source project I work on at Google, if anyone wants to see an example for a good-sized (~100K LoC) codebase: https://github.com/google/nomulus/blob/master/java/google/re... Each subdirectory below the root also has its own BUILD file, where you can see the individual packages being compiled.

Looks like our native representation in Datastore is java.util.Date, so we should be in the clear. Relevant code here: https://github.com/google/nomulus/blob/master/java/google/re...

We support downloadable static premium price lists too (it's all that some registrars can handle), but yes, obviously we prefer the price extension too. Here's the entry point into the static premium pricing lists if you're curious: https://github.com/google/nomulus/blob/master/java/google/re... Said lists are imported into the system from the CSV file format that is given to registrars by this command-line tool: https://github.com/google/nomulus/blob/master/java/google/re... By the way, can I just say as an aside, that it's so awesome that I can finally link to and discuss our code in the open (I wrote this pricing stuff under stuff).