[Kde-imaging] Creating a KIPI SourceForge project?

[Angelo Naselli]

Aurelien Gateau wrote:
> Gilles Caulier wrote:
>  
> 
>>1/ Multiply repository increase project entropy !
>>2/ kipi project isn't a packaging team. it's developpement team.
>>3/ Binaries packaging is dedicaced to packagers.
>>4/ There is a large tasks list to finalize kipi: see in B.K.O. We have no
>>time to lost with packaging.
>>5/ kipi is maintened by digiKam team. This is very fragile because
>>developper ressources are limited. I don't want another one repository to
>>manage. 6/ We develop and provide source tarballs. It's enough.
> 
> 
> I  agree 100% with Angelo. Creating this repository would not change a lot
> for you: instead of uploading to the Digikam SF project, you would upload
> to KIPI SF project. On the other hand it would make life easier for people
> who create binary packages (like Angelo) or who get sent binary packages
> (like me), since they will be able to upload their packages.
And it would be more reliable since the one who uploads the packages is
also the one who is grant to. No more free ftp and md5sums (ok md5sum
could be good anyway :) or...
One thing more though e.g. while i can (well not now :( ) update
gwenview home page after an upload, to help Aurelien, I can't do
that for kipi since i should need svn access... But the
packages would be downloadable from sf site.

Anyway OTH we can use digikam sf site, but I'm not digikam mandriva
maintainer, and i'd prefer to have different places since they are
(as you all said) different projects.

Angelo