# Users <-> Porters Communication
The benefits of building a community around ports are enormous for the community and the project.

There is a small gap between porters and users where users can help with testing. The goal is to close that bridge by "converting" users to testers. In addition, some of the problems porters are dealing with require testing.

Bery your mind testing requires technical skills to solve a problem.
1. ADB Installed
2. Debugging and logs decription
3. A lot of patience

I conduct interviews among three ports with different skills of communication.

**#1** One is a trendy person, and he has 400 people group which is very active

**#2** Less known, quite a person who is "Committed" to the project for a long time, he doesn't have good communication skills or has an active group.

**#3** Porter has writing skills high communication skills to hold long-talks

## When do users require to test things?
To unite people to solve the problem, we need to unify them under "events."


### 1. While porting process continues
Users tend to ask the porter how to install, avoid breaking their device, and solve problems while boarding with the OS.

### 2. When OTA announced
In most cases, the tester will be the device owner (not distro hopers)

# The solution
I added the design Call to testing under two of the above conditions. First, we know when its ports are "Active," which means (Reletivly hot) under development and has a "non-tested" feature. Connect the dots with an excellent copy, and you'll have a good CTA opportunity.

**Only** when a port is finished and ready to daily drive can be used for OTA testing. So, now every everyday use port has a banner to join the general testing group, calling anyone with this device to help.

The conclusion is not final and requires more research on harnessing distro hopers to the project.

I've been told it's hard to draw in volunteers who started to help in the past. Yes, that is true. However, it is possible with the right content, copy, and time.