targets

Trying to define the different ddclient targets

Milestone 3.8: current release

• working version with dual WAN.
• should work with multiple services. Should work with only one fit.
• merging with released versions, at least ubuntu and debian.

Milestone 3.9: Fixing stuff

• fixing documentation - bugfixes. Maybe implementing a new help feature which allows documentation about one provider or use case. Synchronising ddclient and website.
• will be the release while working on 4.0
• no extra services will be add

Milestone 4.0: Provider cleaning

• cleaned providers: only with api, good documentation and free service by default. Would be nice if we have a test-case per provider, someone who uses the provider and knows how the configuration works.
• split configuration, making ddclient pluggable
• split documentation on website
• changing default provider since dyndns doesn't support any free service.

Other stuff to do, other comments

• backup trac and import somewhere else to prevent issues when sf.net stops supporting trac
• when moving to another service, it would be nice if we could take the bugs and stuff with us.
• cleaning up mailing lists. I would suggest just using the support list, it can be used for discussions about ddclient.
• should we move to a git based ddclient?
• I'm still wondering if it is a good idea to keep the documentation into ddclient. It is nice to have the docs when configuring but it's a pain in the ass to keep all of them up to date. Could we provide a way to generate the documentation with ddclient?