|Gilles Caulier||<caulier dot gilles at gmail dot com>||Aix en provence, France|
|Marcel Wiesweg||<marcel dot wiesweg at gmx dot de>||Essen, Germany|
|Abhinav Badola||<mail dot abu dot to at gmail dot com>||Chandigarh, India|
|Smit Mehta||<smit dot meh at gmail dot com>||Chennai, India|
|Islam Wazery||<wazery at ubuntu dot com>||Cairo, Egypt|
|Benjamin Girault||<benjamin dot girault at gmail dot com>||Lyon, France|
|Robin Mills||<robin at clanmills dot com>||San Jose, USA|
|Pankaj Kumar||<me at panks dot me>||Hyderabad, India|
Students and mentors will use digikam-soc-devel at kde dot org mailing-list to coordinate projects.
To be able to code and work on digiKam project, each student must ask for a developer account to KDE Git repository administrator. See this page for details about KDE developers rules.
For Exiv2 project, please contact your mentor to get write access on Subversion repository.
digiKam and Exiv2 have registred in Coverty Scan Program to report all source code dysfunctions. Code is parsed automatically through a cronned script each week end. Reports are forwarded to digikam-soc-devel_at_kde_dot_org mailing-list.
To be able to review and fix errors reported by Scan analyzer, all students must be registered in the relevant Coverity project :
All students working on digiKam will play with KDE Git repository from Git master branch.
We have a digiKam Software Compilation Repository where you will be able to checkout all sub-repositories including all shared libraries managed by team. This not included Exiv2 which is hosted outside KDE.
Students must have configured KDE developer account and checkout all code from KDE repository using SSH method.
Instructions to checkout and compile code is given in this README file.
During GSoC 2013 coding time, git/master will still the stable implementation receiving important fixes. Each students must create a dedicated development branch for each project (your branch name is defined in project list by "Working on" property). In charge for each students to sync it with git/master periodically. To do it, see below as example how to sync digiKam "MY_DEVEL_BRANCH" branch tracking "remotes/origin/development/MY_DEVEL_BRANCH" from KDE git repository:
$>git checkout master $>git pull --rebase $>git checkout -b MY_DEVEL_BRANCH remotes/origin/development/MY_DEVEL_BRANCH Branch MY_DEVEL_BRANCH set up to track remote branch development/MY_DEVEL_BRANCH from origin. Switched to a new branch 'MY_DEVEL_BRANCH' $>git merge master Merge made by the 'recursive' strategy. ... $>git push
The 2 first lines take a sure that your local master repository is up to date. The 3rd line create in local the "MY_DEVEL_BRANCH" development branch. Merge between master and MY_DEVEL_BRANCH branch is done with 4th line. Git can ask you to resolve conflicts here. When it's done, it will ask you a commit comment. Finally push your merge into remote KDE repository.
Note: If you have already created MY_DEVEL_BRANCH branch, just run "git checkout MY_DEVEL_BRANCH" as well instead git checkout -b MY_DEVEL_BRANCH remotes/origin/development/MY_DEVEL_BRANCH. This give this concatenated command line:
$>git checkout master; git pull --rebase; git checkout MY_DEVEL_BRANCH; git pull; git merge master ... $>git push
For advanced rules, especially to create remote working branches in KDE git repository, please look on this tutorial from KDE TechBase.
|02 Jun 2013||digiKam Software Collection 3.3.0-beta1 released||-|
|09 Jun 2013||digiKam GSoC-2013 branches created in KDE git repository||see branches listed in projects list|
|09 Jun 2013||Kipi-plugins GSoC-2013 branches created in KDE git repository||see branches listed in projects list|
|09 Jun 2013||Exiv2 GSoC-2013 branches created in SVN repository||see branches listed in projects list|
|21 Jul 2013||digiKam Software Collection 3.3.0 released||sync with KDE SC 4.10.5|
|01 Sep 2013||digiKam Software Collection 3.4.0 released||sync with KDE SC 4.11.1|
|29 Sep 2013||digiKam Software Collection 3.5.0 released||sync with KDE SC 4.11.2|
|02 Oct 2013||digiKam GSoC-2013 development branches are merged back to git/master||Note : only Tags Manager and Image Quality Sort projects|
|03 Nov 2013||Kipi-plugins GSoC-2013 development branches are merged back to git/master||Note : only Cloud Integration Export project|
|01 Dec 2013||digiKam Software Collection 4.0.0 beta1||Note : new implementation of libkdcraw using an external shared libraw|
|15 Dec 2013||digiKam GSoC-2013 development branches are merged back to git/master||Note : only Showfoto Qt4 model/view port project|
|12 Jan 2014||digiKam Software Collection 4.0.0 beta2||Note : huge fixes from Import tool included|
|02 Feb 2014||digiKam GSoC-2013 development branches are merged back to git/master||Note : only Image Editor Qt4 model/view port project|
|23 Feb 2014||digiKam Software Collection 4.0.0 beta3||Note : Qt3Support classes dependency removed|
|30 mar 2014||digiKam Software Collection 4.0.0 beta4|
|13 apr 2014||digiKam Software Collection 4.0.0 RC|
|11 may 2014||digiKam Software Collection 4.0.0||sync with KDE SC 4.12.3|
As lots of students come from India this year, it will be nice to plan a reunion between developers in this country to reduce travel and hotel costs.