[Interest] Future of Qt [was: Future of Qt3d]

[Konstantin Tokarev]

08.11.2017, 15:22, "Lars Knoll" <lars.knoll at qt.io>:
> Hi Konstantin,
>
> this is probably more a topic for the development mailing list, but since we have it here:

Oops, I didn't check what list this is on :(

>
>> On 8 Nov 2017, at 12:31, Konstantin Tokarev <annulen at yandex.ru> wrote:
>>
>>> Things are probably not perfect though, and I do believe we have areas where we (as in TQtC) can and should improve. One example: Since we have development teams working in the same office, some items and ideas that are discussed over the coffee table are not visible enough to others.
>>
>> Here are a few (minor) issues that I'm facing when working on QtWebKit:
>>
>> 1. Many things are only possible when you have access to the internal network
>> 1a. Check integration progress or look at build logs before all jobs of integration finish
>> (in the past sometimes logs weren't uploaded even after finish, maybe it's fixed now)
>
> I haven’t checked the latest status, but I agree that would be great to have.
>
>> 1b. Try build stuff manually on CI build machine to debug build issue which doesn't
>> reproduce locally
>> 1c. Get access to artifacts (mostly fixed for QtWebKit as artifacts with "Packaging" flag
>> are now automatically exported, still relevant for other modules, and there may be cases
>> when artifacts without Packaging flag should be checked
>
> Both of those would be nice.
>
> For 1b, we need to find a way to make that safe and secure. There are a couple of infrastructure problems to solve to make that possible. Note that until half a year ago, it was very hard even for people inside TQtC to get a VM for debugging. That’s now solved, so hopefully we can somehow make the service public for contributors in the future.
>> 2. Releasing process is completely opaque, and members of release team who are the
>> only ones who can help, are almost always overloaded
>>
>> 3. It would be great if it was possible to get email notifications about state changes in
>> patches for Coin (I cannot view them, but automatic notification that patch went in and was
>> deployed would help)
>
> Isn’t that working for you? I do get email notifications from gerrit for all my patches when they get merged.

Ah, it's not about my patches, it's about cases when change in code of Coin (which is not open-source) is needed, e.g. changes related to provisioning process, or changes like what was done for QTQAINFRA-1492. Not a high-prority item, sure. Maybe it can be done differently, e.g. by showing Coin tag/commit number on generated web pages, and placing release notes somewhere in public access.


>
> Cheers,
> Lars


-- 
Regards,
Konstantin