Community

Code of Conduct

Introduction

The QuantConnect community consists of 250,000 quants and investors with diverse backgrounds. Our platform supports several channels of communication so that our members can discuss with the core team, other community members, and third-party contractors. Our community members are a great source for assistance when creating trading algorithms, but we recommend all users complete our base training material before requesting assistance from other members.

Our community forum was created to be a hub for sharing quality quantitative science insights, discussions on quantitative philosophies, and solving problems. Our goal is to embrace new ways of thinking while keeping a friendly, welcoming environment where people feel comfortable amongst their peers. Our community's exceptional and diverse range of opinions and experiences make us a unique platform. Coming together with mutual respect and courtesy can unite us in growing together as quants.

We ask that our users adhere to the community code of conduct to ensure QuantConnect remains a safe, healthy environment for high-quality quantitative trading discussions.

Expectations

If you're here to get help, make it as easy as possible for others to help you. Follow our guidelines and remember that our community is made possible by volunteers.

Be clear and constructive when giving feedback, and be open when receiving it. Edits, comments, and suggestions are healthy parts of our community.

If you're here to help others, be patient and welcoming. Learning how to participate in our community can be hard. Offer support if you see someone struggling or otherwise in need of help.

Be inclusive and respectful. Avoid sarcasm and be careful with jokes — tone is hard to decipher online. Prefer gender-neutral language when uncertain. If a situation makes it hard to be friendly, stop participating and move on.

The following table shows examples of friendly and unfriendly content:

UnfriendlyFriendly
res-cross "Google is free!"res-cross "I think googling this might provide you with more helpful information."
res-cross "Obviously that's wrong because..."res-cross "I think I can help you with this! Try this..."
res-cross "Can you speak English?"res-cross "I think you're trying to say ____. Is that correct?"
res-cross "Your strategy will never work because ___."res-cross "Here are some suggestions for your strategy..."

Policies

Please follow our community policies.

Item green tick Respect

We want our forum to be a place of general respect for one another. Keep interactions constructive, but friendly and lighthearted. Remember — we're all here to help one another and keep our community strong.

Item green tick Due Diligence

We have hundreds of quants posting their questions. Your question is important, but make sure to check a few places before posting. We've worked hard on providing comprehensive documentation and bootcamp tutorials — make sure to check there first. Next, try Googling the concept to see if you can get another perspective before posting. Furthermore, our Debugger is a great tool to identify bugs in the code logic.

Item green tick Relevancy

Keep posts related to algorithmic trading or quantitative finance.

Item green tick Patience

Be patient with the community responses to your questions. Keep in mind the community are volunteers contributing to your quantitative growth voluntarily. When possible, answer your own questions to leave a path for future readers. Avoid "bumps", "+1", "Any Update?", double posting, thread hijacking, or necro-bumping discussions. Contributions are often rewarded with QuantConnect Credit.

Item red cross Bigotry

QuantConnect is firmly rooted in our policy against bigotry in our community forum. We are vehemently against racist, sexist, xenophobic, homophobic, or otherwise discriminatory behavior in our community. Any language that may offend anyone based on race, sexual orientation, gender, religion, will not be tolerated.

Item red cross Harassment

Bullying is not a part of our core culture at QuantConnect. We do not tolerate bullying, sexual harassment, profanity, threats of violence or otherwise, or any sexual harassment in our community forum.

Item red cross Bug Reports / Data Issues

We request bug reports be sent to the Support Team. The forums are not an effective bug tracking tool and often the reported issue is simply confusion on how the platform operates. For data issues please report the specific dates, times, contracts, and type of issue to the Data Explorer Issues List. This is a system we've designed to track, fix and notify users when issues are fixed.

Item red cross Promotional Activity

Spam and other forms of promotional activity isn't permitted in the community forum. Posts that deliver immediate value to the readers are permitted such as sharing a well-performing algorithm with an attribution to the author's company in the code comments.

Item red cross Can Someone Make My Algorithm?

We understand people are at different stages of their quant-growth, but if you are soliciting assistance you should have completed Boot Camp, and attach a backtest or code snippet with your best attempt at building your algorithm. This shows respect for the reader's time. You will need to know how to code to use QuantConnect.

Reporting Violations

We monitor our forum diligently, but if you see something unsavory, please message us to report the activity.

About This Code of Conduct

We aspire to have a welcoming community filled with high-quality discussions about quantitative and algorithmic trading. Since our founding in November 2012, we ran an informal code of conduct and evolved those principles to support the community. Starting January 1st, 2021 as the scale of community content surpassed our ability to review each post, we have sought to write down these guidelines to provide transparency and framework for productive discussions. We welcome your feedback and expect this code of conduct to evolve over time.

You can also see our Videos. You can also get in touch with us via Discord.

Did you find this page helpful?

Contribute to the documentation: