Feedback Package descriptions

Would it be possible to flesh out the package descriptions a bit?

Stuff like "The editor coroutines package allows developers to start constructs similar to Unity's monobehaviour based coroutines within the editor using abitrary objects. " is meaningless for many users.

And when new users read "[The] 2D Tilemap Editor is a package that contains editor functionalities for editing Tilemaps."... that doesn't explain why it's included in the 3D project template they just started.

There aren't that many packages available so having considerably more detailed descriptions shouldn't take you that much time. It would also be a good opportunity to do a QA check on everything. In the Editor Coroutines description above, there's a typo in "arbitrary" and the package name is not capitalised (inconsistent).

In an ideal world, for each and every package it should be clearly slated:

- when this package is needed
- when this package is helpful
- when this package is not needed

 

Hey there.

Thanks for your feedback here! I've passed this along to the Package Manager team who have advised us that they are very well aware of this issue. While we do have internal guidelines, some are slipping the mark. We've taken some steps internally to see if we can improve on this and have authors perform a rewrite of their package descriptions.