Please make sure nobody else is working on porting it already. We would like to avoid doing redundant work. We ask that you communicate clearly in that you are going to work on some part of the project. A committer will then either approve or alert you someone else is working on that part already.

Use automated tools to do the basic porting work, and then start a manual clean-up process. For automatic conversion we are using (we have licenses to give to committers) and it proved to work quite nicely, We also good things on Sharpen. Check this version out: Pick the tool you are more comfortable with.

Conventions & standards: not too picky at this point, but we should definitely align with the common conventions in .NET:

For reference have a look at Lucene.Net.Core, while not perfect it is starting to shape up the way we want it.

In general, prefer .NETified code over code resembling Java. Enumerators over Iterators, yields when possible, Linq, BCL data structures and so on. We are targeting .NET 4.5.1, use this fact. Sometimes you will have to resort to Java-like code to ensure compatibility; it's ok. We would rather ship fast and then iterate on improving later. Common Java to .NET type conversion

While porting tests, we don't care about all those conventions and .NETification. Porting tests should be reduced to a copy-paste procedure with minimal cleaning up procedure. We are working on tools and code helpers to help with that, see for examples see: (Java style methods to avoid many search-replace in porting tests), and a R# plugin that will help making some stuff auto-port when pasting 

Code that is currently pending being ported from scratch (+ tests) == up for grabs:

The spatial module (the situation there is a bit subtle, if you are interested let me know)

More analysis modules:


Code that is ported and now pending manual cleanup, and then once its compiling porting of its tests == up for grabs:


The rest is pretty much under control already

If you are more into fixing existing tests: