This is a joke right? Those are our choices? I vote you don't change the name, all of those are terrible.

Wow I would rather have my ballz ripped off than choose one of those choices, seriously awful! I refuse to choose one of those!

Ok. I hate to be a bad citizen but really, those names are AWFUL. I also vote no name change. None of those names have anything close to a good feel. Sorry guys but my opinion is this effort is a massive fail.

I was never a big fan of NuPack, but these names are even worse! Is this a joke? Those seriously can't be the best names that you guys came up with.

Yeah those suck.

Eh, NFetch isn't so bad; it's got a nice ring to it and it brands well all the other dotnet "Nxxx" projects out there.

Don't want to be too harsh, especially since you're not the one to blame, but I have to agree, they aren't really good. SnapFetch actually isn't that bad, it's just a bad name for a Packaging System IMHO. Same for NFetch. DotNetPack and OuterPack are just uninspired and Bland :(

I know, no suggestions, but I still make some, e.g. the PowerShell-styled "Get-Packages", or something that has Repo(sitory) in it. Or something that's really made up. "Parcels"? "NetLets" (inspired by CmdLets)? "FuncBits"? (Functional Bits, as in Bits and Pieces).

I don't know, all I can say is: I really recommend taking another shot at this.

If its like apt-get, then rename it net-get

If its supposed to work like gems, then ngems

SnapPack (the .com and .org are both parked and I bet they could be obtained)

How about "GuPack" ;)

This must a publicity stunt - like the GAP logo thing.

Something can be said for having a name like similar tools from other platforms. Its worked well for NUnit, PSake, NHibernate, etc...

I agree that all of these are worse than NuPack.

As I mentioned on OuterCurve, I think nFetch is the most conventional and self explanatory.

As someone who has tried naming a startup before, I sympathise.

Ninclude

After reading the announcement explaining the background of this renaming snafu, I suggest you simply revert back to the original name "NPack". It's simple and consistent with the NWhatever thing you've got going on, and it makes sense given it's a packaging system. What could be more perfect?

NPack, NPack, NPack.

You had it right the first time. You know you did.

Could go for the Russell Brand approach:

Haack's Paacky Whaack

But I guess things that sound like open source projects works aswell.

NDubz did it when they stopped producing their music in Java and used .NET Framework insted. NHybernate isn't on iTunes yet.

What about SubPack? Sounds slightly healthier than McPack.

I seriously urge you to reconsider those names. NUPack is a TON better than the ones you have suggested.

I suggest DotStream, LibStream, or NetFetch.

Absolutely rubbish names.

NuPack is better than the suggested names.
I think you should un-announce the renaming ;)

But wait... what about: Microsoft .NET Visual Studio Package Download Foundation Add-in?

I did not lookup if it meets all the criteria, but how about
uNpack? ;)

// Ryan

@Martin I'm with you, was about to suggest it myself :)

NPack.

@Phil Sorry, posted before I saw your 2 minute earlier comment about NPack :)

All of the proposed names are horrible. If you insist that these are our only choices... well, shucks then I guess, I vote for none of them.

If you wanted us to propose a name... then I'd rather have NCase, but that's also taken... damn. I feel your pain, but again, those proposed names are worse than nupack.

Maybe it is better to propose other 5 names to choose from...
I vote for none of the proposed names and NuPack sounds better :)

Phil,

I'm your biggest fan. I love Microsoft. But...these names stink like rotten fish.

Please....don't embarrass the community.

Hmmm...I like NuGet.

FUBUPack

What about PackMan name? :)
Or dotPackMan

Guys, let's go for a brainstorm here
nupackname.uservoice.com/forums/82621-general

Lol. :D

You look at all the comments from all the programmers and you still need to wonder why software doesn't get made?

The instructions are clear yet nobody is following them. :P

Why, we're like art critics now!

I vote for NFetch. (It's the best of a sorry lot).

See guys, wasn't this simple?

You'll almost always add a reference to the packaged code so nRef?

Pak

From the four - NFetch

New - pacaroni

I would have voted for NGem.

NPack... it's the best of a bad lot.

How about Cargo?

"Cargo (or freight) is goods or produce transported, generally for commercial gain, by ship, aircraft, train, van or truck. In modern times, containers are used in most intermodal long-haul cargo transport."

If we have to change, here's some 2c brain dumps...

NPack +1
.Pack / dotPack
RefPac / RefPack / .Ref / NRef(as in reference package).
Pallet

Out of those I think NFetch is the best.

Shame.. I liked the NuPack name :(

I'll vote for NInclude, does what it says on the tin and (IMHO) quite snappy.

+1 for Cargo - short, recognizable, meaningful

Rob Conery have a good suggestion, compatible with Microsoft Branding Style Guidelines: "Microsoft .NET Live Code Delivery Platform Installer" ( http://goo.gl/tD7X )

I suggest: Visual Studio Packing Utility For .Net Developers Enterprise Edition

To be serious i suggest: VsPack because it works with Visual Stuido :-)

Trying to be civil about it, but it's hard. NuPack is soooo much better. Part of the allure of "gem" is that sounds cute and works well as a noun. "There's a gem for that"!

Therefore I really like one suggestion by "GP" above, "NuGet", which could easily be transformed into "nugget" (maybe in pronunciation only). "I'll just get a couple of nuggets to complete this task".

Keep the current name. Renaming it will just cause confusion and this is all just bikeshedding anyway.

NuPamelaAndersonPack?

Two options missing:

.NET Package Manager Windows Edition

Visual DotNet FetchSafe Suite

Is that cut-off in PDT? :)

IMHO NFoo implies a 'port' of the Foo project? (NHibernate, obviously, being a/the prime example)

In the most civilized manner possible, I'll add 2 more names for no real reason (since the finalists are already chosen :)

#1 - since it's not about fetching arbitrary packages (we're not installing applications AFAICT, in contrast to what apt/dpkg/rpm/etc can do), focus on the role of 'get this dependency' - ***DepFetch*** (google shows it not having any obvious usage currently)

#2 - gem makes sense for ruby (obviously). In similar fashion, we could find a name based on the Iron* line of naming (especially as a show of support as those teams have suffered). Combined with a focus on simplicity, and inspired by my son's favorite movie (Cars), we get Rust-eze or ***RustEze*** (PascalCasing for Anders reasons :). We even get a Billy Mays-like tag line for free: 'Bringing you libraries with the Power of Oxygen!' ... there are shorter, dorkier versions around too, of course, like 'Some assemblies required' :)

Go for NPack is better than the suggested names.

Question. How many people have to comment on the absurdness of the choices given, in order for the team to realize that the factors for choosing the name would never result in a good name?

Just ask Jeff Atwood what happened when he let the community brainstorm names for their newly launched stack exchange sites, but limited the suggestions to those with a domain available. He launched, and then reverted the name (and redirected the domain). At least he had the courage to do so. With NuPack I don't think it's gonna revert, no matter how bad it is. Sadness.

How about NCourier?

I think the physical package delivery analogy matches the project's purpose quite well.

sNatch

Why not IronPack!!! :D

I agree these names suck :)

I vote for no name change or nPack.

Off-topic: why not learn from Mercurial and make your commands less verbose e.g. add instead of add-package, list instead of list-packages, etc... maybe even np instead of nupack or npack. so you can do things like

np list
np add

etc... less typing = no carpel tunnel = good

Nice work though and I will try and contribute whenever I have time.

In honor of the Lewis and Clark expedition: Packagawea

But seriously, the given names suck. So let me make a serious suggestion I came up with while thinking about names this morning: Modularizer.

It's descriptive, it's cooler than any of the given names. And since I liked the name regardless of whether it gets used or not, I registered the domain and would be happy to donate it to the cause.

NBubbleWrap

Hmmmmmmmmm...

A New Package Manager, what to call it? NuPack? Apparently not.

Pacman? What do you mean its already taken?

Well what about Packman? Too Close to Pacman?

HaackMan? Too personal?

Get Me Code - GMC - more about trucks.

MSVSPM - We all know how much Microsoft like acronyms (Microsoft Visual Studio Package Manager)

GuPack (named after that red polo) still too personal?

RedPolo? - does RedPolo have a chance? - All .net developers will think that they have their very own guy in a red polo running around fetching their code.

OK naming stuff is a bit more difficult than first imagined, especially Big Company Stuff.

Just call it Brian.

k, my vote is for nbacon, nbacon.com is available. bacon! bacon! bacon! Everybody loves bacon.

+1 for NuPack being better than the names listed in this post

Guess MS could have used this link before picking the original name http://justfuckinggoogleit.com/?q=~nupack

I guess FudgePack isn't a good one either?

Those are still free:
uupack.com
vupack.com

qupack.com
wupack.com
xupack.com
zupack.com

The first two are my favorite...

My suggestion would have been: NStall

;)

hmm..
- No "Nu" because so many future users will wonder what this is.
- No "Iron" because this is not a DLR related project. Much confusion will come.
- No "N" prefix unless you really want to hint people this is ported from other platforms. This is no longer the case for many apps with similar naming but still I may think so when reading such name.
- No "Fetch" or words that need better explanation of the job of the thing

Then what? Really couldn't think of something sold enough. Maybe ".NET Package Explorer"? It should be as easy and straight forward as this (without more geekiness or special name parts). Not saying it should be exactly this one though, but you get the idea...

I knew this would happen the moment it was announced. Microsoft either comes up with names like Extended Package Manager Professional 2010 Live or something like NuPack.

Outercurve is pretty silly too. Funny, since I think Codeplex is a really good name.

Anyway, I'm not voting, new names are silly too.

hibernate--> NHibernate
gems--> NGems

NetGet
SharpPack
NoDllHell

nsetup.net

No need to change. Leave it as is. NuPack is my vote.