5 comments
Comment actions Permalink

The short version of the answer is: you don't. The wishlist is not curated in any way, it does not influence JetBrans' planning in any way, and many of the requests there are already supported as features in the products. Also, it doesn't look like the wishlist influences which plugins get built by the community.

If you want JetBrains to add a feature to our products, please file a YouTrack issue.

0
Comment actions Permalink

Ok, so how do I influence which plugins get built by JetBrains/the-community?  I have a concept idea for a code review plugin, and my employer wants an estimate of how much it would cost someone to build (we wouldn't want to build it ourselves).

0
Comment actions Permalink

If you want to hire a team to build a plugin for you, the wishlist is really not going to help you. As for JetBrans, we have a code review product already (called Upsource), and we don't plan to do any code review plugin other than the Upsource integration with IntelliJ.

0
Comment actions Permalink

So then, to summarize:

  • JetBrains has a central location (wishlist) for people who want plugins developed (clients) and people who can develop plugins (pdevelopers)
  • A client cannot add a wish
  • A pdeveloper cannot mark a wish as fulfilled
  • The wishlist is stale but still live
  • The wishlist isn't a YouTrack instance
  • A client can find a pdeveloper, but JetBrains will not help the client
  • Users already have to leave the IDE for git, so why should code review be any different?
  • JetBrains wants users to "develop the JetBrains way" and not "develop with pleasure"


Something doesn't make sense here.

0
Comment actions Permalink

Yes, you're right. We're going to solve the things that don't make sense by removing the wishlist feature from the plugins website.


0

Please sign in to leave a comment.