You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are several ways you can volunteer with the Document Assembly Line:
13
+
There are several volunteer teams you can join:
13
14
14
-
*[Updates.](#interview-updates) Help us work through our backlog of update tasks.
15
-
*[Testing.](#user-testing) Test live interviews and report issues for the updates team.
15
+
*[Updates.](#interview-updates) Help us work through our backlog of interview improvements and updates.
16
+
*[Testing.](#user-testing) Test interviews and create issue reports to help us make improvements and updates.
16
17
*[Translation.](#translation) Review translations for accuracy.
17
-
*[Data validation.](#data-validation) Update data sources like courthouse addresses.
18
+
*[Information gathering.](#information-gathering) Gather and update the information sources that power interview features, like courthouse addresses.
18
19
19
20
All volunteer work is done remotely, and all training, meetings, and communication happen online, via Zoom, Microsoft Teams, and GitHub.
20
21
21
22
### Interview updates
22
23
23
-
Update interviews from a backlog of tasks. **No coding experience is necessary to join this team**. This does involve coding in Docassemble, but we will teach you everything you need to get started and support you with regular check-ins. You just need to be willing to learn!
24
+
Update interviews from a backlog of tasks. This involves coding in Docassemble, but **no coding experience is necessary to join this team**. we will teach you everything you need to get started and support you with regular check-ins. You just need to be willing to learn!
24
25
25
-
The updates team requires a long-term commitment. Volunteers should be able to commit at least 5–10 hours per month for at least 3 months.
26
+
Updating interviews is an ongoing project, and the updates team requires a long-term commitment. Volunteers should be able to commit at least 5–10 hours per month for at least 3 months.
26
27
27
28
### User testing
28
29
29
30
Test interviews independently or live over Zoom, depending on what we need to test. No experience or legal knowledge is necessary.
30
31
31
-
We organize an interview testing project about once a year, usually during the summer, and we ask for live-testing volunteers as needed.
32
+
We organize an interview testing project about once a year, usually during the summer. Otherwise, we ask for testing volunteers as needed, by notifying the testing team via email and Teams. To get notified, complete the [signup form](#sign-up-to-volunteer) so we know you are interested.
32
33
33
34
### Translation
34
35
35
36
Review draft translations for accuracy to help make interviews more accessible. The translation team primarily needs native speakers to ensure clear translations.
36
37
37
-
We ask for translation volunteers as needed.
38
+
We ask for translation volunteers as needed, by notifying the translation team via email and Teams. To get notified, complete the [signup form](#sign-up-to-volunteer) so we know you are interested.
38
39
39
-
### Data validation
40
+
### Information gathering
40
41
41
-
Collect and update the information that powers guided interview features, such as courthouse addresses or resources.
42
+
Gather and update information that powers guided interview features. For example, guided interviews may fill in courthouse addresses or suggest other resources, but that information is only useful if it is up-to-date.
42
43
43
-
We ask for data validation volunteers as needed.
44
+
We ask for information volunteers as needed, by notifying the information team via email and Teams. To get notified, complete the [signup form](#sign-up-to-volunteer) so we know you are interested.
44
45
45
46
## Expectations
46
47
47
-
We expect volunteers who are actively working on a project to check in once a week. There are several options for checking in:
48
-
49
-
- Come to office hours (you can find the schedule in the [**General** channel in Teams](https://teams.microsoft.com/l/channel/19%3A8b0fa1d62a014c7d9c27b69939e38644%40thread.tacv2/General?groupId=eaa9bd9d-cf39-4686-8f30-e55aa9d98c75&tenantId=78733fa9-540e-4eb8-bf29-73c4eeb63412))
50
-
- Attend the Monday community standup (interview updates team only)
51
-
- Post an update in the [**Volunteers** channel in Teams](https://teams.microsoft.com/l/channel/19%3A51759e27ee9749c1956ad38f08560c1f%40thread.tacv2/Volunteers?groupId=eaa9bd9d-cf39-4686-8f30-e55aa9d98c75&tenantId=78733fa9-540e-4eb8-bf29-73c4eeb63412)
52
-
- Email your update to the person you are working with
48
+
We expect volunteers who are actively working on a project to check in regularly. In general, check-ins are brief. They are usually Zoom meetings, but in some cases we may use asynchronous updates in Teams.
53
49
54
-
Check-ins are meant to be brief. Whether you join us live on Zoom or post your update in Teams, plan to share three things:
50
+
The purpose of check-ins is to keep the project on track by sharing your progress, plan, and questions or blockers with your team:
55
51
56
52
1.**Progress.** What did you do last week?
57
53
2.**Plan.** What are you going to do this week?
58
-
3.**Blockers.** Is anything preventing you from making progress?
54
+
3.**Questions/blockers.** Is anything preventing you from making progress?<br />Blockers can include questions, tech support issues, uncooperative third parties, etc. We often address questions and blockers live during meetings, or we can follow up later.
59
55
60
-
Blockers can include questions, tech support issues, uncooperative third parties, etc. And if you are ready for another assignment, let us know!
56
+
Also, let us know if you need something else to work on.
0 commit comments