Feature Requests

Introduction #

The Liferay open source project relies on its community for many of the evolutionary and revolutionary ideas that eventually find their way into a release. Liferay strongly believes in empowering the community not only to be able to create change through feature requests but also to feel responsible for socializing, communicating, recommending, and implementing their own and others' ideas.

The JIRA issues database and the Feature Request Dashboard aim to do just that! By having an easy way to create, view, and recommend feature requests, the community can help steer the direction of Liferay!

This is a tool used by the community, for the community. It allows the best feature ideas to float up based on recommendations from the community. The community can then target the most desired features in future projects and releases.

What is a Feature Request? #

Feature Requests are concrete ideas for implementing new features in or around the Liferay Platform. Feature Requests can be completely new ideas, or enhancements to existing features. Feature Requests can be implemented by anyone in the community. As a commercial entity, Liferay Inc. will choose to implement some, but not all Feature Requests. Community members are strongly encouraged to help recommend and even implement features that are important to them, and share this with the community. That's what open source is about, and this will serve to strengthen the platform for others.

It's also important for Feature Requests to be concrete - that is, something that is reasonably well defined and can be understood by someone with a basic understanding of web software. It is not a complete functional specification, but instead is a beginning of an idea for a feature that could be implemented directly in the Liferay Platform, or as an add-on through the Liferay Marketplace.

What is the Feature Request Dashboard? #

The Feature Request Dashboard is a web page on liferay.com that allows the community to easily view and create new Feature Requests, in addition to providing general information, polls, recent participants, and more.

Viewing Feature Requests #

In the central section of the dashboard, you'll find the following lists:

Latest Feature Requests #

This list shows the most recently created feature requests, with the most recent requests shown first. Clicking on the title or number of votes for the request will display a window showing details of the request, which you can use to find out more details about the request. If you are logged into issues.liferay.com, you can vote and comment on the request.

You can also click on one of the various social media icons to share the feature request with your social networks. Sharing is one of the best ways to draw attention to your favorite requests (whether you created them or not).

Most Popular #

This list shows the most popular Feature Requests, based on JIRA votes.

Once a Feature Request is created, it is the responsibility of the creator and anyone else interesting in seeing the feature implemented to communicate (share) the idea with others, to spur interest. As a given request accrues votes, it will rise in the Most Popular list, allowing the entire community to see the most desired features, and take action if desired. 

Under Development #

This list shows each Feature Request that Liferay Inc. has selected to develop. Feature Requests listed here are under active development and will appear in the next major Liferay release.

Recently Resolved #

Once a Feature Request is actually implemented, either in the core Liferay Platform, or as a Marketplace App (authored by Liferay Inc. or any other community member), the Feature Request will be closed with an appropriate resolution (see below), and be listed here, ordered by date.

Each of the above lists also features an RSS feed for monitoring the list outside of the Dashboard, using the RSS Feed link at the upper right of the list. For better performance of the dashboard, only the most recent Feature Requests are shown here.  Clicking the Show All link (next to the RSS Feed link) will reveal the entire list of Feature Requests for that category.

Recent Participants #

A quick snapshot of people who have recently created or participated in a Feature Request. Hovering over the picture will reveal the person's name, and clicking on them will take you to their JIRA profile. If you are logged into issues.liferay.com in the same browser, you will be able to see each participant's picture, otherwise a generic picture is substituted.

Creating Feature Requests #

On the left side of the dashboard is a listing of all of the Feature Areas in Liferay (for example, WCM, Collaboration, Security, and many more), along with the number of Feature Requests created in that area. Clicking on the name of a Feature Area will reveal a list of Feature Requests in that area. Clicking on the + icon will allow you to enter a new Feature Request, by filling out a simple form including the Summary (short sentence describing the request), and a longer Description (for giving additional information about the feature).

Writing Good Feature Requests #

A good feature request is:

  • A concrete idea that is reasonable for use in the core Liferay Platform or as a Marketplace App
  • Includes relevant information such as background information, the need for such a feature, pertinent use cases, expected outcomes, and any other information useful to one who is considering the request.

Before filing a feature request, be sure to search existing feature requests to see if the idea has already been proposed. Feel free to add commentary to existing feature requests as needed, by entering JIRA comments for the Feature Request ticket.

Once you write your feature request, socialize it using the convenient social networking links on the dashboard, or use your own mechanism. Garnering votes is one of the most important things you can do to increase the chance that someone will implement it!

How do I promote a Feature Request? #

Once you've created a feature request, your next step is to let the community know about it! The more people learn about your proposal the more feedback you will get and the more people will comment and vote for your feature. Feature Requests with more votes and activity will always have a better chance of being implemented sooner. This applies not only to requests you have made, but to requests made by others that you wish to promote and for which you want to generate buzz. Here are some ways in which you can promote these feature requests:

  • Tweet it
  • Like it on Facebook
  • +1 it on Google+
  • Mention it on the Liferay Forums
  • Talk about it in any event or conversation (electronic or not) with people interested in Liferay

The Feature Request Dashboard includes convenient links for posting of yours and others' ideas to your favorite social media networks.

In general, remember that making buzz is good, especially if it leads to a healthy conversation that improves upon the original idea. However, try to avoid being too pushy or inflexible, which might have a negative effect.

Who can implement Feature Requests? #

All feature requests are open to anyone in the community to implement. Not all top-voted feature requests will be implemented by Liferay Inc. Other community members in the Liferay Ecosystem might consider a particular Feature Request as very important to them, and make the effort to implement it, either as a contribution to the Liferay Platform or as a separate Marketplace App. This is highly encouraged in the Liferay community!

Liferay Inc. will periodically review a subset of the submitted Feature Requests (based on criteria such as number of votes), and determine whether or not to implement the feature itself. Once Liferay Inc. reviews a given Feature Request, a special tag reviewed-by-liferay-inc will appear alongside the request on the dashboard. If Liferay Inc. decides to implement the feature request (either in the core platform or as a Marketplace App), the status of the Feature Request will change to Selected for Development, and a separate workflow (beginning with the creation of one or more linked Story tickets) will be filed, and the normal Liferay software development process will see it through to the next major Liferay release.

If Liferay Inc. does not desire to implement the request itself in the next major Liferay release, the Feature Request will remain Open (but will have the reviewed-by-liferay-inc tag, indicating Liferay Inc. has reviewed it). 

Liferay Inc. does not reserve the exclusive right to ideas that it decides to implement itself. If you wish to implement an idea that Liferay Inc. has also decided to implement, go for it! All ideas, whether or not implemented by Liferay Inc., must pass through the same quality and relevance filters that any software feature must go through, before being included. Again, Liferay Inc. will not implement every Feature Request - through this open process, the community can see exactly what people are looking for, and can evaluate the suitability of the feature for themselves, and promote it, or take the extra step of implementing it as a core contribution or a Liferay Marketplace App.

How do Feature Requests get Resolved? #

Feature Requests get Resolved in one of the following ways, and will appear in the "Recently Resolved" list for a period of time, with one of the following "Resolutions":

  • Discarded. The Feature Request is not appropriate for Liferay or for a Marketplace App. An explanation will be entered into the comments field of the Feature Request.
  • Duplicate. The Feature Request duplicates an existing Feature Request, and will be linked to the duplicate Feature Request.
  • Implemented in Platform. The Feature has been implemented in the Liferay Platform (either by Liferay Inc. or contributed via a 3rd party). The Fix Version/s JIRA field will indicate in which release the feature can be found.
  • Implemented in Marketplace. The Feature has been implemented as a Marketplace App (either by Liferay Inc. or a 3rd party). A link to the Marketplace app will be entered into the comments for the ticket.

More Information #

0 Attachments
Average (2 Votes)
The average rating is 5.0 stars out of 5.