Sure! I think at least some form of these core rules should be followed.
Synopsis & Goals
A brief description of the game, and plans for this game's future. This should include game genre and type (ex. "horror survival game", "medieval action-RPG", etc.), target audience (if applicable), introducing the main feature of the game that will set it apart from others, a sentence or so about the plot, and intent of the developer (ex. "make a game in a year", "sell game for profit", "permanent team to make studio after this game's release", etc.). Short and sweet but descriptive.
Plot and Characters
Describe the plot in just a little more detail and introduce the cast. Images of the cast are optional, but appreciated. This does not have to reflect the detail of the actual project thread, but rather provide a quick at-a-glance information dump.
(if the game has a Project Thread, the owner can and should link that thread to the recruitment thread!)
Current Team
What team members are already working on this project? What are their names/usernames and positions within the team? Most importantly: What role does the project leader play on the project? This is often skipped over, and many talented individuals will not join a team in which the team makes the entire game for a single person. We like to know that project leaders are as dedicated to the project as they would like us to be!
Positions Available
Unless restricted for good purpose, this section should identify the positions and number of people per position needed, as well as a very informative chart of what the recruits are expected to do. Include: Main tasks those seeking to fill the part are expected to do, years of experience needed (if applicable), what programs or tools will be used (if applicable), deadline expectations (will the team be lax or rigid?), compensation (if applicable) and terms of use in the works that will be created for the game, and any extra detail the project owner wants to squeeze in.
Concept Art/Screenshots/Demos
!Screenshots should be mandatory! This is just to let those looking for a project know that the lead is serious about creating the game. Projects that are mere ideas should belong in another section OR have a prefix or something saying that the game hasn't passed an idea phase yet.
I'd like to make a suggestion, if I may, regarding this.
I am of a similar opinion to
@MinisterJay, but I do certainly appreciate the thought and effort that has gone into this list
@FANGirl. If something like this were to be enforced as a rule for recruitment, or at least as a guide, I would probably make it something like this:
Synopsis & Goals
Certainly, recruitment would need to have at the very least, a general idea as to what the project will be about. This would likely also include things like the genre and target audience. I wouldn't, however, expect there to be a significant amount of detail here; I'd expect a "hook", or something else to grab potential team members' interest.
Plot and Characters
I would not include plot, at least, not in a public post. If people enquire and wish to assist, and the recruiter has a plot outline, then by all means, send it to those people. As a developer, you don't want to give your ideas away. Character names could be listed, however, even if they are not final.
Current Team
Again, I wouldn't include this as necessary. Optional maybe, but not a requirement. Realistically, if you look up a job advertisement in a newspaper, you won't know who you are working with specifically until you are offered the job. Similarly, a recruiter shouldn't feel the need to divulge this information publicly, unless the recruiter wishes to do so. Information like this can be given out later and/or via PM should you accept someone as a member of the team.
Positions Available
Definitely a must. No point in recruiting for a project if you don't let people know the types of team members you are looking for.
Concept Art/Screenshots/Demos
While these things are useful, they shouldn't be required. Perhaps concept documentation could be added, detailing some aspects of the game. These however can be given in PM if the recruiter so chooses.
I feel that as long as a recruitment post has the core elements such as a summary, positions and what the recruiter is looking for, that should be enough. While PMing people is annoying, its actually not all that uncommon. If PMing lots of people for different projects is annoying or daunting, perhaps shortlist the projects you are most interested in and wait for responses from those people first.
