Hacker News Reader

Comment by abarth | Hacker News Reader

As a principal software engineer that works on Fuchsia, I can assure you that the project does not exist solely to retain me. :)

View on HN

Congrats on the promo! It didn't quite retain me either, but I was a lowly staff software engineer. I am returning to Google though (back to the Google Fonts team), and it's entirely possible we'll get a chance to work together again.

I look forward to it!

Yay! Welcome back!

Congrats on the promo! It didn't retain me (though I didn't get promoted to Principal, so maybe I don't count) but I did enjoy working on Fuchsia. Nice to see much of the syscall design seems to have survived.

Thanks! Yes, your ideas are alive and well in the project.

Not solely, but in part? ;-)

Adam, how much were you involved in drafting this manifest?

I'm sorry, but I'm not sure what you mean by "this manifest." The blog post linked above was written by Wayne Piekarski, who is a Developer Advocate for Fuchsia. My role in the project is as a software engineer.

What was your journey to principal?

... but also your colleagues?

Since you're here, "abarth", it took me several clicks to get to the OWNERS file and all I saw was a list of email addresses. Calling that "governance" is... could we at least get some names and maybe brief bios on these people?

I understand where you're coming from, but that ends up being an inclusion issue in the project. I'm comfortable having my name and bio "out there" on the Internet, but I recognize that's a privilege. Not everyone who contributes to the project will be comfortable doing that.

The Eng Council is 5 people in a position of governance, not everyone who contributes.

Ah, I didn't realize the comment above was about the Eng Council. I'll raise the issue at our next meeting. Thanks!

The OWNERS file is typically used, sometimes by automated tooling, to answer the "who should I ask to code review these changes?" question.

https://chromium.googlesource.com/chromium/src/+/HEAD/docs/c...

https://docs.github.com/en/free-pro-team@latest/github/creat...

https://docs.gitlab.com/ee/user/project/code_owners.html

It's not meant to be a place for developer bios. If for no other reason than one developer could appear in many OWNERS files scattered throughout a repo, or in multiple repos, and keeping the bio current across all of them would be a nightmare.

Let me add some context. I was looking at the governance links on the site and found https://fuchsia.dev/fuchsia-src/contribute/governance/eng_co... which at the bottom simply says "The current members of the Fuchsia Eng Council are listed in this OWNERS file." I think it would improve the transparency/accountability of the project to have more than a list of email addresses here.

Probably not in the OWNERS file though, as it’s a machine-consumable file, heavy used inside and outside google for automation.

Reply on news.ycombinator.com