We gladly accept contributions via GitHub pull requests! We encourage you to read the
Welcome remarks in the Flutter
framework's contributing guide, as all of that information applies to contributing to the flutter/evals
repo as well.
We communicate primarily over GitHub and Discord on the #hackers-devtools channel.
Contributions to this project must be accompanied by a Contributor License Agreement (CLA). You (or your employer) retain the copyright to your contribution; this simply gives us permission to use and redistribute your contributions as part of the project.
If you or your current employer have already signed the Google CLA (even if it was for a different project), you probably don't need to do it again.
Visit https://cla.developers.google.com/ to see your current agreements or to sign a new one.
Before you get started, we encourage you to read these documents from the Flutter repository, which describe some of our community norms:
-
Our code of conduct, which stipulates explicitly that everyone must be gracious, respectful, and professional. This also documents our conflict resolution policy and encourages people to ask questions.
-
Values, which talks about what we care most about.
We won't review pull requests in this repository until there's an associated issue filed. This repository is primarily a tool for improving Flutter itself, rather than apps built with Flutter. Therefore, we'll be quite strict about what code we add. Please don't work on a new feature without first confirming with the the CODEOWNERS, which is primarily done via filing an issue.
We ascribe to the same style guide as main Flutter repo. For specific code formatting, we follow the Effective Dart guide.
All submissions, including submissions by project members, require review. We use GitHub pull requests for this purpose.