So you are interested in contributing to the Dibbler project?
Great! Here are some tasks you could do. Of course, you can contribute
in other ways if you want to.

1. You could start with something small (like fix one of many bugs). 
There's a link "All current bugs" on the website. Take a look at that 
list.

2. Are you interested in low-level stuff? There's a feature missing: 
client is not able to detect link down event (wifi reattachment or Etherent 
unplug/plug). You may want to take a look at it. Client should send 
CONFIRM after such event. [DONE for Linux, but still requires some testing]
[TODO for Windows, Mac and BSDs]

3. Other idea is to develop server recovery after shutdown. That looks 
fairly simple. Server stores all assigned parameters in 
server-AddrMgr.xml. When you shutdown server and restart it, it forgets 
all assigned addresses. So it should read this file and load it into 
database + some extra time checking (remove expired leases). [DONE]

4. Do you have access to Apple hardware? It would be great if someone 
could port Dibbler to Mac OS X. Or maybe to Solaris? Do you have 
experience with FreeBSD? That port would be welcome, too. [DONE]

5. There are some new drafts that Dibbler does not support yet. You may 
take a look at them and see if you find that interesting.
http://www.ietf.org/html.charters/dhc-charter.html

6. Client should start only if M bit in the Router Advertisement is set. 
You may want to develop support for this. Also O bit is supposed to 
instruct client to ask for other (non-address related) options.

7. If you are more of a sysadmin rather than code developer, there are two 
things that you could do: try to limit the size of the client code. It's 
way too big for some deployment areas like booting from floppy or some 
embedded devices. This would require some Makefile tuning and code 
cleanup.

8. There are no RPM packages for Fedora. That one is really important as 
Fedora and derived distros have huge user base.

9. Windows. Windows XP client discards most options as I don't know how to 
set them in the system. I'm really a Linux guy.

10. Vista/Win7. Vista port is experimental and requires some testing and 
most probably fixing.

11. Reconfigure support. This may be a tough one. Server must be able to 
reread updated configuration and notify clients about new configuration.
Clients must be able to react appropriately.

12. DNS Update stability. In some cases DNS update may crash client and/or
server. That should be fixed.

13. FreeBSD port. [DONE]

14. Solaris port.

15. Bulk LEASEQUERY implementation. There's RFC5460 for that.

16. Create new Debian package dibbler-utils with extra tools, like 
dibbler-requestor used for leasequeries.

17. Implement routing configuration [DONE]
  http://datatracker.ietf.org/doc/draft-ietf-mif-dhcpv6-route-option/