-
Notifications
You must be signed in to change notification settings - Fork 10
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
13 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -3,6 +3,19 @@ title: DHTech Working Groups | |
description: | ||
--- | ||
|
||
DHTech members with a common interest can form a DHTech working group. To be considered a working group, DHTech asks that the group: | ||
- designates two people to serve as point of contact between the working group and the steering committee. | ||
- writes a short paragraph for this page describing the group. | ||
- provides bi-monthly updates about what the group is doing and how people can get involved to be included in our newsletter. | ||
|
||
The benefits of being recognized as an official working group are that the group: | ||
- is included on the list of working groups on this page. | ||
- can optionally have their own github repository and website under the DHTech GitHub organization (e.g. https://github.com/dh-tech/wg-education-training). | ||
- can apply to use some of the money we get from ADHO as a SIG to further the work of the working group. | ||
|
||
|
||
# Current DHTech Working Groups | ||
|
||
## Code Review Working Group | ||
|
||
The Code Review Working Group works on developing a community code review system for the digital humanities. The group meets on the third Wednesday of every month 11am-12pm ET. Please join the `#code-review-wg` channel on Slack or get in touch with Julia Damerow ([email protected]) if you are interested in joining. | ||
|