Inclusion of simon in kde-accessibility

Alvaro Soliverez asoliverez at
Wed Jul 21 11:39:53 BST 2010

On Wed, Jul 21, 2010 at 7:11 AM, Sebastian K├╝gler <sebas at> wrote:
> On Wednesday 21 July 2010 10:59:44 Peter Grasch wrote:
>> On Wednesday 21 July 2010 09:41:24 Frederik Gladhorn wrote:
>> > Now Peter asked if the review could start already. I'm not sure about
>> > that. Hasn't this happened before, that someone put a note where to find
>> > the to- be-reviewed app into kdereview instead of cloning the sources?
>> > If I recall correctly for rekonq the situation was/is similar.
>> > So would this be acceptable in this special situation?
>> > I know we have our rules. On the other hand, sometimes we need to
>> > accommodate reality ;)
>> Thanks for the uplifting words :)
>> At this point I just want to point out again that keeping a copy of the
>> sources on the kdereview SVN wouldn't really be a problem imho if it were
>> just for the period of the review.
>> I am the only active developer on the codebase on sf anyways and syncing my
>> changes wouldn't really be an issue for me.
> I think that's a fine solution: Put Simon into kdereview, announce it on k-c-d
> (this list :)), and have it reviewed. Then, when the review is done, wait for
> to become open and move it there.

Why not just wait until is open and THEN go through the
kdereview process?
After all, the kdereview process is only 2 weeks (if all goes well, I
know), so it's not like a big delay if he waits for it to be open.
Like others said, and I can tell from experience, once in the KDE SVN,
it's not only you making changes, and I don't see much sense in going
through the review and then moving back out of KDE until git is open.

More information about the kde-core-devel mailing list