diff options
Diffstat (limited to 'chromium/docs/website/site/teams/web-capabilities-fugu/index.md')
| -rw-r--r-- | chromium/docs/website/site/teams/web-capabilities-fugu/index.md | 74 |
1 files changed, 0 insertions, 74 deletions
diff --git a/chromium/docs/website/site/teams/web-capabilities-fugu/index.md b/chromium/docs/website/site/teams/web-capabilities-fugu/index.md deleted file mode 100644 index fe47edb9a01..00000000000 --- a/chromium/docs/website/site/teams/web-capabilities-fugu/index.md +++ /dev/null @@ -1,74 +0,0 @@ ---- -breadcrumbs: -- - /teams - - Teams -page_name: web-capabilities-fugu -title: "Web Capabilities (Project Fugu \U0001F421)" ---- - -**Overview** - -Project Fugu 🐡 is an effort to close gaps in the web's capabilities enabling new -classes of applications to run on the web. The developer-friendly landing page -of the project is <https://web.dev/fugu-status/>. The list of in-process APIs is -available at <https://goo.gle/fugu-api-tracker>. -APIs that Project Fugu is delivering enable new experiences on the web while -preserving the web's core benefits of security, low-friction, and cross-platform -delivery. All Project Fugu API proposals are made in the open and on the -standards track. -Fugu is organized as Chromium project, open to all Chromium contributors and -organizations. Today, that includes Microsoft, Intel, Samsung, and Google (among -others). Fugu Leads triage incoming requests from partners, determine demand, -prioritize them, find champions, track development, and help organize the -release and documentation for the capability. - -#### Bridging the native app gap (Chrome Dev Summit 2019) - -**Contacts** - -Mailing List: -[fugu-dev@chromium.org](https://groups.google.com/a/chromium.org/forum/#!forum/fugu-dev) - -Slack Channel: #fugu on [@chromium](https://chromiumdev.slack.com/) - -**Capability Process** - -[Guideline and -template](https://docs.google.com/document/d/1kzNch5P6lLcHm2ER7YOCJQG4OGY4XttJ42FDn-2vdO0/edit#heading=h.hsplb8xxfif5): -This is the guideline and template to be used by Chrome developers who are about -to introduce a new capability. It outlines the process and when to reach out to -specific people. - -[DevRel Process for Fugu -Capabilities](https://docs.google.com/document/d/1qy-XmiCIu6QP1bbEAqfCAZQ65q5F9I6OJKvUgYLQ4GU/edit#): -A guide on how we will approach Fugu capabilities, including how we gather -developer demand, externalize our steps, and generate blog posts / tutorials. - -[Developer Updates Status -page](https://developers.google.com/web/updates/capabilities): Public list -showing the status of current capabilities. - -**Specific Capabilities & Prioritization model** - -We prioritize capabilities by which partners we enable or improve by a given -capability. - -[Full list of -capabilities](https://bugs.chromium.org/p/chromium/issues/list?can=2&q=proj-fugu&sort=pri&colspec=ID+Pri+M+Stars+ReleaseBlock+Component+Status+Owner+Summary+OS+Modified&x=m&y=releaseblock&cells=ids): -Every capability that is currently considered as part of Fugu - -[Bug Tracking -Process](https://docs.google.com/document/d/1bAcLkqbEQJEphmjvnguB7WxltT_zEEXrUlwawpbrCNQ/edit?usp=sharing): -Information on how we track bugs & partners through crbug, as well as the -meaning of different labels - -**Monthly Meetings** - -To share updates on capabilities work and discuss opportunities and priorities, -we have monthly video chat meetings. The meetings are open to all Chromium -contributors working on Fugu capabilities, regardless of affiliation. Note that -these meetings tend to be high level, and don't dive into technical details. For -an invite to the meeting ask on the #fugu channel on chromium.slack.com or email -fugu-dev@chromium.org. Agendas for upcoming meetings and notes for past meetings -are captured in a shared [Notes -Doc](https://docs.google.com/document/d/1vC2IRBel2PIahJLE1Mrnd4nm0OMvWDQcKUQSsfxMFBY/edit#)
\ No newline at end of file |