Project ideas - looking for more contributors

[Kai Nacke via digitalmars-d-ldc]

Hi all!

LDC is a community effort. All kinds of contributions are 
welcome!!! This is a great way to speed up development and 
increase quality of LDC!

But how to start? Well, Ian (from GDC project) told everybody 
that compiler construction is no rocket science. Yes, that's 
true! Here are some ideas to start with:

* First, report all bugs you find. Just make sure that it is a 
genuine LDC bug (e.g. not a frontend problem which is solved in 
an upcoming DMD version) and provide a nice test case.

* Build LDC from source. Improve the build instructions if you 
find inaccuracies or tell us about build problems.

* In general improve the wiki pages at http://wiki.dlang.org/LDC

* Maybe you want to get some dirty hands? Just look at the 
reported issues (https://github.com/ldc-developers/ldc/issues/) 
and fire up your debugger. It is quite easy to understand LDC 
source just be single stepping through some functions.

* Implement some missing feature, e.g. support for @ldc.attribute.

If you really dislike C++ then there are still areas which need 
help:

* Implement shared library support on Linux. The basic 
infrastructure is in place but still needs some cleanup.

* Port LDC to a new environment. E.g. LDC itself compiles on 
Solaris 11 but misses some files in druntime and phobos. Or try 
LDC on OpenBSD, NetBSD, Plan 9, ....

* Translate ldmd2 to D. This would be a great start to eat our 
own dog food.

* Provide a D module replacing libconfig. This would help in 
transition of LDC to D.

* The CMake scripts can be improved in various way. Just look up 
the related issues.

If you provide a pull request then you should have a look at the 
CI servers https://travis-ci.org/ldc-developers/ldc/ and 
http://ci.lycus.org/job/LDC/
to identify possible problems.

And don't hesitate to ask your questions here in the newsgroup!

Regards,
Kai