first commit

Author: AminPIC

general_resources.md

@@ -0,0 +1,75 @@
+# General Resources
+
+Example Playbooks
+[**Digital Services Playbook**](https://playbook.cio.gov/) https://playbook.cio.gov/
+Format: intro paragraph, checklist, and key questions
+* Understand what people need
+* Address the whole experience, from start to finish
+* Make it simple and intuitive
+* Build the service using agile and iterative practices
+* Structure budgets and contracts to support delivery
+* Assign one leader and hold that person accountable
+* Bring in experienced teams
+* Choose a modern technology stack
+* Deploy in a flexible hosting environment
+* Automate testing and deployments
+* Manage security and privacy through reusable processes
+* Use data to drive decisions
+* Default to open
+ 
+**18F Partnership Principles: Collaboration approaches to help your project succeed** 
+https://18f.gsa.gov/partnership-principles/
+Format: based on Digital Services Playbook; allows for easy PDF download
+* Methodologies
+  * Lettings users guide our work
+  * Working in an agile way
+  * Building in the open
+* Tactics
+  * Understanding your problem first
+  * Partnering with an empowered product owner
+ 
+**Citizen Science Toolkit**
+https://www.citizenscience.gov/toolkit/howto/#
+Format: basic process steps for planning, designing and carrying out a crowdsourcing our citizen science project; steps are sequential, but each is also independent and includes resources (to help answer specific questions, case studies to provide success story examples, and the ability to navigate to any step at the top)
+Step 1: Scope your problem
+* Brief paragraph with links
+* Bulleted tips (linked)
+* Case studies (linked)
+* Resources
+ 
+**Challenge Toolkit** 
+https://challenge.gov/a/buzz/pages/toolkit
+Format: outlines project planning phases
+ 
+**GitHub’s Open Source Guides**
+Format: each guide walks the user through a specific topic with links and examples
+* How to Contribute to Open Source
+* Starting an Open Source Project
+* Finding Users for your Project
+* Building Welcoming Communities
+* [Best Practices for Maintainers](https://opensource.guide/best-practices/)
+  * What does it mean to be a maintainer?
+  * Documenting your processes (e.g., Jekyll, CocoaPods, and Homebrew are several examples of projects with ground rules for maintainers and contributors.)
+  * Learning to say no
+  * Leverage your community
+  * Bring in the robots
+  * It’s okay to hit pause
+  * Take care of yourself first
+* Leadership and Governance
+  * Understanding governance for your growing project
+  * What are examples of formal roles used in open source projects?
+  * How do I formalize these leadership roles?
+* Getting Paid for Open Source Work
+* Your Code of Conduct
+* Open Source Metrics
+* The Legal Side of Open Source
+
+Google [Lead Generation](https://services.google.com/fh/files/events/pdf_leadgen_ux_playbook.pdf) playbook 
+
+Google [Playbooks](https://www.thinkwithgoogle.com/intl/en-gb/marketing-resources/playbooks/) (generally) 
+
+UK [Developer Docs](https://github.com/alphagov/govuk-developer-docs)
+UK [Digital Services](https://www.gov.uk/service-manual/service-standardl) Playbook
+* Current [Communities of Practice](https://www.gov.uk/service-manual/communities) in UK Government Digital Services
+  * Guide to [developing COPs](https://www.gov.uk/government/publications/community-development-handbook/community-development-handbook) in government
+* [Open Standards](https://www.gov.uk/service-manual/technology/working-with-open-standards) in UK Government