If it's part of VS, I don't see how healthy it will be. If it's not supporting the push behind things like TFS, it's not going to go far. If it is, then it will be a crappy deal.
The reason that MS went to this is due to the amount of exposure users of nu would have to Ruby.
I don’t understand the statement that NuPack is read-only?
Ahh, right. No, there isn’t a public repository like RubyGems right now. The current repository is hosted and there’s no mechanism to push new packages up to that repository (yet). There are plans for a gallery (much like the VS gallery today) that is currently being worked on. When that’s delivered, you’ll have the push capability (just upload your .nupkg file).
In the interim, just setup a file share on your corporation to use it internally or create a simple web site that provides an ATOM feed (see NuPack.Server for an example) and setup your own public repository.
First of all, congratulations. I think this is an exciting project.
Unfortunately, I take a bit of exception to this statement...
> Basically both Nu and NuPack will co-exist for awhile until as a community,
> everyone is ready to make the jump.
There is no reason to believe that "everyone" will eventually make the jump,
except for some limited subset of "everyone" who use Visual Studio. My
understanding of the nu project was that it was thinking more broadly.
That said, it's open source, so if nu dies, something nu-er may emerge. :-)
Charlie
--
Adam
http://adventuresinagile.blogspot.com/
http://twitter.com/adymitruk/
http://www.agilevancouver.net/
http://grou.ps/altnetvan/
-----Original Message-----
From: nu-...@googlegroups.com [mailto:nu-...@googlegroups.com] On Behalf Of Adam Dymitruk
Sent: Wednesday, October 06, 2010 12:30 PM
To: nu-...@googlegroups.com
Subject: Re: Nu v2 == NuPack
What are you not hoping will go forward? That a hosted repository will be setup (in progress, just don’t know when it goes live) or that individuals can setup their own servers (already possible).
Agreed. Phil has updated the NuPack FAQ pointing out that the current repository is only a temporary one, but the intent is to have a gallery (much like the VS one) where anyone can add a package (just like RubyGems today).
As many of you have probably seen this morning, NuPack was announced. I have a blog post coming, but Bil already has one up: http://weblogs.asp.net/bsimser/archive/2010/10/06/unicorns-triple-rainbows-package-management-and-lasers.aspx
Basically both Nu and NuPack will co-exist for awhile until as a community, everyone is ready to make the jump.
I'm blessed to be part of both and glad that Microsoft came to us asking for feedback instead of just crushing us like they have been known to do in the past. It's definitely a different Microsoft these days. Especially considering that NuPack is the first true OSS project by Microsoft and can have non-MS core contributors.
____
Rob
"Be passionate in all you do"
http://devlicio.us/blogs/rob_reynolds
http://ferventcoder.com
http://twitter.com/ferventcoder
Absence of Ruby. Major MS win.
--
--
Glad you like it. :-)
I agree with everything you say, to the extent that "benefit to us" refers to
the Microsoft .NET developer community. This is a major opening up of
Microsoft - or a part of it anyway - to Open Source. I would be very
happy about it even if this were not a project I was interested in.
But I was defining "us" differently.
I was hoping to see something equally useful to the greater .NET
community, which counts those developing under Linux, Mac and
other platforms. You'll recall that one of the first questions I asked you
about the nu project was whether it would work on those other platforms.
With the ruby base, it did and that was a Good Thing.
Microsoft, OTOH, is focusing on users of Microsoft Windows and
primarily Visual Studio. That's as we would expect from a commercial
entity with it's own platforms to protect. I don't think they're evil or
anything like that, just that their interests do not 100% coincide with
mine and with those of other developers like me.
So while I see what _they_ are doing as a really big plus for both
Open Source at large and for the more purely MS-oriented developers,
I see a down-side as well.
What was once a project open to multiple communities is now limited
to just one. It will probably do more for that one community than would
have otherwise been possible but I don't imagine it will focus very much
on those other communities it is leaving behind.
That's OK if it's a considered decision on your part and on the part of
others who made the call. But you were writing about it as if it were
all up-side, with no tradeoffs involved. There are definitely tradeoffs.
I will say that I'm happy to see Microsoft apparently getting smart
about open source at long last. But because they are smart about
it we who are independent need to be smart about where we
work with them and where we work separately - just as folks do
now with Novell, IBM, Sun, etc.
Charlie
My impression is that the MS focus is on the VS extension. But
maybe community members can push for a free-standing gui or
even develop separate extensions for other IDEs.
Charlie
OTOH, a ruby gui would work on all environments.
Nevertheless, I agree that it will be built if it's needed.
Charlie