Hi Adam,
from my point of view it'd be great to have more people involved. I've been doing some development, but more or less out of necessity (I enjoy working on the project when I can, but don't really have the time to commit to it much more than I have been unfortunately).
To give you some background around why there's the renshawbay repo as well as the main repo; Initially I created the renshawbay repo as there were various changes I needed to make to the project while it was hosted in sourceforge, and for me it was easier to manage that in github. I added Python 3 support, and later some stuff around subclassing .net classes in Python. It was then decided to move the project to github, so we created the pythonnet repo directly from the sourceforge repo rather than fork the renshawbay repo. The thinking back then was that we should do a 2.0 release based off that fork, and then once that was stable look at merging in the Python 3 work from the renshawbay fork.
So, to answer your first question - pythonnet/pythonnet is the official repo, but most new development (new features etc) has taken place on the renshawbay/pythonnet fork in the python3 branch (which maintains support for Python 2).
There's no official roadmap that I'm aware of. There are some issues and milestones in the github repo, but AFAIK no one is actively working on those right now. There are only a couple of issues remaining for the 2.0 release however.
Pull requests to the official repo are reviewed and merged by the project owners (of which I'm one). So far those have been bug fixes or changes necessary for the 2.0 release. I keep the renshawbay fork up to date with any commits to the main repo.
For what it's worth, here's what I'm aware of that needs attention:
- Finalizing and releasing to PyPI the 2.0 release for Python 2.x only
- Testing and getting the renshawbay python3 branch working on non-windows platforms (the linux build currently has problems, and I've not tested any mac builds)
- Merging the renshawbay python3 branch into the main pythonnet fork
- Updating the docs
If you're able to help at all that would be much appreciated.
Best regards,
Tony