Qt for Python/Community Calls

From Qt Wiki
< Qt for Python
Revision as of 15:22, 9 March 2020 by CristianMaureiraFredes (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

What's this about?

The main idea of the call is to share with the community what is the Development Team focusing right now, and what are the priorities for the next releases. Additionally, we would like to know what are your opinions and vision for the development of the project.

When? Where?

Next Thursday 12th of March at 17:00h (CET / GMT+1 / EDT+5 / PDT+8)

We will use Zoom, on the following link: https://zoom.us/j/121049577

We are limited to 40 minutes, so I believe that will allow us to keep it short.

In case of needing more time to discuss other things, we would change the platform for the next one.

Who can participate?

Anyone from the community can join the meeting if they are interested in the status of the project.

You don't need to be an expert to join, since most of the later changes to our documentation, for example, come from people new to Qt, so if you are just starting and have some suggestions, we will be more than happy to listen to them.

Can I ask questions?

Yes, hopefully, we can quickly state what are we working on, and what are the priorities at the moment, then we will leave the remaining time to hear your questions, comments, ideas, and more!

Why you don't send an email instead?

The motivation for this call is to hear back from you. Before the official release, we got the help and feedback from many members of our community, so we believe we should have an instance to communicate things more personally, and to see what's the vision you all have for the project, or maybe as users what is the project currently missing.

Having a call will allow us to have a quick discussion instead of a long email thread that maybe can last weeks.

How frequent is this meeting?

We would really like to see your response and depending on the interest we can transform this into a more frequent instance.