Sorry everyone - but the hack happened overnight our time - all should be restored now.
We've just found that someone has hacked into the dotproject.net site, forums.dotproject.net, and docs.dotproject.net. We will be working to resolve this issue as quickly as we can.
We will post more details here as we have them.
Update: From what we can tell it's a basic "script kiddy" sort of hacking (read, mostly just annoying). We are working to remove the problem and get things back to normal.
Update: We're back!
Please Note: This version has a requirement of PHP 5.2 or greater as it utilizes multi-byte character functionality to help our large amount of international users. We are looking into a more backward compatible solution for earlier versions of PHP. Stay tuned!
To all of you who have patiently waited on us, Thank you! To those who have contributed to this releases success through bug reports, forum posts, and code contributions, a very special thank you!!
We, the dotProject team, are happy to announce the immediate availability of dotProject 2.1.3. This release is primarily a security and bug fix release, but it also marks the first successful release since we've switched to Git.
If you are currently running dotProject, we highly recommend that you upgrade to this release. Please report any issues that you find at our bug tracking site.
A complete list of changes is available in the Changelog file (which is also in the downloads).
Happy Thanksgiving and enjoy this new release!
One of the largest changes we've made as a team so far is to move dotProject 2.x development from Subversion on SourceForge.net (where dotProject 2.x development continues) to Git on GitHub.com. More detailed information on the new setup is available on the dotProject Code Repository page on the docs site.
In the survey results we've found that over 40% of you have customized dotProject in some way. Many of the comments we've seen have also stated interesting customizations and improvements.
Historically, those have been tricky to get back into the core of dotProject. Now, with the move to Git, the process is much simpler.
GitHub provides an easy system for "forking" a project. In Git terminology a "fork" is merely a clone of an existing Git repository. This means that you can create your own fork of dotProject within Git, add your code to the Git repository, pull in changes we make via Git, and request to push your changes to us--which would get them added to a feature branch and eventually the core of dotProject after they're approved.
The particulars of doing this sort of thing is more the realm of the forums.
We hope that this move will allow you the opportunity to contribute your customizations and improvements back to the community in a way that will benefit the entire dotProject community.
for The dotProject Team
dotProject 2.x has been moving very slowly for the past couple years. This is in part to our announcement in December 2007 that dotProject 3.0 would be a complete rewrite. The rewrite continues and you can checkout the progress at the dotProject SVN repo.
However, we realize that 3.0 is still very much "in progress" and that most of you are using some version of dotProject 2.x (or even 1.x). As such, we have begun giving dotProject 2.x renewed focus and energy with the hopes of providing an actively improving project management system for you while you wait on dotProject 3.0.
To that end, we'd like to get some feedback from you on what you're currently using to host dotProject (what version of PHP, MySQL, Apache, etc). We want to consider the typical hosting environment, as we consider implementing the "latest and greatest" technology into dotProject 2.x.
Please take a moment to fill out this brief survey. As always, we welcome any and all feedback at the dotProject support forums.
for The dotProject Team