{"id":11504,"date":"2016-07-07T04:43:34","date_gmt":"2016-07-07T11:43:34","guid":{"rendered":"\/blog\/?p=11504"},"modified":"2023-06-05T16:07:33","modified_gmt":"2023-06-05T14:07:33","slug":"a-guide-to-get-your-favorite-feature-in-exo-platform","status":"publish","type":"post","link":"https:\/\/www.exoplatform.com\/blog\/a-guide-to-get-your-favorite-feature-in-exo-platform\/","title":{"rendered":"A Guide to get Your Favorite Feature in eXo Platform"},"content":{"rendered":"

At eXo, we are proud of our community, and we are grateful to all who contribute to make eXo Platform a better solution and an effective ecosystem.
\nAs the main contributor to the source code, eXo has a great responsibility toward the community, and we strive to best serve both through discussion forums, through documentation, and in the constitution of our product roadmap.<\/p>\n

<\/p>\n

One of the biggest challenge of our product managers is to select the features that will make up this roadmap. Indeed, there are so many different requests that we can\u2019t satisfy them all. This can sometimes generate some understandable frustration. And let’s be honest–it takes a lot of effort to be heard in such a large community. Therefore we\u2019ve created a handy guide to give the best chance for your favorite feature idea to capture attention to our product team and ultimately to be implemented.<\/p>\n

Do your homework<\/h2>\n

You think you have the best idea. And you are even surprised that no one had it before you. Well, think again–someone has probably already thought about it. But to be sure, go to the Feature Requests<\/a> page and run a search.<\/p>\n

\"ScreenS<\/a><\/p>\n

If you find nothing, I suggest you expand your search to the discussion forums<\/a>. In fact, your idea may have been mentioned during a discussion on the forums, and an answer to your request may have already been given.<\/p>\n

Warning: it is very tempting to skip this step and simply create a new feature request. After all, someone will be notified when you make your request, right? This may be true, but in doing so, you risk creating a duplicate request.
\nAnd be aware that in order to serve the greatest number, the eXo product team focuses greater attention on requests that are voted on and discussed by many. Thus, if a request exists, it is always a better idea to weigh in on it by leaving a comment or by rating it.<\/p>\n

Weigh in on existing requests<\/h2>\n

To support an existing feature request, we encourage you to vote and give your opinion in the comments.<\/p>\n

\"wiki<\/a><\/p>\n

In the interest of all, avoid useless comments like “+1<\/em>,” “me too<\/em>,” “great idea!<\/em>” or “nope<\/em>.” However, opinionated comments on how to implement the feature, examples of use cases, or anything that clarifies your expectations are more than welcome. In general, anything that will advance the conversation will be useful.<\/p>\n

While you’re there, take a moment to browse other requests and vote on the ones you find interesting. Indeed, the rating of a request is the average of the ratings awarded. So more ratings indicate that there is a greater overall interest in a request.<\/p>\n

Write the perfect request<\/h2>\n

When you are sure that the request does not already exist, you are ready to enter a new one. Here are some recommendations for your application to be taken seriously.<\/p>\n

\"Support<\/a><\/p>\n

Give it a good title<\/h2>\n

To be effective, the title of the request must concisely describe the expected functionality. Avoid the following:<\/p>\n