New Post: Creating a ".NET Framework Packages" NuGet feed

For discussions about the new NuGet API design, you can read the spec here:
https://github.com/NuGet/NuGetApi/blob/master/specs/API-v3-Specification.md

And then you can file issues on that github repository.

Private repositories are out of scope for nuget.org. MyGet.org does a good job with private repos, and we don't intend to go that direction with nuget.org. Instead, nuget.org will be the home of public packages, but we'll be providing several means for serving subset feeds. Think of it this way: nuget.org is the gallery of all public packages, and it will serve customized feeds that are all subsets of the full gallery. No feed from nuget.org will contain a package that is only available on that feed.

We do understand the important of companies needing to have private feeds. For that, there are several options:

1. MyGet.org
2. File share based feeds
3. NuGet.Server based feeds
4. Internal deployments of the NuGet Gallery from http://github.com/nuget/nugetgallery
   

We do want to make internal deployments of the NuGet Gallery simpler over time. Couple that with the extensibility point we're discussing here where the registry can be used to augment users' nuget.config settings, and the enterprise space should improve quite a bit.