There are some external tools I'd like to use during my build that are distributed by chocolate.org. Do\could you support build.bat using choco to install those tools on the build machine? I'm assuming the build machines are snapshot VMs that get reverted after each build? That would also be nice to know\have documented.

The licenses view with pie chart is great, but I'd like to be able to download the license report as a CSV file. I need to provide a report of licenses for due diligence purposes and giving a login to MyGet to view it directly is not a viable option.

I like the fact that there is now support for npm and bower packages as well. Adding support for Ruby gems would even be more awesome. Are there any plans for this?

So do we want to have a private docker hub registry so that we can store our docker images? Hmm myget is great for nuget, NPM, bower and VSIX. Does docker come into play here? I can see some automation scenarios for deployments with chef to Linux or Azure but this would probably be more of a store and retrieve manually when needed. There is a paid subscription private hub with docker but it would be nice to have this all under one roof. Thoughts?

myget currently displays the content of README.MD from my master branch (which is perfectly fine in most cases) but sometimes the release I'm working on includes changes to the README and I would like to be able to review these changes before merging my release branch into master and publishing my release.

I would like to support python package sources.
Is there any change you can support that?

In short: Google Analytics for packages

It would be grat to have a series of metrics and statistics about my feed. Where do downloads of packages come from? Which version of NuGet are they using?

My build produces six different build logs that I would like to examine for each build. You could identify them by suffix. Mine are suffixed with diag, detailed, normal, error, summary, and warning. Or you could choose a suffix. Say anything ending in build.log. They get big so maybe you only need to retain them for a few days.

Hi,

At the moment all permissions are assigned on per user basis which requires significant effort if you have more than a handful of users or/and a several feeds.

* Could you rovide a way of assigning permission on per group/role basis so it is enough to assign user to a single role/group and then they get access to required resources ?
* Could you also add ability to assign newly authenticated users to a default group/role

Thanks

Pawel

I have just uploaded package and unfortunatelly myget downloaded about 30 depended packages, it was my mistake. I would like to remove these packages but I have to do this one by one, this will take me half an hour :(

Bitbucket has a feature called "Deployment keys" which is primarily used for build services because they give read-only access to repositories, and does not count as an user license.

https://confluence.atlassian.com/display/BITBUCKET/Use+deployment+keys

This would be great for small teams that uses bitbucket's free plan for 5 users, because we don's have to create a "fake" readonly user for myget's Build service.

I know that we can use our personal accounts as authentication, but I would rather not :-)

I'd like be able to highlight multiple versions of a package and then perform the same operation on all of them.
We've got a bunch of packages that were uploaded and shouldn't have been. At the moment it takes about a chunk of time to delete each one, with lots of waiting for pages to refresh. Because the delete doesn't give automatic feedback I then have to keep track of the ones I've already deleted.

It would be nice to get a progress indication when uploading packages (especially for larger ones).

It would be good to see what other packages in myget that has dependencies to the package currently being viewed.

Pin all packages of a particular version

Hey X and M,

I like the product so far but the Add Package window definitely needs some improvement or a total makeover even. The autocomplete in the search bar is also flaky to scroll through.
Why not give the option to actually search and select from the resulting packages?

It would be nice if packages that were completely unlisted where shaded red or something to indicate that status without having to click through.