How to bring more attention and participation to 4.2 Testing Category

[adw]

@moonlitOrca

As for the testing team, I did read the testing team forum post (article Sven posted) before originally posting to this thread in the first place, but I still don’t feel it explains to me why the testing team is exclusive? Again, it’s just a topic I asked about to honestly try to help and contribute, since the question was posed how to get more involvement and attention. It seems making it exclusive automatically limits that?

I think this thread contains the answer to your question:

Testing team - how to deal with in Forum

Nice long title to clear the filters. There was a previous thread about feedback on testing which resulted in the “Testing 4.1” category under #user-support. We are revitalising the testing process in Qubes - there’s already a mail group for this purpose. I wondered what people thought about having a separate forum, (possibly closed membership), aimed specifically at testing, or a “testing” category under User-Support. The aim would be to have people commit to using the testing repositor…

@moonlitOrca

I have re-read the description twice, but I don’t see any unique ability afforded by joining the testing team?

This page shows the forum permissions granted to members of the testing team:

https://forum.qubes-os.org/g/testing-team/permissions

@moonlitOrca

Is it mostly just an organizational thing to have people who can be counted on to consistently test and who communicate directly?

I think the general idea is to have a higher-than-usual signal-to-noise ratio, which is enforced by allowing only members to post in the testing forum.

@moonlitOrca

If I am reading correctly, it looks like anyone can enable the testing repositories.

Correct.

@moonlitOrca

Great work by everyone (I especially don’t understand how marmarek can do everything he does. Incredible )

Agreed!