That's fantastic Daniel, it's great to see the whole summary in one place.
One thought is that it might be helpful to split the items under 'API and architecture' and 'Template language' into those intended for a first release and those that are 'nice to haves' that may come later. My impression is that there are a lot of great ideas in there but the first pass on FM3 could be much easier by limiting the scope. What should be in the first release versus later is a matter of opinion, and I have my own biases based on how I typically use FreeMarker. From a read through it looks like a few things in the 'Template language' section could wait until after the first release, and a couple in the 'API and architecture' section (like Android compatibility, but I don't know much about what would be involved there aside from supporting at least back to Java 7). The most important ones to get before the first in are probably the breaking changes and clean ups (including removal of deprecated features). Other things like named bodies or fragments in macros would be nice, but seem like they could be added later while remaining backward compatible with FM3 release 1 (v3.0.0 or whatever). As a first pass these changes (breaking changes and cleanups) would also push toward the goal of making it easier for others to get involved and contribute more. It might even be a good idea to mention that in this wiki document, basically plant a seed that might result in more contributors. -David  On Jun 12 2017, at 4:34 am, Daniel Dekany <[email protected]> wrote: > I have made a page about what FreeMarker 3 is about and how it should look, because all this was only extractable from mailing list discussions so far. > > https://cwiki.apache.org/confluence/display/FREEMARKER/FreeMarker+3 > > Something you are missing from it, or disagree with it? Eventually we should tweet this, but first of course I need some feedback. > > \-- Thanks, Daniel Dekany
