(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.
  

(01.01.2011, 17:26:26)Nighthawk200 Wrote: I'd be willing to re-apply for project manager again if needed.

Quote:Project manager require that the manager is very active. No offence, and I may very well be wrong, but you are not so active.