On Friday 28 March 2014 20:17:40 Markus Slopianka wrote:
> On Friday 28 March 2014 15:42:16 David Faure wrote:
> > Well we can't deprecate both khtml and kdewebkit. What do we use then,
> > right now, to browse the web in a KDE application?
>
> Deprecate does not mean that both are not available a
On Friday 28 March 2014 15:42:16 David Faure wrote:
> Well we can't deprecate both khtml and kdewebkit. What do we use then, right
> now, to browse the web in a KDE application?
Deprecate does not mean that both are not available any longer, just that 3rd
party developers don't get a wrong impre
On Tuesday 18 March 2014 17:32:58 Markus Slopianka wrote:
> On Tuesday 18 March 2014 13:37:01 Aleix Pol wrote:
> > Can we maybe agree that we want an extra value in the .yaml
> > file
> > indicating the maturity of the project?
>
> It's not about maturity, it's about security. QtWebKit is no longe
On Wednesday 26 March 2014 20:47:23 John Layt wrote:
> On 26 March 2014 20:08, Kevin Ottens wrote:
> > Hello,
> >
> > On Tuesday 25 March 2014 16:41:12 Jos Poortvliet wrote:
> >> Just imagine what header would you like to see on an
> >> announcement/article:
> >> * Frameworks 5 To Not Include Dep
On 26 March 2014 20:08, Kevin Ottens wrote:
> Hello,
>
> On Tuesday 25 March 2014 16:41:12 Jos Poortvliet wrote:
>> Just imagine what header would you like to see on an announcement/article:
>> * Frameworks 5 To Not Include Deprecated Technologies
>> * KDE Porting Aids To Have Three Releases
>> *
Hello,
On Tuesday 25 March 2014 16:41:12 Jos Poortvliet wrote:
> On Monday 17 March 2014 18:15:09 Kevin Ottens wrote:
> > Adding kde-promo in CC since it might have implications on future
> > communication.
>
> Ok, reading the whole thing - it seems a simple dot story would be useful to
> explain
Hi!
El 26/03/2014 13:04, "Jos Poortvliet" escribió:
>
> On Monday 17 March 2014 18:15:09 Kevin Ottens wrote:
> > Hello,
> >
> > Thanks for the feedback!
> >
> > Adding kde-promo in CC since it might have implications on future
> > communication.
>
> Ok, reading the whole thing - it seems a simple
On Monday 17 March 2014 18:15:09 Kevin Ottens wrote:
> Hello,
>
> Thanks for the feedback!
>
> Adding kde-promo in CC since it might have implications on future
> communication.
Ok, reading the whole thing - it seems a simple dot story would be useful to
explain that we've made some decisions t
On Tuesday 18 March 2014 13:37:01 Aleix Pol wrote:
> Can we maybe agree that we want an extra value in the .yaml file
> indicating the maturity of the project?
It's not about maturity, it's about security. QtWebKit is no longer maintained
by Digia and I am not aware that anybody stepped up to ma
On Monday 17 March 2014 18:15:09 Kevin Ottens wrote:
> Now, the last point... What else do we want to move from KDE Frameworks to
> KDE Porting Aids? Aleix and Aaron proposed the following content for KDE
> Porting Aids:
> * kde4support (obvious);
> * khtml (planned for a long time);
> * kjs (b
Hello,
On Tuesday 18 March 2014 13:37:01 Aleix Pol wrote:
> On Tue, Mar 18, 2014 at 4:36 AM, Markus Slopianka wrote:
> > On Monday 17 March 2014 18:15:09 Kevin Ottens wrote:
> > > Now, the last point... What else do we want to move from KDE Frameworks
> >
> > to
> >
> > > KDE Porting Aids? Alei
On Monday 17 March 2014 20:14:24 John Layt wrote:
> On 17 March 2014 18:15, Kevin Ottens wrote:
> > I think that list makes sense. Is there anyone who couldn't sleep at night
> > if those were in KDE Porting Aids?
>
> +1 to this strategy, although some bikeshedding on the "portingaids"
> name mig
On Tue, Mar 18, 2014, at 5:37, Aleix Pol wrote:
Maybe coming up with the list of modules now is not the most useful
thing now.
Can we maybe agree that we want an extra value in the .yaml
file indicating the maturity of the project?
+1
Aurélien
___
Kde
On Tue, Mar 18, 2014 at 4:36 AM, Markus Slopianka wrote:
> On Monday 17 March 2014 18:15:09 Kevin Ottens wrote:
>
> > Now, the last point... What else do we want to move from KDE Frameworks
> to
> > KDE Porting Aids? Aleix and Aaron proposed the following content for KDE
> > Porting Aids:
> > *
On 17 March 2014 20:14, John Layt wrote:
> I like the limit on kde4support, we only have to look to Qt3Support to
> know that if the aids are left in place people will avoid porting away
> from them until they absolutely have to. I'm not sure we need to call
> it a "product" though, perhaps just
On 17 March 2014 18:15, Kevin Ottens wrote:
> So let's pick the following cocktail: 1, 2 and 4.
>
> That means we immediately move khtml and kde4support out of KDE Frameworks (to
> be widely advertised) and into a KDE Porting Aids product (to be advertised
> only to existing KDE developers).
>
> B
16 matches
Mail list logo
