Author Topic: Priorities for feature/request implementation  (Read 2026 times)

Offline alex

  • Developer
  • Global Moderator
  • Hero Member
  • *****
  • Posts: 2172
  • Karma: +37/-3
    • View Profile
    • HippoEDIT
Priorities for feature/request implementation
« on: May 20, 2011, 10:15:02 am »
There are a lot of features suggested/requested from one side, but there are some resource limits from another side.
So, not all features can be implemented immediately,  but most important first and less important later. And some never.

Here is brief list of priorities, which are taken into account, when selecting what is more important and what should be implemented first:
  • it is a usability improvement for current feature
  • it is for text editor itself (not for GUI around)
  • it is simple to implement, but brings significant benefits
  • it is not a new entity (not some new concept/way but reuse of existing)
  • it is a basic functionality, which can be used to extend or build other features
  • it suits good into current architecture (basically it is same as easy to implement and basic feature)
  • a lot of people request it / it brings new customers
  • ....
  • ....
  • it is a documentation
  • it is an promotion work

And also very important: I like the feature.  It is maybe on place 3-4.

 

Related Topics

  Subject / Started by Replies Last post
2 Replies
1842 Views
Last post February 23, 2009, 03:34:54 pm
by alex
10 Replies
4157 Views
Last post April 23, 2009, 04:58:57 pm
by Chuck
3 Replies
1734 Views
Last post September 02, 2009, 09:10:11 pm
by alex
0 Replies
1100 Views
Last post January 28, 2015, 02:10:32 am
by alex
4 Replies
1025 Views
Last post September 20, 2016, 05:59:04 am
by wendy