Hi Valentin,

> 1. Is there a list of "good first issues" or something like that?

There are various tags set on tickets that could help find such issues,
but we could indeed do better - if only by providing some easy-to-find
links to searches that will find everything with those tags.

There is one solid answer I can give though: scratch your own itch.  The
issues ticket to work on is the one that fixes a problem you actually
experience.

> 2. Is there a way to claim an issue to avoid implementing it with
> someone in parallel?  I understand new contributors may be
> unreliable. But it would be nice to have some means to claim a ticket
> with an obligation to report on progress within a reasonable
> timeframe.

Assigning it to yourself and setting "Work in progress" (select "Start
work" from the status drop-down that probably describes it as "Reported"
or "Open" - you might need to go via "Accept" to get that option) is
about as good as we can offer.  It's no guarantee that no-one else will
work on it, but it's a good way of saying "I'm working on it".

That is, of course, susceptible to someone doing so and then abandoning
the effort without setting it back to Open (via "Stop work").  Some
clues to whether that has happened may be found by looking at the
history on the ticket and, if it has any Gerrit reviews, looking at them
to see what their status is, or how active they are.

If you find a ticket you'd be interested in working on, or if you're
just interested in how work on it is progressing, you can either comment
on it or use the Share icon in the top right to contact the person who
claims to be working on it.  Asking them how it's going and offering to
take it over if they've given up work on it is entirely reasonable.  If
you get no answer, it's a fair guess that they've abandoned it so you
may as well have a go at it yourself.

> 3. What is the process for proposing new features?  I read somewhere
> on the Qt Forum that they need to be voted on or something like this.

First search Jira for whether someone has already suggested it.  If not,
file a Suggestion ticket in Jira.  It won't necessarily get acted on, of
course.  Looking at relevant code's git history, and at who the ticket
gets auto-assigned to, can give you some clues to who to get in touch
with to ask whether a contribution implementing your suggestion would be
likely to get accepted.  And, of course, there's always this mailing
list.

> 4. What should I do if I get stuck while implementing something and
> want to ask more experienced developers to help?  Or if I have some
> draft implementation which I know is imperfect, but I do not know how
> to improve?

Check who was auto-assigned the ticket when it was first filed, and
anyone else that it's been assigned to since.  Look at the git history,
of code you suspect is relevant, for authors and reviewers.  Those are
the folk most likely to be able to help.  Also, check out the
[[Maintainers]] page on wiki.qt.io, if you can work out which components
of Qt seem likely relevant, and contact their maintainers.

> Overall, I think current guidelines mostly cover technical aspects
> (...). But they barely cover communication and workflows.

Sounds about right, modulo how up to date the technical guidelines are
(or, in some cases, aren't).

        Eddy.
-- 
Development mailing list
[email protected]
https://lists.qt-project.org/listinfo/development

Reply via email to