|
Hi,
what is planned for the GSoC students: Will they work in trunk after the 1.3.0 release, or in a dedicated branch? If it's done in a branch, please not three different branches, one at most, it's a lot of unproductive work to merge branches and compile different versions. Marcel _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
|
Hi Marcel,
Gabriel and I are working on the already branched GPSSync2 and WorldMapWidget2, both are trivial to re-merge into kipi-plugins. Once we are ready to integrate them with digikam, we will contact you to discuss things further. We also set up a wiki page where you can find the URLs: http://community.kde.org/Digikam/GSoC2010/ReverseGeocoding Not sure whether it is on the right wiki, but the Nondestructive editing page was also there ;-) Michael _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
|
> Hi Marcel, > > Gabriel and I are working on the already branched GPSSync2 and > WorldMapWidget2, both are trivial to re-merge into kipi-plugins. Once we > are ready to integrate them with digikam, we will contact you to discuss > things further. That's fine for me. I mainly care about digikam, at least my student will mainly work on digikam proper. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
|
I agree with Marcel. Only one digiKam branch must be done for GOsC if
student work in a separated implement it will limit concurrent changes and merging operation to trunk will be more easy... Gilles Caulier 2010/5/10 Marcel Wiesweg <[hidden email]>: > >> Hi Marcel, >> >> Gabriel and I are working on the already branched GPSSync2 and >> WorldMapWidget2, both are trivial to re-merge into kipi-plugins. Once we >> are ready to integrate them with digikam, we will contact you to discuss >> things further. > > That's fine for me. I mainly care about digikam, at least my student will > mainly work on digikam proper. > _______________________________________________ > Digikam-devel mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-devel > Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
|
MArcel,
I propose to create a new entry at this place : http://websvn.kde.org/branches/extragear/graphics/digikam/ A folder named "digikam-gosc2010" can be fine. Note : I think that "0.10-trunk" and "1.0-databaseext" can be removed now. Gilles Caulier 2010/5/11 Gilles Caulier <[hidden email]>: > I agree with Marcel. Only one digiKam branch must be done for GOsC if > student work in a separated implement it will limit concurrent changes > and merging operation to trunk will be more easy... > > Gilles Caulier > > 2010/5/10 Marcel Wiesweg <[hidden email]>: >> >>> Hi Marcel, >>> >>> Gabriel and I are working on the already branched GPSSync2 and >>> WorldMapWidget2, both are trivial to re-merge into kipi-plugins. Once we >>> are ready to integrate them with digikam, we will contact you to discuss >>> things further. >> >> That's fine for me. I mainly care about digikam, at least my student will >> mainly work on digikam proper. >> _______________________________________________ >> Digikam-devel mailing list >> [hidden email] >> https://mail.kde.org/mailman/listinfo/digikam-devel >> > Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
| Free forum by Nabble | Edit this page |
