Odoo R&D

Task Guidelines — All developments should conform to a series of usability guidelines.
Task Stages — The lifecycle of tasks follows a precise process from inception to deployment.
Translations — Stability guidelines.
RD Teams — You are not alone, a guru is here to help you.
Git — We host Odoo's codebase on GitHub repositories.

Submitting ideas

If you have an improvement to suggest, send it to the internal feedback email address (ask a product owner for it).

Write a good mail subject because it will become the title of the task: "[app_module] short explanation"
Motivate your idea with at least one use case. Don't say: A lot of clients are asking for it. What's important is why they want it.

Is the technical cost worth it ? Priorities are based on the value of a feature divided by the development efforts. Example: English typo because it's cheap to fix, Odoo.sh because it is valuable
Does it impact a lot of users ? The more users are impacted, the more valuable a task is; widely used apps (CRM, stock, accounting, website, project....) or cross-app features (chatter, kanban view, mobile app...).
Does it improve the on-boarding experience ? Improving new users' experience is a top priority: ease of use, first steps, wow effect. When pleasing expert users conflicts with simplifying for new users, the priority goes to new users.
Will it have an impact on the business ? A task is valuable if people are ready to pay for it, or if it will bring more users to the platform. Users' pain points are always valid, but users' proposals seldom are.
Is it a new feature ? Improving existing apps is usually preferred to than adding more apps or features: 20 perfect apps is better than 40 half-perfect apps.