From kde-release-team Thu Nov 27 20:18:32 2008 From: "Rafi Yanai" Date: Thu, 27 Nov 2008 20:18:32 +0000 To: kde-release-team Subject: Re: [Krusader-devel] Re: Krusader in KDE's SVN Message-Id: <430196c30811271218y1e033b5p61ef6e2efe932e4c () mail ! gmail ! com> X-MARC-Message: https://marc.info/?l=kde-release-team&m=122829211109355 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--===============1985820998==" --===============1985820998== Content-Type: multipart/alternative; boundary="----=_Part_34154_10453212.1227817112697" ------=_Part_34154_10453212.1227817112697 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline I=B4m following the disscution from afar (Chile right now..), I havn=B4t commited any code for quite sometime and when I=B4ll come back I=B4ll proba= bly concentrate on bug fixes - but I feel that the general mood is to accept th= e offer. I don=B4t feel that I should cast a vote on this matter due to the reasons above - but why don=B4t the krew vote on this issue ? If most people are comfartable with the idea - we can talk about details like saving history and the right point in time to do it later, if the krew rather contiue with the current SVN - than the details are irrelevent :) Keep up the great work (both on KDE and Krusader), Rafi. On Wed, Nov 26, 2008 at 12:40 PM, Sebastian K=FCgler wrote: > On Tuesday 25 November 2008 23:31:23 Jonas B=E4hr wrote: > > Since 2.0.0 would be our first KDE-4 release, it would be an > > acceptable point to beginn with a blank history. Sebastian, you > > mentioned "possibly losing history" as a disadvantage. Does this mean > > there is a chance to keep our history? Under which conditions? My svn > > knowledge regarding such migrations is limited, but I could only think > > of a replay of our repository. This does not really make sense.... > > As David said (and which might not have made it to the krusader list), it > *might* be possible to import history using svk. But you need to talk to > sysadmin@k.o about that. So I cannot be conclusive here. > > > > i think it has other advantages not mentioned here (mostly from PR > > > perspective), but that aside, i would like to know which module > > > krusader would be getting into. ideally, i'd like to see krusader in > > > a package that usually gets installed by default, which (i *think*) > > > is not the situation with extragear? > > > > I think extragear would be perfectly fine, at least for the beginning. > > Some of the most popular KDE apps, like Amarok, live in extragear. > > Plus, there we have the maximum of freedom. We can't claim our > > independence on the one hand and ask for inclusion in a core module on > > the other. > > Well, installed by default is ambiguous. If you're referring to kdebase, = I > think that is not an option for Krusader (at least not in the current > situation). We're already shipping two filemanagers with it (while, with > KDE4, > we've tried really hard to get the number of apps in the standard modules > down > to one per type (i.e. one image viewer, one video player, ...). Extragear= , > to > *me* sounds like a sensible option indeed, but ultimately it's up to modu= le > maintainers where Krusader can find its home. > > > > what do you think guys? > > > > I'm all fo a move as soon as 2.0 is out of the door. What does the > > rest of the Krew think? > > Cheers, > -- > sebas > > http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.9 (GNU/Linux) > > iQEcBAABAgAGBQJJLTW2AAoJEGdNh9WRGQ759JcIAIb77OkZcWQTEE43CPoKh4fC > 9d2s1SsDPik1r6tCdmwbtoKhyKU4JJLuh+4cVWoOyjEBu79+NENAlo3Ysudn56UV > 0BEJBk0+kJauZ0e02ri7nV08+g/EP9cWKVKWMr7KwAP8bW3HRG3CTYSzcybDNUVg > 1KmoDXniF7N4J52cH1T5lgShpSiWiUCnLISiZzO5M4i5z2j2sejO1P/mTUhdMHnu > G8m70kiCtZPVOHkR9eH+zMp3zi+0pNWJDxz5fnff5at+2AJ6GkyjU3JFrXRVXo4G > EwIsWBNiqYJgkU3sied04jCinmMEIyeJ0L9x+dpwNTiutMgsrWYkuASeBeFZEhI=3D > =3Dwvve > -----END PGP SIGNATURE----- > > ------=_Part_34154_10453212.1227817112697 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline I=B4m following the disscution from afar (Chile right now..), I havn=B4t co= mmited any code for quite sometime and when I=B4ll come back I=B4ll probabl= y concentrate on bug fixes - but I feel that the general mood is to accept = the offer.

I don=B4t feel that I should cast a vote on this matter due to the reas= ons above - but why don=B4t the krew vote on this issue ? If most people ar= e comfartable with the idea - we can talk about details like saving history= and the right point in time to do it later, if the krew rather contiue wit= h the current SVN - than the details are irrelevent :)

Keep up the great work (both on KDE and Krusader),
Rafi.

On Wed, Nov 26, 2008 at 12:40 PM, Sebastian K=FCgler= <sebas@kde.org&g= t; wrote:
On Tuesday 25 November 2008 23:31:23 Jonas B=E4hr wrote:
> Since 2.0.0 would be our first KDE-4 release, it would be an
> acceptable point to beginn with a blank history. Sebastian, you
> mentioned "possibly losing history" as a disadvantage. Does = this mean
> there is a chance to keep our history? Under which conditions? My svn<= br> > knowledge regarding such migrations is limited, but I could only think=
> of a replay of our repository. This does not really make sense....

As David said (and which might not have made it to the krusader list)= , it
*might* be possible to import history using svk. But you need to talk to sysadmin@k.o about that. So I cannot be conclusive here.

> > i think it has other advantages not mentioned here (mostly from P= R
> > perspective), but that aside, i would like to know which module > > krusader would be getting into. ideally, i'd like to see krus= ader in
> > a package that usually gets installed by default, which (i *think= *)
> > is not the situation with extragear?
>
> I think extragear would be perfectly fine, at least for the beginning.=
> Some of the most popular KDE apps, like Amarok, live in extragear.
> Plus, there we have the maximum of freedom. We can't claim our
> independence on the one hand and ask for inclusion in a core module on=
> the other.

Well, installed by default is ambiguous. If you're referring to k= debase, I
think that is not an option for Krusader (at least not in the current
situation). We're already shipping two filemanagers with it (while, wit= h KDE4,
we've tried really hard to get the number of apps in the standard modul= es down
to one per type (i.e. one image viewer, one video player, ...). Extragear, = to
*me* sounds like a sensible option indeed, but ultimately it's up to mo= dule
maintainers where Krusader can find its home.

> > what do you think guys?
>
> I'm all fo a move as soon as 2.0 is out of the door. What does the=
> rest of the Krew think?


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iQEcBAABAgAGBQJJLTW2AAoJEGdNh9WRGQ759JcIAIb77OkZcWQTEE43CPoKh4fC
9d2s1SsDPik1r6tCdmwbtoKhyKU4JJLuh+4cVWoOyjEBu79+NENAlo3Ysudn56UV
0BEJBk0+kJauZ0e02ri7nV08+g/EP9cWKVKWMr7KwAP8bW3HRG3CTYSzcybDNUVg
1KmoDXniF7N4J52cH1T5lgShpSiWiUCnLISiZzO5M4i5z2j2sejO1P/mTUhdMHnu
G8m70kiCtZPVOHkR9eH+zMp3zi+0pNWJDxz5fnff5at+2AJ6GkyjU3JFrXRVXo4G
EwIsWBNiqYJgkU3sied04jCinmMEIyeJ0L9x+dpwNTiutMgsrWYkuASeBeFZEhI=3D
=3Dwvve
-----END PGP SIGNATURE-----


------=_Part_34154_10453212.1227817112697-- --===============1985820998== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team --===============1985820998==--