veyepar: Technical writing as public service: working on open source in government

Author(s):	Britta Gustafson
Location	Crystal Ballroom
Date	may Mon 23	Days Raw Files
Start	09:30	First Raw Start	09:17
Duration	00:30.0:00	Offset	0:12:33
End	10:00	Last Raw End	10:17
Chapters	00:00 0:16:18 0:29:43
Total cuts_time	29 min.

http://lanyrd.com/2016/writethedocs/sfbzrt/
raw-playlist raw-mp4-playlist encoded-files-playlist host tweet mp4 svg png

assets release.pdf Technical_writing_as_public_service_working_on_open_source_in_government_Britta_Gustafson.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:

Locked:

clear this to unlock

Locked by:

user/process that locked.

Start:

initially scheduled time from master, adjusted to match reality

Duration:

length in hh:mm:ss

Name:

Video Title (shows in video search results)

Emails:

email(s) of the presenter(s)

Released:

has someone authorised pubication

Normalise:

Channelcopy:

m=mono, 01=copy left to right, 10=right to left, 00=ignore.

Thumbnail:

filename.png

Description:

markdown

What if U.S. federal agencies decided to reuse and contribute to open source software projects built by other agencies, since agencies often have similar technology problems to solve? And what if they hired technical writers with open source community experience to write documentation for these projects? That would be pretty cool. Also, that’s my work. I&#39;m part of 18F, a digital services consulting team within and for the federal government, and all of our work is open source.
I’ll explain surprising and rewarding aspects of working on documentation in government, through the lens of the cross-agency eRegulations project I’ve been working on. The Consumer Financial Protection Bureau started it, our 18F team (in the General Services Administration) adapted it for the Bureau of Alcohol, Tobacco, Firearms, and Explosives, and we’re adapting it for use by two more agencies.
I believe open source software development with good documentation aligns with core values of our government: work by the government belongs to the people, so it should be as transparent as possible, open to input from the people, and reusable by the people. The implementation of those values is the complicated part, of course! I’ll explain how we get stuff done at both the big-picture level (how laws and government economics shape our work) and the day-to-day details (how we work across teams to get useful information online).

Comment:

production notes