The code has already been moved and restructured, and we have been working hard to iron out any wrinkles that might be left.
From now on you will slowly see the information (links, texts etc.) change to reflect the move.
Why move to GitHub?
PMS has a very active and supporting community. That is one of the reasons why it works so well and why we see lots of active members with their own flavored builds. With the move we unleash the social power of GitHub, making it easy to check out or compare different builds, fork new ones, or to create patches and pull requests. All of a sudden contributing will become a lot easier, as will assessing those contributions become for the devs.
At the same time we want more stability and more comparable builds across platforms, so we can provide higher quality releases. That is where Maven comes in; it has already pointed out some flaws we weren't aware of.
What does the move to GitHub mean to you?
Regular user: nothing changes!
- You will still be able to download PMS from the homepage.
- New versions of PMS will keep appearing as they have before.
- PMS will install just like it did before.
- Issues can be reported on the forums or on the issue list.
Developers: quite a few changes!
- PMS code version control in Git instead of SVN.
- Building is done with Maven instead of Ant, i.e. the introduction of "pom.xml" and "assembly-*.xml"
- The standard Maven directory layout has been adopted, i.e. files have been moved.
- Binaries are separated from the source code and will still be available from Google Code.
- The source code in SVN will no longer be actively maintained, except for the separated binaries. The full history has been transferred to GitHub and maintenance takes place there.
- Forking the code is easy on GitHub, as is branching in git. Feel free to experiment!
Thank you for all your contributions in the past!
We hope this move to GitHub will make you enjoy contributing even more in the future!