[prev in list] [next in list] [prev in thread] [next in thread] 

List:       koffice-devel
Subject:    We need a decision now (Was: Re: Koffice sprint -- call for decision)
From:       Cyrille Berger <cberger () cberger ! net>
Date:       2009-09-18 8:38:35
Message-ID: 200909181038.35857.cberger () cberger ! net
[Download RAW message or body]

Hello,

We need to take a decision now and start buying tickets.

The choice is between 14-15th and 28-29th November. Sounds like the difference 
is that on 14-15th we have Capser, and on 28-29th we have Inge and Jan (we 
also have me, but since I wasn't able to give my availability before, it 
wouldn't be faire to take me into account).

Since there are many people who are not interested in doing API review, and 
it's probably true that it's not usefull to have all KOfficers doing API review, 
and that we have identify "bugs" as the main user experience problem. But my 
self, I think debugging is something that I do best alone, and some have raise 
concerns that 12h isn't enough (which I also agree), maybe what can be done 
instead is unit test writting.

If you agree with my suggestion, I propose the following agenda:

9h->10h Discussion on the governance of the KOffice project and decision making.
10h->11h Presentations
11h->whenever we are tired, actual work.

== governance of the KOffice project and decision making ==
About the governance, I won't spend time on speaking about our issues, I think 
we are all aware of them. I also think we are all a bunch of nice people, very 
motivate by KOffice, and I might even say pationnate about it. But we have a 
problem working together, and listening to each other.
So I had like us to take one hour of that meeting on brainstorming what we can 
do to improve the way we work together, and the way we take decision.
It will probably be a good idea to name a maintainer for each of our library.

And we should take 10 minutes to speak about our library spliting.

== Presentations ==
I had like a presentation on "API designing" and one on "unit testing".

== Actual work ==
Splited in two:
* API review of Flake and/or libkoodf
* Unit testing

I would still encourage everybody to go assist at least one hour of the API 
review, since I am sure it will be instructive to every body, since we are all 
more or less hacking on those libraries.

-- 
Cyrille Berger
_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel
[prev in list] [next in list] [prev in thread] [next in thread]