Switching application from markdown to YAML format

projects/pdks.yml

@@ -0,0 +1,53 @@
+# Project name
+name: Open source PDKs & Workgroup
+# Project status - sandbox, graduated or archived
+status: sandbox
+# Links to project repos - may be one or list of several in YAML list format
+repositories:
+  - https://github.com/google/skywater-pdk
+  - https://github.com/google/gf180mcu-pdk
+# A one-sentence summary of the project
+brief_summary: Open source process design kits for the SkyWater Technology 130nm and GlobalFoundries 180MCU manufacturing processes. These GitHub repos are currently maintained by Google, but proposing to move them into CHIPS Alliance and to form a new workgroup for governance moving forward.
+# The project's open source license, normally Apache 2.0 unless special exception is granted
+license: Apache-2.0
+# Link to issue tracker
+issue_tracker_link: https://github.com/google/skywater-pdk/issues
+# Link to website
+website_link: N/A
+# Links to social media, if present, can be a list, or N/A if none
+social_media_links: N/A
+# Brief summary of how widely the project is used e.g. list of companies
+project_usage_and_scale: Commercial chip designers, academic researchers, educators, students, and hobbyists have created over 700 projects based on these PDKs. Projects have been manufactured via Google’s [Open MPW Shuttle program](https://efabless.com/open_shuttle_program) and [efabless’](https://efabless.com/) chipIgnite service.
+# Project's motivation to join CHIPS
+why_join_chips: To take open source PDKs to the next level, Google seeks to advance our initial PDK efforts by “graduating” them out of Google and into a sustainable, ecosystem-driven governance model. This effort has an initial approval via governing board vote (October 5, 2023) and is now applying for sandbox status and TSC consideration.  With sandbox status, we will work towards drafting the mission statement and workgroup charter before applying for graduation to instantiate the rest of the project and workgroup.
+# The primary contact person for the project, will become TSC representative once admitted
+primary_contact:
+  # Contact's full name
+  name: Aaron Cunningham
+  # Contact's work email
+  email: [email protected]
+  # Contact's GH handle, without the @
+  github_handle: cunninghamsandwich
+  # Contact's role in the project
+  project_role: Technical Program Manager
+### Data above this line is needed for Sandbox application, additional data below is needed for Graduated application
+# Data about active project contributors
+active_committers: 
+# Information about project's release methodology and mechanics
+release_methodology: No regular release policy has been adopted as of yet; a policy is going to be developed in collaboration within CHIPS.
+# Link to project's mission statement
+mission_statement_link: 
+# Link to logo in .svg format, if present
+svg_logo_link: 
+# Did the project accept the LF Code of Conduct? See https://lfprojects.org/policies/code-of-conduct/
+accepted_lf_code_of_conduct: yes
+# Did the project adopt the CHIPS Alliance IP Policy? See https://technical-charter.chipsalliance.org
+adopted_chips_alliance_ip_policy: yes
+# Did the project put links to CHIPS in the header or footer of its website? If no website, still answer "yes" as declaration of will to do so.
+chips_header_footer_text_on_website: yes
+# Did the project transfer any registered trademarks and domains to CHIPS? If none are present, still answer "yes" as declaration of intent if that should change.
+trademarks_and_domains_transferred_to_lf: yes
+# Describe briefly the project's security vulnerability reporting process, or just defer to https://github.com/chipsalliance/tsc#reporting-security-vulnerabilities
+security_vulnerabilities_reporting_process: The project will use [CHIPS Alliance's default security policy](https://github.com/chipsalliance/tsc#reporting-security-vulnerabilities)
+# (For specifications only) link to reference implementation of the specification, N/A for non-spec projects
+spec_public_reference_implementation: N/A