Reminder for this week: calligracommon online coding sprint

2012-04-28 Thread C. Boemann
Hi Just On Sunday 15 April 2012 07:34:48 C. Boemann wrote: > On Friday 13 April 2012 07:08:03 C. Boemann wrote: > > Hi > > > > I was thinking that since calligracommon bugs normally fall outside the > > itches each of us like to scratch the number of bugs in that component > > will just continue t

Re: calligracommon online coding sprint

2012-04-14 Thread Boudewijn Rempt
On Sunday 15 April 2012 Apr, C. Boemann wrote: > I hereby declare week 18 our Calligra common online coding sprint. Just for extra clarity, that's 30 April to 6 May. > It is your duty as a Calligra developer (and that includes krita) to > contribute. It's not enforced in any way, but please try

Re: calligracommon online coding sprint

2012-04-14 Thread C. Boemann
On Friday 13 April 2012 07:08:03 C. Boemann wrote: > Hi > > I was thinking that since calligracommon bugs normally fall outside the > itches each of us like to scratch the number of bugs in that component > will just continue to grow > > I suggest we organize an online coding sprint where each of

Re: calligracommon online coding sprint

2012-04-14 Thread Boudewijn Rempt
On Friday 13 April 2012 Apr, C. Boemann wrote: > Hi > > I was thinking that since calligracommon bugs normally fall outside the > itches > each of us like to scratch the number of bugs in that component will just > continue to grow > > I suggest we organize an online coding sprint where each o

Re: calligracommon online coding sprint

2012-04-13 Thread Inge Wallin
On Friday, April 13, 2012 07:08:03 C. Boemann wrote: > Hi > > I was thinking that since calligracommon bugs normally fall outside the > itches each of us like to scratch the number of bugs in that component > will just continue to grow > > I suggest we organize an online coding sprint where each

calligracommon online coding sprint

2012-04-12 Thread C. Boemann
Hi I was thinking that since calligracommon bugs normally fall outside the itches each of us like to scratch the number of bugs in that component will just continue to grow I suggest we organize an online coding sprint where each of us fixes two bugs from that component. If we are 20 hackers