• Ares has been modified to show a very clear disclaimer in unstable builds, making additional marking of unstable builds as unstable unnecessary.
  
• We accept the publication and usage of unstable builds by the general community.
  

• Any version that is not one of the publicly released stable versions is a testing version and only meant for testers.
  
• Anyone who is using a testing version despite not being a tester is not entitled to any support from us. If you're not a tester, you weren't supposed to use the testing version in the first place.
  
• Testing versions are not released or marked as stable versions because they're not fucking stable. Any particular testing version could unexpectedly and randomly be utterly broken and unplayable. They can be unstable, subtly flawed, features can randomly be broken, they can be slow due to excessive debugging code, or can be built for a very specific purpose only the testers know about. Using testing versions without being a tester is an invitation of trouble and frustration and nothing else.
  
• Testing versions can be outdated rapidly. In a development cycle, it's entirely possible there are multiple new versions per hour, each one fixing issues that existed in the one before, or introducing new issues. Picking one at random is akin to Russian roulette. Just because a build is the latest version released doesn't mean it's the most stable build of the past 24 hours. Educate yourself before picking an unstable version.
  

• In any situation, adhere to the license. To put this simply, your right to redistribute Ares is founded on your acceptance and adherence to the license it is under - if you violate the license, you don't have the right to distribute Ares, legal or otherwise. Before you redistribute Ares with anything, read the goddamn license and act accordingly. It's right there in every release, so don't pretend you didn't know.
  
• If you're distributing a stable version:
  • Always make sure your Ares is up to date. We only support the latest public release, and if anyone with an outdated version asks for support, our first and only suggestion will be to update to the latest stable release. Patches exist for a reason, we don't release them for fun. If you're distributing your mod with an outdated version and/or your mod is incompatible with the latest version, you're risking support troubles and you're risking broken games.
    
  • If you or your users uncover Ares issues, report them to the bugtracker.
    
  • Make sure you deliver Ares cleanly. Do not distribute a virus-infected Ares.
    (Sidenote: Since a virus modifies the Ares binary, and you would not mark Ares as modified in accordance to the license, you would technically commit software piracy by distributing a virus-infected version of Ares. Just sayin'.)
    
• If you're distributing an unstable version:
  • First of all, you're stupid. Plain and simple. Releasing your mod based on and with software that has officially not been deemed stable is in no way smart.
    
  • If you're doing it anyway, we expect the following disclaimer in very clear view in an unmissable place:
    

    Ares Testing Version Disclaimer Wrote:The version of Ares distributed with this mod is an unstable testing version not meant for public consumption. The Ares developers do not support the usage or distribution of testing versions with public mods. This version of Ares has a certain likelihood of being broken in various ways, including, but not limited to:
    * frequent Internal Errors
    * broken features
    * incomplete features
    * frequent Reconnection Errors in multiplayer
    * broken stock functionality
    * degraded performance due to debugging code
    
    We, the authors of this mod, consider this version of Ares stable enough for general distribution, but we are required to stress that the Ares developers disagree and do not support this move.

  • Do not dare blaming us for your mistakes. Should it turn out that you distributed the wrong version and your mod's players are angry, don't you fucking dare blaming Ares - it was your stupid decision to include a broken testing version with your mod. We told you it was a stupid decision in the first place. It's your stupid mistake, and it's on you to take the blame.
    
  • Do not advertise the inclusion of Ares any more than required by the license. Do not go forward and boast about all the awesome additions made possible by new and not-yet-publicly-released Ares features. If you want to include a testing build, do it quietly. (Except for the loud disclaimer, obviously.)
    
  • Choose. fucking. wisely. As said above: Just because something is the latest build available doesn't mean it's the most stable build available. The latest version could introduce horrible bugs or even intentionally be only half-finished. If you must include a testing version, make an educated choice which build to include, and make note of known issues with that version.
    

1. Scrap the feature. Disable it, and, should 0.3 happen, fix it up for that. That would hurt since it's a community submission and mostly done, but would require little further work before 0.2's release.
   
2. Leave it as-is. We could just drop the feature on the community as it is, with a list of unsupported cases and known issues in the documentation. That would be the easiest and quickest solution, but also the sloppiest.
   
3. Invest the time to fix it. Which means delaying Ares 0.2's release.
   

• We have one working feature in the pipeline whose implementation is a seed for bugs and issues in the future.
  
• We have one almost-working feature which seems to cause bugs and issues right now.
  
• We have a number of fresh bug reports to sort through and vet for fixing in 0.2.
  

• Since the Mystery Patch seems to work, as much as I think it'll complicate things in the long run, I'll merge it into trunk as soon as I have the time for it.
  
• Prism Forwarding is a great feature, and I'm sure it'll be awesome one day - but to be perfectly honest, it has delayed 0.2 for months now, and enough is enough. Prism Forwarding has come a long way in its almost year-long history, but it's simply not done yet. It's almost there, it's definitely in very late beta stages, but it's not mature enough for release yet.
  And since no coder is around to fix it right now, we have opted to put it back into its own branch for now and release 0.2 without it.
  If Marshall or another coder has the time to fix it, it'll probably be in 0.3.
  

• Basically, you'll have to update, append to and correct the manual.
  
• You should be able to write in clear and readable English, as the manual will be read by any user of Ares, and it needs to be understandable.
  
• You should have an idea of what HTML is, since the manual is an HTML document. Help on this can be given, however.
  
• You should also be active both on the forums and on the IRC channel, as the manual will need updated quite often.

• Basically, you're the people who make screenshots, videos, creative crop circles, anything needed to spread the existence of Ares to the masses.
  
• Knowledge of image editing would be an obvious necessity, and preferably you'd know how to create and edit videos.
  
• Constant activity is not as pertinent a requirement here as it is for documentation maintenance. However, when it comes close to a release time, we will expect you to be able to turn out material quickly and on time.
  
• Expect to be issued with deadlines, and we will in turn expect you to meet them. However, you can take pride in having your work on show around the community to advertise Ares.

• Public Relations. PR. Whatever you want to call it. You'll be the people who drum up support for Ares among the general proletariat.
  
• This will involve posting news on community sites, creating the odd teaser topic for a modding forum, and generally spreading information and answering inquiries on Ares on sites around the community.
  
• You should ideally be friendly people who can communicate well with random members of the community. To this end, a good command of English is preferred, as almost all major community sites operate in English.
  
• You will work with the Promo Material Creators to help devise interesting news posts for display around the community.
  
• Basically, Ares needs support and attention. You will be the people who will go forth and bring it.

• Not everyone is a brilliant modder. Some need a little bit of help to get going. That's where you come in.
  
• User Support Agents should have a good working knowledge of the latest stuff in Ares - after all, how can you give advice on a product without knowing how to use it yourself?
  
• Basically answer any member queries about how to accomplish something in Ares, how to get it installed, how to make mods compatible with it, etcetera.
  
• Again, a friendly and approachable persona is preferred. Being able to communicate well is also recommended.

• We've had an endemic problem with testers throughout Ares' lifetime - they simply can't be bothered.
  
• Out of the many testers currently on the roster, only a minutely small fraction of those do any regular testing. This will change - inactive testers will be culled, and we will be looking for replacements.
  
• Do not think of this as easy access to Ares. You will be working with potentially unstable beta versions - not the best thing to base a mod on.
  
• Your holding of the "tester" title is entirely dependent on your activity. If you behave like our many previous testers, i.e. appear for a week, test some issues you have interest in, then bugger off and don't show up again, we will fire you. Simple as.
  
• As an active tester, you will be expected to be active. Additionally, you will be required to test all and any issues to their fullest and to the best of your ability. Don't just stick a couple of values in rulesmd and observe the result - push those values to their limits, observe the effects, make sure we've got our theories correct.
  
• Modding experience is a necessity, and preferably you've used Ares before.
  
• Keeping a frequent presence on our IRC channel is recommended.
  
• Ares development will halt if we do not have a quorum of active testers.
  
• Do not apply to be an Active Tester if you will not be able to live up to the title. We will not look back if we have to cut you loose.

(06.11.2010, 17:54:37)Modder666 Wrote: I'd point out the fact most of those "probably switching" modders lol at Ares due to the way it's developed, the feature list, and how instable it can be at times. While you may think they're switching, rewiring an entire game from one patch system to another is NOT the easiest thing in the world to do, and would set them back so much time it's not even worth doing for current mods. [...]

• 5 Active Testers
  This is the most obvious one. Our issues with testers are known, and we're sick of it. In the future, unless we have at least 5 active testers, we'll cease development.
  In case you're interested in helping out, being a testers includes, but is not limited to, checking and trying to confirm as many issues as possible, whether they affect you or not, whether they interest you or not.
  We need feedback on issues all the time, no matter if you can confirm the issue or not.
  If you can confirm an issue, that's important to us.
  If you cannot confirm an issue, that's important to us, too!
  
  We are not interested in people who'll only try out new features and post "me too" every once in a while.
  We need detailed examination of all reported issues and the effects of all code changes.
  We especially need regular tests of existing features, to make sure new developments didn't break old ones.
  If you can't or won't do that, don't volunteer.
  
  We need testers, not players.
  
• 1 Documentation Maintainer
  This guy's job is simple: Keep the user manual and the readme up to date.
  That's it.
  If a new feature appears, add it to the manual. If there are notes to be made about it, add them. If it's unclear how it's used, ask the developers and update the manual. If somebody reports an issue with the manual, check it and fix, if necessary. If Launch Base or Ares usage changes, update the readme, etc., etc.
  
  It's really as simple as that: Look at the manual and readme from an Ares user's perspective, see if they're complete and clear, and if they're not, make it so they are.
  You won't have to guess how stuff works, and you won't have to read C++ or Assembler code, we'll happily answer all the questions you might have.
  We just want someone to have a dedicated eye on the state and the style of the manual.
  
  One tiny requirement would be that you are capable of following simple markup conventions in so far as that you should be able to replicate existing manual entries.
  You don't even have to understand how the manual "gets pretty", you just have to understand what to copy-paste to make it look right.
  
• 1 User Support Agent
  Again, a simple job: Check the forums frequently, and if people have trouble with Ares, try to help them.
  That's all there is to it.
  If there's no one with a problem, you don't even have to work.
  We just want to be sure that, if somebody has a problem, there someone's there to help, or at least to guide the user somewhere he can get help.
  
  Basically, your job is to make sure people who come here for help don't feel abandoned.
  
  Requirements: Being able to post on the forums, being able to read the user manual and readme, being able to try out stuff in Ares.
  
• 1 Project Ambassador/PR Guy/Ares Evangelist
  Once more, a simple job: Just hover other forums and sites and represent Ares where necessary.
  If there's a question about Ares on PPM, be there.
  If there's a discussion about YR extensions on Revora, make sure we're described accurately.
  
  You don't have to lie, you don't have to badmouth other patches, you're not supposed to be aggressive, you're just supposed to be there and represent us.
  
  Requirements: Being active on the majority of currently open and active community forums, being enthusiastic about Ares, not being a goddamn moron, troll, asshole or otherwise unfit for being a representative.
  Also, the ability to talk to the User Documentation Maintainer in case you're unsure about the feature set helps.
  
• 1 Promo Material Creator
  Job difficulty? You guessed it: Simple.
  All you have to do is work with Ares, make your work shiny, and then make screenshots and videos of it.
  That's all there is to it.
  
  We need a continuous stream of pretty screenshots of all the features in Ares so people can see how Ares can look and extend their mods.
  In addition, we need one "exemplary" screenshot of each feature, for the documentation.
  
  Requirements: Being able to mod YR, being able to mod YR with Ares, being able to hit the screenshot key, being able to properly convert screenshots to PNG.
  
• 1 Project Manager
  This job is about the only one on this list that's a little bit harder: Keeping it all together.
  The Project Manager's job is basically one of control, coordination and oversight.
  • In terms of the Community Support Crew's work, he's the main administrator. When positions are vacant or volunteers need to be replaced, he's the one assigned to do it. He coordinates the different people (e.g. making sure the Promo guy gets the PR guy a few nice shots if he needs them somewhere), he expands the team when necessary, etc., etc.
    
  • In terms of development issues (bugs and features), he helps decide which issues to focus on for the next release, by contributing the perspective of a non-coder and having information from the User Support Agent and the Project Ambassador about the wants and needs of the general community. He also helps decide when to target releases for, and what to do when release dates need to be re-evaluated.
    
  • In terms of overall coordination, he's the one making sure that everyone is on the same page and working towards the same goal at the same time - e.g. if there's a release scheduled, he's the one making sure that the coders code enough, that the Documentation Maintainer updates the docs, that the Promo guy produces enough material, that the PR guy spreads the word, and that a few news posts detailing features of the new release are made.
    The Project Manager makes sure all parts of the project are in sync.
    
  The Project Manager is not the leader of the project. He's more of the administrator of all things not code. Essentially, us coders provide Ares, and the Project Manager makes sure everything else is ready for it. In return, in order to make sure he can do his job right, the Project Manager is directly involved in the decision making process and an important voice in the direction of the project.
  
  Requirements: Being trustworthy, being capable of organizing half a dozen people, being enthusiastic about Ares, being interested in Ares's success, being calm and reasonable, being communicative and willing to (learn to) use Internet Relay Chat, not being easily frustrated and wanting this particular position for its duties. Let me make that last part very clear: Don't take this job if you really just want advanced access to Ares, and don't take it for its title. Only volunteer if you want this position because you are passionate about coordinating projects like this, or because you want Ares to succeed.
  There is no point in applying for this position if you don't want the full scope of what it entails.
  
  Also, since this is a pretty important position, we'll be very careful who we select for it. Knowing us is a definite advantage.
  

• [525] Allow different types of stealth
  
• [1121] Parachuted=yes
  
• [957] custom storms
  
• [556] Drain weapon with ranged weapon dont work
  
• [715] Extending Upgrades to include documented limits
  
• [612] AI Enhancements
  
• [349] Add a "Guard area" or "Combat Air Patrol" feature
  
• [510] Multiple Voxel-Turrets (Battleships like in RA2)
  
• [609] Researches
  
• [322] Restore NonVehicle= function
  
• [504] Make the units fire two weapons at same time
  
• [316] Ammo= on weapons
  
• [603] Turrets and IFV logic on buildings
  
• [991] New tiberium/ore tree types
  
• [518] Waypoint Mode Aircrafts