On Fri, 2019-08-30 at 22:06 -0400, Danny Lee wrote:
its definitely overwhelming with so many directions to go and
to learn. The challenge of trying to mentally grasp so many moving
parts is difficult, but I am taking it slow and getting involved
feel needed and feel interesting.
Don't be afraid. Time and patience are your friends. Look around, lurk
on mailing lists and IRC/Telegram channels/groups you could be
interested in. Sometimes there are discussion that let you to
understand how things work and that are the occasions to work on
something. And to learn new skills. I always recommend to read this
wiki page: How to be a successful contributor .
Sometimes I'd like to ask questions like "So, how do you
python 3?" but it seems a little bit much at this point. :)
Yes, this is a question that doesn't lead anywhere. Questions should be
focused on specific topics and aspects.
This is an interesting document: "How To Ask Questions The Smart Way"
Also, I notice there is a tempo that seems to come with the
feel like I arrived at the tail end of the previous release and so
testing/QA did not seem too busy (although I may be wrong).
Testing single packages is always ongoing.
On the other hand, talking about next release, well, take into account
that 17 September is the F31 Beta release preferred target. So there
will be a need to deeply test F31 images, it's going to be a bumpy
now that the freeze has occurred and the rawhide is moving towards a
release, I feel like there will be more testing to do.
Perhaps you can tell me if regular QA people are testing 29/30
constantly or is it just around release times.
People, not only QA members, test packages during the whole period the
releases are supported. Indeed new updates for various packages are
pushed in the testing repository every day at a fast pace.
You're not supposed to test everything. The advice here is to test
packages you really use in every day tasks (it is also more easy to
evaluate if the update works or not).  
This mail getting too long :-) so I stop here.