Skip to content

Call for contributors! #1347

@sebmck

Description

@sebmck

So Babel has become a pretty big beast. I'm looking for contributors. Right now contributions have been pretty inconsistent. Don't get me wrong, I love and appreciate all contributions but at the end of the day I'm still maintaining Babel and attend to the majority of the bug fixes and new features. This can become incredibly stressful and in the interests of my personal free time and sanity I'd like for that to change.

Where can I contribute?

Documentation/Website

Seriously, this is mega-important. The documentation so far has been great and has been a killer feature of Babel. There are sections that could certainly use some work and even the addition of a paragraph here or there is extremely appreciated.

If you have any free time and you see areas of the documentation that you think can be improved please submit a pull request. See the babel.github.io repo for the website source.


Work on Babel core

Feel free to ping me on slack if you have any specific internal questions. I'll be looking into doing some screencasts on the internals and/or blog posts to ease the transition into the code base for newcomers.

If you're looking to dive in and fix something, consider picking from the list of issues labeled good first bug.

Note about pull requests

Please note that before any significant contributions (feature additions etc) I'd love if an issue was open prior discussing what it is you want to do. There's nothing worse than having to turn down a PR if it could have been avoided prior to all the effort being put in.

Optimisations

This is an area that hasn't really been given much love since @gaearon did some V8 optimisations.

The code generator is an area that needs a lot of work, it takes exponentially longer the larger the source file is, this is crap. Files that are megabytes or hundreds of kilobytes should not take a million years to generate. This will be especially important moving forward as Babel becomes a more general JavaScript transformer.


Respond to issues

Responding to issues is another extremely effective way to help out. I've been trying to keep support and questions out of GitHub issues, even though the README is literally 3 lines, some people don't seem to read it. Pointing these people in the right direction (eg. to slack, website repo, StackOverflow etc) is extremely appreciated.


Answer questions on slack

Babel has an incredibly active slack channel. Slack has an IRC bridge as well as a range of apps which makes idling and answering questions super easy.


Anything else!

Seriously, any contributions are appreciated.


Thank you in advance to anyone who helps out!

💅 ✨

Metadata

Metadata

Assignees

No one assigned

    Labels

    outdatedA closed issue/PR that is archived due to age. Recommended to make a new issue

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions