├── README.md ├── Draft_EDA_Annual_Data_Plan.md ├── Bureau-Annual-Data-Plan-Template.md ├── Draft_Census_Annual_Data_Plan.md ├── LICENSE └── GithubGuidanceforDepartmentofCommerce.md /README.md: -------------------------------------------------------------------------------- 1 | # Policies-Guidance 2 | Official instructions that are directly relevant to work performed by @CommerceGov on Github. 3 | -------------------------------------------------------------------------------- /Draft_EDA_Annual_Data_Plan.md: -------------------------------------------------------------------------------- 1 | __Draft document. In-Process and Representative. Does not reflect actual government plans.__ 2 | 3 | # Economic Development Administration (EDA) 4 | ## 2016 Data Plan 5 | 6 | ###Bureau's Mission: 7 | Economic Development creates the conditions for economic growth and improved quality of life by expanding the capacity of individuals, firms, and communities to maximize the use of their talents and skills to support innovation, lower transaction costs, and responsibly produce and trade valuable goods and services. 8 | 9 | Economic Development requires effective, collaborative institutions focused on advancing mutual gain for the public and the private sector. Economic Development is essential to ensuring our economic future. 10 | 11 | ###Annual Data Deliverables: 12 | 13 | 1. Fiscal Year 2014 Annual Report 14 | 2. Fiscal year 2015 Trade Adjustment Assistance for Firms (TAAF) Annual Report 15 | 16 | ###Schedule Milestones: 17 | 18 | * Q3 FY 2016: Deliverable #1 19 | * Q4 FY 2016: Deliverable #2 20 | 21 | ###Owners & Points of Contact: 22 | 23 | * Deliverables 1 & 2 = Bryan Borlik, Director Trade Adjustment Assistance, bborlik@eda.gov. 24 | -------------------------------------------------------------------------------- /Bureau-Annual-Data-Plan-Template.md: -------------------------------------------------------------------------------- 1 | __Draft document.__ 2 | 3 | General guidelines: 4 | 5 | 1. The total length of this plan should not exceed the equivalent of one printed page. 6 | 2. To support brevity, feel free to include hyperlinks to other public information resources. 7 | 3. All plans need three things: scope, resources and schedule. As long as you have these three categories sufficiently included, you will satisfy the reporting requirements. 8 | 4. A common phrase used in this template is "data product", this refers to any document, file, visualization, report, index, press release, blog, software, web site, web platform, web service, or other information service that is created and published and that supports the Department of Commerce's "Open for Business" Strategic Plan. 9 | 10 | # Sample 2016 Data Plan 11 | ## Bureau XYZ 12 | 13 | ###Bureau's Mission: 14 | To support America's economic prosperity and its competitiveness abroad. Bureau's desired outcomes under the [Department's Strategic Plan](http://2010-2014.commerce.gov/sites/default/files/documents/2014/march/doc_fy2014-2018_strategic_plan.pdf) for Data are: 15 | 16 | * Improved dissemination pathways for information that is already public. 17 | * Stronger and more engaged users around data products. 18 | * Higher quality data products that is more responsive to customer requests. 19 | * Continued vigilance in the rigorous protection of privacy and confidentiality. 20 | 21 | ###Annual Data Deliverables: 22 | 23 | 1. Product-A and Product-B available via an API 24 | 2. Launch Beta-version of one popular portion of bureau.gov site 25 | 3. Publish report on how Bureau's data products are being used. 26 | 4. Provide in-browser visualization tools for data located at bureau.gov/data 27 | 5. Launch bureau.gov/developer portal that features current open source projects 28 | 6. Make raw data available for all future publications of "Popular Report ABC" 29 | 7. Conduct a full, internal enterprise inventory of all data assets 30 | 8. Host second-annual customer user conference 31 | 9. Announce public-private partnership with industry leaders in support of "Project ABC" 32 | 10. Stand up Bureau's Office of Data Analytics with full-time resources 33 | 34 | ###Schedule Milestones: 35 | 36 | * Q1 FY 2016 = Deliverables 1, 2 and 3 37 | * Q2 FY 2016 = Deliverables 4 and 5 38 | * Q3 FY 2016 = Deliverables 6, 7 and 8 39 | * Q4 FY 2016 = Deliverables 9 and 10 40 | 41 | ###Owners & Points of Contact: 42 | 43 | * Deliverables 1, 5 and 10 = FirstLastName-A 44 | * Deliverables 2 = FirstLastName-B 45 | * Deliverables 3 = FirstLastName-C 46 | * Deliverables 4 = FirstLastName-D 47 | * Deliverables 6 = FirstLastName-E 48 | * Deliverables 7 = FirstLastName-F 49 | * Deliverables 8 and 9 = FirstLastName-G 50 | 51 | The Lead Owner of this Plan is "FirstLastName-A" and can be contacted at fLastName-A@doc.gov. 52 | -------------------------------------------------------------------------------- /Draft_Census_Annual_Data_Plan.md: -------------------------------------------------------------------------------- 1 | __Draft document. In-Process and Representative. Does not reflect actual government plans.__ 2 | 3 | # U.S. Census Bureau 4 | ## 2016 Data Plan 5 | 6 | ###Bureau's Mission: 7 | The Census Bureau's mission is to serve as the leading source of quality data about the nation's people and economy. We honor privacy, protect confidentiality, share our expertise globally, and conduct our work openly. We are guided on this mission by scientific objectivity, our strong and capable workforce, our devotion to research-based innovation, and our abiding commitment to our customers. 8 | 9 | ###Annual Data Deliverables: 10 | 11 | Note that this list does not include Decennial Census or Economic Census data releases. Decennial releases beginning at the end of years ending in "0"; Economic Census releases begin after each collection period - years ending in "2" or "7." It also doesn't include the dozens of infographics released throughout the year. For the sake of brevity, each recurring release is listed only once. 12 | 13 | 1. Population Estimates: Voting-Age Population Estimates 14 | 2. Annual Survey of Public Employment and Payroll 15 | 3. Annual Capital Expenditures Survey 16 | 4. Annual Survey of Manufactures 17 | 5. Annual Wholesale Trade Survey 18 | 6. Annual Survey of Public Pensions: State- and Locally-Administered Defined Benefit Data 19 | 7. Annual Survey of State Government Finances 20 | 8. Population Estimates: Metropolitan, Micropolitan, County, and Puerto Rico Municipio Population Estimates 21 | 9. Small Area Health Insurance Estimates (SAHIE) 22 | 10. Annual Revision of Monthly Wholesale Trade: Sales and Inventories 23 | 11. Annual Retail Trade Survey 24 | 12. Information and Communication Technology Survey 25 | 13. Annual Revision of Monthly Retail and Food Services: Sales and Inventories 26 | 14. Population Estimates: City and Town Population Estimates; and National, State, and County Housing Unit Estimates 27 | 15. Building Permits Final Annual State & Local Estimates 28 | 16. Annual Survey of State Government Tax Collections 29 | 17. Population Estimates: National, State, and County Population Estimates by Age, Sex, Race, and Hispanic Origin; and Puerto Rico Commonwealth and Municipio Population Estimates by Age and Sex 30 | 18. County Business Patterns 31 | 19. Nonemployer Statistics 32 | 20. ZIP Code Business Patterns 33 | 21. New Housing Characteristics 34 | 22. Construction Put in Place Final Annual Data 35 | 23. Nonresidential Construction Put in Place Geographic Series 36 | 24. American Community Survey: 1-Year Data (Areas with populations of 65,000 or more) 37 | 25. Income, Poverty and Health Insurance 38 | 26. Supplemental Poverty Measure 39 | 27. Residential Construction Length of Time 40 | 28. Service Annual Survey 41 | 29. National, State, and Puerto Rico Total Population Estimates 42 | 30  Small Area Income and Poverty Estimates (SAIPE) 43 | 31. American Community Survey 5-Year Estimates (All Geographic Areas, down to Block Groups) 44 | 32. Census of Governments: Finance - Survey of State and Local Government Finances 45 | 33. Advance Monthly Sales for Retail and Food Services 46 | 34. Advance Report on Durable Goods- Manufacturers' Shipments and Orders 47 | 35. Building Permits Revised Data with State & Local Estimates 48 | 36. Construction Put in Place 49 | 37. Full Report on Manufacturers' Shipments, Inventories and Orders 50 | 38. Manufacturing and Trade: Inventories and Sales 51 | 39. Manufacturing Housing Survey 52 | 40. Monthly Wholesale Trade: Sales and Inventories 53 | 41. New Residential Construction 54 | 42. New Residential Sales 55 | 43. Price Indexes of New Homes Under Construction 56 | 44. Housing Starts and Completions by Purpose and Design 57 | 45. New Homes Sold by Price and Financing 58 | 46. Price Index of New Homes Sold 59 | 47. QFR -Retail Trade (QFR-R) 60 | 48. Quarterly Financial Report for Manufacturing, Mining, Wholesale Trade and Selected Service Corporations (QFR-MMWS) 61 | 49. Quarterly Retail E-Commerce Sales 62 | 50. Quarterly Services Survey (QSS) 63 | 51. Commodity Flow Survey 64 | 52. Quarterly Survey of Plant Capacity Survey 65 | 53. Survey of Market Absorption 66 | 54. Housing Vacancies and Home Ownership 67 | 55. Quarterly Summary of State and Local Government Tax Revenues 68 | 56. Quarterly Survey of Public Pensions 69 | 70 | ###Schedule Milestones: 71 | 72 | * Deliverables 1, 2: Annually in January 73 | * Deliverables 3, 4, 5, 6, 7: Annually in February 74 | * Deliverables 8, 9, 10, 11, 12: Annually in March 75 | * Deliverable 13: Annually in April 76 | * Deliverables 14, 15, 16: Annually in May 77 | * Deliverables 17, 18, 19, 20, 21: Annually in June 78 | * Deliverables 22: Annually in July 79 | * Deliverables 23: Annually in August 80 | * Deliverables 24, 25, 26, 27: Annually in September 81 | * Deliverable 28: November 82 | * Deliverables 29, 30, 31: Annually in December 83 | * Deliverables 32-42: Monthly 84 | * Deliverables 43-55: Quarterly 85 | 86 | ###Owners & Points of Contact: 87 | 88 | * Deliverables 1, 8, 14, 17, 29 = Ryan Burson 89 | * Deliverables 2, 3, 4, 5, 6, 7, 11, 12, 18, 19, 20, 32, 54, 55 = Erika Becker Medina 90 | * Deliverables 9, 29, 30 = Lucy Datzell 91 | * Deliverables 10, 37, 39 = Bill Abriatis 92 | * Deliverables 112, 32, 48 = Ian Thomas 93 | * Deliverables 15, 21, 22, 23, 27, 34, 35, 39, 40, 41, 42, 43, 44, 45 = Erica Filipek 94 | * Deliverables 24, 31 = Deb Stempowski 95 | * Deliverable 25 = Carmen DeNavas-Walt 96 | * Deliverable 26 = Kathy Short 97 | * Deliverables 33, 36 = Adriana Stoica 98 | * Deliverables 46, 47 = Brandi Maxson 99 | * Deliverable 49 = Aidan Smith 100 | * Deliverable 50 = James Hinckley 101 | * Deliverable 51 = Susan Bucci 102 | * Deliverable 52 = George Boyd 103 | * Deliverable 53 = Bob Callis 104 | 105 | The Lead Owner of this Plan is Jeannie Shiffer who can be contacted at Jeannie.L.Shiffer@census.gov. 106 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | CC0 1.0 Universal 2 | 3 | Statement of Purpose 4 | 5 | The laws of most jurisdictions throughout the world automatically confer 6 | exclusive Copyright and Related Rights (defined below) upon the creator and 7 | subsequent owner(s) (each and all, an "owner") of an original work of 8 | authorship and/or a database (each, a "Work"). 9 | 10 | Certain owners wish to permanently relinquish those rights to a Work for the 11 | purpose of contributing to a commons of creative, cultural and scientific 12 | works ("Commons") that the public can reliably and without fear of later 13 | claims of infringement build upon, modify, incorporate in other works, reuse 14 | and redistribute as freely as possible in any form whatsoever and for any 15 | purposes, including without limitation commercial purposes. These owners may 16 | contribute to the Commons to promote the ideal of a free culture and the 17 | further production of creative, cultural and scientific works, or to gain 18 | reputation or greater distribution for their Work in part through the use and 19 | efforts of others. 20 | 21 | For these and/or other purposes and motivations, and without any expectation 22 | of additional consideration or compensation, the person associating CC0 with a 23 | Work (the "Affirmer"), to the extent that he or she is an owner of Copyright 24 | and Related Rights in the Work, voluntarily elects to apply CC0 to the Work 25 | and publicly distribute the Work under its terms, with knowledge of his or her 26 | Copyright and Related Rights in the Work and the meaning and intended legal 27 | effect of CC0 on those rights. 28 | 29 | 1. Copyright and Related Rights. A Work made available under CC0 may be 30 | protected by copyright and related or neighboring rights ("Copyright and 31 | Related Rights"). Copyright and Related Rights include, but are not limited 32 | to, the following: 33 | 34 | i. the right to reproduce, adapt, distribute, perform, display, communicate, 35 | and translate a Work; 36 | 37 | ii. moral rights retained by the original author(s) and/or performer(s); 38 | 39 | iii. publicity and privacy rights pertaining to a person's image or likeness 40 | depicted in a Work; 41 | 42 | iv. rights protecting against unfair competition in regards to a Work, 43 | subject to the limitations in paragraph 4(a), below; 44 | 45 | v. rights protecting the extraction, dissemination, use and reuse of data in 46 | a Work; 47 | 48 | vi. database rights (such as those arising under Directive 96/9/EC of the 49 | European Parliament and of the Council of 11 March 1996 on the legal 50 | protection of databases, and under any national implementation thereof, 51 | including any amended or successor version of such directive); and 52 | 53 | vii. other similar, equivalent or corresponding rights throughout the world 54 | based on applicable law or treaty, and any national implementations thereof. 55 | 56 | 2. Waiver. To the greatest extent permitted by, but not in contravention of, 57 | applicable law, Affirmer hereby overtly, fully, permanently, irrevocably and 58 | unconditionally waives, abandons, and surrenders all of Affirmer's Copyright 59 | and Related Rights and associated claims and causes of action, whether now 60 | known or unknown (including existing as well as future claims and causes of 61 | action), in the Work (i) in all territories worldwide, (ii) for the maximum 62 | duration provided by applicable law or treaty (including future time 63 | extensions), (iii) in any current or future medium and for any number of 64 | copies, and (iv) for any purpose whatsoever, including without limitation 65 | commercial, advertising or promotional purposes (the "Waiver"). Affirmer makes 66 | the Waiver for the benefit of each member of the public at large and to the 67 | detriment of Affirmer's heirs and successors, fully intending that such Waiver 68 | shall not be subject to revocation, rescission, cancellation, termination, or 69 | any other legal or equitable action to disrupt the quiet enjoyment of the Work 70 | by the public as contemplated by Affirmer's express Statement of Purpose. 71 | 72 | 3. Public License Fallback. Should any part of the Waiver for any reason be 73 | judged legally invalid or ineffective under applicable law, then the Waiver 74 | shall be preserved to the maximum extent permitted taking into account 75 | Affirmer's express Statement of Purpose. In addition, to the extent the Waiver 76 | is so judged Affirmer hereby grants to each affected person a royalty-free, 77 | non transferable, non sublicensable, non exclusive, irrevocable and 78 | unconditional license to exercise Affirmer's Copyright and Related Rights in 79 | the Work (i) in all territories worldwide, (ii) for the maximum duration 80 | provided by applicable law or treaty (including future time extensions), (iii) 81 | in any current or future medium and for any number of copies, and (iv) for any 82 | purpose whatsoever, including without limitation commercial, advertising or 83 | promotional purposes (the "License"). The License shall be deemed effective as 84 | of the date CC0 was applied by Affirmer to the Work. Should any part of the 85 | License for any reason be judged legally invalid or ineffective under 86 | applicable law, such partial invalidity or ineffectiveness shall not 87 | invalidate the remainder of the License, and in such case Affirmer hereby 88 | affirms that he or she will not (i) exercise any of his or her remaining 89 | Copyright and Related Rights in the Work or (ii) assert any associated claims 90 | and causes of action with respect to the Work, in either case contrary to 91 | Affirmer's express Statement of Purpose. 92 | 93 | 4. Limitations and Disclaimers. 94 | 95 | a. No trademark or patent rights held by Affirmer are waived, abandoned, 96 | surrendered, licensed or otherwise affected by this document. 97 | 98 | b. Affirmer offers the Work as-is and makes no representations or warranties 99 | of any kind concerning the Work, express, implied, statutory or otherwise, 100 | including without limitation warranties of title, merchantability, fitness 101 | for a particular purpose, non infringement, or the absence of latent or 102 | other defects, accuracy, or the present or absence of errors, whether or not 103 | discoverable, all to the greatest extent permissible under applicable law. 104 | 105 | c. Affirmer disclaims responsibility for clearing rights of other persons 106 | that may apply to the Work or any use thereof, including without limitation 107 | any person's Copyright and Related Rights in the Work. Further, Affirmer 108 | disclaims responsibility for obtaining any necessary consents, permissions 109 | or other rights required for any use of the Work. 110 | 111 | d. Affirmer understands and acknowledges that Creative Commons is not a 112 | party to this document and has no duty or obligation with respect to this 113 | CC0 or use of the Work. 114 | 115 | For more information, please see 116 | 117 | 118 | -------------------------------------------------------------------------------- /GithubGuidanceforDepartmentofCommerce.md: -------------------------------------------------------------------------------- 1 | # GitHub Guidance 2 | This is Department of Commerce (DOC) guidance for how DOC uses GitHub. We are using GitHub to share code and content in the spirit of collaboration and open government. Other agencies and organizations may use social media differently. This guidance covers DOC’s GitHub account and the accounts of DOC bureaus. 3 | 4 | Remember that your official activities online are subject to applicable Federal law, ethics regulations, and agency policies. Existing policies and guidance for accessibility, privacy, external site links, cookies, and writing style apply to social media tools as well. 5 | 6 | ## What is GitHub? 7 | GitHub is a third-party website that offers code repositories that developers can use to collaborate on software development projects in real-time. Many users also use GitHub to publish and track documents, such as style guides and policies. In addition, GitHub provides social networking features that allow developers to follow open source projects, share code, and learn how code changes are made throughout the development process. The public can submit suggested changes to a developer’s content that the developer can accept and integrate. GitHub is so named because it uses the open source version control system called Git. [Learn more about GitHub and how to use it](https://github.com/about). 8 | 9 | ## Department of Commerce Accounts on GitHub 10 | GitHub offers free public repositories for open source projects as well as subscription-based private repositories for closed projects. DOC has created an organization account with GitHub, which includes a limited number of private repositories and unlimited public repositories. DOC staff interested in using GitHub to post content must create a repository in the DOC account that is applicable to the staff’s project. Project documents are grouped by GitHub repositories. If your project is a DOC-wide project, then you must create a repository on http://www.github.com/commercegov. If your project is a project owned by a bureau under the Department of Commerce, you may use the bureau’s GitHub account. Your bureau’s GitHub account must include at least two bureau employees as a part of the bureau's owners group. Questions can be directed to the DOC Office of Digital Engagement at webmaster@doc.gov, or to the Deputy Director of Digital Strategy, Alicia Sowah. 11 | 12 | ## Basics for GitHub Users 13 | All users (from DOC and its bureaus) should 14 | 1. Use a real picture as their GitHub profile pic. 15 | 2. Enable [two-factor authentication](https://help.github.com/articles/about-two-factor-authentication/) for their Github account. 16 | 17 | 18 | ## Who May Have Administrative and Write Access to the Department of Commerce GitHub Account or Official DOC Bureau GitHub Accounts? Who may be team members? 19 | DOC civil service staff may be account owners and team leaders with administrative level rights, giving them the ability to create repositories and assign team members to their GitHub projects. Both DOC civil service staff and authorized contractors may be team members able to contribute content to existing repositories. Under no circumstances may non-DOC staff, unauthorized contractors, or members of the public become team members. The public can make [pull requests](https://help.github.com/articles/using-pull-requests/), comment, and make content suggested edits to your content. Pull requests are the heart of collaboration on GitHub. When GitHub members make a pull request, they are proposing their changes to your content and requesting that you pull in their contribution. They will not be allowed to make actual changes until you review and approve those changes. 20 | 21 | ## Getting Started 22 | ### Approval Steps 23 | 1. Get approval from your supervisor to proceed. 24 | 2. Login to the DOC Social Media Application Tracking System and apply for permission to create a Github account. You must register with your work email, which should be independent from any personal account you may have on Github. 25 | 3. Get approval from the information owner of the DOC software or code that you want to put on GitHub. Permission from the information owner ensures that DOC or the DOC bureau allows the information to be placed on GitHub private repositories for internal collaboration or on GitHub public repositories for internal collaboration, public comment, and public use. 26 | 4. Forward your approval from your manager and the information owner to your bureau’s normal approvers for web content. 27 | 5. Upon approval from the proper web content approving authority, post the code, and share the link with the data owner and the web content approving authority. 28 | 29 | 30 | # Posting Department of Commerce Content to GitHub Public Repositories 31 | The DOC GitHub account can be used to publish DOC software, design patterns, style guides, documents, and code as open source, making the content available for developers to fork and build upon for their own projects. Developers also may help you by commenting on your content with suggested improvements and questions. In order to comply with the Department of Commerce’s Social Media Policy (intranet link), data and software code posted in a public repository on GitHub must be available on DOC’s public website or a DOC bureau’s public website. If you are publishing to a public repository on DOC’s main GitHub account or a DOC bureau's GitHub account, and this will be the only source of the code, then you must download a quarterly copy of that content from the GitHub repository and publish it on your agency or bureau official website. Your project plan must include quarterly download and publication for every quarter that there are changes made to the GitHub repository. Each project published on a GitHub repository must be recorded in the DOC Social Media Application Tracking System. 32 | 33 | Bureaus may only post content in which the DOC has the right to share or distribute. Content that was created solely by DOC employees in the course of their employment may be shared subject to this policy. Before posting content, the bureau must determine whether any part of the content was created by a DOC contractor or a third party. If the content was created in whole or in part by a contractor, the bureau must determine whether the contractor has assigned all its rights in the content to DOC. If the bureau is either unable to determine whether the content was created by a contractor or unable to verify that the contractor has assigned its rights to DOC, then the bureau must not post the content that was created by or subject to the contractor’s contributions. Content created by third parties (not DOC employees or contractors) may not be shared except as permitted by the terms of the applicable license, including any open-source licenses. 34 | 35 | It is your responsibility to ensure your content contains only content that DOC has a right to share. It is also your responsibility to ensure that any content we share pursuant to a license comports with the terms of the license, including open-source licenses. Failure to do so could lead to legal ramifications for your project and the Department. If you have questions about whether DOC has been assigned all rights in content created by a contractor, please first consult the contracting officer responsible for the contract under which the content was created. If there remain outstanding legal questions about DOC’s legal rights in the content and the ability to share the content, please consult the Office of General Counsel’s General Law Division. 36 | 37 | All projects posted to a DOC or DOC bureau GitHub public repository must include a link to the location where the project code resides on the DOC or DOC bureau public website, as well as the following disclaimer in a README file: 38 | 39 | “The United States Department of Commerce (DOC) GitHub project code is provided on an ‘as is’ basis and the user assumes responsibility for its use. DOC has relinquished control of the information and no longer has responsibility to protect the integrity, confidentiality, or availability of the information. Any claims against the Department of Commerce stemming from the use of its GitHub project will be governed by all applicable Federal law. Any reference to specific commercial products, processes, or services by service mark, trademark, manufacturer, or otherwise, does not constitute or imply their endorsement, recommendation or favoring by the Department of Commerce. The Department of Commerce seal and logo, or the seal and logo of a DOC bureau, shall not be used in any manner to imply endorsement of any commercial product or activity by DOC or the United States Government.” 40 | After you have published your content to a DOC bureau’s public GitHub repository, you must email the DOC Office of Digital Engagement at webmaster@doc.gov, or the Deputy Director of Digital Strategy, Alicia Sowah, with the link to your repository so that the DOC GitHub account can “watch” your repository and be notified of updates. DOC will do this by selecting the “Watch” button at the top of your repository. All DOC bureau public repositories should be “watched” by DOC GitHub administrators so that they appear on the administrators’ dashboards. 41 | 42 | ## Licensing and Making Available to the Public 43 | When new code is posted to a DOC or DOC bureau GitHub public repository, they should be accompanied by the following statement, in a LICENSE file in the repository: 44 | 45 | “Software code created by U.S. Government employees is not subject to copyright in the United States (17 U.S.C. §105). The United States/Department of Commerce reserve all rights to seek and obtain copyright protection in countries other than the United States for Software authored in its entirety by the Department of Commerce. To this end, the Department of Commerce hereby grants to Recipient a royalty-free, nonexclusive license to use, copy, and create derivative works of the Software outside of the United States.” 46 | 47 | By publishing your government content to a public GitHub repository, you are making it freely available to the public for download and use. 48 | 49 | If you wish to allow those outside of the federal government to offer their own contributions (such as code improvements or bug fixes), then you must include in the repository a CONTRIBUTING file containing the following language: “By submitting a pull request, you grant to the U.S. Department of Commerce lifelong, paid-up, worldwide, non-exclusive permission to reproduce, use for Governmental purposes, and further disseminate your contributions in all media now existing or to be created in the future, including posting to the U.S. Department of Commerce’s GitHub or the Github repositories of Commerce’s component bureaus.” 50 | 51 | ## What Not to Post on GitHub, Publically or Privately 52 | When considering what content to post on GitHub, no distinction should be made between the public and private GitHub repositories. The private repositories are only meant to provide a closed environment for working projects not yet ready for public use and should never contain sensitive code. All DOC projects hosted on GitHub should be suitable for eventual public access. For questions about DOC's GitHub account or this guidance document, please contact the DOC Office of Digital Engagement at webmaster@doc.gov, or the Deputy Director of Digital Strategy, Alicia Sowah. 53 | 54 | ## Follow Federal Requirements 55 | ### Section 508 56 | Social Media tools, like other web-based applications, whether inside the DOC network or in the other areas of the Web, must make every effort to comply with Section 508 and other policies on accessibility, privacy, and record keeping. In some rare instances, it's not possible to redesign an outside system to be accessible, but it's usually possible to link back to equivalent information on a DOC website. A DOC email address must always be visible on a DOC or DOC bureau GitHub site for users who require alternative methods of accessing the information posted. 57 | 58 | ### Privacy Policy 59 | The [Department of Commerce’s Privacy Policy](http://www.commerce.gov/privacy-policy) applies to any DOC or DOC bureau GitHub site or repository. 60 | 61 | ### Plain Language Policy 62 | When applicable, GitHub publications made by DOC should comply with [The Plain Writing Act of 2010](http://www.commerce.gov/plain-language), which requires federal agencies to write "clear Government communication that the public can understand and use." 63 | 64 | ### Comment Policy 65 | GitHub comments from and to the public will adhere to [DOC’s Comment Policy](http://www.commerce.gov/comment-policy). 66 | 67 | ## Department of Commerce GitHub Accounts 68 | If you do not see your official DOC GitHub account listed, please contact the DOC Office of Digital Engagement at webmaster@doc.gov, or the Deputy Director of Digital Strategy at webmaster@doc.gov, Alicia Sowah. 69 | 70 | [CommerceGov](https://github.com/commercegov) 71 | 72 | [InternationalTradeAdministration](https://github.com/InternationalTradeAdministration/developerportal) 73 | 74 | [NOAA-ORR-ERD](https://github.com/NOAA-ORR-ERD) 75 | 76 | [NOAA-GFDL](https://github.com/NOAA-GFDL) 77 | 78 | [NMML](https://github.com/NMML) 79 | 80 | [NTIA](https://github.com/NTIA) 81 | 82 | [USPTO](https://github.com/uspto) 83 | --------------------------------------------------------------------------------