paradigm/community-oriented-programming
DokMelody should reduce to a minimum the effort for pubblishing private improvements to the code and documentation to the upstream repository. The community can receive these pull requests, improve them, vote them. Every user of Dok should be a boyscout and he must be able to leave the environment as a better place respect how he found it. It must be very easy to apply small incremental improvements.
This can reduce also the proliferation of macro and DSL, because the community can create something of good.
The problem of Lisp is that there are too much half-backed DSL and libraries, because it is more easy start from scratch than extending the work of others. DokMelody should avoid this problem.