Index: trunk/www/sites/kphotoalbum/documentation/index.php =================================================================== --- trunk/www/sites/kphotoalbum/documentation/index.php (revision 1534947) +++ trunk/www/sites/kphotoalbum/documentation/index.php (revision 1534948) @@ -1,17 +1,17 @@
There are many great features. Many are really straightforward.
The good starting point is to look at this fast overview and to watch these videos. A PDF version of the KDE style documentation is available as well as an on-line version. Once you have KPhotoAlbum running you should be able to access the documentation under the Help menu using KDE Help Center.
-The documentation can always be improved. If you wish to help us don't hesitate to contact us at IRC or at mailing-lists +The documentation can always be improved. If you wish to help us don't hesitate to contact us via IRC or via our mailing list!
\ No newline at end of file Index: trunk/www/sites/kphotoalbum/gettinginvolved/juniorjobs/index.php =================================================================== --- trunk/www/sites/kphotoalbum/gettinginvolved/juniorjobs/index.php (revision 1534947) +++ trunk/www/sites/kphotoalbum/gettinginvolved/juniorjobs/index.php (nonexistent) @@ -1,40 +0,0 @@ - - -A junior job, is a job that can be done without too much knowledge -about the project. Reworking the backend, or the core datastructures of -KPhotoAlbum might not be the best way to start.
- -A junior job is not just a boring job with an outcome that nobody will use! Actually, -some of the junior jobs have been requested by users over and over -again over the years!
-In bugzilla we have marked a number of issues as junior -jobs, along with the entries we have added some text that give some -hints on how to get started.
- -When you have found a job you would like to work on, come to IRC, so we can help you get over -some of the bumbs on your road. Some of your issues may be stuff others -know of the top of their head, so no reason to spent hours on those.
-The First Step as a -KPhotoAlbum Developer page tells you how to get started checking out, -compiling, etc etc.
- -Once you have decided to participate in the development of KPhotoAlbum, you need to get your hands on the sources. See details on how to check out kphotoalbum from GIT
-When you have made a change, please mail a patches to the mailing list (see details below).
++Once you have decided to participate in the development of KPhotoAlbum, you need to get your hands on the sources. See details on how to check out kphotoalbum from git. +
-Please read this page to learn how to compile the sources
++When you have made a change, please mail a patches to the mailing list (see details below). +
+ ++Please read this page and the build instructions to learn how to compile the sources. +
Imagine you have your changes committed in kphotoalbum-my-commit and the -version prior the changes in kphotoalbum-prev-revision, then run this -command to produce a patch:
++Imagine you have your changes committed in kphotoalbum-my-commit and the version prior the changes in kphotoalbum-prev-revision, then run this command to produce a patch: +
-+git format-patch kphotoalbum-prev-revision kphotoalbum-my-commit +
-You can mail the patch that is produced by this command to the -KPhotoAlbum mailing list. +You can mail the patch that is produced by this command to the KPhotoAlbum mailing list.
-Once you have supplied a number of patches, it is time to get your own -git account. While sending patches is a great way for you to align up with -coding standards and ways of doing things in KPhotoAlbum, it is not -effective on a larger scale. +Once you have supplied a number of patches, it is time to get your own git account. While sending patches is a great way for you to align up with coding standards and ways of doing things in KPhotoAlbum, it is not effective on a larger scale.
-See this page for detail on how to get developer acces
- -+Read How to get read-write developer access. +
-Like any piece of software KPhotoAlbum has a learning curve to climb -before you are totally up to speed. A good start is to find a relatively -easy job on the Junior Jobs page, and -looking at the reference -documentation generated from the source code itself.