So we can do this in the current codebase but what's our longer term plan on where the source for .nuspec content should be? In Nu, the creator of the Gem holds the info and we encourage them to either a) talk to the maintainer of the orginal project to
get them to fold it into their own build process or b) be the Gem owner and just keep it up to date separately from the project code. I did this with Ayende and RavanDB for example, and just made him the owner of the gem so it works well as it's part of RavanDB
build now.

Thoughts around longer term storage, short term updates, etc. for packages?

Eventually, we'll have a real gallery. For now, people can just send pull request on the http://nupackpackages.codeplex.com/ repo. 3 people already submitted packaged this
way today. But this is definitely a short term solution.

Eventually, we'll have a real gallery. For now, people can just send pull request on the
http://nupackpackages.codeplex.com/ repo. 3 people already submitted packaged this way today. But this is definitely a short term solution.