[Kde-accessibility] qt-atspi bug tracker and hosting

[Frederik Gladhorn]

Hi,

I spent a little more time pondering this.
In the end we need to get the bridge into Qt itself, otherwise it will always 
be a catching up with changes. I looked at Qt 5 and there is quite some work 
to do (I will change many things and move plugins and classes around) as 
discussed earlier. Also I need to move the framework to work with the new 
QGuiApplication and friends and make sure it still works with the legacy 
QApplication. Then there is QML.

One part about this would then be copyrights. I will check how we can procede 
with merging the bridge (target would be some Qt 5 version, preferably the 
first one ;)).

Out of curiosity: I think Mark, Jeremy and Jose are the only contributors. Are 
you all ok with the Contributor License Agreement? I think you all contributed 
to Qt before in some way. (http://qt.nokia.com/merge_requests/agreement)

Greetings
Frederik



Monday 15. August 2011 23.00.06 skrev Jeremy Whiting :
> Frederik, Jose, all,
> 
> I spoke with the kde sysadmins and they agree it doesn't make sense to put
> qt-atspi into bugs.kde.org unless it's code is moved from gitorious to
> kdesupport on git.kde.org.  I thus hereby propose we migrate it.  I would
> like feedback though, as I'm not sure if that's enough reason to migrate
> (convenience for those developing)
> 
> Arguments for:
> 1 Convenient and good location, since kde accessibility will rely on the
> bridge to work with at tools like orca, etc.
> 2 Mostly KDE developers have worked on it so far, besides Mark Doffman's
> initial work on it at codethink.
> 
> Arguments against:
> 1 Makes it slightly harder for non kde developers to contribute to it than
> leaving it on gitorious.
> 2 Other qt-only applications that might want it may not look for it hosted
> under kdesupport.
> 
> ideas? thoughts?
> Jeremy