Hi,

I'm fine with delaying things a bit, but at the same time, that leaves
me with a bit of a problem. The problem being that I have patches on
top of components that I really don't want to keep private
indefinitely. For instance, I've fixed ScrollDecorator in the QtQuick2
branch so far, I have some other bugs I want to persue there too. I've
also (in the past) done a port of components to blackberry
(http://www.youtube.com/watch?v=kEJhMhhnqGo&feature=plcp) that I'd
like to try port to QML2 and get integrated in one central location so
that everyone can share benefits and work from a single codebase.

Now, obviously, it's a bit difficult for me to do that if I can't push
changes to that central location - so how can I best proceed here? I
have a signed CLA already, so is there a way that I can get access to
the existing repository to push changes, with the eventual aim of
moving it to Gerrit in a few months?

BR,

Robin

On Tue, Jun 26, 2012 at 10:45 AM,  <[email protected]> wrote:
> Hello,
>
> For Symbian team it would be best not to move QtComponents to Gerrit until 
> say September. We can work with Gerrit, but just in case there is some 
> glitches in the transfer, we are better prepared to solve those at that time. 
> I am hopefully a good contact person to QtComponents Symbian development :)
>
> Regards,
> Jaska
> ext-jaakko.helanti (at) nokia.com
>
>>-----Original Message-----
>>Behalf Of Robin Burchell
>>Sent: 25. kesäkuuta 2012 19:52
>>To: [email protected]
>>Subject: Re: [Development] Importing (mobile) qt-components to gerrit
>>
>
>> One slight complication with this move is that the Symbian team
>> appears to still be actively working on their components - does anyone
>> have any contact with them to know what they'd like to do?
>
> _______________________________________________
> Development mailing list
> [email protected]
> http://lists.qt-project.org/mailman/listinfo/development
_______________________________________________
Development mailing list
[email protected]
http://lists.qt-project.org/mailman/listinfo/development

Reply via email to