meineerde

Any .de domain is affected, regardless of the domain's dnssec deployment status, as long as you use a resolver which validates dnssec.

Note that this article is almost half a year old and might not be fully up-to-date...

Although it appears to be forking season at the moment, such a bold move as a fork doesn't happen just out of thin air. Yes, there were disagreements between several Redmine contributors, but I think the time is not ripe yet to spread out every detail of the conflict.

It should be suffice to say that both projects are going to continue to co-exist and probably going to be rather similar for quite some time. We don't want any bad blood between us and we are going to try to work together towards our common goal. We on the ChiliProject side just feel that more open and engaging development process helps the product and is more fun for all participants.

The primary goal of the fork is to open up the project to the community. That means we have a much more open governance and decision process and try to actually talk about what we do and have planned. That way, we want to have a faster and more focused development process. The short story of the fork is on the Why Fork? page: https://www.chiliproject.org/projects/chiliproject/wiki/Why_...

Feature-wise we try to make ChiliProject more modular and extensible by plugins and third-party tools (via the REST API). Also, we plan a deep UI/UX overhaul and having more flexible workflows and permissions. The exact roadmap is still to be defined (in an open community process), but I think you get an idea.

The first release will be compatible to Redmine 1.0.5, and we try to keep the migration path between Redmine and ChiliProject open as long as possible.