James (anath47) wrote in suggestions,

New Suggestions System

New Suggestions System

Short, concise description of the idea
A whole lot of great suggestions get left uncoded and then forgotten. Many of these suggestions that recive a lot of support in their comments area die soon after because no one picks them up.

Full description of the idea
reading back to see if my suggestion has already been posted, I came across sevral great suggestions, that everyone agreed were great ideas, but nothing was ever done about it. a perfect example is the new LJ comm tag, suggested over and over, never implimented until now. What I'm suggesting is a coalition between suggestions, lj_dev and perhaps [Unknown LJ tag]. When a suggestion starts out in suggestions it will be commented on, as normal, by users who will argue out it's merits. Instead of going into memories, it will go into a page similar to memories(or an enhanced memories) that states the idea in a simple manner and weather or not the idea was supported in the suggestions forum. If the idea is rejected, it's left at that. If accepted, the LJ dev crew can start work on it, which leads to the next part of the suggestions development. On this enhanced memories page, it will say which user has picked up the task and the percentage done, all the way through implementation. once it makes it into changelog and the feature is fully implimented and the memory is updated to show that it's in place, and possibly linked to a FAQ to show how the new feature works, if applicable.

An ordered list of benefits

  • more dynamic LJ system.
  • great ideas will be put into use more often.
  • new developers will have a place to go and know exactly what needs to be done, at least in the way of suggestions.
  • less redundant posting of ideas, old, but still good ideas will be used.
  • more suggestions supported by the LJ community will be put into effect.
  • better organization of suggestions and the development there of.
  • An ordered list of problems/issues involved

  • if the suggestions maintainer has to maintain this as well, their job will be a lot more time consuming.
  • people agruing weather or not their suggestion should have been marked rejected on the board.
  • getting developers to keep on task and keep the maintainer updated once they accept the job.
  • setting up the table all of this will go in, but this is minimal.
  • An organized list, or a few short paragraphs detailing suggestions for implementation

  • I think I did a pretty good job above.
  • Tags: ~ historical
    • Post a new comment


      Anonymous comments are disabled in this journal

      default userpic

      Your reply will be screened

      Your IP address will be recorded