Hmm, I hadn't quite anticipated this. Not the umanned landing, that was to be expected, but the idea that it would constitute a separate workgroup. The current workgroup structure was designed to split things up across skill sets/disciplines. But a project like "unmanned lunar lander" cuts across most of them – it will require navigation (Navigation and Guidance Workgroup), communication (Communication Workgroup), etc.
The problem with creating an ad hoc "Unmanned Lander Workgroup" is that then, e.g., our radio wizards would need to pay attention to the Communication Workgroup *and* the Unmanned Lander Workgroup, and so on for all the other groups.
The obvious solution to this would be to redefine the workgroups so they cut across crafts/mission types, but in a sense this reduces their usefulness, in that they don't split the work into independent sub-projects.
We could define our workgroups hierarchically, with the current structure mirrored for manned and unmanned missions, but that feels like it may result in too many groups for us to sensibly keep track of.
Is there a particular part of the unmanned lander project you are interested in? If it is mainly the shape/size/functions of the unmanned lander, you might perhaps be best off working within the Spacecraft Engineering Workgroup?