On 1 September 2015 at 02:14, Yue Liu wrote:
>
> On Aug 31, 2015 2:50 AM, "Dmitry Kazakov" wrote:
> >
> >
> >>> 1) I'm ok with forking Krita repository. We already depend from quite
> few libraries from calligra libs. That is mostly, KoCanvasBase,
> KoDocumentBase, flake and pigment.From all fou
On Aug 31, 2015 2:50 AM, "Dmitry Kazakov" wrote:
>
>
>>> 1) I'm ok with forking Krita repository. We already depend from quite
few libraries from calligra libs. That is mostly, KoCanvasBase,
KoDocumentBase, flake and pigment.From all four only pigment looks
>>> reusable enough for me to have a sep
On Monday 31 August 2015 03:46:23 Friedrich W. H. Kossebau wrote:
> Am Sonntag, 30. August 2015, 20:36:06 schrieb Boudewijn Rempt:
> > Long mail :-) Sven already said a lot of what I wanted to say. The thing
> > is, with KOffice 2.0, we actually got further along the road to making
> > fine-grained
Am Montag, 31. August 2015, 12:19:32 schrieb Cyrille Berger:
> On Sunday 30 August 2015 17:30:22 Sven Langkamp wrote:
> > We started out offering endless choise for the users and gave them
> > everything. But at some point it became clear that in many cases it was
> > just overkill. We spend a huge
On Sunday 30 August 2015 17:30:22 Sven Langkamp wrote:
> We started out offering endless choise for the users and gave them
> everything. But at some point it became clear that in many cases it was
> just overkill. We spend a huge amout of time to fix things like bugs that
> showed up in Krita when
On Monday 31 August 2015 12:50:12 Dmitry Kazakov wrote:
> > The repo size is one reason I'm actually considering to drop all
> > history. Create a fresh new repo with cleaned-up code only and start
> > again from commit 0. I know we check history a lot, but that history is
> > the history of Krita
On Mon, 31 Aug 2015, Dmitry Kazakov wrote:
1) I'm ok with forking Krita repository. We already depend from
quite few libraries from calligra libs. That is mostly, KoCanvasBase,
KoDocumentBase, flake and pigment.From all four
only pigment looks
reusable enou
On Mon, 31 Aug 2015, Dmitry Kazakov wrote:
Hi, all!
Just my two cents:
1) I'm ok with forking Krita repository. We already depend from quite few
libraries from calligra libs. That is mostly, KoCanvasBase, KoDocumentBase,
flake and pigment.From all four only pigment looks
reusable enough for
Am Sonntag, 30. August 2015, 20:36:06 schrieb Boudewijn Rempt:
> Long mail :-) Sven already said a lot of what I wanted to say. The thing
> is, with KOffice 2.0, we actually got further along the road to making
> fine-grained composite document possible. We got further than Apple,
> IBM or Microsof
Long mail :-) Sven already said a lot of what I wanted to say. The thing
is, with KOffice 2.0, we actually got further along the road to making
fine-grained composite document possible. We got further than Apple,
IBM or Microsoft with projects like Taligent, Opendocs or OLE. Sure, we
made architec
On Sat, Aug 29, 2015 at 10:41 PM, Friedrich W. H. Kossebau wrote:
> Am Donnerstag, 27. August 2015, 09:57:32 schrieb Boudewijn Rempt:
> > For Krita, and I hate to say this, it probably makes sense to fork our
> > shared libraries. The office-apps maintainers can then strip out all the
> > krita-s
On 27 August 2015 at 16:27, Friedrich W. H. Kossebau wrote:
> Am Donnerstag, 27. August 2015, 09:57:32 schrieb Boudewijn Rempt:
>> I'm not really happy writing this mail... But anyway, back to practical
>> issues. I'd like to start taking steps next week already.
>>
>> * split up our git repo whic
eleases etc then it still might be better to do the spltting ( but is that
>> a guarantee things will be released or will krita/kexi eventually split up
>> or do their own releases anyway. In which case Calligra will be split and no
>> one to do the even larger release process.
>
On Thursday 27 August 2015 16:27:21 Friedrich W. H. Kossebau wrote:
> I fear splitting git repos, unless done brutally, will take some time to be
> well prepared (and also needs an agreement who to do it of all involved).
> So hoping to do that already next week might be ambitious
Also, lets not f
Am Donnerstag, 27. August 2015, 09:57:32 schrieb Boudewijn Rempt:
> For Krita, and I hate to say this, it probably makes sense to fork our
> shared libraries. The office-apps maintainers can then strip out all the
> krita-specific stuff, and for Krita, we can strip out the stuff that only
> makes s
amilla Boemann
>
> -Original Message-
> From: calligra-devel [mailto:calligra-devel-boun...@kde.org] On Behalf Of
> Boudewijn Rempt
> Sent: 29. august 2015 09:38
> To: Calligra Suite developers and users mailing list <
> calligra-devel@kde.org>
> Subject: Re: Af
can only
hope splitting libs will not produce the same fate
Best regards
Camilla Boemann
-Original Message-
From: calligra-devel [mailto:calligra-devel-boun...@kde.org] On Behalf Of
Boudewijn Rempt
Sent: 29. august 2015 09:38
To: Calligra Suite developers and users mailing list
Subject
On Sat, 29 Aug 2015, Cyrille Berger wrote:
On Friday 28 August 2015 15:43:12 Boudewijn Rempt wrote:
Well, we started the discussion with the idea that making separate repos
for the libraries and applications was going to be useful. That rather
soon turned into a discussion of the problems we ha
On Friday 28 August 2015 15:43:12 Boudewijn Rempt wrote:
> Well, we started the discussion with the idea that making separate repos
> for the libraries and applications was going to be useful. That rather
> soon turned into a discussion of the problems we have making our libraries
> fit for purpose
Am Freitag, 28. August 2015, 15:48:39 schrieb Boudewijn Rempt:
> On Thu, 27 Aug 2015, Friedrich W. H. Kossebau wrote:
> > In the meantime for everyone I would propose to turn Boud's other proposal
> > about turning frameworks into master and open it back for development in
> > this schedule:
> >
>
On Thu, 27 Aug 2015, Friedrich W. H. Kossebau wrote:
I fear splitting git repos, unless done brutally, will take some time to be
well prepared (and also needs an agreement who to do it of all involved). So
hoping to do that already next week might be ambitious :)
Well, sure. But postponing it
On Fri, 28 Aug 2015, Cyrille Berger wrote:
On 2015-08-27 09:57, Boudewijn Rempt wrote:
For Krita, and I hate to say this, it probably makes sense to fork our
shared libraries. The office-apps maintainers can then strip out all
the
krita-specific stuff, and for Krita, we can strip out the stuff
On 2015-08-27 09:57, Boudewijn Rempt wrote:
For Krita, and I hate to say this, it probably makes sense to fork our
shared libraries. The office-apps maintainers can then strip out all
the
krita-specific stuff, and for Krita, we can strip out the stuff that
only
makes sense for office applicati
+ 1
On Thursday 27 August 2015 14:22:19 Friedrich W. H. Kossebau wrote:
> Hi,
>
> Am Donnerstag, 27. August 2015, 09:57:32 schrieb Boudewijn Rempt:
> > I think that the frameworks branch is now ready to be called 3.0. It's
> > obviously not ready to release to end users, but we should make it the
Am Donnerstag, 27. August 2015, 09:57:32 schrieb Boudewijn Rempt:
> I'm not really happy writing this mail... But anyway, back to practical
> issues. I'd like to start taking steps next week already.
>
> * split up our git repo whichever we we like
> * ask sysadmin to put our repos up
> * update a
Am Donnerstag, 27. August 2015, 14:27:17 schrieb Boudewijn Rempt:
> On Thu, 27 Aug 2015, Friedrich W. H. Kossebau wrote:
> > Hi,
> >
> > Am Donnerstag, 27. August 2015, 09:57:32 schrieb Boudewijn Rempt:
> >> I think that the frameworks branch is now ready to be called 3.0. It's
> >> obviously not
On Thu, 27 Aug 2015, Friedrich W. H. Kossebau wrote:
Hi,
Am Donnerstag, 27. August 2015, 09:57:32 schrieb Boudewijn Rempt:
I think that the frameworks branch is now ready to be called 3.0. It's
obviously not ready to release to end users, but we should make it the
new master. But let's call it
Hi,
Am Donnerstag, 27. August 2015, 09:57:32 schrieb Boudewijn Rempt:
> I think that the frameworks branch is now ready to be called 3.0. It's
> obviously not ready to release to end users, but we should make it the
> new master. But let's call it the frameworks branch for now.
+1 for making fram
Hi,
We had a long discussion on #calligra yesterday, but I don't know whether
we came to any conclusion... There are a bunch of things we have to
consider before moving on after 2.9.7.
I think that the frameworks branch is now ready to be called 3.0. It's
obviously not ready to rele
29 matches
Mail list logo
