Re: [Kde-pim] PIM Sprint: Porting PIM to Frameworks

2013-11-25 Thread Kevin Ottens
On Sunday 24 November 2013 21:36:02 Stephen Kelly wrote: > Kevin Ottens wrote: > >> Tiers above 1 are not especially relevant. A tier is a fluid label. It > >> doesn't matter when we are using split repos. > > > > If you could stop spreading that it'd be nice. It's not because you see no > > value

Re: [Kde-pim] PIM Sprint: Porting PIM to Frameworks

2013-11-24 Thread Stephen Kelly
Kevin Ottens wrote: >> Tiers above 1 are not especially relevant. A tier is a fluid label. It >> doesn't matter when we are using split repos. > > If you could stop spreading that it'd be nice. It's not because you see no > value in tier 2 and 3 distinction that this value doesn't exist. I think

Re: [Kde-pim] PIM Sprint: Porting PIM to Frameworks

2013-11-24 Thread Kevin Ottens
Hello, On Tuesday 19 November 2013 22:59:15 Stephen Kelly wrote: > John Layt wrote: > > It was agreed that the ideal plan for kdepimlibs was to split all the > > libraries up and make them all stand-alone Frameworks, aiming for Tier > > 2 or even Tier 1 where possible. > > Tiers above 1 are not es

Re: [Kde-pim] PIM Sprint: Porting PIM to Frameworks

2013-11-20 Thread John Layt
On 19 November 2013 22:59, Stephen Kelly wrote: > John Layt wrote: > Those TODO tasks are very 'vertical'. Many tasks, and most useful tasks in > frameworks porting, are horizontal. The horizontal tasks should largely be > done before the vertical ones. Horizontal tasks are things like: > > * Po

Re: [Kde-pim] PIM Sprint: Porting PIM to Frameworks

2013-11-20 Thread John Layt
On 19 November 2013 22:59, Stephen Kelly wrote: > John Layt wrote: > Those TODO tasks are very 'vertical'. Many tasks, and most useful tasks in > frameworks porting, are horizontal. The horizontal tasks should largely be > done before the vertical ones. Horizontal tasks are things like: > > * Po