From 29774cdc28aa5acbf312eb44b150ca8c72472f34 Mon Sep 17 00:00:00 2001 From: natemcintosh Date: Wed, 7 Aug 2024 17:09:42 +0000 Subject: [PATCH] =?UTF-8?q?Deploying=20to=20gh-pages=20from=20@=20CDCgov/c?= =?UTF-8?q?fa-epinow2-pipeline@d3b008fa655deaebea6e40bc97c9cfb2a4417c88=20?= =?UTF-8?q?=F0=9F=9A=80?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- authors.html | 3 ++- news/index.html | 3 ++- pkgdown.yml | 2 +- search.json | 2 +- 4 files changed, 6 insertions(+), 4 deletions(-) diff --git a/authors.html b/authors.html index 0f88efe1..5cb25fc4 100644 --- a/authors.html +++ b/authors.html @@ -49,13 +49,14 @@

Citation

Susswein Z, Gostic K (2024). CFAEpiNow2Pipeline: EpiNow2 wrapper for deployment to Azure Batch. -R package version 0.0.0.9000. +R package version 0.0.0.9000, https://cdcgov.github.io/cfa-epinow2-pipeline/. 

@Manual{,
   title = {CFAEpiNow2Pipeline: EpiNow2 wrapper for deployment to Azure Batch},
   author = {Zachary Susswein and Katelyn Gostic},
   year = {2024},
   note = {R package version 0.0.0.9000},
+  url = {https://cdcgov.github.io/cfa-epinow2-pipeline/},
 }
diff --git a/news/index.html b/news/index.html index ca47e2e8..e7e8b465 100644 --- a/news/index.html +++ b/news/index.html @@ -33,7 +33,8 @@

Changelog

CFAEpiNow2Pipeline (development version)

-
diff --git a/pkgdown.yml b/pkgdown.yml index 99b41ab2..272fb06c 100644 --- a/pkgdown.yml +++ b/pkgdown.yml @@ -2,7 +2,7 @@ pandoc: 3.1.11 pkgdown: 2.1.0 pkgdown_sha: ~ articles: {} -last_built: 2024-08-07T15:26Z +last_built: 2024-08-07T17:09Z urls: reference: https://cdcgov.github.io/cfa-epinow2-pipeline/reference article: https://cdcgov.github.io/cfa-epinow2-pipeline/articles diff --git a/search.json b/search.json index 591bac97..c6f72855 100644 --- a/search.json +++ b/search.json @@ -1 +1 @@ -[{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/CONTRIBUTING.html","id":null,"dir":"","previous_headings":"","what":"Welcome!","title":"Welcome!","text":"Thank contributing CDC’s Open Source projects! questions doubts, don’t afraid send way. appreciate contributions, looking forward fostering open, transparent, collaborative environment. contributing, encourage also read LICENSE, README, code--conduct files, also found repository. inquiries questions answered content repository, feel free contact us.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/CONTRIBUTING.html","id":"public-domain","dir":"","previous_headings":"","what":"Public Domain","title":"Welcome!","text":"project public domain within United States, copyright related rights work worldwide waived CC0 1.0 Universal public domain dedication. contributions project released CC0 dedication. submitting pull request agreeing comply waiver copyright interest.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/CONTRIBUTING.html","id":"requesting-changes","dir":"","previous_headings":"","what":"Requesting Changes","title":"Welcome!","text":"pull request/merging process designed give CDC Surveillance Team space opportunity consider discuss suggested changes. policy affects CDC spaces, -line , users expected abide .","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/CONTRIBUTING.html","id":"open-an-issue-in-the-repository","dir":"","previous_headings":"Requesting Changes","what":"Open an issue in the repository","title":"Welcome!","text":"don’t specific language submit like suggest change something addressed, can open issue repository. Team members respond issue soon possible.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/CONTRIBUTING.html","id":"submit-a-pull-request","dir":"","previous_headings":"Requesting Changes","what":"Submit a pull request","title":"Welcome!","text":"like contribute, please submit pull request. order us merge pull request, must: * least seven days old. Pull requests may held longer necessary give people opportunity assess . * Receive +1 majority team members associated request. significant dissent team, meeting held discuss plan action pull request.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/DISCLAIMER.html","id":null,"dir":"","previous_headings":"","what":"DISCLAIMER","title":"DISCLAIMER","text":"Use service limited non-sensitive publicly available data. Users must use, share, store kind sensitive data like health status, provision payment healthcare, Personally Identifiable Information (PII) /Protected Health Information (PHI), etc. circumstance. Administrators service reserve right moderate information used, shared, stored service time. user abide disclaimer Code Conduct may subject action, including revoking access services. material embodied software provided “-” without warranty kind, express, implied otherwise, including without limitation, warranty fitness particular purpose. event shall Centers Disease Control Prevention (CDC) United States (U.S.) government liable anyone else direct, special, incidental, indirect consequential damages kind, damages whatsoever, including without limitation, loss profit, loss use, savings revenue, claims third parties, whether CDC U.S. government advised possibility loss, however caused theory liability, arising connection possession, use performance software.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/LICENSE.html","id":null,"dir":"","previous_headings":"","what":"Apache License","title":"Apache License","text":"Version 2.0, January 2004 ","code":""},{"path":[]},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/LICENSE.html","id":"id_1-definitions","dir":"","previous_headings":"Terms and Conditions for use, reproduction, and distribution","what":"1. Definitions","title":"Apache License","text":"“License” shall mean terms conditions use, reproduction, distribution defined Sections 1 9 document. “Licensor” shall mean copyright owner entity authorized copyright owner granting License. “Legal Entity” shall mean union acting entity entities control, controlled , common control entity. purposes definition, “control” means () power, direct indirect, cause direction management entity, whether contract otherwise, (ii) ownership fifty percent (50%) outstanding shares, (iii) beneficial ownership entity. “” (“”) shall mean individual Legal Entity exercising permissions granted License. “Source” form shall mean preferred form making modifications, including limited software source code, documentation source, configuration files. “Object” form shall mean form resulting mechanical transformation translation Source form, including limited compiled object code, generated documentation, conversions media types. “Work” shall mean work authorship, whether Source Object form, made available License, indicated copyright notice included attached work (example provided Appendix ). “Derivative Works” shall mean work, whether Source Object form, based (derived ) Work editorial revisions, annotations, elaborations, modifications represent, whole, original work authorship. purposes License, Derivative Works shall include works remain separable , merely link (bind name) interfaces , Work Derivative Works thereof. “Contribution” shall mean work authorship, including original version Work modifications additions Work Derivative Works thereof, intentionally submitted Licensor inclusion Work copyright owner individual Legal Entity authorized submit behalf copyright owner. purposes definition, “submitted” means form electronic, verbal, written communication sent Licensor representatives, including limited communication electronic mailing lists, source code control systems, issue tracking systems managed , behalf , Licensor purpose discussing improving Work, excluding communication conspicuously marked otherwise designated writing copyright owner “Contribution.” “Contributor” shall mean Licensor individual Legal Entity behalf Contribution received Licensor subsequently incorporated within Work.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/LICENSE.html","id":"id_2-grant-of-copyright-license","dir":"","previous_headings":"Terms and Conditions for use, reproduction, and distribution","what":"2. Grant of Copyright License","title":"Apache License","text":"Subject terms conditions License, Contributor hereby grants perpetual, worldwide, non-exclusive, -charge, royalty-free, irrevocable copyright license reproduce, prepare Derivative Works , publicly display, publicly perform, sublicense, distribute Work Derivative Works Source Object form.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/LICENSE.html","id":"id_3-grant-of-patent-license","dir":"","previous_headings":"Terms and Conditions for use, reproduction, and distribution","what":"3. Grant of Patent License","title":"Apache License","text":"Subject terms conditions License, Contributor hereby grants perpetual, worldwide, non-exclusive, -charge, royalty-free, irrevocable (except stated section) patent license make, made, use, offer sell, sell, import, otherwise transfer Work, license applies patent claims licensable Contributor necessarily infringed Contribution(s) alone combination Contribution(s) Work Contribution(s) submitted. institute patent litigation entity (including cross-claim counterclaim lawsuit) alleging Work Contribution incorporated within Work constitutes direct contributory patent infringement, patent licenses granted License Work shall terminate date litigation filed.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/LICENSE.html","id":"id_4-redistribution","dir":"","previous_headings":"Terms and Conditions for use, reproduction, and distribution","what":"4. Redistribution","title":"Apache License","text":"may reproduce distribute copies Work Derivative Works thereof medium, without modifications, Source Object form, provided meet following conditions: () must give recipients Work Derivative Works copy License; (b) must cause modified files carry prominent notices stating changed files; (c) must retain, Source form Derivative Works distribute, copyright, patent, trademark, attribution notices Source form Work, excluding notices pertain part Derivative Works; (d) Work includes “NOTICE” text file part distribution, Derivative Works distribute must include readable copy attribution notices contained within NOTICE file, excluding notices pertain part Derivative Works, least one following places: within NOTICE text file distributed part Derivative Works; within Source form documentation, provided along Derivative Works; , within display generated Derivative Works, wherever third-party notices normally appear. contents NOTICE file informational purposes modify License. may add attribution notices within Derivative Works distribute, alongside addendum NOTICE text Work, provided additional attribution notices construed modifying License. may add copyright statement modifications may provide additional different license terms conditions use, reproduction, distribution modifications, Derivative Works whole, provided use, reproduction, distribution Work otherwise complies conditions stated License.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/LICENSE.html","id":"id_5-submission-of-contributions","dir":"","previous_headings":"Terms and Conditions for use, reproduction, and distribution","what":"5. Submission of Contributions","title":"Apache License","text":"Unless explicitly state otherwise, Contribution intentionally submitted inclusion Work Licensor shall terms conditions License, without additional terms conditions. Notwithstanding , nothing herein shall supersede modify terms separate license agreement may executed Licensor regarding Contributions.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/LICENSE.html","id":"id_6-trademarks","dir":"","previous_headings":"Terms and Conditions for use, reproduction, and distribution","what":"6. Trademarks","title":"Apache License","text":"License grant permission use trade names, trademarks, service marks, product names Licensor, except required reasonable customary use describing origin Work reproducing content NOTICE file.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/LICENSE.html","id":"id_7-disclaimer-of-warranty","dir":"","previous_headings":"Terms and Conditions for use, reproduction, and distribution","what":"7. Disclaimer of Warranty","title":"Apache License","text":"Unless required applicable law agreed writing, Licensor provides Work (Contributor provides Contributions) “” BASIS, WITHOUT WARRANTIES CONDITIONS KIND, either express implied, including, without limitation, warranties conditions TITLE, NON-INFRINGEMENT, MERCHANTABILITY, FITNESS PARTICULAR PURPOSE. solely responsible determining appropriateness using redistributing Work assume risks associated exercise permissions License.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/LICENSE.html","id":"id_8-limitation-of-liability","dir":"","previous_headings":"Terms and Conditions for use, reproduction, and distribution","what":"8. Limitation of Liability","title":"Apache License","text":"event legal theory, whether tort (including negligence), contract, otherwise, unless required applicable law (deliberate grossly negligent acts) agreed writing, shall Contributor liable damages, including direct, indirect, special, incidental, consequential damages character arising result License use inability use Work (including limited damages loss goodwill, work stoppage, computer failure malfunction, commercial damages losses), even Contributor advised possibility damages.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/LICENSE.html","id":"id_9-accepting-warranty-or-additional-liability","dir":"","previous_headings":"Terms and Conditions for use, reproduction, and distribution","what":"9. Accepting Warranty or Additional Liability","title":"Apache License","text":"redistributing Work Derivative Works thereof, may choose offer, charge fee , acceptance support, warranty, indemnity, liability obligations /rights consistent License. However, accepting obligations, may act behalf sole responsibility, behalf Contributor, agree indemnify, defend, hold Contributor harmless liability incurred , claims asserted , Contributor reason accepting warranty additional liability. END TERMS CONDITIONS","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/LICENSE.html","id":"appendix-how-to-apply-the-apache-license-to-your-work","dir":"","previous_headings":"","what":"APPENDIX: How to apply the Apache License to your work","title":"Apache License","text":"apply Apache License work, attach following boilerplate notice, fields enclosed brackets [] replaced identifying information. (Don’t include brackets!) text enclosed appropriate comment syntax file format. also recommend file class name description purpose included “printed page” copyright notice easier identification within third-party archives.","code":"Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License."},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/authors.html","id":null,"dir":"","previous_headings":"","what":"Authors","title":"Authors and Citation","text":"Zachary Susswein. Author, maintainer. Katelyn Gostic. Author.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/authors.html","id":"citation","dir":"","previous_headings":"","what":"Citation","title":"Authors and Citation","text":"Susswein Z, Gostic K (2024). CFAEpiNow2Pipeline: EpiNow2 wrapper deployment Azure Batch. R package version 0.0.0.9000.","code":"@Manual{, title = {CFAEpiNow2Pipeline: EpiNow2 wrapper for deployment to Azure Batch}, author = {Zachary Susswein and Katelyn Gostic}, year = {2024}, note = {R package version 0.0.0.9000}, }"},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/code-of-conduct.html","id":null,"dir":"","previous_headings":"","what":"Creating a Culture of Innovation","title":"Creating a Culture of Innovation","text":"aspire create culture people work joyfully, communicate openly things matter, provide great services globally. like team communities (government private sector) reflect diversity kinds, just classes protected law. Diversity fosters innovation. Diverse teams creative teams. need diversity perspective create solutions challenges face. code conduct (adapted 18F’s Code Conduct). follow Equal Employment Opportunity laws expect everyone work adhere GSA Anti-harassment Policy, even work Centers Disease Control Prevention GSA. expect every user follow code conduct laws policies mentioned .","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/code-of-conduct.html","id":"be-empowering","dir":"","previous_headings":"","what":"Be Empowering","title":"Creating a Culture of Innovation","text":"Consider can encourage support others. Make room quieter voices contribute. Offer support enthusiasm great ideas. Leverage low cost experimentation support colleagues’ ideas, take care acknowledge original source. Look ways contribute collaborate, even situations normally wouldn’t. Share knowledge skills. Prioritize access input traditionally excluded civic process.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/code-of-conduct.html","id":"rules-of-behavior","dir":"","previous_headings":"","what":"Rules of Behavior","title":"Creating a Culture of Innovation","text":"understand must complete security awareness records management training annually order comply latest security records management policies. understand must also follow Rules Behavior use HHS Information Resources understand must use, share, store kind sensitive data (health status, provision payment healthcare, PII, etc.) circumstance. knowingly conceal, falsify, remove information. understand can use non-sensitive /publicly available data. understand passwords create set accounts need comply CDC’s password policy. understand stewards reserves right moderate data time.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/code-of-conduct.html","id":"boundaries","dir":"","previous_headings":"","what":"Boundaries","title":"Creating a Culture of Innovation","text":"Create boundaries behavior consider can create safe space helps prevent unacceptable behavior others. can’t list instances unacceptable behavior, can provide examples help guide community thinking respond experience types behavior, whether directed others. unsure something appropriate behavior, probably . person interact can define line . Impact matters intent. Ensuring behavior negative impact responsibility. Problems usually arise assume way thinking behavior norm everyone.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/code-of-conduct.html","id":"here-are-some-examples-of-unacceptable-behavior","dir":"","previous_headings":"Boundaries","what":"Here are some examples of unacceptable behavior","title":"Creating a Culture of Innovation","text":"Negative offensive remarks based protected classes listed GSA Anti-harassment Policy race, religion, color, sex, national origin, age, disability, genetric information, sexual orientation, gender identity, parental status, maritual status, political affiliation well gender expression, mental illness, socioeconomic status backgrounds, neuro()typicality, physical appearance, body size, clothing. Consider calling attention differences can feel alienating. Sustained disruption meetings, talks, discussions, including chatrooms. Patronizing language behavior. Aggressive behavior, unconstructive criticism, providing correction improve conversation (sometimes referred “well actually’s”), repeatedly interrupting talking someone else, feigning surprise someone’s lack knowledge awareness topic, subtle prejudice. Referring people way misidentifies gender /rejects validity gender identity; instance using incorrect pronouns forms address (misgendering). Retaliating anyone files formal complaint someone violated codes laws.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/code-of-conduct.html","id":"background","dir":"","previous_headings":"","what":"Background","title":"Creating a Culture of Innovation","text":"CDC Scientific Clearance process obtaining approvals appropriate CDC officials CDC information product released public CDC’s external public health partners. Information products require formal clearance include print, electronic, oral materials, CDC employees author co-author, whether published CDC outside CDC. CDC contractors developing content behalf CDC public CDC’s external public health partners also required put content formal clearance process. collaborative functions related projects include blogs, wikis, forums, bug tracking sites, source control others deemed necessary. individuals within CDC, adherence following policies required: * CDC “Clearance Information Products Disseminated Outside CDC Public Use” * HHS “Ensuring Quality Information Disseminated HHS agencies” collaborative materials controlled rules contained within document. allow real-time collaboration opportunities among CDC employees, CDC contractors CDC public health partners.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/code-of-conduct.html","id":"credit","dir":"","previous_headings":"","what":"Credit","title":"Creating a Culture of Innovation","text":"code conduct mainly adapted 18F’s Code Conduct CDC’s Informatics Innovation Unit R&D Lab’s code conduct.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/code-of-conduct.html","id":"relevant-legal-considerations","dir":"","previous_headings":"","what":"Relevant Legal Considerations","title":"Creating a Culture of Innovation","text":"Laws enforced Equal Employment Opportunity Commission Types discrimination prohibited law New proposed regulations","code":""},{"path":[]},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/index.html","id":"overview","dir":"","previous_headings":"","what":"Overview","title":"EpiNow2 wrapper for deployment to Azure Batch","text":"lightweight wrapper around {EpiNow2} add functionality deployment Azure Batch.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/index.html","id":"project-admin","dir":"","previous_headings":"","what":"Project Admin","title":"EpiNow2 wrapper for deployment to Azure Batch","text":"@zsusswein @natemcintosh @kgostic","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/index.html","id":"general-disclaimer","dir":"","previous_headings":"","what":"General Disclaimer","title":"EpiNow2 wrapper for deployment to Azure Batch","text":"repository created use CDC programs collaborate public health related projects support CDC mission. GitHub hosted CDC, third party website used CDC partners share information collaborate software. CDC use GitHub imply endorsement one particular service, product, enterprise.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/index.html","id":"public-domain-standard-notice","dir":"","previous_headings":"","what":"Public Domain Standard Notice","title":"EpiNow2 wrapper for deployment to Azure Batch","text":"repository constitutes work United States Government subject domestic copyright protection 17 USC § 105. repository public domain within United States, copyright related rights work worldwide waived CC0 1.0 Universal public domain dedication. contributions repository released CC0 dedication. submitting pull request agreeing comply waiver copyright interest.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/index.html","id":"license-standard-notice","dir":"","previous_headings":"","what":"License Standard Notice","title":"EpiNow2 wrapper for deployment to Azure Batch","text":"repository utilizes code licensed terms Apache Software License therefore licensed ASL v2 later. source code repository free: can redistribute /modify terms Apache Software License version 2, (option) later version. source code repository distributed hope useful, WITHOUT WARRANTY; without even implied warranty MERCHANTABILITY FITNESS PARTICULAR PURPOSE. See Apache Software License details. received copy Apache Software License along program. , see http://www.apache.org/licenses/LICENSE-2.0.html source code forked open source projects inherit license.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/index.html","id":"privacy-standard-notice","dir":"","previous_headings":"","what":"Privacy Standard Notice","title":"EpiNow2 wrapper for deployment to Azure Batch","text":"repository contains non-sensitive, publicly available data information. material community participation covered Disclaimer Code Conduct. information CDC’s privacy policy, please visit http://www.cdc.gov//privacy.html.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/index.html","id":"contributing-standard-notice","dir":"","previous_headings":"","what":"Contributing Standard Notice","title":"EpiNow2 wrapper for deployment to Azure Batch","text":"Anyone encouraged contribute repository forking submitting pull request. (new GitHub, might start basic tutorial.) contributing project, grant world-wide, royalty-free, perpetual, irrevocable, non-exclusive, transferable license users terms Apache Software License v2 later. comments, messages, pull requests, submissions received CDC including GitHub page may subject applicable federal law, including limited Federal Records Act, may archived. Learn http://www.cdc.gov//privacy.html.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/index.html","id":"records-management-standard-notice","dir":"","previous_headings":"","what":"Records Management Standard Notice","title":"EpiNow2 wrapper for deployment to Azure Batch","text":"repository source government records copy increase collaboration collaborative potential. government records published CDC web site.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/index.html","id":"additional-standard-notices","dir":"","previous_headings":"","what":"Additional Standard Notices","title":"EpiNow2 wrapper for deployment to Azure Batch","text":"Please refer CDC’s Template Repository information contributing repository, public domain notices disclaimers, code conduct.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/open_practices.html","id":null,"dir":"","previous_headings":"","what":"CDC GitHub Practices for Open Source Projects","title":"CDC GitHub Practices for Open Source Projects","text":"CDCGov organization GitHub designated use CDC programs publish open source code. set practices help programs release secure compliant open source projects successfully. interested using GitHub non-open source projects, please see information enterprise organization. designed practices straightforward helpful, accept feedback community updating . Required Practices, Projects don’t adhere Required Practices subject archival removal.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/open_practices.html","id":"getting-started","dir":"","previous_headings":"","what":"Getting Started","title":"CDC GitHub Practices for Open Source Projects","text":"can publish project, must request access added CDCgov organization. Complete steps: Review Rules Behavior. Confirm Github profile setup properly. require CDC login, don’t login, ask someone request behalf, get touch. receive email notification given access first repository setup . subsequent projects, able create repository organization using Github’s interface. template repository maintained easy way quick start repository complies guidelines. completed ’re ready follow required guidelines publish code.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/open_practices.html","id":"required-practices","dir":"","previous_headings":"","what":"Required Practices","title":"CDC GitHub Practices for Open Source Projects","text":"must follow practices publish real code repository. GitHub third party service used CDC collaborate public. Official CDC health messages always distributed www.cdc.gov appropriate channels, make sure plan project along official public health program cdc.gov. Add topics improve discovery use project. AI-related projects, Code.gov Implementation Guidance Federal Agencies Regarding Enterprise Data Source Code Inventories must followed setting topics. overview project, including purpose, goals team responsible. description development process README.md file. project longer active, mark archived. Public Domain Standard Notice License Standard Notice Privacy Standard Notice Contributing Standard Notice Records Management Standard Notice Additional Standard Notices need help choosing license, please review article, refer existing CDCgov projects, ask consultation support choosing license. final step publishing critical. unsure compliance, reach organization’s security officers. Make sure commit history Github repository also doesn’t things. many cases ’s easier start new repository push code sensitive information removed first commit. Enable GitHub automated security alerts configure notification repo admin see. Two-factor authentication (2FA). Project admins must secure account two-factor-authentication. Respond critical security issues communication administrators. Ignoring security issues responding communication administrators can result archiving removal. Archive old projects. ’re longer updating project moved ’s location, update README.md file let users know archive repository.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/open_practices.html","id":"recommended-practices","dir":"","previous_headings":"","what":"Recommended Practices","title":"CDC GitHub Practices for Open Source Projects","text":"Optional improvements make open source project successful. Establish pull request templates make easier contributors send pull requests. example SDP-V checklist PR match development practices. Agree project conventions include README.md file. Depending type project, includes folder structure data, linters, editor configuration (eg, MicrobeTrace’s .editorconfig). help improve quality project make easier others contribute project. Add support community procedures. CDC provide warranty official support open source projects, describing like questions issues assist users project. use wiki, project board, package manager, describe link . Official contribution steps make easier people outside CDC contribute project. Include references publications, presentations, sites featuring project. Add entry open.cdc.gov data, code, api, event page help people find project cdc.gov Add versions tags describing major releases milestones. example, open.cdc.gov’s releases time new version published web site geneflow’s changelog. Follow Semantic Versioning 2.0.0 creating versions project. Describe test reproducible practices install build project. example, injury_autocoding’s code section running project’s scripts). Recognize contributors existing resources helped project. example, fdns-ms-hl7-utils’ AUTHORS file. Automate build test procedures reduce effort outside contributors send pull requests (eg, Travis CI, Circle CI, GitHub Actions) Appropriately gather metrics project used incorporate feature planning process. Incorporate documentation development cycle, possible, automate generation documentation likely date useful people interested project.","code":""},{"path":[]},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/open_practices.html","id":"support-and-feedback","dir":"","previous_headings":"Guidance","what":"Support and Feedback","title":"CDC GitHub Practices for Open Source Projects","text":"need additional support setting project, feedback ideas guidance please open issue send email data@cdc.gov. also accept pull requests want directly edit guidance.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/open_practices.html","id":"non-compliance-procedure","dir":"","previous_headings":"Guidance","what":"Non-Compliance Procedure","title":"CDC GitHub Practices for Open Source Projects","text":"Projects organization reviewed occasionally compliance Required Practices. project found compliance, contacted administrators help bring project compliance. Projects respond habitually fail meet practices archived removed organization, depending severity.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/open_practices.html","id":"profile-setup","dir":"","previous_headings":"Guidance","what":"Profile Setup","title":"CDC GitHub Practices for Open Source Projects","text":"Please make sure profile set properly help us work better together. Specifically, keep profile date : Name: first last name. Company: government agency contracting company. (also use GitHub personal projects, consider specifying “CDC (work) + personal projects” make clear GitHub projects may personal nature.) Location: primary work location (city, state). Photo: headshot photo, appropriate image unique . admin projects, make sure secure account two-factor authentication (2FA). Although probably already smart.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/open_practices.html","id":"open-source-checklist","dir":"","previous_headings":"Guidance","what":"Open Source Checklist","title":"CDC GitHub Practices for Open Source Projects","text":"’ve decided set open source project CDC. steps , common order. Create new project using template repo. Update readme.md following CDC GitHub Practices Open Source Projects Choose license. projects ASL2, license meet public health program need. See https://www.philab.cdc.gov/index.php/2012/03/27/open-source-development--public-health-informatics/ info choosing license. Remove sensitive info. Talk ADI, ADS, ISSO review clearance. approval, create GitHub user. Fill Request Repo form new repo CDCGov CDCai. get email push alert repo ready, push GitHub Add entry open.cdc.gov code page officially linked cdc.gov. helps users find use project. Keep project date, ’re finished flag archived. checklist adapted CDC Guard Rail put help people don’t access intranet.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/open_practices.html","id":"cdc-enterprise","dir":"","previous_headings":"Guidance","what":"CDC Enterprise","title":"CDC GitHub Practices for Open Source Projects","text":"CDCent organization used private, non-public projects CDC staff approved outside collaborators work projects, can request access GitHub Enterprise Cloud form.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/open_practices.html","id":"reference-links","dir":"","previous_headings":"Guidance","what":"Reference Links","title":"CDC GitHub Practices for Open Source Projects","text":"helpful links across Federal Government regarding open sourcing code. CFPB Open Tech TTS Engineering Practices Guide 18F Open Source Policy Practicing open source policy GitHub Government: agencies build software code.gov Federal Source Code Open Source Toolkit Federal Source Code Policy (M-16-21) openCDC Digital Services Playbook CDC/ATSDR Policy Releasing Sharing Data (old version, still useful reference) Clearance Information Products Disseminated Outside CDC Public Use Federal Source Code Toolkit","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/reference/add_two_numbers.html","id":null,"dir":"Reference","previous_headings":"","what":"A temp function — add_two_numbers","title":"A temp function — add_two_numbers","text":"temp function","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/reference/add_two_numbers.html","id":"ref-usage","dir":"Reference","previous_headings":"","what":"Usage","title":"A temp function — add_two_numbers","text":"","code":"add_two_numbers(x, y)"},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/reference/add_two_numbers.html","id":"arguments","dir":"Reference","previous_headings":"","what":"Arguments","title":"A temp function — add_two_numbers","text":"x number y Another number","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/reference/add_two_numbers.html","id":"value","dir":"Reference","previous_headings":"","what":"Value","title":"A temp function — add_two_numbers","text":"sum","code":""},{"path":[]},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/rules_of_behavior.html","id":"purpose","dir":"","previous_headings":"","what":"Purpose","title":"Rules of Behavior and Posting Guidelines for the Use of GitHub as a Third-Party Web Application","text":"rules behavior establish privacy information security requirements use Third Party Web Applications (TPWAs) conjunction CDC GitHub.com organizations established open source projects. rules behavior developed ensure CDC confidential information technologies compromised, well protecting general CDC interests services risks associated use TPWAs allowing increased efficiencies cost savings come appropriate use third party services.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/rules_of_behavior.html","id":"scope","dir":"","previous_headings":"","what":"Scope","title":"Rules of Behavior and Posting Guidelines for the Use of GitHub as a Third-Party Web Application","text":"rules behavior related guidance apply federal employees, contractors, external collaborators access GitHub CDC directly use non-sensitive data obtained CDC. engagement TPWAs related GitHub governed rules behavior, well Rules Behavior Use HHS Information Services.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/rules_of_behavior.html","id":"ownership","dir":"","previous_headings":"","what":"Ownership","title":"Rules of Behavior and Posting Guidelines for the Use of GitHub as a Third-Party Web Application","text":"CDC assigns three stewards charge rules policy compliance: Business Steward, Security Steward, Technical Steward. business security stewards responsible establishing policy providing approval, technical steward fulfills requests users. Users requesting access GitHub approved yet need assign main backup point contact (POC) business steward, well provide justification security steward. security steward responsible security GitHub usage TPWA impact CDC network compliance CDC security policies. users, including POCs, responsible adherence policy associated processes. rule behavior provides explicit guidance, users must best safeguard CDC network services security risks.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/rules_of_behavior.html","id":"rules-of-behavior","dir":"","previous_headings":"","what":"Rules of Behavior","title":"Rules of Behavior and Posting Guidelines for the Use of GitHub as a Third-Party Web Application","text":"new users GitHub must read acknowledge rules using approved TPWAs. acknowledgment must completed annually, establishes agreement part user adhere rules. understand must complete security awareness records management training annually order comply latest security records management policies. understand must also follow Rules Behavior use HHS Information Resources. understand must use, share, store kind sensitive data (health status, provision payment healthcare, pictures, PII, etc.) TPWAs circumstance. knowingly conceal, falsify remove information.includes editing removing template language provided Github repository created. understand can use non-sensitive /publicly available data GitHub. unsure constitutes non-sensitive information, please see guidance . understand passwords create set GitHub accounts need comply CDC’s password policy. understand steward reserves right moderate data time. understand responsibilities protect systems data specified CDC policies.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/rules_of_behavior.html","id":"guidance-regarding-non-sensitive-and-publicly-available-information","dir":"","previous_headings":"","what":"Guidance Regarding Non-Sensitive and Publicly Available Information","title":"Rules of Behavior and Posting Guidelines for the Use of GitHub as a Third-Party Web Application","text":"support program collaboration use GitHub, portions GitHub projects either currently open public may become open public future. following guidelines inform assist user determining information posted GitHub sensitive. bottom line content posting appropriate post public access, posted GitHub. posting information involves CDC programs, employees, etc. GitHub, important poster ensures receive approval relevant CDC entity post information. Questions consider posting information include: reservations anyone viewing information? | Yes | post. | individuals informed information posted GitHub? | | post. | information contain details descriptions CDC security systems sensitive infrastructures? | Yes | post. | information reflect program efforts engage inform external partners public? | | post. | Examples information deemed sensitive may posted GitHub include following. Source Code Use cases User stories/requirements Process flows Program pain points Software Service Descriptions Sensitive information, posted, includes (limited ) following. Information directly attributed individual sensitive manner names pictures individuals Protected health information Project management material. includes posting discussing security documentation, implementation plans, communications regarding project specifics, etc. Opinions related programs tools, specifically may adverse impact Non-public Links CDC SharePoint internal references Non-public Details CDC internal infrastructure ’s question whether information may sensitive (detailed interview notes specific references provided program interview), guidance sought security steward prior posting information GitHub.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/rules_of_behavior.html","id":"enforcement","dir":"","previous_headings":"","what":"Enforcement","title":"Rules of Behavior and Posting Guidelines for the Use of GitHub as a Third-Party Web Application","text":"Users looking use GitHub unable follow rules behavior authorization . users violate rules behavior CDC security policies may subject action, including revoking access GitHub. Technical security stewards right enforce rules behavior based violations time.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/rules_of_behavior.html","id":"references","dir":"","previous_headings":"","what":"References","title":"Rules of Behavior and Posting Guidelines for the Use of GitHub as a Third-Party Web Application","text":"Policy Managing Use Third-Party Websites Applications Rules Behavior Use HHS Information Resources Security Awareness Training (requires login)","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/thanks.html","id":null,"dir":"","previous_headings":"","what":"Thanks and Acknowledgements","title":"Thanks and Acknowledgements","text":"Starting file way late, wanted recognize contributions made people helped repo. many , started file years ago. Chris Sandlin @cssandlin Drewry Morris @drewry","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/news/index.html","id":"cfaepinow2pipeline-development-version","dir":"Changelog","previous_headings":"","what":"CFAEpiNow2Pipeline (development version)","title":"CFAEpiNow2Pipeline (development version)","text":"Initial R package checks running CI","code":""}] +[{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/CONTRIBUTING.html","id":null,"dir":"","previous_headings":"","what":"Welcome!","title":"Welcome!","text":"Thank contributing CDC’s Open Source projects! questions doubts, don’t afraid send way. appreciate contributions, looking forward fostering open, transparent, collaborative environment. contributing, encourage also read LICENSE, README, code--conduct files, also found repository. inquiries questions answered content repository, feel free contact us.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/CONTRIBUTING.html","id":"public-domain","dir":"","previous_headings":"","what":"Public Domain","title":"Welcome!","text":"project public domain within United States, copyright related rights work worldwide waived CC0 1.0 Universal public domain dedication. contributions project released CC0 dedication. submitting pull request agreeing comply waiver copyright interest.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/CONTRIBUTING.html","id":"requesting-changes","dir":"","previous_headings":"","what":"Requesting Changes","title":"Welcome!","text":"pull request/merging process designed give CDC Surveillance Team space opportunity consider discuss suggested changes. policy affects CDC spaces, -line , users expected abide .","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/CONTRIBUTING.html","id":"open-an-issue-in-the-repository","dir":"","previous_headings":"Requesting Changes","what":"Open an issue in the repository","title":"Welcome!","text":"don’t specific language submit like suggest change something addressed, can open issue repository. Team members respond issue soon possible.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/CONTRIBUTING.html","id":"submit-a-pull-request","dir":"","previous_headings":"Requesting Changes","what":"Submit a pull request","title":"Welcome!","text":"like contribute, please submit pull request. order us merge pull request, must: * least seven days old. Pull requests may held longer necessary give people opportunity assess . * Receive +1 majority team members associated request. significant dissent team, meeting held discuss plan action pull request.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/DISCLAIMER.html","id":null,"dir":"","previous_headings":"","what":"DISCLAIMER","title":"DISCLAIMER","text":"Use service limited non-sensitive publicly available data. Users must use, share, store kind sensitive data like health status, provision payment healthcare, Personally Identifiable Information (PII) /Protected Health Information (PHI), etc. circumstance. Administrators service reserve right moderate information used, shared, stored service time. user abide disclaimer Code Conduct may subject action, including revoking access services. material embodied software provided “-” without warranty kind, express, implied otherwise, including without limitation, warranty fitness particular purpose. event shall Centers Disease Control Prevention (CDC) United States (U.S.) government liable anyone else direct, special, incidental, indirect consequential damages kind, damages whatsoever, including without limitation, loss profit, loss use, savings revenue, claims third parties, whether CDC U.S. government advised possibility loss, however caused theory liability, arising connection possession, use performance software.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/LICENSE.html","id":null,"dir":"","previous_headings":"","what":"Apache License","title":"Apache License","text":"Version 2.0, January 2004 ","code":""},{"path":[]},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/LICENSE.html","id":"id_1-definitions","dir":"","previous_headings":"Terms and Conditions for use, reproduction, and distribution","what":"1. Definitions","title":"Apache License","text":"“License” shall mean terms conditions use, reproduction, distribution defined Sections 1 9 document. “Licensor” shall mean copyright owner entity authorized copyright owner granting License. “Legal Entity” shall mean union acting entity entities control, controlled , common control entity. purposes definition, “control” means () power, direct indirect, cause direction management entity, whether contract otherwise, (ii) ownership fifty percent (50%) outstanding shares, (iii) beneficial ownership entity. “” (“”) shall mean individual Legal Entity exercising permissions granted License. “Source” form shall mean preferred form making modifications, including limited software source code, documentation source, configuration files. “Object” form shall mean form resulting mechanical transformation translation Source form, including limited compiled object code, generated documentation, conversions media types. “Work” shall mean work authorship, whether Source Object form, made available License, indicated copyright notice included attached work (example provided Appendix ). “Derivative Works” shall mean work, whether Source Object form, based (derived ) Work editorial revisions, annotations, elaborations, modifications represent, whole, original work authorship. purposes License, Derivative Works shall include works remain separable , merely link (bind name) interfaces , Work Derivative Works thereof. “Contribution” shall mean work authorship, including original version Work modifications additions Work Derivative Works thereof, intentionally submitted Licensor inclusion Work copyright owner individual Legal Entity authorized submit behalf copyright owner. purposes definition, “submitted” means form electronic, verbal, written communication sent Licensor representatives, including limited communication electronic mailing lists, source code control systems, issue tracking systems managed , behalf , Licensor purpose discussing improving Work, excluding communication conspicuously marked otherwise designated writing copyright owner “Contribution.” “Contributor” shall mean Licensor individual Legal Entity behalf Contribution received Licensor subsequently incorporated within Work.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/LICENSE.html","id":"id_2-grant-of-copyright-license","dir":"","previous_headings":"Terms and Conditions for use, reproduction, and distribution","what":"2. Grant of Copyright License","title":"Apache License","text":"Subject terms conditions License, Contributor hereby grants perpetual, worldwide, non-exclusive, -charge, royalty-free, irrevocable copyright license reproduce, prepare Derivative Works , publicly display, publicly perform, sublicense, distribute Work Derivative Works Source Object form.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/LICENSE.html","id":"id_3-grant-of-patent-license","dir":"","previous_headings":"Terms and Conditions for use, reproduction, and distribution","what":"3. Grant of Patent License","title":"Apache License","text":"Subject terms conditions License, Contributor hereby grants perpetual, worldwide, non-exclusive, -charge, royalty-free, irrevocable (except stated section) patent license make, made, use, offer sell, sell, import, otherwise transfer Work, license applies patent claims licensable Contributor necessarily infringed Contribution(s) alone combination Contribution(s) Work Contribution(s) submitted. institute patent litigation entity (including cross-claim counterclaim lawsuit) alleging Work Contribution incorporated within Work constitutes direct contributory patent infringement, patent licenses granted License Work shall terminate date litigation filed.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/LICENSE.html","id":"id_4-redistribution","dir":"","previous_headings":"Terms and Conditions for use, reproduction, and distribution","what":"4. Redistribution","title":"Apache License","text":"may reproduce distribute copies Work Derivative Works thereof medium, without modifications, Source Object form, provided meet following conditions: () must give recipients Work Derivative Works copy License; (b) must cause modified files carry prominent notices stating changed files; (c) must retain, Source form Derivative Works distribute, copyright, patent, trademark, attribution notices Source form Work, excluding notices pertain part Derivative Works; (d) Work includes “NOTICE” text file part distribution, Derivative Works distribute must include readable copy attribution notices contained within NOTICE file, excluding notices pertain part Derivative Works, least one following places: within NOTICE text file distributed part Derivative Works; within Source form documentation, provided along Derivative Works; , within display generated Derivative Works, wherever third-party notices normally appear. contents NOTICE file informational purposes modify License. may add attribution notices within Derivative Works distribute, alongside addendum NOTICE text Work, provided additional attribution notices construed modifying License. may add copyright statement modifications may provide additional different license terms conditions use, reproduction, distribution modifications, Derivative Works whole, provided use, reproduction, distribution Work otherwise complies conditions stated License.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/LICENSE.html","id":"id_5-submission-of-contributions","dir":"","previous_headings":"Terms and Conditions for use, reproduction, and distribution","what":"5. Submission of Contributions","title":"Apache License","text":"Unless explicitly state otherwise, Contribution intentionally submitted inclusion Work Licensor shall terms conditions License, without additional terms conditions. Notwithstanding , nothing herein shall supersede modify terms separate license agreement may executed Licensor regarding Contributions.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/LICENSE.html","id":"id_6-trademarks","dir":"","previous_headings":"Terms and Conditions for use, reproduction, and distribution","what":"6. Trademarks","title":"Apache License","text":"License grant permission use trade names, trademarks, service marks, product names Licensor, except required reasonable customary use describing origin Work reproducing content NOTICE file.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/LICENSE.html","id":"id_7-disclaimer-of-warranty","dir":"","previous_headings":"Terms and Conditions for use, reproduction, and distribution","what":"7. Disclaimer of Warranty","title":"Apache License","text":"Unless required applicable law agreed writing, Licensor provides Work (Contributor provides Contributions) “” BASIS, WITHOUT WARRANTIES CONDITIONS KIND, either express implied, including, without limitation, warranties conditions TITLE, NON-INFRINGEMENT, MERCHANTABILITY, FITNESS PARTICULAR PURPOSE. solely responsible determining appropriateness using redistributing Work assume risks associated exercise permissions License.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/LICENSE.html","id":"id_8-limitation-of-liability","dir":"","previous_headings":"Terms and Conditions for use, reproduction, and distribution","what":"8. Limitation of Liability","title":"Apache License","text":"event legal theory, whether tort (including negligence), contract, otherwise, unless required applicable law (deliberate grossly negligent acts) agreed writing, shall Contributor liable damages, including direct, indirect, special, incidental, consequential damages character arising result License use inability use Work (including limited damages loss goodwill, work stoppage, computer failure malfunction, commercial damages losses), even Contributor advised possibility damages.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/LICENSE.html","id":"id_9-accepting-warranty-or-additional-liability","dir":"","previous_headings":"Terms and Conditions for use, reproduction, and distribution","what":"9. Accepting Warranty or Additional Liability","title":"Apache License","text":"redistributing Work Derivative Works thereof, may choose offer, charge fee , acceptance support, warranty, indemnity, liability obligations /rights consistent License. However, accepting obligations, may act behalf sole responsibility, behalf Contributor, agree indemnify, defend, hold Contributor harmless liability incurred , claims asserted , Contributor reason accepting warranty additional liability. END TERMS CONDITIONS","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/LICENSE.html","id":"appendix-how-to-apply-the-apache-license-to-your-work","dir":"","previous_headings":"","what":"APPENDIX: How to apply the Apache License to your work","title":"Apache License","text":"apply Apache License work, attach following boilerplate notice, fields enclosed brackets [] replaced identifying information. (Don’t include brackets!) text enclosed appropriate comment syntax file format. also recommend file class name description purpose included “printed page” copyright notice easier identification within third-party archives.","code":"Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License."},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/authors.html","id":null,"dir":"","previous_headings":"","what":"Authors","title":"Authors and Citation","text":"Zachary Susswein. Author, maintainer. Katelyn Gostic. Author.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/authors.html","id":"citation","dir":"","previous_headings":"","what":"Citation","title":"Authors and Citation","text":"Susswein Z, Gostic K (2024). CFAEpiNow2Pipeline: EpiNow2 wrapper deployment Azure Batch. R package version 0.0.0.9000, https://cdcgov.github.io/cfa-epinow2-pipeline/.","code":"@Manual{, title = {CFAEpiNow2Pipeline: EpiNow2 wrapper for deployment to Azure Batch}, author = {Zachary Susswein and Katelyn Gostic}, year = {2024}, note = {R package version 0.0.0.9000}, url = {https://cdcgov.github.io/cfa-epinow2-pipeline/}, }"},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/code-of-conduct.html","id":null,"dir":"","previous_headings":"","what":"Creating a Culture of Innovation","title":"Creating a Culture of Innovation","text":"aspire create culture people work joyfully, communicate openly things matter, provide great services globally. like team communities (government private sector) reflect diversity kinds, just classes protected law. Diversity fosters innovation. Diverse teams creative teams. need diversity perspective create solutions challenges face. code conduct (adapted 18F’s Code Conduct). follow Equal Employment Opportunity laws expect everyone work adhere GSA Anti-harassment Policy, even work Centers Disease Control Prevention GSA. expect every user follow code conduct laws policies mentioned .","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/code-of-conduct.html","id":"be-empowering","dir":"","previous_headings":"","what":"Be Empowering","title":"Creating a Culture of Innovation","text":"Consider can encourage support others. Make room quieter voices contribute. Offer support enthusiasm great ideas. Leverage low cost experimentation support colleagues’ ideas, take care acknowledge original source. Look ways contribute collaborate, even situations normally wouldn’t. Share knowledge skills. Prioritize access input traditionally excluded civic process.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/code-of-conduct.html","id":"rules-of-behavior","dir":"","previous_headings":"","what":"Rules of Behavior","title":"Creating a Culture of Innovation","text":"understand must complete security awareness records management training annually order comply latest security records management policies. understand must also follow Rules Behavior use HHS Information Resources understand must use, share, store kind sensitive data (health status, provision payment healthcare, PII, etc.) circumstance. knowingly conceal, falsify, remove information. understand can use non-sensitive /publicly available data. understand passwords create set accounts need comply CDC’s password policy. understand stewards reserves right moderate data time.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/code-of-conduct.html","id":"boundaries","dir":"","previous_headings":"","what":"Boundaries","title":"Creating a Culture of Innovation","text":"Create boundaries behavior consider can create safe space helps prevent unacceptable behavior others. can’t list instances unacceptable behavior, can provide examples help guide community thinking respond experience types behavior, whether directed others. unsure something appropriate behavior, probably . person interact can define line . Impact matters intent. Ensuring behavior negative impact responsibility. Problems usually arise assume way thinking behavior norm everyone.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/code-of-conduct.html","id":"here-are-some-examples-of-unacceptable-behavior","dir":"","previous_headings":"Boundaries","what":"Here are some examples of unacceptable behavior","title":"Creating a Culture of Innovation","text":"Negative offensive remarks based protected classes listed GSA Anti-harassment Policy race, religion, color, sex, national origin, age, disability, genetric information, sexual orientation, gender identity, parental status, maritual status, political affiliation well gender expression, mental illness, socioeconomic status backgrounds, neuro()typicality, physical appearance, body size, clothing. Consider calling attention differences can feel alienating. Sustained disruption meetings, talks, discussions, including chatrooms. Patronizing language behavior. Aggressive behavior, unconstructive criticism, providing correction improve conversation (sometimes referred “well actually’s”), repeatedly interrupting talking someone else, feigning surprise someone’s lack knowledge awareness topic, subtle prejudice. Referring people way misidentifies gender /rejects validity gender identity; instance using incorrect pronouns forms address (misgendering). Retaliating anyone files formal complaint someone violated codes laws.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/code-of-conduct.html","id":"background","dir":"","previous_headings":"","what":"Background","title":"Creating a Culture of Innovation","text":"CDC Scientific Clearance process obtaining approvals appropriate CDC officials CDC information product released public CDC’s external public health partners. Information products require formal clearance include print, electronic, oral materials, CDC employees author co-author, whether published CDC outside CDC. CDC contractors developing content behalf CDC public CDC’s external public health partners also required put content formal clearance process. collaborative functions related projects include blogs, wikis, forums, bug tracking sites, source control others deemed necessary. individuals within CDC, adherence following policies required: * CDC “Clearance Information Products Disseminated Outside CDC Public Use” * HHS “Ensuring Quality Information Disseminated HHS agencies” collaborative materials controlled rules contained within document. allow real-time collaboration opportunities among CDC employees, CDC contractors CDC public health partners.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/code-of-conduct.html","id":"credit","dir":"","previous_headings":"","what":"Credit","title":"Creating a Culture of Innovation","text":"code conduct mainly adapted 18F’s Code Conduct CDC’s Informatics Innovation Unit R&D Lab’s code conduct.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/code-of-conduct.html","id":"relevant-legal-considerations","dir":"","previous_headings":"","what":"Relevant Legal Considerations","title":"Creating a Culture of Innovation","text":"Laws enforced Equal Employment Opportunity Commission Types discrimination prohibited law New proposed regulations","code":""},{"path":[]},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/index.html","id":"overview","dir":"","previous_headings":"","what":"Overview","title":"EpiNow2 wrapper for deployment to Azure Batch","text":"lightweight wrapper around {EpiNow2} add functionality deployment Azure Batch.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/index.html","id":"project-admin","dir":"","previous_headings":"","what":"Project Admin","title":"EpiNow2 wrapper for deployment to Azure Batch","text":"@zsusswein @natemcintosh @kgostic","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/index.html","id":"general-disclaimer","dir":"","previous_headings":"","what":"General Disclaimer","title":"EpiNow2 wrapper for deployment to Azure Batch","text":"repository created use CDC programs collaborate public health related projects support CDC mission. GitHub hosted CDC, third party website used CDC partners share information collaborate software. CDC use GitHub imply endorsement one particular service, product, enterprise.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/index.html","id":"public-domain-standard-notice","dir":"","previous_headings":"","what":"Public Domain Standard Notice","title":"EpiNow2 wrapper for deployment to Azure Batch","text":"repository constitutes work United States Government subject domestic copyright protection 17 USC § 105. repository public domain within United States, copyright related rights work worldwide waived CC0 1.0 Universal public domain dedication. contributions repository released CC0 dedication. submitting pull request agreeing comply waiver copyright interest.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/index.html","id":"license-standard-notice","dir":"","previous_headings":"","what":"License Standard Notice","title":"EpiNow2 wrapper for deployment to Azure Batch","text":"repository utilizes code licensed terms Apache Software License therefore licensed ASL v2 later. source code repository free: can redistribute /modify terms Apache Software License version 2, (option) later version. source code repository distributed hope useful, WITHOUT WARRANTY; without even implied warranty MERCHANTABILITY FITNESS PARTICULAR PURPOSE. See Apache Software License details. received copy Apache Software License along program. , see http://www.apache.org/licenses/LICENSE-2.0.html source code forked open source projects inherit license.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/index.html","id":"privacy-standard-notice","dir":"","previous_headings":"","what":"Privacy Standard Notice","title":"EpiNow2 wrapper for deployment to Azure Batch","text":"repository contains non-sensitive, publicly available data information. material community participation covered Disclaimer Code Conduct. information CDC’s privacy policy, please visit http://www.cdc.gov//privacy.html.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/index.html","id":"contributing-standard-notice","dir":"","previous_headings":"","what":"Contributing Standard Notice","title":"EpiNow2 wrapper for deployment to Azure Batch","text":"Anyone encouraged contribute repository forking submitting pull request. (new GitHub, might start basic tutorial.) contributing project, grant world-wide, royalty-free, perpetual, irrevocable, non-exclusive, transferable license users terms Apache Software License v2 later. comments, messages, pull requests, submissions received CDC including GitHub page may subject applicable federal law, including limited Federal Records Act, may archived. Learn http://www.cdc.gov//privacy.html.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/index.html","id":"records-management-standard-notice","dir":"","previous_headings":"","what":"Records Management Standard Notice","title":"EpiNow2 wrapper for deployment to Azure Batch","text":"repository source government records copy increase collaboration collaborative potential. government records published CDC web site.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/index.html","id":"additional-standard-notices","dir":"","previous_headings":"","what":"Additional Standard Notices","title":"EpiNow2 wrapper for deployment to Azure Batch","text":"Please refer CDC’s Template Repository information contributing repository, public domain notices disclaimers, code conduct.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/open_practices.html","id":null,"dir":"","previous_headings":"","what":"CDC GitHub Practices for Open Source Projects","title":"CDC GitHub Practices for Open Source Projects","text":"CDCGov organization GitHub designated use CDC programs publish open source code. set practices help programs release secure compliant open source projects successfully. interested using GitHub non-open source projects, please see information enterprise organization. designed practices straightforward helpful, accept feedback community updating . Required Practices, Projects don’t adhere Required Practices subject archival removal.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/open_practices.html","id":"getting-started","dir":"","previous_headings":"","what":"Getting Started","title":"CDC GitHub Practices for Open Source Projects","text":"can publish project, must request access added CDCgov organization. Complete steps: Review Rules Behavior. Confirm Github profile setup properly. require CDC login, don’t login, ask someone request behalf, get touch. receive email notification given access first repository setup . subsequent projects, able create repository organization using Github’s interface. template repository maintained easy way quick start repository complies guidelines. completed ’re ready follow required guidelines publish code.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/open_practices.html","id":"required-practices","dir":"","previous_headings":"","what":"Required Practices","title":"CDC GitHub Practices for Open Source Projects","text":"must follow practices publish real code repository. GitHub third party service used CDC collaborate public. Official CDC health messages always distributed www.cdc.gov appropriate channels, make sure plan project along official public health program cdc.gov. Add topics improve discovery use project. AI-related projects, Code.gov Implementation Guidance Federal Agencies Regarding Enterprise Data Source Code Inventories must followed setting topics. overview project, including purpose, goals team responsible. description development process README.md file. project longer active, mark archived. Public Domain Standard Notice License Standard Notice Privacy Standard Notice Contributing Standard Notice Records Management Standard Notice Additional Standard Notices need help choosing license, please review article, refer existing CDCgov projects, ask consultation support choosing license. final step publishing critical. unsure compliance, reach organization’s security officers. Make sure commit history Github repository also doesn’t things. many cases ’s easier start new repository push code sensitive information removed first commit. Enable GitHub automated security alerts configure notification repo admin see. Two-factor authentication (2FA). Project admins must secure account two-factor-authentication. Respond critical security issues communication administrators. Ignoring security issues responding communication administrators can result archiving removal. Archive old projects. ’re longer updating project moved ’s location, update README.md file let users know archive repository.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/open_practices.html","id":"recommended-practices","dir":"","previous_headings":"","what":"Recommended Practices","title":"CDC GitHub Practices for Open Source Projects","text":"Optional improvements make open source project successful. Establish pull request templates make easier contributors send pull requests. example SDP-V checklist PR match development practices. Agree project conventions include README.md file. Depending type project, includes folder structure data, linters, editor configuration (eg, MicrobeTrace’s .editorconfig). help improve quality project make easier others contribute project. Add support community procedures. CDC provide warranty official support open source projects, describing like questions issues assist users project. use wiki, project board, package manager, describe link . Official contribution steps make easier people outside CDC contribute project. Include references publications, presentations, sites featuring project. Add entry open.cdc.gov data, code, api, event page help people find project cdc.gov Add versions tags describing major releases milestones. example, open.cdc.gov’s releases time new version published web site geneflow’s changelog. Follow Semantic Versioning 2.0.0 creating versions project. Describe test reproducible practices install build project. example, injury_autocoding’s code section running project’s scripts). Recognize contributors existing resources helped project. example, fdns-ms-hl7-utils’ AUTHORS file. Automate build test procedures reduce effort outside contributors send pull requests (eg, Travis CI, Circle CI, GitHub Actions) Appropriately gather metrics project used incorporate feature planning process. Incorporate documentation development cycle, possible, automate generation documentation likely date useful people interested project.","code":""},{"path":[]},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/open_practices.html","id":"support-and-feedback","dir":"","previous_headings":"Guidance","what":"Support and Feedback","title":"CDC GitHub Practices for Open Source Projects","text":"need additional support setting project, feedback ideas guidance please open issue send email data@cdc.gov. also accept pull requests want directly edit guidance.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/open_practices.html","id":"non-compliance-procedure","dir":"","previous_headings":"Guidance","what":"Non-Compliance Procedure","title":"CDC GitHub Practices for Open Source Projects","text":"Projects organization reviewed occasionally compliance Required Practices. project found compliance, contacted administrators help bring project compliance. Projects respond habitually fail meet practices archived removed organization, depending severity.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/open_practices.html","id":"profile-setup","dir":"","previous_headings":"Guidance","what":"Profile Setup","title":"CDC GitHub Practices for Open Source Projects","text":"Please make sure profile set properly help us work better together. Specifically, keep profile date : Name: first last name. Company: government agency contracting company. (also use GitHub personal projects, consider specifying “CDC (work) + personal projects” make clear GitHub projects may personal nature.) Location: primary work location (city, state). Photo: headshot photo, appropriate image unique . admin projects, make sure secure account two-factor authentication (2FA). Although probably already smart.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/open_practices.html","id":"open-source-checklist","dir":"","previous_headings":"Guidance","what":"Open Source Checklist","title":"CDC GitHub Practices for Open Source Projects","text":"’ve decided set open source project CDC. steps , common order. Create new project using template repo. Update readme.md following CDC GitHub Practices Open Source Projects Choose license. projects ASL2, license meet public health program need. See https://www.philab.cdc.gov/index.php/2012/03/27/open-source-development--public-health-informatics/ info choosing license. Remove sensitive info. Talk ADI, ADS, ISSO review clearance. approval, create GitHub user. Fill Request Repo form new repo CDCGov CDCai. get email push alert repo ready, push GitHub Add entry open.cdc.gov code page officially linked cdc.gov. helps users find use project. Keep project date, ’re finished flag archived. checklist adapted CDC Guard Rail put help people don’t access intranet.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/open_practices.html","id":"cdc-enterprise","dir":"","previous_headings":"Guidance","what":"CDC Enterprise","title":"CDC GitHub Practices for Open Source Projects","text":"CDCent organization used private, non-public projects CDC staff approved outside collaborators work projects, can request access GitHub Enterprise Cloud form.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/open_practices.html","id":"reference-links","dir":"","previous_headings":"Guidance","what":"Reference Links","title":"CDC GitHub Practices for Open Source Projects","text":"helpful links across Federal Government regarding open sourcing code. CFPB Open Tech TTS Engineering Practices Guide 18F Open Source Policy Practicing open source policy GitHub Government: agencies build software code.gov Federal Source Code Open Source Toolkit Federal Source Code Policy (M-16-21) openCDC Digital Services Playbook CDC/ATSDR Policy Releasing Sharing Data (old version, still useful reference) Clearance Information Products Disseminated Outside CDC Public Use Federal Source Code Toolkit","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/reference/add_two_numbers.html","id":null,"dir":"Reference","previous_headings":"","what":"A temp function — add_two_numbers","title":"A temp function — add_two_numbers","text":"temp function","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/reference/add_two_numbers.html","id":"ref-usage","dir":"Reference","previous_headings":"","what":"Usage","title":"A temp function — add_two_numbers","text":"","code":"add_two_numbers(x, y)"},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/reference/add_two_numbers.html","id":"arguments","dir":"Reference","previous_headings":"","what":"Arguments","title":"A temp function — add_two_numbers","text":"x number y Another number","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/reference/add_two_numbers.html","id":"value","dir":"Reference","previous_headings":"","what":"Value","title":"A temp function — add_two_numbers","text":"sum","code":""},{"path":[]},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/rules_of_behavior.html","id":"purpose","dir":"","previous_headings":"","what":"Purpose","title":"Rules of Behavior and Posting Guidelines for the Use of GitHub as a Third-Party Web Application","text":"rules behavior establish privacy information security requirements use Third Party Web Applications (TPWAs) conjunction CDC GitHub.com organizations established open source projects. rules behavior developed ensure CDC confidential information technologies compromised, well protecting general CDC interests services risks associated use TPWAs allowing increased efficiencies cost savings come appropriate use third party services.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/rules_of_behavior.html","id":"scope","dir":"","previous_headings":"","what":"Scope","title":"Rules of Behavior and Posting Guidelines for the Use of GitHub as a Third-Party Web Application","text":"rules behavior related guidance apply federal employees, contractors, external collaborators access GitHub CDC directly use non-sensitive data obtained CDC. engagement TPWAs related GitHub governed rules behavior, well Rules Behavior Use HHS Information Services.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/rules_of_behavior.html","id":"ownership","dir":"","previous_headings":"","what":"Ownership","title":"Rules of Behavior and Posting Guidelines for the Use of GitHub as a Third-Party Web Application","text":"CDC assigns three stewards charge rules policy compliance: Business Steward, Security Steward, Technical Steward. business security stewards responsible establishing policy providing approval, technical steward fulfills requests users. Users requesting access GitHub approved yet need assign main backup point contact (POC) business steward, well provide justification security steward. security steward responsible security GitHub usage TPWA impact CDC network compliance CDC security policies. users, including POCs, responsible adherence policy associated processes. rule behavior provides explicit guidance, users must best safeguard CDC network services security risks.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/rules_of_behavior.html","id":"rules-of-behavior","dir":"","previous_headings":"","what":"Rules of Behavior","title":"Rules of Behavior and Posting Guidelines for the Use of GitHub as a Third-Party Web Application","text":"new users GitHub must read acknowledge rules using approved TPWAs. acknowledgment must completed annually, establishes agreement part user adhere rules. understand must complete security awareness records management training annually order comply latest security records management policies. understand must also follow Rules Behavior use HHS Information Resources. understand must use, share, store kind sensitive data (health status, provision payment healthcare, pictures, PII, etc.) TPWAs circumstance. knowingly conceal, falsify remove information.includes editing removing template language provided Github repository created. understand can use non-sensitive /publicly available data GitHub. unsure constitutes non-sensitive information, please see guidance . understand passwords create set GitHub accounts need comply CDC’s password policy. understand steward reserves right moderate data time. understand responsibilities protect systems data specified CDC policies.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/rules_of_behavior.html","id":"guidance-regarding-non-sensitive-and-publicly-available-information","dir":"","previous_headings":"","what":"Guidance Regarding Non-Sensitive and Publicly Available Information","title":"Rules of Behavior and Posting Guidelines for the Use of GitHub as a Third-Party Web Application","text":"support program collaboration use GitHub, portions GitHub projects either currently open public may become open public future. following guidelines inform assist user determining information posted GitHub sensitive. bottom line content posting appropriate post public access, posted GitHub. posting information involves CDC programs, employees, etc. GitHub, important poster ensures receive approval relevant CDC entity post information. Questions consider posting information include: reservations anyone viewing information? | Yes | post. | individuals informed information posted GitHub? | | post. | information contain details descriptions CDC security systems sensitive infrastructures? | Yes | post. | information reflect program efforts engage inform external partners public? | | post. | Examples information deemed sensitive may posted GitHub include following. Source Code Use cases User stories/requirements Process flows Program pain points Software Service Descriptions Sensitive information, posted, includes (limited ) following. Information directly attributed individual sensitive manner names pictures individuals Protected health information Project management material. includes posting discussing security documentation, implementation plans, communications regarding project specifics, etc. Opinions related programs tools, specifically may adverse impact Non-public Links CDC SharePoint internal references Non-public Details CDC internal infrastructure ’s question whether information may sensitive (detailed interview notes specific references provided program interview), guidance sought security steward prior posting information GitHub.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/rules_of_behavior.html","id":"enforcement","dir":"","previous_headings":"","what":"Enforcement","title":"Rules of Behavior and Posting Guidelines for the Use of GitHub as a Third-Party Web Application","text":"Users looking use GitHub unable follow rules behavior authorization . users violate rules behavior CDC security policies may subject action, including revoking access GitHub. Technical security stewards right enforce rules behavior based violations time.","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/rules_of_behavior.html","id":"references","dir":"","previous_headings":"","what":"References","title":"Rules of Behavior and Posting Guidelines for the Use of GitHub as a Third-Party Web Application","text":"Policy Managing Use Third-Party Websites Applications Rules Behavior Use HHS Information Resources Security Awareness Training (requires login)","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/thanks.html","id":null,"dir":"","previous_headings":"","what":"Thanks and Acknowledgements","title":"Thanks and Acknowledgements","text":"Starting file way late, wanted recognize contributions made people helped repo. many , started file years ago. Chris Sandlin @cssandlin Drewry Morris @drewry","code":""},{"path":"https://cdcgov.github.io/cfa-epinow2-pipeline/news/index.html","id":"cfaepinow2pipeline-development-version","dir":"Changelog","previous_headings":"","what":"CFAEpiNow2Pipeline (development version)","title":"CFAEpiNow2Pipeline (development version)","text":"CI running Ubuntu & working pkgdown deploy Github Pages Initial R package checks running CI","code":""}]