People

Teams

Maintainers

We maintain Flycheck and all official extensions within the Flycheck organisation, and set the direction and scope of Flycheck. We review and accept pull requests and feature proposals and fix bugs in Flycheck.

Emphasized users are also owners of the Flycheck Organisation, and thus have administrative privileges for all repositories in Flycheck. Notably only owners can currently make Flycheck releases, and their GPG keys sign release tags for Flycheck.

Mention with @flycheck/maintainers.

Moderators

Our moderators help uphold our Flycheck Code of Conduct. Currently, we do not have a dedicated moderation team; all our Maintainers also serve as moderators in our Github organisation and in our official communication channels.

Mention with @flycheck/moderators.

Note

If you’d like to help out with moderation, please contact a maintainer.

Language teams

These teams provide support for particular languages in Flycheck.

Elixir

Mention with @flycheck/elixir.

Go

Mention with @flycheck/go.

Haskell

  • Sergey Vinokurov (sergv)

Mention with @flycheck/haskell.

Javascript

Mention with @flycheck/javascript.

Lua

Mention with @flycheck/lua.

Puppet

  • Romanos Skiadas (rski)

Mention with @flycheck/puppet.

Rust

Mention with @flycheck/rust.

TypeScript

Mention with @flycheck/typescript.

Packagers

We would like to thank all people who package Flycheck on behalf of distributions and support our development efforts with their feedback, their patches and their testing:

Acknowledgements

We would also like to thank the following people and projects:

  • Sebastian Wiesner (lunaryorn) for creating Flycheck in the first place, for taking the time and dedication to maintain it for over 4 years, while maintaining high standards of code quality and nurturing a healthy, active community around it, giving Flycheck the best chances to thrive after his departure.
  • Bozhidar Batsov (bbatsov) for his valuable feedback and his constant support and endorsement of Flycheck from the very beginning. Notably he added Flycheck to his popular Prelude project at a very early stage and thus brought Flycheck to many new users.
  • Magnar Sveen (magnars) for his dash.el and s.el libraries, which support considerable parts of Flycheck internals, and greatly helped to overcome Sebastian’s initial aversion to Emacs Lisp.
  • Martin Grenfell (scrooloose) for the Vim syntax checking extension Syntastic which saved Sebastian’s life back when he was using Vim, and served as inspiration for Flycheck and many of its syntax checkers.
  • Matthias Güdemann (mgudemann), for his invaluable work on Flycheck’s logo.
  • Pavel Kobyakov for his work on GNU Flymake, which is a great work on its own, despite its flaws and weaknesses.
  • Simon Carter (bbbscarter), for his patient in-depth testing of automatic syntax checking, and his very constructive feedback.
  • Steve Purcell (purcell) for his valuable feedback, the fruitful discussions and his important ideas about the shape and design of Flycheck, and his indispensable and dedicated work on MELPA, which drives the continuous distribution of Flycheck to its users.

Contributors

The following people—listed in alphabetical order—contributed substantial code to Flycheck:

For a complete list of all code contributors see the Contributor Graph or git shortlog --summary.