I am interested in us establishing some kind of guidelines, then eventually have a tool one can run against a code base to check for those guidelines and then receive recommendations and links to tutorial/docs etc as to how to match our expectations. For example on a MediaWiki extension a guideline would be to use JSDoc for JavaScript documentation, and one could detect whether it is in use on the repository, if not a tool could automagically add it to the dependencies, add some basic configuration and point to a document as to how to use JSDoc.

Or is the session more on the workflows and social aspect of development?

@Volans, @Etonkovidova - Would either (or both) of you be interested in leading this session?

@kaldari thanks for the offer, but I think this deserves some preparatory work that I cannot commit to at the moment, I'm sorry.

In T234653#5558186, @kaldari wrote:

@Volans, @Etonkovidova - Would either (or both) of you be interested in leading this session?

Sure, it could be a short presentation of how QA processes are integrated into teams' workflow now, and then, an open discussion.

@Etonkovidova - That sounds great. I'll change the title and description to focus on the QA aspect. Please add yourself as the session leader above and feel free to add more details to the description (or change it completely).

In T234653#5564851, @kaldari wrote:

@Etonkovidova - That sounds great. I'll change the title and description to focus on the QA aspect. Please add yourself as the session leader above and feel free to add more details to the description (or change it completely).

Thanks!

In T234653#5552319, @hashar wrote:

I am interested in us establishing some kind of guidelines, then eventually have a tool one can run against a code base to check for those guidelines and then receive recommendations and links to tutorial/docs etc as to how to match our expectations. For example on a MediaWiki extension a guideline would be to use JSDoc for JavaScript documentation, and one could detect whether it is in use on the repository, if not a tool could automagically add it to the dependencies, add some basic configuration and point to a document as to how to use JSDoc.
Or is the session more on the workflows and social aspect of development?

As far as I understand it, this session is more about high level QA practices, not about tooling. Some tooling could be a part of the recommended practices, of course.