Open to anyone with a .gov or .mil email address.
To join, email email@example.com with nothing in the subject and
subscribe code in the body.
We are a community of federal government employees and contractors interested source code and open source software (OSS). We support the implementation of the Federal Source Code Policy (FSCP) and associated technology platform Code.gov.
What we do
We support federal agency implementation of the FSCP. According to the FSCP, agencies are required to create their own source code policy, update acquisition language to capture new custom code, and create a source code inventory and encouraged to open sourcing a portion of the inventory.
We have a listserv with approximately 650+ agency members interested in federal software and hold an agency-wide community-of-pracitce (CoP) monthly meeting on the third Thursday of the month. Through the Code.gov website and API, we facilitate aggregatation of agency source code for sharing across agencies and with the public.
Who we are
We are developers and open source experts, dedicated to helping you with any questions or concerns you may have about source code and OSS in the federal government. Curious about something regarding open source software or Code.gov? Ask us.
Amin Mehr, Washington, DC
Joseph Castle, Washington, DC
When participating in this CoP, follow Digital.gov Etiquette Guidelines. Respect your peers, use plain language, be patient, practice constructive criticism, and stay organized. By participating in this CoP conversation, you agree to abide by the TTS Code of Conduct.
The Communities of Practice are hosted by digital.gov, a service of the Technology Transformation Services (TTS) within the General Services Administration (GSA). GSA is a federal agency subject to the Freedom of Information Act (FOIA) and must comply with requests for records made under FOIA. As a result, all communications made on this Communities of Practice LISTSERV are subject to release under FOIA.
When participating in this CoP, follow Digital.gov Community Guidelines.
Have feedback or questions? Send us an email »