Thanks for the question, I wrote about this in a post before: https://medium.com/@hzoo/ossthanks-some-thoughts-d0267706c2c6 I was inspired by a bunch of projects like khan academy, d3, bootstrap, etc. But Jonathan Neal was the one got me to intentionally look into contributing into a project (https://github.com/angular/angular.js and then http://jscs.info/). BTW, You can use https://github.com/pulls?q=is%3Apr+author%3Ahzoo+sort%3Acreated-asc+is%3Aclosed to check someone's PRs Technically my first PR was https://github.com/Khan/khan-exercises/pull/10765 (not merged since I didn't rebase correctly and didn't understand git at all). My first PR to JSCS (the first project I eventually contributed regularly too and then became a maintainer for) was https://github.com/jscs-dev/node-jscs/pull/677 to update the table of contents. My first PR to Babel was https://github.com/babel/babel/pull/932 to add ES6. Thus all of my first PRs were very simple: typos, changing docs, basic refactoring/reformatting/updating tools. This is probably part of the reason why I got interested in the tooling side of things and wanting to automate a lot of it (especially autofixing which lead me to work on JSCS)

Similar to https://hashnode.com/ama/with-babel-team-cj7awmk5e00ij54wu6onnyc5w#cj7f1sjql01v9nrwtagrkpvzd

Can check out https://github.com/babel/notes . This is kinda generic so not sure how to answer. Like a lot of projects, it's not that organized. People tend to work on what they like and we push those people to lead that effort and find more people to get involved. We try to have meetings to focus on certain efforts but ultimately we can't/don't really have deadlines.

It's impossible to know everything that's going on in a codebase - not that different from work, even more so for an open source project where you aren't reviewing every single PR or know about each aspect or part of the code. We try to have team leads for different packages/areas which are mostly determined based on interest/history https://github.com/babel/notes/blob/master/2017-04/april-08.md#proposed-team-structuregovernance . We have to invest in getting more people involved so that we can get more reviewers ultimately. You can find the time if it's (hopefully) fun enough to do, otherwise live your life with other hobbies, family, friends,et c.

Yeah I'l talk to people if they want, I don't remember everyone who reached out already

Not thinking about being awesome and working on things for the future/vision of what they can be. Balancing learning to do things out of joy/passion while doing things I know are good for me but I don't want to do - aka. practice

(Maybe it's weird) I'm not particularly excited about any of them 🙂 , same with the ones we've already landed

I've always been using Sublime

I don't install a lot, https://github.com/junegunn/fzf?

There is https://gitlab.com/Rich-Harris/buble which is "smaller" but I don't think it's use case is the same. There is almost no configuration (not a bad thing at all) so no custom plugins, and it only compiles performant ES5. It's scope has expanded a bit (used to only be ES6, but now JSX, and people will continue to ask for more), and tries to compile to readable ES5 rather than be spec compliant. However like any open source project you need a lot of maintainers to continually update it over the months/years. If someone wants to make something new instead, that sounds fine but depends on the goals and why you wouldn't contribute back to Babel already or refactor internally. No, I don't really see it happening, it's already hard enough to maintain Babel as is 😛