We’re adding in a lot of features to both the Pligg CMS and Pligg.com this month and we need beta testers to assist in helping us find and fix bugs until the end of the month. The beta testers will need to be familiar with using SVN to checkout the latest version of Pligg and create .patch files for our developers to test out. If you don’t know how to do this we can provide you with some helpful resources, including video tutorials, to get you started. Testers will need to simply run the latest version of Pligg on their own test servers and navigate around looking for bugs. Whenever they discover a bug they will need to report it to us in a private invite-only forum that we will invite beta testers to submit bugs to. We will open up a thread in that same forum with more detailed instructions and testing procedures. We also are in need of fluent linguists who are able to translate Pligg from English to another langauge. We have spent many hours (and will continue to spend more) making Pligg multilingual-friendly for our next release. As a translator you are required to speak both English and the translated language fluently so that the translation will be as accurate as possible. The most basic translation requires that you translate the contents of the /language folder in Pligg using the latest SVN version. For those who want to go the extra mile we could also use some help translating Pligg documentation that will be included in the next release. Translators won’t be needed for another two weeks though as we wrap up our final build for release, until that point our language files will be changing frequently as we add new features and modify existing ones. We will begin translations on September 20, 2008, but translators should sign up before then so that we can notify you when the release is ready for translation. To apply to become a translator use your new Translator Application Page. If you are interested in applying to become a beta tester please private message Yankidank through the Pligg forums or leave a comment to this post. If you leave a message on this blog post I will use the email you provided to contact you, which will be kept confidential.