Depending on how hands on you want to be, there are a myriad of managerial/organisational type things that you could do. Having been involved in an (ultimately failed) large mod project before, I know firsthand that these sorts of things live or die based on organisation. Trying to get a group of disparate modders to do anything collectively is like herding cats. It will quickly fall into a heap unless things are very clearly planned out.
As an example, for myself as a potentially interested contributor, what I absolutely need is a clear outline of exactly what the project is doing, what has been done, and what yet remains to be done, and who is doing what. I need a list of tasks that are awaiting assignment that I can peruse, and if one takes my fancy I need very specific guidelines for what is required and by when. To use the Yavin station as an example, I would want specifics of size/dimensions, does it have to be fully constructed or do you only need a camera facing half, is it a high poly CG model or a low poly game model, does it need lightmapping UVs, do I need to create the textures, what's the timeline for completion, etc. Who do I talk to if I have questions/problems, how do I report my progress, what do I do with the final assets? And if I agree to undertake this task, then it needs to be made clear that this task has been assigned, so someone else isn't doubling up the same work. Someone, or possibly several someones, needs to implement and manage such a system.
- Kexikus likes this