BLOG

Changing the NuPack Project Name

Oct 21

Written by: Phil Haack
10/21/2010 4:27 PM  RssIcon

We’re going to change the name of the NuPack project and we want your help!

Why is the name changing?

We want to avoid confusion with another software project that just happens to have the same name. This other project, NUPACK, is a software suite by a group of researchers at Caltech having to do with analysis and design of nucleic acid systems.

Why was it even called NuPack?

When we started incubating this project, we developed it under the code name NPack. After merging with the Nu team, it seemed like a good idea to merge our names too and call it NuPack.

At the time, we didn’t find any uses of the NuPack name in the same domain as our package manager.

It’s not always easy to find a project name that’s not already in use by someone else. We’re trying our best though and definitely want to do what’s right.

Fortunately, the Outercurve foundation has provided some helpful guidance in a blog post entitled:

The Naming Game: Things to consider when naming an open source project

What is the new name?

We don’t know. You tell us! The NuPack project team brainstormed a set of names and narrowed down the list to four names.

I’ve posted a set of names as issues in our NuPack CodePlex.com site and will ask you to vote for your favorite name among the lot. Vote for as many as you want, but realize that if you vote for all of them, you’ve just cancelled your vote.

Here are the choices:

Voting will close at 10/26 at 11:59 PM.

I don’t like these choices. How did you come up with these?

Honestly, we would have really liked to have involved the community in brainstorming this initial set of names, but we wanted to avoid a goldmine for domain squatters. So we had a long brainstorming sessions among the project team and narrowed the list of choices using the following criteria:

  • Domain name available
  • No other project/product with a name similar to ours in the same field
  • No outstanding trademarks on the name that we could find

Can I write in my own suggestion?

Unfortunately no. Again, we want to make sure we can secure the domains for our new project name, so we needed to start with a list that was actually attainable. If you really can’t bring yourself to pick even one, we won’t be offended if you abstain from voting. And don’t worry, the product will continue to function in the same way despite the name change.

Also, give it some time. It may grow on you.

40 comment(s) so far...


Gravatar

Re: Changing the NuPack Project Name

Shame, I really wanted to have Package-o-tron-3000

Miguel.

By Miguel de Icaza on   10/21/2010 5:27 PM
Gravatar

Re: Changing the NuPack Project Name

How about 'gems'

By Dan Lash on   10/21/2010 5:31 PM
Gravatar

Re: Changing the NuPack Project Name

Don't rename NuPack just because a completely unrelated project with the same name exists. And if you do (you shouldn't!!), available DNS names should not influence the decision. You have so much positive press, web, and social content built around the NuPack brand and it developed organically. Now you're going to rename it and squander all of that? You should really integrate NuPack into Codeplex & not have/care to have a separate domain/website. When it comes to logos, brand names, web sites... less is more.

Check out my suggestion discussion on the Codeplex site:
codeplex.codeplex.com/Thread/View.aspx?ThreadId=230945

By Scott Holodak on   10/21/2010 5:36 PM
Gravatar

Re: Changing the NuPack Project Name

I see that OuterWrap.com is available.

By Joe Troublemaker on   10/21/2010 5:57 PM
Gravatar

Re: Changing the NuPack Project Name

Don't want to be too harsh, but I have to say that 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.

By Michael Stum on   10/21/2010 6:46 PM
Gravatar

Re: Changing the NuPack Project Name

I agree with Scott Holodak. The project may not have been public for very long but I've already seen a ton of blog posts under NuPack, not to mention the huge flood of packages.

This is big a mistake for an otherwise awesome tool.

By Doug Wilson on   10/21/2010 7:17 PM
Gravatar

Re: Changing the NuPack Project Name

How about packoverflow.com

:-)

By Craig on   10/21/2010 8:48 PM
Gravatar

Re: Changing the NuPack Project Name

How about packoverflow.com

:-)

By Craig on   10/21/2010 8:53 PM
Gravatar

Re: Changing the NuPack Project Name

I'd also say try keep it if you can ( bribery? ;) )

But if it has to change I'd vote for nFetch - it's self explanatory, and follows a long held convention of n* for .Net OS projects like nUnit, nHapi & nHibernate.

By Craig D on   10/21/2010 9:23 PM
Gravatar

Re: Changing the NuPack Project Name

What about:

1. LibFlow
2. NLibs
3. Ntegrate
4. LibLocker

?

By Quooston on   10/21/2010 9:38 PM
Gravatar

Re: Changing the NuPack Project Name



What about DotNetGem or NGem?

By Anoop Madhusudanan on   10/21/2010 9:44 PM
Gravatar

Re: Changing the NuPack Project Name

With complete respect Phil, these are terrible names. I mean that in the completely nicest way possible :-)

I agree with Michael. I think it is worth it to take another shot at some other names. I really hope this doesn't come off ofensive, I just have come to love NuPack and would hate to have to call it something I hate.

Ok. I will give them some thought. Hopefully one will grow on me.

By Ryan Farley on   10/21/2010 9:49 PM
Gravatar

Re: Changing the NuPack Project Name

My vote is for : NFetch

By Cameron F on   10/21/2010 9:53 PM
Gravatar

Re: Changing the NuPack Project Name

All of new names are quite bad. That's a pity, because original one was very good.

By Andrey Shchekin on   10/21/2010 10:52 PM
Gravatar

Re: Changing the NuPack Project Name

I totally agree with Scott Holodak and Doug Wilson. Renaming NuPack won't do the project any good. Just stick with it and keep it solely on CodePlex, it doesn't need it's own website.

Have the other party change it's name to NAPACK (Nucleic Acid PACKage), after all they're just as beta! ;-)

Just my two cents.

By Ramses Matabadal on   10/21/2010 10:53 PM
Gravatar

Re: Changing the NuPack Project Name

All of new names are quite bad. That's a pity, because original one was very good.

By Andrey Shchekin on   10/21/2010 10:54 PM
Gravatar

Re: Changing the NuPack Project Name

NGem!!!

Both short and concise, and a nice tribute to Ruby Gems which have solved the same problem in the Ruby world in a great way.

By Geir-Tore Lindsve on   10/21/2010 11:25 PM
Gravatar

Re: Changing the NuPack Project Name

Most people complaining are just used to the NuPack name. NFetch will grow on them just as good, maybe even better. Good job guys!

+1 for NFetch.

By Peter on   10/21/2010 11:38 PM
Gravatar

Re: Changing the NuPack Project Name

NGems or NFetch.

By Richard Kimber on   10/22/2010 12:39 AM
Gravatar

Re: Changing the NuPack Project Name

what's wrong with npack?

By Mark Lennox on   10/22/2010 1:17 AM
Gravatar

Re: Changing the NuPack Project Name

oh right

npack.codeplex.com/

By Mark Lennox on   10/22/2010 1:17 AM
Gravatar

Re: Changing the NuPack Project Name

nGems! Seriously - these names are terrible. Rather ignore the domain issue and go with a a proper name. Even if it's not a .com domain.

By Jaco on   10/22/2010 1:26 AM
Gravatar

Re: Changing the NuPack Project Name

how about Iron* things since the pack's will submit by community's.
IronRuby, IronPython and it could be IronPack

By dede on   10/22/2010 2:31 AM
Gravatar

Re: Changing the NuPack Project Name

NRocks. Work item: nupack.codeplex.com/workitem/276

Reasons in short:
* nrocks.org
* showing appreciation to you favorite project "Autofac Rocks", "NHibernate Rocks" etc
* Rocks are like jems, but less shiny and more rough.
* NRocks means that .NET Framework rocks as well

By Rinat Abdullin on   10/22/2010 2:41 AM
Gravatar

Re: Changing the NuPack Project Name

My vote is to let the community suggest the names instead of be forced to vote in someone else's choices.

By Guilherme Guimarães on   10/22/2010 2:50 AM
Gravatar

Re: Changing the NuPack Project Name

Guilherme , you can suggest your own item, just like I did. People could vote afterwards.

Of course unofficial options will get less visibility, but that's life))

By Rinat Abdullin on   10/22/2010 2:57 AM
Gravatar

Re: Changing the NuPack Project Name

Rinat, did you read the "Can I write in my own suggestion?" section?

That is the point: it should not exist official and unofficial options...

By Guilherme Guimarães on   10/22/2010 3:34 AM
Gravatar

Re: Changing the NuPack Project Name

Guilherme, to my best knowledge, name of NRocks complies with all the conditions.

Probably OuterCurve foundation wanted a wording like "name should comply with all the conditions, but it will be the responsibility of the person suggesting it to ensure this compliance".

By Rinat Abdullin on   10/22/2010 3:41 AM
Gravatar

Re: Changing the NuPack Project Name

Hi

I think NFetch looks a good name both technically and from a project name perspective.

My vote - NFetch

regards
Lohith

By Lohith on   10/22/2010 3:50 AM
Gravatar

Re: Changing the NuPack Project Name

I like 'PackMan'... but I guess that's gotta be taken by somebody else somewhere.
Mike

By Mike Simpson on   10/22/2010 4:14 AM
Gravatar

Re: Changing the NuPack Project Name

I have to agree with a lot of the comments regarding these names. You also have to consider what to use to refer to an individual "pack". Ruby did this well with "Gems", a name that fits the framework and is itself a nice name for an individual entity. Calling something a "pack" is ok but still rather vague and non-descript, NFetch and SnapFetch don't lend themselves to an item name well at all.

I have to say that NRocks so far sounds the best choice, the project name feels good and it fits for individual items "just add the NHibernate.Linq Rock". At least give it a fair chance and add it to the list of 4 at the top.

By Liam Slater on   10/22/2010 5:24 AM
Gravatar

Re: Changing the NuPack Project Name

Vote: NRocks
Idea from: abdullin.com/journal/2010/10/22/suggesting-name-for-nupack-nrocks.html

By mynkow on   10/22/2010 6:15 AM
Gravatar

Re: Changing the NuPack Project Name

Vote for PackMan (PACKage MANager). It's not the same as PacMan, so I think, there shouldn't be any problems. NPack - my second choice.

By Anton on   10/22/2010 6:36 AM
Gravatar

Re: Changing the NuPack Project Name

Sometimes we are victims of our own success, and NuPack has generated so much buzz that it caught CalTech's attention. They have been using NuPack since 2007 and theoretically could assert their common law right of "first use" (and, they recently filed a TM application). Phil and the project team are doing the right thing in making the change now while the project is young. Did they have to? The answer is debatable, but they want to eliminate confusion and show respect to CalTech's project team.

Naming is tough, and you can't please everyone, but a year from now, most won't remember the old name. How many remember Mozilla "Firebird"?

By Paula Hunter on   10/22/2010 7:16 AM
Gravatar

Re: Changing the NuPack Project Name

What about Packraken ?

Then you could have a project mascot called Zak?

Zak Packraken... Come on, this is quality!!

By Nick on   10/22/2010 7:18 AM
Gravatar

Re: Changing the NuPack Project Name

I like SnapFetch, but I'm biased because my OSS project, SNAP, is a NuPack project for download.

By Tyler Brinks on   10/22/2010 7:40 AM
Gravatar

Re: Changing the NuPack Project Name

Hi all, I followed up with a blog post that addresses many of the repeated questions I'm seeing: haacked.com/archive/2010/10/22/naming-is-hard.aspx

By Haacked on   10/22/2010 8:21 AM
Gravatar

Re: Changing the NuPack Project Name

Really, ClrPack.com, .org and .net are all available, and this is about Common Language Runtime sharing, right?

By Marc Brooks on   10/22/2010 11:56 AM
Gravatar

Re: Changing the NuPack Project Name

stay with NuPack

By Eber on   10/22/2010 1:42 PM
Gravatar

Re: Changing the NuPack Project Name

Terrible names...

That said, good domain names are hard to come by.

By Richard Collette on   10/26/2010 3:38 PM

Your name:
Gravatar Preview
Your email:
(Optional) Email used only to show Gravatar.
Your website:
Title:
Comment:
Security Code
CAPTCHA image
Enter the code shown above in the box below
Add Comment   Cancel 

Blog Roll

Indent Example
Sam Ramji
Thoughts from the President of the Board of Directors
Indent Example
Paula Hunter
On the business of OSS and Non Profit Foundations
Indent Example
Stephen Walli
Guest Blogger
Indent Example
Phil Haack
Project leader: NuGet
Indent Example
Bradley Millington
News from the ASP.NET Gallery Manager
Indent Example
Bradley Bartz
WebsitePanel Project Leader
Indent Example
Guest Blogger
Posts from Guest contributors
Indent Example
Spyros
Posts from DLSI Gallery Manager
Indent Example
Rob Mensching
WiX Project Leader
Indent Example
Eric Schultz
Developer Advocate
Indent Example
Bertrand Le Roy
Orchard project updates and news
Indent Example
Staff
Posts from Outercurve Staff