I feel overwhelmed with all that needs to get done with the NMaven IDE and
know that I am neglecting a lot of important details, particularly in
regards to code quality and testing; these details are going to keep
mounting up on top of each other. We have Néstor helping out with the Linux
testing, which is a good start. Could I get a list of people who would be
interested in helping out with any of the following?

1) Helping to prepare for a release (starting with getting the license info
into all of the file headers)
2) FxCop pointed out a whole list of suggestions for fixing the .NET code,
so I need someone to look that over
3) The half-completed NCover and Sandcastle plugins need work.
4) The unit test coverage for both NUnit and JUnit is still poor ( doubt
that we have more than 5% code coverage, 0% on the .NET side).
5) Find out how to use log4net (http://logging.apache.org/log4net/) with
NMaven. Log4net is a top level project and we should be using it. This work
would involve: 1) replacing Console statements with log4net statements'2)
importing of log4net libs during build; 3) dumping the existing NMaven
logging component (based on java.util.logging) that handles the logging for
both VS and SD
6) Get NMaven working with log4net and/or Lucene.NET. We can provide the
patches to mavenize those projects and work through any issues that may
have.

Regards,
Shane

Reply via email to