Very good and important question
So the main role is to of course constantly make the UiPath better and better. Every resource is limited and we are only human. Many times happens that people need some activity related to one of application. Imagine that you are user of this application and you figured out how to work with Studio on this app. So you are publishing your workflow as a library and you can share this library among any other Studio users. This is very similar like “mod scene” for computer games. We are allowing everyone to build and extend Studio capabilities
Regarding feeds mentioned by You:
- This is feed which comes from orchestrator. If you have some packages/libs implemented in Orchestrator but you don’t have them in Studio, this is the way to make them implemented in Studio too.
- Same as above but applies to local kept packages.
- Feed for official UiPath company packages
- This is the place (www.go.uipath.com) where every user can make an account and share his own packages/libraries to the other
- Feed for packages made by other companies and published in Nuget.org (not all packages are working)
- You can make your own feed (network/local) and just use it here.
I think there isn’t the best practice but as a good practice I think it’s awesome if you can share your work with the others. So parallel with keeping your libs locally I encourage you to publish them in Go! as well!