I'm redoing some of the evas module stuff to have somewhat better option naming as well as matching the existing default enable states.

Sure! Just push before Friday, I will rebase there again :)

There's a number of places where .so is hardcoded as a shared library/module extension. Is that accurate for all platforms?

Thats what i am fixing right now

And what is partly fixed in the feature branch

A #Goal ticket should not be set to a milestone.

I propose the following:

• squash devs/bu5hm4n/meson into a single "implement meson" patch on top of any non-meson patches (e.g., D6795)
• maintain that branch in a single commit + dependencies
• other branches are merged into it and squashed, with author attribution added into the commit log as needed

This should provide a more workable system for managing individual patches and determining what is going on in each branch/commit.

We can do that.
Any commit, not related to meson, should land in master before that anyways. Which is the case for D6795.

I would prefer to get the meson work into master as soon as its running on linux, across distributions.

I agree, though I think it should only be merged once it is complete (i.e., all parts of tree are building and running).