So far I've received no PM's from anyone claiming to be leadership of this group.

Thus, I'll post a few pointers in general.
SimHQ Mission TitlesOn the SimHQ mission titles, you'll notice a naming system that indicates how many playable slots are available. Some examples:
SHQ MEU Raid 01 (24) -- The schema we used during ArmA2. This is a Marine Expeditionary Unit Raid mission type, for 24 players max.
(ARMY 8-10) Air Clearance -- The schema we use starting with OA. This is an Army mission named "Air Clearance" suitable for 8 to 10 players.
Often, you can make some logical assumptions about mission size for smaller groups. An 8 player mission is likely two 4 man fire teams. This can be staffed with 2 groups of 3 players, so suitable for 6. Similarly, often a 12 man mission is good for 9.
Observe the playable slots for what appears to be mission critical assets. Things like Demolitions (satchel charges) or AT/AA units... Assume the mission maker put these here because they will be needed, and staff them ahead of less critical roles.
Server CommandsOne player needs to be the server admin. Make this decision, then vote him in using the following command typed into the chat window:
#vote admin adlabs6
...replace my example name "adlabs6" with the chosen player name.
The player who is currently admin should keep watch for when players have completed all objectives, but the mission doesn't end with a "MISSION COMPLETE" fade to black. This happens for countless reasons which I will not detail.
Anyway, if you waited 30 secconds after completing all objectives and no ending, just type the following in the chat window:
#missions
Other common issues with some server commands:
#reassign
#restart
These seem like they would make easy the tasks of reassigning mission roles, or simply restarting the current mission. Alas, they are not perfect. More often than not, a handful of players will get stuck at a "Wait for host" screen while others progress perfectly fine.
In this case, everyone who got stuck has to hit ESCAPE and rejoin.
Sure fire work around is to never use those commands. Use #missions instead, and do any slot reassignment or mission restarting from there.