Official Project Reality Development Team Rules
External
- Although everyone is entitled to their opinion, always remember that with your tag / PR membership you represent not only yourself but the team as a whole. This being said, respect all members of the community, other mods & game developers.
- English is not the first language of everyone, but I expect everyone to use a certain level of professionalism. So write in full sentences, use capitals, no 1337 talk. Also, make correct use of the signature function in the forums. If you will use an image, use the PR template. The only requirement is that you put in an unedited military photo. It's either that or nothing.
- Last but not least, do not remind another team member of the rules or his/her duties in front of anyone else. Deal with this one on one. If this doesn't settle the issue, escalate to the next level (Section Lead or Project Lead).
-Do not openly mock, or speak negatively about DICE or EA with the public. Although EA/Dice don't openly support us, they have in the past labeled us as a "preferred mod team". As the above states by being part of the team, you somewhat lose 'your' public voice, because it affects the whole team if you say something that is negative or when comments are aimed at an entity such as EA/Dice and they'll be less inclined to provide us with favors, not considering how infrequent their favors to mods are to start with.
-Do not pose ideas for the mod to the public in the suggestions section, being a dev, you have the Idea Generator section to do that. Although it gets the public engaged, other mod teams (competition) do browse our boards, as do other professional game companies. We don't want to give them any new ideas, nor give them a hint at something we may or may not be working on. Keep it to the secret Dev section!
Internal
- Includes all external rules.
- Confidentiality. Do not release any information or media relating to the Mod and the team unless approved by the Project Lead. If you are not sure if something is confidential or not, ask. Breaching this rule will result in immediate dismissal without warning.
- You are expected to visit the internal forums on a regular basis in order to keep up-to-date, voice your opinion and generally contribute to the mods future & well-being. Advise the team of any vacation, business trips or other significant offline time.
- Verify the e-mail address in your profile so that the Project Lead can send group e-mails if anything urgent and/or important arises.
- Be conscientious / reasonable, a lot of time is spent creating a mod. If we've come a long way on a certain model, i.e. a vehicle, it is not reasonable to suggest that we should go back to Step 1 to fix a certain minor error. Also included is your position in the organization. If you are a sound artist, it is not your place to comment on a texture artists work flow. Constructive criticism in a field which is not yours yet you have knowledge of is fine, but please do not step on any toes if it's not your field.
Copyright and Your Contributions to Project Reality
Implicitly as part of the Project Reality Dev team in an R-DEV or R-CON role allowing an asset (code, image, model, idea, etc) to be included in a test or public release of Project Reality assigns equal copyrights of that asset to the Project Reality mod team and the asset creator.
The asset creator may continue to own shared copyrights to the asset and continue to use and modify that asset as they see fit. The Project Reality mod also holds shared copyrights to that asset and may continue to use, modify and distribute the asset as the team sees fit.
To put it simply, if it's included in a test or public release of the mod, the mod team has the right to continue to use that asset after the R-DEV or R-CON has left the team.
