Development of LuaMetaTeX (the engine) is mostly finished. We now entered the stage where we conduct experiment with the more difficult aspects (often unsolvable due to constraints). For that one needs to be quite a bit experienced in tex and the way context approaches things.
As an example, project like updating math took many man-years and intense testing, discussion and experimenting (so also quite some long term commitment). In a similar fashion (and related) we now are playing with the par and pagebuilder where user input and testing is required. Things like that get discussed at meetings and personal cummunication.
The source code is under rather stict dev regime. We don't want to break compatibility, all has to fit into the user interface, performance might not be impacted significantly. We don't have an official dev team but everone knows what the de-facto team is (last week those that had time and were within reasonable traveling distance met at the context meeting) and it's also a kind of friends and fun thing where everyone brings in competence and inspiration. At such meetings we also set the objectives for the next year.
That said, the usual way to come up with something that a user needs is to use a mix of lua, tex and metapost and wrap that in a module. That way the core is not crippled. Also, no all has to go into the engine but is done in Lua.
Hans
So I guess I need to learn TeX, Metapost and Lua. I know a bit of these but will go a bit deeper. Once I have learned these I will try to help by updating the Wiki documentation. -- Respect, Shiv Shankar Dayal