I believe that the paper does provide several points which the GDT needs to be aware of, especially within the Design and Architecture of these tools.
Since the beginning of my involvement within this group, I have tried to steer us into a model of development which closely reflects what we as a movement are trying to achieve.
Taking it from this perspective, as an example, and looking at section 2. Crises of an old form, in the paper, we can see that the GDT (I am talking about the Phoenix part) decided to follow an old form for it's basis, i.e. the LAMP stack.
"When the old forms and principles no longer work efficiently, the old system runs into a crisis."
In addition to the GDT's Mission Statement:
"The Developers Team's primary short and medium range goals focus on facilitating and innovating a broad scope of intelligent applications and automation tools to further enhance the functionality of the Movement's websites and related communication technologies and projects. "
Anyhow the point I am trying to make is that we should be aiming towards building a 'doubly free' applications to use within the community.
This is a direction we should explore and use, rather then build systems that from the outset have restrictions imposed onto us.