[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-release-team
Subject: Re: [Krusader-devel] Krusader in KDE's SVN
From: "shie erlich" <shie.erlich () gmail ! com>
Date: 2008-11-25 18:36:26
Message-ID: 97dbe3470811251036y58a0f7d0y4f721e766c9c228a () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
hi Sebas,
thanks for the informative mail.
I, for one, feel confident that the time is right for krusader to move
closer together with kde.
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?
what do you think guys?
thanks,
shie
On Tue, Nov 25, 2008 at 6:52 AM, Sebastian Kügler <sebas@kde.org> wrote:
> Hi,
>
> Let me try to shine some light on some of the questions raised in the
> "should
> krusader move into KDE's SVN?" discussion. Please reply to both lists,
> krusader-devel@googlegroups.com and release-team@kde.org
>
> From the thread held on the krusader list, I'm sensing the misconceptions
> that
> being developed in KDE's SVN, it means you have to comply with KDE's
> release
> schedule. Not true, you can in fact decide that yourself. (Trade-off is
> basically between doing release management yourself and being free to
> decide
> when to release vs. having the KDE release team do it for you, but you have
> to
> respect the overall KDE release schedule then). That's your choice,
> however.
>
> * rules
> That depends largely on how you'd like to release. If you want krusader to
> be
> part of KDE releases (be it by means of extragear or some other module),
> you'll have to respect feature and string freezes. This kind of comes with
> the
> release management and translation the KDE team then does for you. I'm not
> aware of any other hard rules, but the policies page on techbase gives more
> info: http://techbase.kde.org/Policies (Note: not all applies to an app
> like
> krusader).
>
> * control
> You remain in control. If you choose to have Krusader released with regular
> KDE releases, rules for that apply. Basically, you can decide how you want
> to
> have your release cycle, commit policies etc. Sometimes, people will commit
> into your code, in almost all cases, those are trivial fixes then. If
> something that might raise objections go in, the committer should (as usual
> in
> KDE) contact the developers before committing. Everybody with a KDE SVN
> account has commit rights though. Basically, you can have Krusader in KDE's
> SVN and be as independent as you want.
>
> * advantages:
> - less infrastructure maintainance
> - more likely participation of developers that have a KDE SVN account
> already
> - code review, a lot of people follow commits and review patches (no
> promise,
> it's just more likely due to increased visibility)
> - can be released alongside KDE (whereever it ends up, even extragear)
> - integration of SVN with bugtracker (Krusader is already using
> bugs.kde.org,
> right?)
> - translation done be KDE translation teams (manpower, consistency across
> desktop)
> - shows stronger KDE ties, taking a bit more advantage of KDE's brand
>
> * disadvantages
> - possibly losing history
> - migration effort
>
> I for one would be happy to welcome the Krusader team in KDE's SVN. If
> there
> are any questions left I would be happy to answer (as I'm sure that applies
> to
> others as well).
>
> Cheers,
> --
> sebas
>
> http://www.kde.org | http://vizZzion.org <http://vizzzion.org/> | GPG
> Key ID: 9119 0EF9
>
>
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.9 (GNU/Linux)
>
> iQEcBAABAgAGBQJJLBFDAAoJEGdNh9WRGQ75JKYH/jKSzcbE62uo9bO1xJlo+DFO
> f3/mw4Jl1EVfdyUd9IkBSHDEmAGDpLZF0kR8B8uFraUN6FC0X8ZPSbjl+h48r3Ye
> xOtWq3NyMGG5K1S8bu3C5Zlgi0P1IkGSdfPbnejmcX/jDoEwfLhP93De+VcJwrgh
> EazG+fdOWwsISPsbd/zG3hYaqSEluIuFtYdOau3FhYLYNxEVzLjraqDV/GLHK+Ey
> 5PsWYshY8iFH1zQVkcw0c1KI1ldPTd8iwxtqT0mEwTGaEPfb95pZUd+CnygbIAMi
> 4Vq++mu/5GCgVFhdCscSVmCjnYoTGAAI+DzdSLEhM39j+OUwOkew59ON6QtzFCQ=
> =SaGl
> -----END PGP SIGNATURE-----
>
>
[Attachment #5 (text/html)]
<div>hi Sebas,</div>
<div>thanks for the informative mail.</div>
<div> </div>
<div>I, for one, feel confident that the time is right for krusader to move closer \
together with kde.</div> <div>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? </div>
<div>what do you think guys?</div>
<div> </div>
<div>thanks,</div>
<div>shie</div>
<div><br> </div>
<div class="gmail_quote">On Tue, Nov 25, 2008 at 6:52 AM, Sebastian Kügler <span \
dir="ltr"><<a href="mailto:sebas@kde.org">sebas@kde.org</a>></span> wrote:<br> \
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; \
PADDING-LEFT: 1ex" class="gmail_quote">Hi,<br><br>Let me try to shine some light on \
some of the questions raised in the "should<br>krusader move into KDE's \
SVN?" discussion. Please reply to both lists,<br> <a \
href="mailto:krusader-devel@googlegroups.com">krusader-devel@googlegroups.com</a> and \
<a href="mailto:release-team@kde.org">release-team@kde.org</a><br><br>From the thread \
held on the krusader list, I'm sensing the misconceptions that<br> being \
developed in KDE's SVN, it means you have to comply with KDE's \
release<br>schedule. Not true, you can in fact decide that yourself. (Trade-off \
is<br>basically between doing release management yourself and being free to \
decide<br> when to release vs. having the KDE release team do it for you, but you \
have to<br>respect the overall KDE release schedule then). That's your choice, \
however.<br><br>* rules<br>That depends largely on how you'd like to release. If \
you want krusader to be<br> part of KDE releases (be it by means of extragear or some \
other module),<br>you'll have to respect feature and string freezes. This kind of \
comes with the<br>release management and translation the KDE team then does for you. \
I'm not<br> aware of any other hard rules, but the policies page on techbase \
gives more<br>info: <a target="_blank" \
href="http://techbase.kde.org/Policies">http://techbase.kde.org/Policies</a> (Note: \
not all applies to an app like<br> krusader).<br><br>* control<br>You remain in \
control. If you choose to have Krusader released with regular<br>KDE releases, rules \
for that apply. Basically, you can decide how you want to<br>have your release cycle, \
commit policies etc. Sometimes, people will commit<br> into your code, in almost all \
cases, those are trivial fixes then. If<br>something that might raise objections go \
in, the committer should (as usual in<br>KDE) contact the developers before \
committing. Everybody with a KDE SVN<br> account has commit rights though. Basically, \
you can have Krusader in KDE's<br>SVN and be as independent as you want.<br><br>* \
advantages:<br>- less infrastructure maintainance<br>- more likely participation of \
developers that have a KDE SVN account already<br>
- code review, a lot of people follow commits and review patches (no \
promise,<br> it's just more likely due to increased visibility)<br>- can be \
released alongside KDE (whereever it ends up, even extragear)<br>- integration of SVN \
with bugtracker (Krusader is already using <a target="_blank" \
href="http://bugs.kde.org/">bugs.kde.org</a>,<br> right?)<br>- translation done \
be KDE translation teams (manpower, consistency across<br> desktop)<br>- shows \
stronger KDE ties, taking a bit more advantage of KDE's brand<br><br>* \
disadvantages<br>- possibly losing history<br>
- migration effort<br><br>I for one would be happy to welcome the Krusader team in \
KDE's SVN. If there<br>are any questions left I would be happy to answer (as \
I'm sure that applies to<br>others as well).<br><br>Cheers,<br> <font \
color="#888888">--<br>sebas<br><br> <a target="_blank" \
href="http://www.kde.org/">http://www.kde.org</a> | <a target="_blank" \
href="http://vizzzion.org/">http://vizZzion.org</a> | GPG Key ID: 9119 \
0EF9<br><br><br><br> </font><br>-----BEGIN PGP SIGNATURE-----<br>Version: GnuPG \
v2.0.9 (GNU/Linux)<br><br>iQEcBAABAgAGBQJJLBFDAAoJEGdNh9WRGQ75JKYH/jKSzcbE62uo9bO1xJlo+DFO<br>f3/mw4Jl1EVfdyUd9IkBSHDEmAGDpLZF0kR8B8uFraUN6FC0X8ZPSbjl+h48r3Ye<br>
xOtWq3NyMGG5K1S8bu3C5Zlgi0P1IkGSdfPbnejmcX/jDoEwfLhP93De+VcJwrgh<br>EazG+fdOWwsISPsbd \
/zG3hYaqSEluIuFtYdOau3FhYLYNxEVzLjraqDV/GLHK+Ey<br>5PsWYshY8iFH1zQVkcw0c1KI1ldPTd8iwxt \
qT0mEwTGaEPfb95pZUd+CnygbIAMi<br>4Vq++mu/5GCgVFhdCscSVmCjnYoTGAAI+DzdSLEhM39j+OUwOkew59ON6QtzFCQ=<br>
=SaGl<br>-----END PGP SIGNATURE-----<br><br></blockquote></div><br>
_______________________________________________
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic