On 30-Apr-08, at 1:19 AM, Brett Porter wrote:
Shane,
Just a bit confused about which are the graduation items and which
are the new development ones, in your mind :)
There are elements here that are on the right track - unifying the
users around one codebase is a necessity to growth, for sure. The
questions I'd be asking is:
- how can we support this process?
- for those that are interested in helping to migrate functionality,
where should they start?
We really need to push this along if you're going to be busy with
your day job and Evan with his insane bike ride for the next month :)
Why do we "really need to push this along" ? Graduation happens as a
natural consequence of competent developers with a passion for working
on NMaven getting involved and that just takes time. I think pushing
it along unnaturally is categorically the wrong thing to do.
My thought is that there is no real way "in" for someone just
wanting to contribute
Though that would help that's certainly not true in the case of Evan
and Zak who made their way through the code and started contributing.
Certainly we can work on the roadmap, I agree it should be sorted a
little better.
- navigating briefly from the website I couldn't find the roadmap
for 0.16, pointers to what we need help with, and JIRA is just a
whole bucket of unscheduled, so maybe we could look at that?
Hearing "we will get it all sorted out" is one of those warning
signs that I hear that you may be taking it on yourself too much -
so let's see who else can help out!
Evan did a great job of helping out after demonstrating a real
understanding of the codebase and has done a great deal to help Shane.
As you've referred to, I have some colleagues that have submitted
patches for 0.14 - as I understand it, the plan for this is to apply
them so that there's a unified branch to migrate functionality from
to trunk. Are there any other 0.14 users lurking there that could
confirm the submitted patches?
Do we have other patches, either from 0.14 or trunk that someone can
look at? Again, it's hard to tell without the target versions in
there :)
Graduation is really dependant on being able to gain users, and
having a path to convert them to developers, IMO.
And this just takes time. The CXF project is a great example of
building a project up the right way and it took about two years for it
to get out of the incubator. It doesn't mean that people can't use it.
I know that from Sonatype's perspective we have clients using NMaven
and we're providing support for them with the code in the incubator
and they are fine with that. Obviously they would like it out of the
incubator but the community needs to grow naturally and there needs to
be several people who have intrinsic knowledge about NMaven before it
can leave the incubator.
Cheers,
Brett
On 30/04/2008, at 11:54 AM, Shane Isbell wrote:
It sounds as though we need to start getting people off of 0.14 and
this
means moving the Visual Studio work into trunk. I checked
Sandcastle and it
looks as though Microsoft finally put it under open-source, so
that's one
area we can tackle for API doc generation. Any volunteers for
Sandcastle
plugin?
We also have toolchains as of Maven 2.0.9. I added the NMaven
support for
toolchains into the trunk, but there still is a fair amount we need
to do to
fully leverage it. I've got some Maven related work and then am
scheduled
for the .NET support for Nexus. After that, I'll be jumping into
NMaven a
lot more. I think Evan is doing likewise, after he does his insane
San
Francisco to LA bicycle ride next month (assuming he survives). So
next
month, I expect we will have a lot more activity and start trying
to build
the community and hopefully get in more committers. I know a lot of
people
have submitted patches. Thanks for that. We will get it all sorted
out.
Shane
On Tue, Apr 29, 2008 at 4:04 PM, <[EMAIL PROTECTED]> wrote:
Hi Evan,
We definitely require full IDE integration for Visual Studio, as
well as
solution generation, pom generation from an existing solution
file, and
support for signed assemblies.?Generation of the XML docs is
another feature
we'd love to see.?
The developer community that I'm trying to support doesn't want to
leave
the IDE if at all possible, but we would love to pull them into the
Maven-based environment that we currently use for Java builds.
Shane - thanks for the update.? Keep that whip cracking! ;-)
-- Caulene
-----Original Message-----
From: Shane Isbell <[EMAIL PROTECTED]>
To: [email protected]
Sent: Tue, 29 Apr 2008 2:45 pm
Subject: Re: Graduation?
We are getting there. We have a release under our belt. We just
need to
prove that we have a healthy, sustainable developer community
before we
can
graduate. Cracks whip over Evan's back ;)
Shane
On Tue, Apr 29, 2008 at 2:34 PM, Evan Worley
<[EMAIL PROTECTED]> wrote:
Hi Caulene,
It would be helpful to understand how your company plans to use
NMaven.
E.g. compile, test, package, etc. Is there missing functionality
that
you
would require, such as IDE integration or solution file generation?
(Note: I'm letting Shane handle the graduation question :) )
Thanks for the feedback,
Evan
On Tue, Apr 29, 2008 at 11:28 AM, <[EMAIL PROTECTED]> wrote:
Hi Shane,
I'm trying to implement NMaven within my company, and there are
concerns
that NMaven is still an incubator project.? What are the remaining
barriers
for graduation from the incubator, and is there an estimated
timeline??
How
can we help?
Thanks,
Caulene
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
We all have problems. How we deal with them is a measure of our worth.
-- Unknown
