[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-imaging
Subject:    Re: [Kde-imaging] Creating a KIPI SourceForge project?
From:       Gilles Caulier <caulier.gilles () free ! fr>
Date:       2005-09-29 6:08:44
Message-ID: 200509290808.44693.caulier.gilles () free ! fr
[Download RAW message or body]

Le Mercredi 28 Septembre 2005 11:57 PM, Aurelien Gateau a écrit :
> Le Mercredi 28 Septembre 2005 22:46, Caulier Gilles a écrit :
> > Le Mercredi 28 Septembre 2005 22:38, Aurelien Gateau a écrit :
> > > Le Mercredi 28 Septembre 2005 21:49, Caulier Gilles a écrit :
> > > > Nota : kipi source code tarballs are already hosted by SF digikam
> > > > project. Why duplicate this job ?
> > >
> > > This is what I would like to change: I would like to create an SF
> > > project for KIPI, which would host all kipi tarballs as well as binary
> > > packages.
> > >
> > > Aurélien
> >
> > And _who_ manage this repository ? You ?
>
> No: all the registered developers of the KIPI SF project. Once the project
> has been created, everyone involved in KIPI would create an SF account (if
> he/she doesn't have one) and then be added to the KIPI SF project. This way
> he/she will be able to release source tarballs or binaries.
>
> Aurélien
>

This is my viewpoints :

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.
 
Gilles
_______________________________________________
Kde-imaging mailing list
Kde-imaging@kde.org
https://mail.kde.org/mailman/listinfo/kde-imaging

[prev in list] [next in list] [prev in thread] [next in thread]